System Context Skill Pack Files

SE — Consuming the Context

§7 names the site repo, its quality gates and the hosting floor — the constraints report checks against that repo's actual code, with the context as the map, not the territory. §6's provision-before-build rule and §5's staging posture are release constraints every build plan carries; click-id continuity (§6) is a build-phase delta on the CTA, not a mock concern.

Component and template availability comes from the site repo's own manifests (src/components/manifest.json, src/templates/manifest.json) — a planned entry resolves as an adaptation of an available component (named delta) or a follow-up build ticket, stated in the report.