docs: sprint documentation — ledger + master-plan sync

Updated DEV-LEDGER orientation with post-sprint state:
- live_sha 775960c, tests 303, harness 17/18 on live
- interactions 234 (192 claude-code + 38 openclaw)
- project_state_entries 110 across 6 projects
- nightly pipeline now includes auto-promote, harness, summary

Updated master-plan-status.md "What Is Real Today" to match
actual 2026-04-16 state. Phase 10 moved from "Next" to
operational. New "Now" priorities: observe pipeline, knowledge
density, multi-model triage, fix p04-constraints.

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

docs/master-plan-status.md

@@ -126,25 +126,29 @@ This sits implicitly between Phase 8 (OpenClaw) and Phase 11
 (multi-model). Memory-review and engineering-entity commands are
 deferred from the shared client until their workflows are exercised.
 
-## What Is Real Today (updated 2026-04-12)
+## What Is Real Today (updated 2026-04-16)
 
-- canonical AtoCore runtime on Dalidou (build_sha tracked, deploy.sh verified)
-- 33,253 vectors across 5 registered projects
-- project registry with template, proposal, register, update, refresh
-- 5 registered projects:
-  - `p04-gigabit` (483 docs, 5 state entries)
-  - `p05-interferometer` (109 docs, 9 state entries)
-  - `p06-polisher` (564 docs, 9 state entries)
-  - `atomizer-v2` (568 docs, newly ingested 2026-04-12)
-  - `atocore` (drive source, 38 state entries)
-- 47 active memories (16 project, 16 knowledge, 6 adaptation, 3 identity, 3 preference, 3 episodic)
+- canonical AtoCore runtime on Dalidou (`775960c`, deploy.sh verified)
+- 33,253 vectors across 6 registered projects
+- 234 captured interactions (192 claude-code, 38 openclaw, 4 test)
+- 6 registered projects:
+  - `p04-gigabit` (483 docs, 15 state entries)
+  - `p05-interferometer` (109 docs, 18 state entries)
+  - `p06-polisher` (564 docs, 19 state entries)
+  - `atomizer-v2` (568 docs, 5 state entries)
+  - `abb-space` (6 state entries)
+  - `atocore` (drive source, 47 state entries)
+- 110 Trusted Project State entries across all projects (decisions, requirements, facts, contacts, milestones)
+- 84 active memories (31 project, 23 knowledge, 10 episodic, 8 adaptation, 7 preference, 5 identity)
 - context pack assembly with 4 tiers: Trusted Project State > identity/preference > project memories > retrieved chunks
 - query-relevance memory ranking with overlap-density scoring
-- retrieval eval harness: 18 fixtures, 17/18 passing
-- 290 tests passing
-- nightly pipeline: backup → cleanup → rsync → LLM extraction (sonnet) → auto-triage
+- retrieval eval harness: 18 fixtures, 17/18 passing on live
+- 303 tests passing
+- nightly pipeline: backup → cleanup → rsync → OpenClaw import → vault refresh → extract → triage → **auto-promote/expire** → weekly synth/lint → **retrieval harness** → **pipeline summary to project state**
+- Phase 10 operational: reinforcement-based auto-promotion (ref_count ≥ 3, confidence ≥ 0.7) + stale candidate expiry (14 days unreinforced)
+- pipeline health visible in dashboard: interaction totals by client, pipeline last_run, harness results, triage stats
 - off-host backup to clawdbot (T420) via rsync
-- both Claude Code and OpenClaw capture interactions to AtoCore
+- both Claude Code and OpenClaw capture interactions to AtoCore (OpenClaw via `before_agent_start` + `llm_output` plugin, verified live)
 - DEV-LEDGER.md as shared operating memory between Claude and Codex
 - observability dashboard at GET /admin/dashboard
 
@@ -152,26 +156,28 @@ deferred from the shared client until their workflows are exercised.
 
 These are the current practical priorities.
 
-1. **Observe and stabilize** — let the nightly pipeline run for a week,
-   check the dashboard daily, verify memories accumulate correctly
-   from organic Claude Code and OpenClaw use
-2. **Multi-model triage** (Phase 11 entry) — switch auto-triage to a
+1. **Observe the enhanced pipeline** — let the nightly pipeline run for a
+   week with the new harness + summary + auto-promote steps. Check the
+   dashboard daily. Verify pipeline summary populates correctly.
+2. **Knowledge density** — run batch extraction over the full 234
+   interactions (`--since 2026-01-01`) to mine the backlog for knowledge.
+   Target: 100+ active memories.
+3. **Multi-model triage** (Phase 11 entry) — switch auto-triage to a
    different model than the extractor for independent validation
-3. **Automated eval in cron** (Phase 12 entry) — add retrieval harness
-   to the nightly cron so regressions are caught automatically
-4. **Atomizer-v2 state entries** — curate Trusted Project State for the
-   newly ingested Atomizer knowledge base
+4. **Fix p04-constraints harness failure** — retrieval doesn't surface
+   "Zerodur" for p04 constraint queries. Investigate if it's a missing
+   memory or retrieval ranking issue.
 
 ## Next
 
 These are the next major layers after the current stabilization pass.
 
-1. Phase 10 Write-back — confidence-based auto-promotion from
-   reinforcement signal (a memory reinforced N times auto-promotes)
-2. Phase 6 AtoDrive — clarify Google Drive as a trusted operational
+1. Phase 6 AtoDrive — clarify Google Drive as a trusted operational
    source and ingest from it
-3. Phase 13 Hardening — Chroma backup policy, monitoring, alerting,
+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
 
@@ -193,9 +199,10 @@ These remain intentionally deferred.
   plugin now exists (`openclaw-plugins/atocore-capture/`), interactions
   flow. Write-back of promoted memories back to OpenClaw's own memory
   system is still deferred.
-- ~~automatic memory promotion~~ — auto-triage now handles promote/reject
-  for extraction candidates. Reinforcement-based auto-promotion
-  (Phase 10) is the remaining piece.
+- ~~automatic memory promotion~~ — Phase 10 complete: auto-triage handles
+  extraction candidates, reinforcement-based auto-promotion graduates
+  candidates referenced 3+ times to active, stale candidates expire
+  after 14 days unreinforced.
 - ~~reflection loop integration~~ — fully operational: capture (both
   clients) → reinforce (automatic) → extract (nightly cron, sonnet) →
   auto-triage (nightly, sonnet) → only needs_human reaches the user.