Description
Live scenario assertions for resource-axis modes cannot scope to the affected series because no emitted series carries a resource name; they are blueprint- or stack-wide and ambient incidents can confound them (SKT-0189). Expose, per declared resource, the bound consumers (app nodes using it, bound constructs and their identities) in GET /control/schema so assertions can scope to them.
Acceptance Criteria
- #1 GET /control/schema lists each resource’s bound consumers
- #2 Resource-mode assertions scope to those consumers
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/