Record the 2026-07-20 session and the 2026-07-30 senior review

PROGRESS.md gains the ecosystem-hardening session log: entity-aware fact
resolution, the typed Praxis lifecycle client, the durable delivery outbox,
fail-closed IPC handling, correlation IDs, and the fake-ecosystem test harness.
20-07-2026-BACKLOG.md marks item 2 (morning routine engine) as core-engine
done, with the wiring and the read-only /morning page described.

REVIEW-30-07-2026.md is the review the preceding commits act on. Note two of
its findings were wrong on the details and are corrected in the commits rather
than in the document: the covdata failure was upstream Go tool-shipping
behaviour, not a truncated cache, and the resident-model contradiction ran the
opposite way — deploy/mavend.json pointed at a file that existed while the docs
carried the stale claim, because /mnt/hdd1/llms is bind-mounted over the repo's
models/llm/.

One caveat, since the review itself argues against dated markdown accumulating
at the root: this file should go the same way as the SESSION-*.md logs once its
findings are closed. Two remain open — the kuma key rotation and the LLM router
evaluation.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X5JApcrCRVGmqrxnhynSik

PROGRESS.md

@@ -1,13 +1,80 @@
-## Maven — current state (updated 2026-07-18)
+## Maven — current state (updated 2026-07-20)
 
-Architecture decision: the target resident router/phraser is the locally
-trained Qwen3-1.7B model. Older LFM references below describe the currently
-deployed/historical stack, not the target checkpoint. RU CPT has a successful
+### Session 2026-07-20 — ecosystem hardening + entity-aware facts
+
+Ten commits, focused on closing the Nexus/Praxis integration gaps flagged
+as "wired but immature" in the prior review, plus the entity-aware-memory
+backlog item (`20-07-2026-BACKLOG.md` item 5).
+
+- **Entity-aware fact resolution (Vikunja #279)** — facts gain
+  `Subject`/`EntityID`/`ResolutionState`; an async worker resolves
+  free-text subjects to canonical Nexus entity_ids (mirrors Praxis's own
+  enrichment pattern). Ambiguous/unreachable Nexus never guesses — stays
+  `pending` or terminal `ambiguous`. Voice-tapped facts (`IntentFact`) flow
+  into the queue automatically via an optional `Subject` field on
+  `WriteFactReq` (old callers unaffected, no signature break).
+- **Typed Praxis lifecycle client (Vikunja #271)** — `GetItem`/`Search`/
+  `Surface`/`Acknowledge`/`Resolve`/`Ignore`/`Pin`, routed through new RU/EN
+  dialogue verbs. Fixes a real lifecycle-invariant bug: reading an
+  attention item aloud now calls `Surface` — previously the digest path
+  read items without recording that they'd been surfaced, so "Maven
+  mentioned it" was indistinguishable from "never came up."
+- **Durable delivery outbox (Vikunja #270)** — `BeginDeliveryAttempt`
+  before `Send`, `CompleteDeliveryAttempt` after; a stale `pending` row
+  found at startup reconciles to `unknown` (never silently resent or
+  dropped — same rule as Hexis's execution-timeout handling). Closes a
+  crash-window duplicate-send bug. Wired into `DispatchNudge`,
+  `DispatchReminder`, `RepeatUnacked`; reconciliation runs once at boot
+  before the tick loop resumes.
+- **Fail-closed IPC/dependency handling (Vikunja #269, #272/#273)** —
+  ambiguous mutation outcomes (frame sent, reply lost) no longer blindly
+  retry; Nexus/Hexis dependency errors fail closed instead of guessing.
+- **Correlation IDs + version headers (Vikunja #273)** — the hand-rolled
+  Nexus/Praxis HTTP clients now send `X-Nexus-Version`/`X-Praxis-Version`
+  and thread the same correlation ID already generated in
+  `executeCapability` through the whole call chain, matching the Hexis
+  client's existing behavior.
+- **Entity-scoped Praxis attention queries** — callers holding a resolved
+  entity_id can ask "what needs attention for this entity" directly
+  instead of filtering the unscoped list client-side.
+- **Fake-ecosystem test harness with fault injection** — a reusable
+  `fakeServer` (Nexus/Praxis/Hexis fixtures, runtime-toggleable
+  `SetFault`, fake clock) replacing ad-hoc per-test `httptest` servers;
+  covers a gap that had zero test coverage (`handlePraxisAct`) and adds a
+  fault-then-recovery regression test for the fail-closed fixes above.
+- **Ops fix** — `deploy/mavend.json`'s phraser was pointed at a 4B model
+  with `n_gpu_layers=99`, which OOM'd under memory pressure and left a
+  zombie `llama-server` child; swapped to the 2B Qwen model matching the
+  intended resident-model size.
+
+Net effect: the Nexus/Praxis wiring described as "plumbing exists, thin
+compared to Maven's test depth" in the prior review is now materially
+hardened — typed clients, fail-closed error handling, durable delivery,
+and a proper fault-injection test harness are all in place. Evaluation lab
+(`20-07-2026-BACKLOG.md` item 7) is explicitly skipped for now — it runs
+on the GPU box, which is occupied by CPT. Morning routine engine (backlog
+item 3) is next up, not started.
+
+---
+
+> **Resolved 2026-07-30 (task #318).** The resident checkpoint is
+> **Qwen3.5-0.8B** (`Q4_K_M`), set in `deploy/mavend.json`; the **target** is
+> the locally CPT'd **Qwen3-1.7B**, still training (#122). Older model claims
+> below — the LFM references, the pipeline line, and the "swapped to the 2B
+> Qwen model" ops entry above — are historical. Read them as a log of what was
+> true at the time, not as current fact. Note also that `/mnt/hdd1/llms` is
+> bind-mounted over `models/llm/`, so the LFM2.5 gguf in the repo tree is
+> never loaded.
+
+Architecture decision (as written on 2026-07-20): the target resident
+router/phraser is the locally trained Qwen3-1.7B model — still the target as
+of 2026-07-30. Older LFM references below describe the then-deployed
+historical stack, not the target checkpoint. RU CPT has a successful
 full-weight checkpoint at step 1000/8077; evaluation and Qwen3 SFT tooling are
 tracked in `docs/plans/2026-07-18-qwen3-resident-training-eval.md`.
 
 Consolidated status. The reactive↔proactive core is closed and testable through
-the web PWA. The SPEC's open items 1–7 are landed (protocol doc, away-channel
+the web PWA. The former SPEC's open items 1–7 (now `DESIGN.md` § execution ledger) are landed (protocol doc, away-channel
 fallthrough, CalDAV poller, quiet-hours schedule, tools enable/disable, note RAG,
 passkey step-up); item 8 (multi-user) is deliberately deferred — see the tail.
 The two big infra gaps from the jul5 revision are closed on `overnight-jul5`: