The design record states the sealed contract, what it buys, and what it costs - #869

Summary

Documentation only; no code changes. Closure of the sealed-provider-resources feature (#625 phase 10).

• Eight provider documents name the shape. json, yaml, function, git, service, appnet, and memory resources each gain one sentence in the same form: the resource is a sealed interface embedding op.Resource, sealed by a method it declares itself, over an unexported struct, with the registration document as the contract. The file provider's document already said it. The pointer prose is gone from prose (*json.Resource and its siblings); Go signatures keep their pointers, since that is what those functions receive.
• The model says what the seal buys. 4-resource-management.md §2 states the two-level seal, and a new resolved decision (item 19) records that the guarantees — claims true when made, identity as the catalog key, a string as a key and never a constructor, complete intent in the graph — now hold by construction rather than by convention, because nothing outside a provider can build its resource and the announcement refuses any other shape.
• The cost is recorded beside the guarantee. Reflection prints the implementation while the type id and URI name the interface. The two strings differ deliberately; matching one against the other is wrong by construction.
• Status files follow, and the feature plan's phase 10 reads complete. All ten phases have landed; the feature's remaining work is Retire the providers' resource Unmarshal* constructors now that slots record catalog ids #854.

Found on the way: the pkg provider has no design document at all, the only provider without one, filed as #868 under the pkg feature rather than written inside a closure pass.

Plan: docs/plans/doc/647-sealed-contract-design-record.md (complete).

Acceptance — #647

• The 3.5.x per-provider design docs drop any language describing the resource as a struct; each records the sealed shape — eight documents; pkg has no document, filed as The pkg provider has no design document: 3.5.x has an entry for every provider but this one #868
• 4-resource-management.md records what the seal buys — §2's paragraph and §9 item 19, tied to items 9, 15 and 18
• Record the accepted cost: %T prints *service.resource while the URI says service.Resource — §9 item 19's second paragraph
• Status files follow — every touched document, plus the registration document's status

Verification

• No sealed resource is described as a pointer-to-struct in prose (the plan's own current-state table quotes the old spelling as a record)
• Eight documents state the shape
• The tree is otherwise untouched: the full CI gate ran locally, tests and scenarios included

Closes #647.

https://claude.ai/code/session_01SqQVFZz7AdiLZkGoAcUqRW

Time

Computed by the algorithm of noblefactor-ops#188 at merge.