What problem does it solve? Changes to the Go CMS runtime model (SiteRuntime, ProfileBlueprint, ModuleContext, runtime-scoped bindings) can silently break atomic publication, cache coherence, or per-site isolation. This Skill encodes the invariants and review checklist needed to modify runtime code without corrupting published state. ## Core Features & Use Cases - Runtime model guardrails: Preserves the Profile declaration to immutable ProfileBlueprint to per-site SiteRuntime chain, forbidding per-request rebuilds or external-cached runtime objects. - Atomic publication rules: Enforces prepare-then-publish semantics so failed candidate builds leave the previous runtime and HTTP artifacts active. - Deactivation transitions and cache coherence: Defines deterministic prepare/abort ordering for runtime draining and traces read-to-mutation-to-invalidation paths for cached entities. - Use Case: When adding a module that contributes bindings during Build, follow the Skill to keep the registry site-scoped, run RuntimeBuildFinalizer in profile order, and add focused tests proving two sites receive distinct runtimes. ## Quick Start Ask the assistant to review your changes to the site runtime builder and cache invalidation paths using the go-cms-runtime-integrity guidelines before committing.
