Elnor Repo Reader

You are Claude Code working in Will's ELNOR specs repository
(github.com/wbrody/Elnor-Specs, branch main, local clone).

1. Read this runbook in full:
   Memory Rebuild/Flattening/Prompts and Instructions/DOC80_Claude_Code_Master_Execution_Runbook.md
2. Read the governing plan:
   Memory Rebuild/Flattening/Current Plan/Flatten_and_Unify_Plan.md
3. Read RUN_STATE.md:
   Memory Rebuild/Flattening/Execution Ledger/Master/RUN_STATE.md
   If it does not exist, you are at Stage 0 — execute Stage 0, which creates it.
4. Run the Execution Controller in §4. Resume from RUN_STATE.md's current_stage,
   stage_status, and (in Stage 7) active_slice. If a review response has arrived,
   run the Review-Processing Routine (§21) for that stage first.
5. Run FORWARD through stages without pausing between them, until you reach the
   next mandatory stage-gate stop, an architect_stop, or a stage whose review
   tier requires Will or Codex. Do not ask "should I continue?" — the runbook
   and RUN_STATE.md define what is next.
6. At the stop, emit the Stop Gate Report (§7.1) and stop.

Constraints:
- Do not move, delete, rename, rewrite, merge, archive, or reclassify any source
  spec. Inventory and classification stages read only.
- Create or update run artifacts only under Memory Rebuild/. Read-only access to
  repo files outside Memory Rebuild/ (README.md, REPO_FILE_MANIFEST.md, source
  specs) is expected and allowed. Do not edit source specs or repo-index files
  outside Memory Rebuild/ unless Will explicitly authorizes it.
- Do not edit the flattening plan. If the plan appears genuinely contradictory
  (states a rule this runbook actively reverses — not merely a rule this runbook
  refines), raise an architect_stop.
- Do not git push, and do not git commit unless Will explicitly authorizes it.
- The flattening plan is the authority for all schemas, enums, record types,
  slice definitions, and the slice order. Where this runbook is more
  operationally specific than the plan ON WORKFLOW MECHANICS ONLY (which stage,
  which file path, which order to run prompts), the runbook governs and that is
  NOT a plan contradiction. The runbook never overrides the plan on substance.