docs: reflect V1-0 landed + V1 completion track active + resume map

- current-state.md: header bumped to 2026-04-22, live_sha 2712c5d,
  547 tests. New "V1-0 landed" section covers what merged, what the
  prod backfill did, and where the next phase stands.

- master-plan-status.md: new "Active - Engineering V1 Completion
  Track (started 2026-04-22)" section between Now and Next.
  Contains the 7-phase table with V1-0 marked done, V1-A gated,
  V1-B..V1-F pending. V1 removed from the "Next" section since it
  is now Active.

- DEV-LEDGER.md Orientation: two new pointers — active_track points
  to the completion plan + resume map; open_branches points to the
  R14 branch still awaiting Codex review.

- docs/plans/v1-resume-state.md (new): single-page "you are here"
  for any future session. Covers state of play, start-gates for
  V1-A, pre-flight checklist, phase map, parallel-safe work, do-nots,
  open findings, agreement protocol history, reference index.
  Designed to be cold-readable — no prior session context required.

No code changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/master-plan-status.md

@@ -168,16 +168,40 @@ These are the current practical priorities.
    "Zerodur" for p04 constraint queries. Investigate if it's a missing
    memory or retrieval ranking issue.
 
+## Active — Engineering V1 Completion Track (started 2026-04-22)
+
+The Engineering V1 sprint moved from **Next** to **Active** on 2026-04-22.
+The discovery from the gbrain review was that V1 entity infrastructure
+had been built incrementally already; the sprint is a **completion** plan
+against `engineering-v1-acceptance.md`, not a greenfield build. Full plan:
+`docs/plans/engineering-v1-completion-plan.md`. "You are here" single-page
+map: `docs/plans/v1-resume-state.md`.
+
+Seven phases, ~17.5–19.5 focused days, runs in parallel with the Now list
+where surfaces are disjoint, pauses when they collide.
+
+| Phase | Scope | Status |
+|---|---|---|
+| V1-0 | Write-time invariants: F-1 header fields + F-8 provenance enforcement + F-5 hook on every active-entity write + Q-3 flag-never-block | ✅ done 2026-04-22 (`2712c5d`) |
+| V1-A | Minimum query slice: Q-001 subsystem-scoped variant + Q-6 killer-correctness integration test on p05-interferometer | 🟡 gated — starts when soak (~2026-04-26) + density (100+ active memories) gates clear |
+| V1-B | KB-CAD + KB-FEM ingest (`POST /ingest/kb-cad/export`, `POST /ingest/kb-fem/export`) + D-2 schema docs | pending V1-A |
+| V1-C | Close the remaining 8 queries (Q-002/003/007/010/012/014/018/019; Q-020 to V1-D) | pending V1-B |
+| V1-D | Full mirror surface (3 spec routes + regenerate + determinism + disputed + curated markers) + Q-5 golden file | pending V1-C |
+| V1-E | Memory→entity graduation end-to-end + remaining Q-4 trust tests | pending V1-D (note: collides with memory extractor; pauses for multi-model triage work) |
+| V1-F | F-5 detector generalization + route alias + O-1/O-2/O-3 operational + D-1/D-3/D-4 docs | finish line |
+
+R14 (P2, non-blocking): `POST /entities/{id}/promote` route returns 500
+on the new V1-0 `ValueError` instead of 400. Fix on branch
+`claude/r14-promote-400`, pending Codex review.
+
 ## Next
 
-These are the next major layers after the current stabilization pass.
+These are the next major layers after V1 and the current stabilization pass.
 
 1. Phase 6 AtoDrive — clarify Google Drive as a trusted operational
    source and ingest from it
 2. Phase 13 Hardening — Chroma backup policy, monitoring, alerting,
    failure visibility beyond log files
-3. Engineering V1 implementation sprint — once knowledge density is
-   sufficient and the pipeline feels boring and dependable
 
 ## Later