Docs: record the spec-follows-code regime across the working docs

CLAUDE.md

@@ -5,8 +5,9 @@ See @AGENTS.md for project overview, architecture rules, and the AI developer pr
 ## Documentation Index
 
 - **[SOUL.md](SOUL.md)** — project philosophy and identity. _Read first._
-- **[docs/spec/](docs/spec/)** — authoritative behavioral specification (sections 00–10):
-  the **what**. This is the contract; implement to it.
+- **[docs/spec/](docs/spec/)** — behavioral specification (sections 00–10): the **what**.
+  Descriptive, kept current with the code: the code leads; on conflict amend the spec,
+  never drift silently. User-facing behavior ships with its spec section.
 - **[docs/architecture/](docs/architecture/00-overview.md)** — architecture playbook
   (00–11): the **how** (state, persistence, modals, routing, rendering, inference,
   relationships, vega-editor techniques, visual design, interaction & feedback, learning
@@ -31,8 +32,9 @@ See @AGENTS.md for project overview, architecture rules, and the AI developer pr
 
 ## Quick Orientation
 
-- Astrolabe is a **spec-driven rebuild** — the behavior is fixed in `docs/spec/`; the
-  architecture is adapted from Syto. Implement to the spec; don't port legacy code.
+- Astrolabe is a **spec-recorded rebuild** — the architecture is adapted from Syto, and
+  `docs/spec/` records the behavior as built. Build deliberately, record in the spec;
+  don't port legacy code.
 - **`src/core/` is portable and tested hardest.** Browser specifics live in
   `src/app/infrastructure/`. UI is React + Zustand.
 - **Editor is Monaco**, charts render via **vega-embed**, storage is **IndexedDB**.