create-control-manifest

# Create Control Manifest The Control Manifest is a flat, actionable rules sheet for programmers. It answers "what do I do?" and "what must I never do?" — organized by architectural layer, extracted from all Accepted ADRs, technical preferences, and engine reference docs. Where ADRs explain *why*, the manifest tells you *what*. **Output:** `docs/architecture/control-manifest.md` **When to run:** After `/architecture-review` passes and ADRs are in Accepted status. Re-run whenever new ADRs are accepted or existing ADRs are revised. --- ## 1. Load All Inputs ### ADRs - Glob `docs/architecture/adr-*.md` and read every file - Filter to only Accepted ADRs (Status: Accepted) — skip Proposed, Deprecated, Superseded - Note the ADR number and title for every rule sourced ### Technical Preferences - Read `docs/framework/technical-preferences.md` - Extract: naming conventions, performance budgets, approved libraries/addons, forbidden patterns ### Engine Reference - Read `docs/engine-reference/[engine]/VERSION.md` for engine + version - Read `docs/engine-reference/[engine]/deprecated-apis.md` — these become forbidden API entries - Read `docs/engine-reference/[engine]/current-best-practices.md` if it exists Report: "Loaded [N] Accepted ADRs, engine: [name + version]." --- ## 2. Extract Rules from Each ADR For each Accepted ADR, extract: ### Required Patterns (from "Implementation Guidelines" section) - Every "must", "should", "required to", "always" statement - Every spe...