Two compositions of the four conformance rules were reachable and neither
was answered by the text.
First: rule 1 scopes non-conformance to a re-spelling published under a CORE
name, rule 2 permits omitting optional properties, and rule 4 permits declared
extensions whose names this document does not define. Composed, a profile may
omit an optional core member and republish its value under an extension name
— the re-spelling rule 1 exists to forbid, arriving by a legal path. A fifth
rule closes that flank: an omission is not a licence to re-spell.
Second: rule 2 enumerates bounds tightenings and excludes re-typing a member,
but its proviso tests INSTANCES, so narrowing a value schema (say, core
`metadata` from any JSON value to a bounded string) read as both forbidden
schema-level re-typing and permitted instance-level validity. It is neither:
it is a third category, a DEVIATION the profile declares with the same
machinery rule 3 requires for embedded-relation omissions, conformant only if
values failing the narrower schema are omitted entirely rather than coerced,
and only if the declaration says the member may be incomplete.
`Issue.metadata`'s warning against decoding into a string-to-string map is
scoped to clients of THIS document so it no longer reads as contradicting a
profile's declared narrowing; the core warning itself is unchanged.
Description-only: regenerating internal/httpapi/apigen/types.gen.go leaves it
byte-identical (dd0f41b2a8 before and after).