Seal git and appnet #642

Activity

1. David-Noble-at-work

   added

   taskImplementation work itemImplementation work item

   on Aug 24, 2026
2. David-Noble-at-work

   self-assigned this

   on Aug 24, 2026
3. David-Noble-at-work

   added

   Epic:ResourceModelThe resource modelThe resource model

   on Aug 24, 2026
4. David-Noble-at-work commented on Aug 25, 2026

   

   David-Noble-at-work

   on Aug 25, 2026

   ContributorAuthor

   More actions

   Two things phase 1 (#641, merged) established that this phase inherits — neither was in the plan.

   1. Every sealed provider registers two things from its own init, not one:

   func init() {
   	// What reflection runs against. The NON-pointer form, matching what the announcement passed while
   	// the resource was a struct.
   	op.RegisterResourceImplementation(reflect.TypeFor[Resource](), reflect.TypeFor[resource]())
   
   	// What an authored string claims as. An interface asserts no kind, so a plain string bound to an
   	// interface-typed slot is refused (§5.7 rule 6) unless the interface designates a claim type. A
   	// single-implementation provider designates itself.
   	op.RegisterResourceMint(reflect.TypeFor[Resource](), reflect.TypeFor[*resource]())
   }

   Omitting the mint does not fail to compile — it fails at plan time with "an authored string cannot bind the interface-typed resource slot", which is how phase 1 found it.

   2. The generated announcement loses its method metadata. The generator derives it by inspecting the exported type; sealing moves the methods onto the unexported struct, so the emitted map becomes nil. For service that cost three framework-facing entries and nothing noticed.

   Check this per provider before transforming it: any method that must be dispatchable has to be declared on the sealed interface. git and appnet should be checked for author-facing resource methods — the failure mode is a silently smaller Starlark surface, not a build error, so the suite will not catch it.

   Also inherited: op.Resource exposes neither ReachabilityURI, Equal, Format, nor the marshalers, so in-package tests reach the struct through a small concrete(t, r) helper rather than widening the exported contract.
5. David-Noble-at-work

   closed this as completedin #660on Aug 25, 2026