docs: record retrieval stabilization state

docs/current-state.md

@@ -1,11 +1,18 @@
-# AtoCore - Current State (2026-04-24)
+# AtoCore - Current State (2026-04-25)
 
-Update 2026-04-24: audit-improvements deployed as `f44a211`; live harness is
-19/20 with 0 blocking failures and 1 known content gap. Active follow-up branch
-`codex/project-id-metadata-retrieval` is at 567 passing tests.
+Update 2026-04-25: project-id chunk/vector metadata is deployed and backfilled.
+Live Dalidou is on `a87d984`; `/health` is ok with 33,253 vectors and sources
+ready. Live retrieval harness is 19/20 with 0 blocking failures and 1 known
+content gap (`p04-constraints` missing `Zerodur` / `1.2`). Full local suite:
+571 passed.
 
-Live deploy: `2b86543` · Dalidou health: ok · Harness: 18/20 with 1 known
-content gap and 1 current blocking project-bleed guard · Tests: 553 passing.
+The project-id backfill was applied per populated project after a
+Chroma-inclusive backup at
+`/srv/storage/atocore/backups/snapshots/20260424T154358Z`. The immediate
+post-apply dry-run reported 33,253 already tagged, 0 updates, 0 missing, and 0
+malformed. A later repeat dry-run after the code-only ranking deploy was
+aborted because the one-off container ran too long; the earlier post-apply
+idempotency result remains the migration acceptance record.
 
 ## V1-0 landed 2026-04-22
 
@@ -72,7 +79,7 @@ Last nightly run (2026-04-19 03:00 UTC): **31 promoted · 39 rejected · 0 needs
 ## Known gaps (honest, refreshed 2026-04-24)
 
 1. **Capture surface is Claude-Code-and-OpenClaw only.** Conversations in Claude Desktop, Claude.ai web, phone, or any other LLM UI are NOT captured. Example: the rotovap/mushroom chat yesterday never reached AtoCore because no hook fired. See Q4 below.
-2. **Project-scoped retrieval guard is deployed and passing.** The April 24 p05 broad-status bleed guard now passes on live Dalidou. The active follow-up branch adds explicit `project_id` chunk/vector metadata so the deployed path/tag heuristic can become a legacy fallback.
+2. **Project-scoped retrieval guard is deployed and passing.** Explicit `project_id` chunk/vector metadata is now present in SQLite and Chroma for the 33,253-vector corpus. Retrieval prefers exact metadata ownership and keeps path/tag matching as a legacy fallback.
 3. **Human interface is useful but not yet the V1 Human Mirror.** Wiki/dashboard pages exist, but the spec routes, deterministic mirror files, disputed markers, and curated annotations remain V1-D work.
 4. **Harness known issue:** `p04-constraints` wants "Zerodur" and "1.2"; live retrieval surfaces related constraints but not those exact strings. Treat as content/state gap until fixed.
 5. **Formal docs lag the ledger during fast work.** Use `DEV-LEDGER.md` and `python scripts/live_status.py` for live truth, then copy verified claims into these docs.

docs/master-plan-status.md

@@ -131,10 +131,12 @@ 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-24)
+## What Is Real Today (updated 2026-04-25)
 
-- canonical AtoCore runtime on Dalidou (`2b86543`, deploy.sh verified)
-- 33,253 vectors across 6 registered projects
+- canonical AtoCore runtime on Dalidou (`a87d984`, deploy.sh verified)
+- 33,253 vectors across 6 registered projects, with explicit `project_id`
+  metadata backfilled into SQLite and Chroma after snapshot
+  `/srv/storage/atocore/backups/snapshots/20260424T154358Z`
 - 951 captured interactions as of the 2026-04-24 live dashboard; refresh
   exact live counts with
   `python scripts/live_status.py`
@@ -149,10 +151,13 @@ deferred from the shared client until their workflows are exercised.
 - 290 active memories and 0 candidate memories as of the 2026-04-24 live
   dashboard
 - context pack assembly with 4 tiers: Trusted Project State > identity/preference > project memories > retrieved chunks
-- query-relevance memory ranking with overlap-density scoring
+- query-relevance memory ranking with overlap-density scoring and widened
+  query-time candidate pools so older exact-intent project memories can rank
+  ahead of generic high-confidence notes
 - retrieval eval harness: 20 fixtures; current live has 19 pass, 1 known
-  content gap, and 0 blocking failures after the audit-improvements deploy
-- 567 tests passing on the active `codex/project-id-metadata-retrieval` branch
+  content gap, and 0 blocking failures after the project-id backfill and
+  memory-ranking stabilization deploy
+- 571 tests passing on `main`
 - 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
@@ -176,6 +181,10 @@ These are the current practical priorities.
 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.
+5. **Fix Dalidou Git credentials** — the host checkout can fetch but cannot
+   push to Gitea over HTTP in non-interactive SSH sessions. Prefer switching
+   the deploy checkout to a Gitea SSH key; PAT-backed `credential.helper store`
+   is the fallback.
 
 ## Active — Engineering V1 Completion Track (started 2026-04-22)