musememory 3.0.2 → 3.2.0

package/.agents/artifacts/HANDOFF.md

@@ -1,22 +1,131 @@
-# HANDOFF — 2026-10-20T14:05:00Z
-branch: dev | phase: Wave 21 complete; dev green 1285/0 (v2.10.1)
+# HANDOFF — 2026-10-25T23:55:00Z
+branch: `dev` | phase: **v3.1.2 released to `main`** — tag `v3.1.2`, GitHub release published, `dev` re-synced at `fb8ff75`, npm publish still blocked (principal-only)
 
 ## Next Step
-Advance to Wave 22: Review next backlog items from .agents/context/ticket-plan.md (failure attribution, eval harness, dashboard panels, Hermes provider adapter).
+The two filed issues (#313, #314) are **released in v3.1.1** (`main` @ `5f97870`,
+tag pushed, GitHub release up; `dev` re-synced at `ebf4040`). Backlog in
+priority order:
 
-## In-Flight
-- Wave 21 landed on dev via Ticket=Commit=Verify workflow:
-  - T-050: In-lock mutation safety guards (`verifyMutationSafety`, `allowDrastic`).
-  - T-177: Pre-mutation 30-snapshot rolling ring buffer (`captureSnapshotRing`).
-  - T-324: Diff-preserving `CURRENT.md` compaction handoff merge.
-  - Distillation Router: 3-channel router CLI (`distill-route`) & MCP (`memory_distill_route`).
-- Docs pass: `README.md` (1285 passed), `current.md`, `ticket-plan.md`.
+0. **npm publish is blocked** — the tag-triggered `npm-publish` workflow fails
+   with E404 `PUT musememory@3.1.1` exactly like v3.1.0's tag did (v3.0.1/v3.0.2
+   succeeded on Oct 22); the CI npm token no longer owns the package. The
+   principal publishes with owner credentials + 2FA, or rotates the token.
+
+1. **v3.1.2 patch release (optional)** — `dev` now carries the fan-out fix
+   (#328, `17c0abe`) on top of v3.1.1; run the 11-phase release engine when
+   ready. npm publish remains principal-only regardless.
+1. **Production-Grade Showcase Demo** — re-record the terminal demo (see
+   `current.md` → *Next Up*).
+3. **Wave 24 remainder** — T-316 (Hebbian co-activation edges, unblocked),
+   T-318 (ROI auto-tuner, unblocked); T-317 stays blocked on T-178.
+4. **Silent-casing fan-out** — `muse_tech_debt`, `memory_anchor_audit`,
+   `memory_drift_audit`, `/api/drift`, `/api/cognition/*` still silently
+   accept casing misses; the resolution helper
+   (`src/health/resolve.ts`) is ready to fan out as one small train.
+5. **T-405/T-406 closeout filings** — ambiguous-case wording (say the case
+   collision), Studio client 404 echo (`fetchHealth` shows placeholders),
+   wikilink hop-gate conflicted filter (retrieval.ts ~1462), `get_context`
+   handler hardcoding `includeSuperseded:false` while the schema advertises
+   it, hybrid-path `status` plumbing (pre-existing for every status),
+   queryContext superseded/rejected gate status guard (same class T-405
+   fixed).
+6. **Consolidation wave** — duplicate TTL tables, nine token estimators,
+   clamp ceilings, zero-caller exports (behaviour-changing; `current.md` →
+   *Next Up*).
+7. Also waiting on the principal: the parked spec PRs (#52–#56, R28–R32) each
+   carry a `feat/*` spec branch and need review before their waves can start.
+
+## Fix trains (this session)
+- **T-405 (#313)** — PR #321 merged into `dev` at `e30a1b7` (2026-10-24).
+  Conflicted memories are withheld from prompts by default via one shared
+  `includeConflicted` opt-in honored at every consumer gate (queryContext +
+  cache key, FTS + overfetch connective, vector row gate, engine passthrough,
+  ranking veto, muse pool choke point + anchor/route lens strips +
+  constraints + withheld notice, MCP schemas/mapping, CLI flag). Golden
+  recall fixture untouched — the frozen corpus carries zero conflicted
+  entries (verified). Tests-first RED receipts (2 fail → 7 files, suite
+  1408/0 across 213 files); Fresh Critic verdicts 8 → **9.5/10** with a
+  mutation-verified overfetch test (revert-in-isolation → exactly the new
+  test fails, restore byte-identical). Artifacts:
+  `.agents/artifacts/GAUNTLET_JOB_CONTRACT.md`, `ITERATION_LEDGER.md`,
+  `ACCEPTANCE_PACKET.md` (uncommitted working copies).
+- **T-406 (#314)** — PR #322 merged into `dev` at `d3a8f6b` (2026-10-24).
+  `resolveProjectName`/`listProjectNames`/`formatAvailable`
+  (`src/health/resolve.ts`) resolve health-scoping requests case-insensitively
+  and fail loud on unknown/ambiguous asks (CLI exit 1 · MCP isError · Studio
+  404); the gate stays a pure exact-canonical reporter; `--json` stdout kept
+  parseable (critic probe STDOUT_LINES 1/0). Tests-first RED receipts (2 pass
+  by construction / 6 fail on wiring → 8/0 full file, suite 1408/0); Fresh
+  Critic verdicts 8 → **9/10**. Artifacts:
+  `GAUNTLET_JOB_CONTRACT-T406.md`, `ITERATION_LEDGER-T406.md`,
+  `ACCEPTANCE_PACKET-T406.md`.
+- Both tickets carry landing notes in `.agents/context/ticket-plan.md`
+  (T-405, T-406) and a joint block in `current.md` → *Recently Landed Waves*.
+
+## Released (this session)
+- **v3.1.0** — PR #318 merged into `main` at `c5a141d` (*"Release: v3.1.0"*),
+  annotated tag `v3.1.0` pushed on the merge commit, GitHub release
+  published with notes derived from the stamped changelog:
+  https://github.com/harshsinghmp/musememory/releases/tag/v3.1.0
+- **Governance disclosure**: the `main` branch-guard ruleset
+  ("Main Branch Guard & Standards", ruleset 21574872) requires 1 approving
+  review. The principal ordered the release cut; no second reviewer was
+  available, so the merge used `--admin` and the bypass of that one review
+  requirement is written down here and in `current.md`. The `test` check was
+  green before the merge; previous releases (e.g. `3a7edb1` "Release:
+  v3.0.2") landed the same way.
+- The release carried **Waves 23–26** (PRs #315/#316/#317 on `dev`):
+  T-320 claim-based contradiction detection (+ `memory conflicts
+  --dry-run`), T-321 per-project health scoping across every audit
+  surface, the studio Project Scope control, the README flattening, the
+  handoff refresh, and the landing gate (CI wiring + vocabulary contract).
+- `main`'s only child was the un-back-merged showreel hotfix
+  (`fix/showreel-hash-path`, `e683ef2`); the post-release back-merge brought
+  it home (`scripts/showreel-hash.ts`), the branch was pruned local+remote,
+  and `dev` @ `c5a141d` now shares history with `main` — the Phase-10 merge
+  was clean, no conflicts.
+- Release artifacts: `package.json` `3.1.0`; CHANGELOG stamped
+  `[3.1.0] - 2026-10-24` with the `v3.0.2...v3.1.0` compare link and one
+  consolidated `### Added` section (12 items moved byte-identically,
+  verified per category against HEAD); `claims.json` regenerated because it
+  embeds the package version; `docs/mcp-tool-matrix.json` and
+  `docs/cli-reference.md` regenerated byte-identically.
+- Process note: this very file was rewritten *after* the release merged,
+  not inside the release branch — the landing gate forbids writing
+  release-state claims before `check:landed` proves them, so the closeout
+  rides its own small PR once the facts are on the remote.
 
 ## Decisions
-- Safe Mutation Guard: Block drastic shrinks (>50%) & erosion (net -2 drops) unless `allowDrastic`.
-- Snapshot Ring: 30 rolling snapshots in `.memory/snapshots/` before mutations with zero daemons.
-- Checkpoint Merge: Union hand-added constraints with handoff constraints; never clobber.
-- Knowledge Router: 3 lanes (system, content, health) with SHA-256 dedupe to `.memory/distill_state.json`.
+- **SemVer minor (3.0.2 → 3.1.0), not a patch.** The release adds one CLI
+  command, optional `project` arguments on five existing MCP tools and one
+  studio control — additive surface, no breaking changes.
+- **Code-side metrics stay workspace-wide.** Source code is shared between
+  memory projects and cannot be attributed to one, so `scope.code_scope`
+  always reads `workspace`.
+- **The "−0.8 rank" note stays corrected** (from Wave 25's close-out):
+  `STATUS_PENALTY` maps `conflicted: -0.8` and both retrieval paths apply
+  it — but a rank discount is not a filter, which is why #313 is filed.
+- **Generated docs are regen-at-release, not hand-patched**: `claims.json`,
+  `docs/mcp-tool-matrix.json` and `docs/cli-reference.md` came from
+  `bun run claims:generate`.
+
+## Open Issues
+- **#313 (T-405, HIGH)** and **#314 (T-406, LOW)** — as above, both ready.
+- **Backlog, unblocked and ready**: T-316 (Hebbian → write-time
+  `linked_memory_ids` seeding; the retrieval-expansion half already landed
+  as T-307, so the premise is partly stale), T-318 (retrieval weight
+  auto-tuner from ROI telemetry), T-319, T-323, T-328, T-332–T-335.
+  **Still blocked**: T-317 (needs T-178), T-179, T-016, T-201–T-203.
+- **Engineering debt** (counts corrected against the code in
+  `docs/roadmap.md`): three per-type TTL tables across *two* files, nine
+  token estimators across nine files plus six inline expressions, seven
+  `clampLimit` sites in `src/mcp.ts`, twelve genuinely dead exports (74 are
+  exported with no external caller).
 
 ## Verify
-`bun test` 1285/0 + `bunx tsc --noEmit` + `bun run build`
+`bun test` **1393 pass / 0 fail** (211 files, 6490 expect() calls), re-run
+twice on the release branch and again on the back-merged `dev` tree ·
+`tsc --noEmit` clean · `bun run build` clean · `claims:check` up to date ·
+`docs:check` 150 links across 102 files resolve ·
+PR #318 CI `test`: **pass** (3m14s) ·
+`bun run check:landed` after the back-merge: **RESULT: LANDED**.

package/.agents/artifacts/WORKTREE-LEASE.md

@@ -0,0 +1,86 @@
+# 🔒 Worktree Lease — Shared Checkout Protocol
+
+> Referenced by `.agents/artifacts/handoff-20261015-143202.md` and by
+> `.agents/standards/landing-gate.md` §6.
+
+A **shared checkout** is a working directory where a second agent session, a
+dispatched subagent, or a scheduled run may write files while you are in it.
+Git has no lock for that; the lease is one file whose contents name the holder.
+
+## Current lease
+
+> Fill this block to take the lease. Clear it to release it.
+
+| Field | Value |
+| :--- | :--- |
+| holder | _(none — free)_ |
+| session | _(none)_ |
+| task | _(none)_ |
+| since | _(none)_ |
+
+## 1. When the lease applies
+
+Take the lease before any `git add`, `git commit`, `git checkout`, `git stash`,
+`git merge`, `git rebase` or `git push` in a checkout where:
+
+- You dispatched a subagent that may **write files** (a read-only reviewer
+  does not need a lease; a builder does).
+- A second agent session is running in the **same directory**, or you
+  dispatched work through the `git` skill.
+- A scheduled run may touch the tree while you work.
+- A previous session was interrupted mid-mutation and may have left a lease.
+
+**A separate `git worktree` per agent is the real fix.** The lease is the
+fallback for when you were handed a shared checkout.
+
+## 2. Taking the lease
+
+One file: `.agents/artifacts/WORKTREE-LEASE.md`. **Its contents are the
+lease** — the file always exists, so taking the lease means writing your claim
+into the block above and releasing it means clearing that block. No lock file,
+so no stale lock to reason about.
+
+Record four facts and nothing else: the **holder**, the **session/agent id**,
+the **task**, the **timestamp**. Worked example — the exact contents of the
+block while the lease is held:
+
+```markdown
+| Field | Value |
+| :--- | :--- |
+| holder | orchestrator (Muse) |
+| session | ses_9f2c41a7 |
+| task | commit T-321 per-project health gate on `fix/T-321-per-project-health-gate` |
+| since | 2026-10-22T14:32:02Z |
+```
+
+## 3. Releasing the lease
+
+Clear the block back to `_(none — free)_` when the git mutations are done.
+**Release after the push, not after the commit.** A local commit is not a
+delivery — the work is delivered only when it is on the remote, so the lease
+covers the push too. Run `bun run check:landed` before releasing; if it says
+`LOCAL`, the work is still local and the lease is still yours.
+
+## 4. The staging rule
+
+> **Never `git add -A`. Never `git add .`.** In a checkout where another agent
+> or subagent may be writing.
+
+Stage only the exact paths you edited, and run `git status --short` immediately
+before staging. If the output lists files you did not touch, another agent is
+working in this tree — stop and coordinate before committing.
+
+**Why:** a broad `git add` silently sweeps a concurrent agent's in-progress
+edits into your commit. The message then describes work that is not in it — a
+history that is wrong in a way that is very hard to detect later, because the
+diff looks plausible and the tests still pass. This happened for real on
+2026-10-22 and was caught only because a subagent reported it.
+
+## 5. Do not
+
+- Do not `git add -A` or `git add .` in a shared checkout.
+- Do not commit while someone else holds the lease.
+- Do not rewrite a shared branch's history — no `git reset --hard`, no
+  `rebase` of a branch others are on, no force-push.
+- Do not assume a clean `git status` means the tree is yours. It only means
+  nobody has an uncommitted change *right now*.

package/.agents/context/current.md

@@ -1,7 +1,20 @@
 # 📍 Current Shipped State & Active Invariants
 
-> **Version**: `v3.0.2`  
-> **Status**: Patch Release — correctness fixes from the cross-file invariant audit, machine-verified published claims, and the website redesign.
+> **Version**: `v3.1.3`  
+> **Status**: Wave 29 Landed — Sovereign LifeOS Migration & Complete Decommissioning (T-444 to T-448).
+
+---
+
+## 🏛️ Wave 29 — Sovereign Ecosystem Migration & Decommissioning Complete (2026-10-26)
+
+All personal identity, telos, operational rules, and hardware terrain scanning migrated into sovereign `musememory` engines, native Vibeguard secret scanning, and de-LifeOSified agent governance. Legacy import tools have been permanently purged from source:
+
+- **Sovereign Persona & Store Ingestion (`T-444`)**: Identity, telos, and operational rules synthesized directly into sovereign `~/.memory/USER.md` persona and SQLite store. Legacy tool `import_lifeos.ts` permanently deleted from source.
+- **Native Vibeguard CLI (`T-445`)**: `memory scan-secrets [dir]` standalone zero-dependency secret scanner replacing legacy external scripts (`test/cli_secrets.test.ts`).
+- **Machine Terrain Collector (`T-446`)**: `memory terrain [--out file.md]` compiles deterministic hardware, toolchain, and local agent ecosystem maps into `system.md` (`test/vault_system.test.ts`).
+- **Global Governance De-LifeOSification (`T-447`)**: Removed all 6 legacy imports and paths from `~/.agents/AGENTS.md` and repository standards, binding truth directly to `~/.memory/USER.md` and `memory` MCP.
+- **Sovereignty Decommissioning Gate (`T-448`)**: Enforces zero external legacy imports, confirms legacy tool removal, and passes 100% cleanly in `test/sovereignty_gate.test.ts`.
+- **Golden Sequence Documentation**: Published the complete 4-phase best-practice sequence for using Muse Memory with AI coding agents in `README.md`, `docs/agent-reference.md`, and `docs/cli-reference.md`.
 
 ---
 
@@ -125,15 +138,85 @@ on any blocking failure, so CI runs it. Report:
 
 ---
 
-## ⏭️ Next Up (Post-Wave 22 Focus)
-- **Production-Grade Showcase Demo**: Re-record high-fidelity terminal demo video/GIF reflecting v3.0.0 capabilities (failure attribution, HOT.md compounding, memory branch/checkout, MCP context recall) to replace removed legacy demo.
-- **Wave 23**: Review next backlog items from `.agents/context/ticket-plan.md` (e.g. Hebbian co-activation retrieval expansion, query-seeded PPR restart set, retrieval weight auto-tuner, and contradiction engine calibration).
-- **Consolidate the remaining duplicated tables** (deferred from this session as behaviour-changing; full detail with exact locations in [`docs/roadmap.md`](../../docs/roadmap.md) → *Engineering debt*): the three divergent per-type TTL tables in `src/retention.ts`, the eight separate token estimators, the divergent limit-clamping ceilings across retrieval paths, and the remaining zero-caller exports.
+## ⏭️ Next Up (Post-Release Focus)
+- **Wave 23: Dashboard Overhaul, Terrain Maps & High-Speed Agent Hub (`T-405`–`T-422`)**:
+  - Full UI overhaul inspired by Ryoku Rashin (`http://127.0.0.1:3600`): fixed 76px left-rail cyber-minimalist navigation, instant Canvas Graph ↔ Filterable List toggle, 60fps kinetic-settling physics loop, and 52-week activity calendar heatmap.
+  - Multi-scope switcher: Project Scope (`./.memory`) vs Global User Scope (`~/.memory`) vs Cross-Project Mesh.
+  - Workspace Terrain Maps (`stack.md`, `habits.md`, `ownership.md`, `packages.md`, `repo.md`, `logs.md`) for token-efficient agent orientation.
+  - Universal Agents Hub: Auto-discovery, 1-click MCP wiring, and drop-in prompt snippets for 10+ agents (Antigravity, OpenCode, Claude Code, Cursor, Copilot, Hermes).
+  - Poster-style About panel with live architectural facts, interactive quick start onboarding, and CLI command deck.
+  - Sub-10ms UI serving performance with in-memory SQLite read caching and visibility-based zero-CPU idling.
+- **Production-Grade Showcase Demo**: Re-record high-fidelity terminal demo video/GIF reflecting v3.0.0 capabilities to replace removed legacy demo.
+- **Wave 24 remainder**: `T-316` (Hebbian co-activation edges into write-time `linked_memory_ids` seeding — **unblocked**, dep `T-095` landed; note the ticket premise is partly stale: `T-307` already landed the retrieval-expansion side) and `T-318` (retrieval weight auto-tuner from ROI telemetry — **unblocked**, deps `T-127` + `T-140` both landed). `T-317` (query-seeded PPR restart set) stays **blocked** on `T-178` (graph retrieval A/B gate).
+- **Consolidate the remaining duplicated tables** (deferred from this session as behaviour-changing; full detail with exact locations in [`docs/roadmap.md`](../../docs/roadmap.md) → *Engineering debt*): the three divergent per-type TTL tables (`src/retention.ts` **and** `src/retention/expiry_policy.ts` — only two of the three are in `retention.ts`), the **nine** separate token estimators (across nine files, plus six inline expressions — the collapse is *not* behaviour-neutral, because `src/orchestrator/context.ts` deliberately consumes the pessimistic measure), the divergent limit-clamping ceilings across retrieval paths (**seven** sites in `src/mcp.ts` alone), and the remaining zero-caller exports (twelve genuinely dead; 74 exported with no external caller).
 - **Remove the legacy `web/` directory** — done in this session. It was a second, hand-written copy of the site that `apps/website/` superseded; keeping it was the same "second copy that gets forgotten" failure mode this session fixed everywhere else.
 
 ---
 
 ## 🏁 Recently Landed Waves (Verified on `dev`)
+- [x] **Released: v3.1.2** (2026-10-25) — completes the silent-casing fan-out:
+  - PR #330 merged at `d7e875b` (*"Release: v3.1.2"*); annotated tag
+    [`v3.1.2`](https://github.com/harshsinghmp/musememory/releases/tag/v3.1.2)
+    pushed on `d7e875b`; GitHub release published. Back-merge #331 merged at
+    `fb8ff75`; `dev` re-synced.
+  - `package.json` is `3.1.2`; `[Unreleased]` empty.
+  - npm publish still blocked (same E404 as v3.1.0/v3.1.1 — principal-only).
+
+- [x] **Released: v3.1.1** (2026-10-24) — the two post-release defect fixes shipped to `main`:
+  - PR #324 merged at `5f97870` (*"Release: v3.1.1"*); annotated tag
+    [`v3.1.1`](https://github.com/harshsinghmp/musememory/releases/tag/v3.1.1)
+    pushed on the release merge; GitHub release published with notes derived
+    from the stamped changelog. `package.json` is `3.1.1` and `[Unreleased]`
+    is empty again.
+  - Governance disclosure: the `main` branch-guard ruleset requires one
+    approving review; the merge used `--admin` on the principal's order to
+    cut the release (the `test` check was green on the release branch first:
+    1408 / 0 across 213 files).
+  - Back-merge reunited `main` with `dev` (PR #325; `dev` push CI green,
+    3·m·12s). Post-merge `check:landed` → **RESULT: LANDED** at `ebf4040`.
+  - Standing blocker disclosed again: the `npm-publish` workflow failed on the
+    tag with the same E404 as v3.1.0's tag (query history: v3.0.1/v3.0.2
+    published fine on Oct 22; v3.1.0 + v3.1.1 both 404 on `PUT musememory@…`,
+    so the CI npm token lost owner rights to the package between Oct 22 and
+    Oct 24). npm publishing stays **principal-only** (owner credentials + 2FA)
+    until the token is repaired.
+  - CI false positive filed: the #325 back-merge PR's delivery-gate step
+    failed `check-landed --pr --branch main` because the gate greps for an
+    *open* PR at the head branch and the run's queue lag let the merge close
+    it first (`RESULT: NOT REVIEWABLE` on identical, separately-green
+    content). Fence in the gate's head-branch semantics for back-merge PRs.
+- [x] **Fix trains: T-405 + T-406** (2026-10-24) — issues #313/#314, delivered through the gauntlet-loop + code-review engines (contract-frozen scope, blind Fresh Critic, mutation-verified tests):
+  - **T-405** ([#313](https://github.com/harshsinghmp/musememory/issues/313)): PR #321 merged at `e30a1b7`. Conflicted memories are now excluded **by default** from every prompt-serving retrieval path — queryContext lifecycle gate (hidden_count-aware, status-scoped-guarded), FTS store gate with the overfetch connective armed iff any post-fetch hide-gate stays active, vector row gate + engine passthrough, ranking candidate veto before scoring, muse-context pool choke point + anchor/route lens strips + constraint projection + withheld notice — all sharing one `includeConflicted` opt-in (`SearchOptions` cascade; MCP `include_conflicted` schema symmetry on both search/memory_recall tools; CLI `--include-conflicted`). The frozen golden recall fixture was deliberately untouched — the eval corpus carries zero conflicted entries (verified, not assumed); new tests use a self-contained corpus (T-143 promotion discipline respected). RED receipts real (conflicted entry served `kept:high_relevance` into `confident_answers`); critic verdict **9.5/10** with a mutation-verified overfetch test. As-of/temporal queries deliberately keep serving state-at-the-time (documented decision).
+  - **T-406** ([#314](https://github.com/harshsinghmp/musememory/issues/314)): PR #322 merged at `d3a8f6b`. Project names resolve case-insensitively (`resolveProjectName`/`listProjectNames`/`formatAvailable`, `src/health/resolve.ts`) on all three health surfaces, failing **loud** (CLI exit 1 · MCP isError · Studio 404) with the requested name echoed and the available list; resolved-with-case-diff surfaces the canonical label plus a note naming the requested form; `--json` stdout stays pure JSON (probe-verified). The gate stays a pure exact-canonical reporter — `git diff test/health_project_scope.test.ts` empty. Final critic verdict **9/10**.
+  - Full-suite receipts at merge time: `bun test` **1408 pass / 0 fail** (213 files, +13 tests); `tsc --noEmit` clean; claims `1400→1408`; docs links all resolve; secret scan clean; `check:landed:pr` → `RESULT: REVIEWABLE` before both merges, `check:landed` → **`RESULT: LANDED`** after (at `e30a1b7`, then at `d3a8f6b`).
+  - **T-406 fan-out** ([#327](https://github.com/harshsinghmp/musememory/issues/327)): PR #328 merged at `17c0abe`. Same silent-casing defect closed on the remaining 7 audit surfaces — MCP `memory_anchor_audit`, `memory_drift_audit`, `muse_bug_clusters`, `muse_tech_debt` + studio `/api/cognition/anchors`, `/api/cognition/debt`, `/api/cognition/clusters` — all routed through the existing `resolveProjectName()` owner; unknown projects now fail loud (MCP tool error · Studio 404) with the available list. Gates/engines stay exact. +17 tests (1425 total, 0 new failures vs the 9 pre-existing env failures on dev).
+  - Filed follow-ups (deliberate ledger, see HANDOFF): ambiguous-case wording, Studio client 404 echo, silent-casing fan-out (`muse_tech_debt`, anchor/drift audits, `/api/drift`, `/api/cognition/*`), wikilink hop-gate conflicted filter, `get_context` include_superseded schema-vs-handler mismatch, hybrid-path status plumbing, queryContext superseded-gate status guard.
+- [x] **Released: v3.1.0** (2026-10-24) — Waves 23–26 shipped to `main`:
+  - PR #318 merged at `c5a141d` (*"Release: v3.1.0"*); annotated tag
+    [`v3.1.0`](https://github.com/harshsinghmp/musememory/releases/tag/v3.1.0)
+    pushed on the release commit; GitHub release published with notes
+    derived from the stamped changelog. `package.json` is `3.1.0` and
+    `[Unreleased]` is empty again.
+  - Governance disclosure: the `main` branch-guard ruleset requires one
+    approving review; the merge used `--admin` on the principal's order to
+    cut the release (the `test` check was green first). Disclosed also in
+    the handoff.
+  - The post-release back-merge reunited `main` with `dev`
+    (`fix/showreel-hash-path` lived only on `main` until now; the branch is
+    pruned). Gate evidence, quoted: `bun run check:landed` →
+    **RESULT: LANDED**; `git merge-base --is-ancestor HEAD origin/dev`
+    exits 0 at `c5a141d`; `bun test` re-run on the merged tree: 1393 / 0.
+- [x] **Wave 26: The Landing Gate — a commit is not a delivery**:
+  - On 2026-10-22 two complete waves (T-320, T-321) were committed to a local branch and a local `dev`, and the session ended. No push, no PR, no CI run — while the close-out document described them as landed, under a heading reading *"Recently Landed Waves (Verified on `dev`)"*. `dev` did not contain them; `origin/dev` had already moved to v3.0.2, so the branch had diverged and the work was invisible to review and to the release. **The code was correct and every test was green. The failure was a false claim about the remote that nothing had ever checked.**
+  - `scripts/check-landed.ts` is now the machine-checkable form of that claim: work is **landed** only when it is reachable from the integration branch **on the remote**, and until then it is **local**. The gate verifies `HEAD` is an ancestor of `origin/dev` and that nothing is unpushed, exits non-zero otherwise, and prints the exact commands and SHAs so a report can quote the evidence rather than assert it. A pre-review mode (`--pr --branch <name>`) verifies a branch is pushed, has an open PR, and has no failing checks. Wired into CI for both `pull_request` and `push`.
+  - `.agents/standards/landing-gate.md` (routed from `AGENTS.md` as core invariant #7) restricts the vocabulary — *landed / shipped / merged / released / "verified on `dev`"* may only be used after the gate exits 0 — and requires every final report to carry a Remote State block. The closeout DOX pass runs the gate before writing under a "Landed Waves" heading.
+  - `.agents/artifacts/WORKTREE-LEASE.md` — the file was referenced by an earlier handoff but did not exist. It now defines the shared-checkout lease (taken before git mutations, released **after the push**, not the commit) and the staging rule: **never `git add -A` in a checkout another agent may be writing.** A broad `git add` silently absorbs a concurrent agent's in-progress edits into your commit, producing a commit whose message describes work that is not in it — which happened for real on 2026-10-22 and was caught only because a subagent reported it.
+- [x] **Wave 25: T-321 Surface Completion**:
+  - A verification audit of the Wave 24 close-out found the *functions* took `options.project` but five *surfaces* never plumbed it: `memory_anchor_audit` and `memory_drift_audit` (MCP), and `/api/drift`, `/api/cognition/clusters`, `/api/cognition/debt` (studio). A user could scope the health gate but **not** an anchor or drift audit — the capability existed one layer below the surface and was unreachable. All five now take the filter, and the studio gained a labelled **Project Scope** control in the header that drives the health, drift, bug-cluster and technical-debt fetches, seeds from the URL query string (so a scoped link is shareable and reloadable), and renders the report's `scope` back to the user in the CLI's own wording. Cover: `test/health_project_scope_surfaces.test.ts` (7 cases) alongside the original `test/health_project_scope.test.ts` (9 cases).
+- [x] **Wave 24: Per-Project Health Gate Scope**:
+  - `T-321`: The health gate, the bug-clustering scanner and the technical-debt scanner all read the whole store, and the report was then labelled with `entries[0].project` — whichever memory happened to sort first. A number covering every project was presented as one project's health, and there was no way to ask for a single project's health at all. `listForProject()` (`src/store.ts`) is now the single owner of the "filter by project, or take the whole store" decision; the gate, the anchor audit, the drift audit, bug clustering and technical debt all take the same `project` option. The report carries a `scope` object (`filter`, `projects`, `entry_count`, `code_scope`), and its `project` label is the requested filter, the sole project present, or `all` — never a guess. Code-side metrics deliberately stay workspace-wide: source code is shared between projects and cannot be attributed to one. Surfaces: `memory health --project P`, a `project` argument on `muse_health`/`muse_tech_debt`/`muse_bug_clusters`, and `?project=` on the studio's `/api/health` (`test/health_project_scope.test.ts`, 9 cases, commits `60b1aa2`, `27bdc81`).
+- [x] **Wave 23: Contradiction Engine Calibration**:
+  - `T-320`: The contradiction engine compared two memories by testing seven bare regex pairs against their concatenated title and content, so any two memories containing an "enable"-ish and a "disable"-ish word were flagged as contradictory regardless of subject or context. Measured: **8 of 10** realistic non-contradictory pairs were flagged. Flagging flips *both* memories to `conflicted` — 25 health points each (four false positives fail the store-integrity pillar), removal from every future sync broadcast, and still served into agent prompts. Detection now extracts **polarity claims** (`subject`, `relation`, `target`, `scope`) and opposes claims only about the same subject in a compatible scope; re-probe of the same ten pairs: **0 of 10** flagged. New `src/quality/scope.ts` (canonical scope vocabulary, general qualifier extraction, strong/weak scope classification) and `src/quality/polarity.ts` (claim extraction + comparison); scope is now resolved per claim instead of per entry in `src/quality/invalidation.ts`. Dry-run surfaces: `memory conflicts [--dry-run]` (new CLI, read-only preview of what peer-to-peer sync would flag — the one path that flags automatically), `propose({ checkConflict: true, conflictDryRun: true })`, and `detectConflict(store, candidate, { dryRun: true })`. Calibration fixture `test/calibration/contradiction_calibration.json` (21 labelled pairs) gated at precision and recall ≥ 0.9 (`test/contradiction_calibration.test.ts`, `test/cli_conflicts.test.ts`, commits `18bf4f9`, `dc90539`).
 - [x] **Wave 22: Failure Attribution, Negative Memory Mining & Retrieval Compounding**:
   - `T-313`: Scoped failure attribution matching code anchors (`file_path`, `symbol_name`), affected paths, and reproduction commands; session-deduplicated strikes (max 1/session); dual-decay strike counter (2 clean runs or 30 days without failure); constitutional immunity protecting constraints, timeless memories, and salience $\ge 0.95$ from auto-dispute (`test/failure_attribution.test.ts`, commit `41feec4`, `3b270b5`).
   - `T-144`: Trajectory fix-pair mining discovering negative memories (`AVOID: ...`) from *Error ➔ Remediation ➔ No Recurrence* observation sequences with affinity filters excluding non-mutating commands (`ls`, `cat`), dynamic line number normalization, Vibeguard secret scrubbing, and session volume cap of max 3 candidates (`test/fix_pair_mining.test.ts`, commit `cc4b5c5`).
@@ -334,4 +417,6 @@ Removed remaining competitor product names and external comparison links from we
 - **Verification Gate**: Before declaring changes complete, `bun test`, `bun run build`, and `tsc --noEmit` must pass.
 
 ## 1. Verified Shipped Reality
+- **2026-10-22**: T-321 per-project health gate scope
+- **2026-10-22**: T-320 contradiction engine calibration
 - **2026-10-20**: Wave 21: LifeOS Distillation, Mutation Safety & Knowledge Routing (T-050, T-177, T-324)

package/.agents/context/index.md

@@ -13,7 +13,7 @@
 | [`product.md`](./product.md) | Product scope, the live MCP tool matrix, the 7 task profiles, the CLI surface, and the trust gates an agent must assume | Understanding user commands, capabilities, and MCP protocols |
 | [`architecture.md`](./architecture.md) | Dual-Scope storage (`.memory/`), SQLite DB, retrieval scoring formula, and file layout | System design, file locations, state machine, and data flow |
 | [`brand.md`](./brand.md) | Persona profiles (`USER.md` archetypes), voice, and presentation rules | Writing prompts, terminal output copy, and user documentation |
-| [`current.md`](./current.md) | Current shipped state (**v3.0.2**), test coverage, and active constraints | Before starting work on bugs, features, or refactors |
+| [`current.md`](./current.md) | Current shipped state (**v3.1.0**), test coverage, and active constraints | Before starting work on bugs, features, or refactors |
 | [`decisions.md`](./decisions.md) | Locked architectural decisions (zero-daemon, file-backed SQLite, atomic I/O) | Evaluating technical choices or refactors |
 | [`roadmap.md`](./roadmap.md) | Planned improvements, ecosystem expansions, and backlog | Scoping new capabilities |
 | [`ticket-plan.md`](./ticket-plan.md) | Detailed ticket plan for the next work waves | Planning a specific wave of work |

package/.agents/context/roadmap.md

@@ -167,7 +167,7 @@
 |---|---|---|
 | **Speed & Observability** | ✅ Shipped (sub-2ms, <50µs hot cache, 527 tests) | R25 (--include-abstract, --scope) |
 | **Hands-free hooks** | ✅ 3/6 events shipped (GAP-2) | R24 (full plugin registry) |
-| **Trust gates** | ✅ Write-time verify + recall-time freshness gate (GAP-1, GAP-3) | R23 (extend to multi-repo) |
+| **Trust gates** | ✅ Write-time verify + recall-time freshness gate (GAP-1, GAP-3) + calibrated contradiction engine (T-320) | R23 (extend to multi-repo) |
 | **Version control** | ⚠️ No branch-aware memory | R23 (memory branch/checkout/blame) |
 | **Compounding** | ✅ 7-state lifecycle + archival ladder | R23 (access-weighted retention, half-life decay) |
 | **Team/SaaS** | ⚠️ Not yet built | R26 (pricing page, Plausible, SaaS prototype) |
@@ -379,3 +379,12 @@ Exploded ticket plan: `.agents/context/ticket-plan.md` (269 tracked tickets, 21
    - `T-153`: Multi-DB topology (shared team store + personal DBs)
    - `T-387`: Client configuration recipes & shared+personal scoping governance
 
+9. **Wave 23: Dashboard Overhaul, Workspace Terrain Maps & High-Speed Agent Hub (v3.1.0 Roadmap)**
+   - `T-405`–`T-407`: Cyber-minimalist left-rail poster navigation shell, dual-scope switcher (`project` | `global` | `mesh`), and sub-10ms UI static route serving
+   - `T-408`–`T-410`: Memory Studio 2.0 with instant Canvas Graph ↔ Filterable List toggle, 60fps kinetic-settling physics loop, and 52-week activity calendar heatmap
+   - `T-411`–`T-413`: Workspace Terrain Generator (`stack.md`, `habits.md`, `ownership.md`, `packages.md`, `repo.md`, `logs.md`) & split-pane markdown reader with scanline reindexing
+   - `T-414`–`T-416`: Universal Agents Hub with live auto-discovery (Antigravity, OpenCode, Claude Code, Cursor, Copilot, Hermes), 1-click MCP wiring, and drop-in prompt snippets
+   - `T-417`–`T-419`: Poster-style About panel (WHAT, THE PIECES live facts table, PRIVACY guarantee), multi-agent quick start guide, and interactive CLI command deck
+   - `T-420`–`T-422`: In-memory SQLite read projection cache, tab visibility sensors for zero idle CPU burn, and headless UI performance benchmark suite
+
+

package/.agents/context/ticket-plan.md

@@ -251,8 +251,14 @@ Source: read-only gap audit cross-checking the 168 tickets against the four rese
 
 ## Wave I — GOVERNANCE & SCALE
 
-- [ ] T-320 · HIGH (B10) · contradiction engine calibration: 7 regexes flip BOTH sides to `conflicted` at 0.85 on any 0.4-Jaccard pair (quality/contradiction.ts:15-23,85-114) → −0.8 rank, sync removal, −25 health each = 4 false positives = FAIL. Dry-run mode, negation-pair scoping, calibration fixtures · U
-- [ ] T-321 · HIGH (B12) · per-project health gate: gate/clustering/tech-debt call `list(store)` unfiltered and label by `entries[0].project` (health/gate.ts:31,220; cognition/clustering.ts:62; tech-debt.ts:102) — one number attributed to whichever memory sorts first · dep: T-153 · U
+- [x] T-320 · landed Wave 23 — HIGH (B10) · contradiction engine calibration: 7 regexes flip BOTH sides to `conflicted` at 0.85 on any 0.4-Jaccard pair (quality/contradiction.ts:15-23,85-114) → −0.8 rank, sync removal, −25 health each = 4 false positives = FAIL. Dry-run mode, negation-pair scoping, calibration fixtures · U
+  - Landed: claim-based detection (`src/quality/polarity.ts`, `src/quality/scope.ts`); subject + scope must agree before two claims oppose. Measured 8/10 non-contradictory pairs flagged before, 0/10 after. Dry-run surfaces: `memory conflicts [--dry-run]`, `propose({conflictDryRun})`, `detectConflict(…, {dryRun})`. Calibration fixture `test/calibration/contradiction_calibration.json` gated at precision/recall ≥ 0.9. Commits `18bf4f9`, `dc90539`.
+  - Correction to the original ticket text (**superseded 2026-10-22 — the earlier version of this note was wrong**): an earlier revision of this note claimed the "−0.8 rank" penalty does not exist in the ranking engine. **It does exist.** `STATUS_PENALTY` maps `conflicted: -0.8` (`src/types.ts:342`), `src/retrieval.ts:956` reads it into `statusPenalty` and `:1072` adds it to `totalScore`, and `src/retrieval/ranking.ts:6` imports `computeFactors` from `../retrieval.ts` and uses it at `:140` — so **both** retrieval paths penalise conflicted entries by −0.8. What is true is that the penalty is a *soft* rank discount, not a filter: `conflicted` entries are excluded from the status filters in `src/retrieval.ts:1686-1701`, `src/retrieval/ranking.ts:272-273` and `src/orchestrator/context.ts:144-147`, so a genuinely contradicted memory is still injected into agent prompts with no badge. That gap is tracked as **T-405**.
+- [x] T-321 · landed Wave 24 — HIGH (B12) · per-project health gate: gate/clustering/tech-debt call `list(store)` unfiltered and label by `entries[0].project` (health/gate.ts:31,220; cognition/clustering.ts:62; tech-debt.ts:102) — one number attributed to whichever memory sorts first · dep: T-153 · U
+  - Landed: `listForProject()` in `src/store.ts` is the single owner of the filter decision; the gate, the anchor audit, the drift audit, bug clustering and technical debt all take the same `project` option. The report now carries `scope` (`filter`, `projects`, `entry_count`, `code_scope`) and its `project` label is the requested filter, the sole project present, or `all` — never a guess. Surfaces: `memory health --project P`, `project` on `muse_health`/`muse_tech_debt`/`muse_bug_clusters`, `?project=` on `/api/health`. Commit `60b1aa2`, docs `27bdc81`.
+  - **Wave 25 completion (T-321 follow-up)**: a verification audit found the *functions* took `options.project` but five *surfaces* never plumbed it — `memory_anchor_audit` and `memory_drift_audit` (MCP), and `/api/drift`, `/api/cognition/clusters`, `/api/cognition/debt` (studio). A user could scope the health gate but not an anchor or drift audit. All five now take the filter, and the studio gained a labelled **Project Scope** control in the header that drives `/api/health`, `/api/drift`, `/api/cognition/clusters` and `/api/cognition/debt`, seeds from the URL query string (so a scoped link is shareable and reloadable), and renders the report's `scope` back to the user in the CLI's own wording. Cover: `test/health_project_scope_surfaces.test.ts` (7 cases) plus the original `test/health_project_scope.test.ts` (9 cases).
+  - Design note: code-side metrics (the technical-debt scan, the doc/code drift audit) stay **workspace-wide** by design — source code is shared between projects and cannot be attributed to one. `scope.code_scope` records this so the number is never misread.
+  - Note: the scope field is named `entry_count`, not `memory_count` — the published-claim gate treats any backticked `memory_*` identifier in an agent-facing document as an MCP tool name.
 - [ ] T-322 · MEDIUM (B13) · per-file read cache: anchor audit reads every source file 3× per health check (health/gate.ts:82,111,176 → anchors/resolver.ts:121) · U
 - [ ] T-323 · MEDIUM (B14) · anchored memories force-injected to front regardless of `anchor.status` + budget ordering (orchestrator/context.ts:104-147) — anchor to a deleted file wins the slot forever · dep: T-134 · U
 - [x] T-324 · landed Wave 21 · HIGH (B18) · checkpoint merge semantics: parseCurrentConstraints & mergeCurrentConstraints in compaction handoff; diff-preserving update preserves hand-added constraints · compaction · test/current_compaction_guard.test.ts · F
@@ -518,6 +524,8 @@ Canonical detailed artifact: `.agents/artifacts/audit-and-realigned-roadmap-2026
 - [x] T-403 · HIGH · Stored-command doctor sweep: sanitize/migrate legacy non-template `test_command`s across `.memory/memories/*.yaml` to restore 100% clean validation · src/doctor.ts, .memory/ · F
 - [x] T-404 · HIGH · Stdin TTY decoupling: add `process.stdin.isTTY` check in `src/hooks/pack.ts:readStdinJson()` to prevent test runner hanging in interactive terminals · src/hooks/pack.ts · F
 - [x] T-401 · MEDIUM · Bunfig surface hardening: configure explicit test runner timeout and isolation defaults · bunfig.toml · N
+- [x] T-405 · HIGH · [#313](https://github.com/harshsinghmp/musememory/issues/313) · Conflicted memories are still injected into agent prompts with no badge: the status filters in `src/retrieval.ts:1686-1701`, `src/retrieval/ranking.ts:272-273` and `src/orchestrator/context.ts:144-147` exclude `superseded`/`rejected`/`archived`/`expired` but not `conflicted`. A contradicted memory is −0.8 rank-penalised (`STATUS_PENALTY`, `src/types.ts:342`) and removed from sync broadcasts, yet it is still served. Note: the gap is **wider** than the original note — three retrieval paths are affected, not one. Needs its own ticket and test pass because it changes retrieval output and therefore the golden recall fixtures · retrieval, orchestrator · U — **LANDED 2026-10-24**: PR #321 (`fix/T-405-conflicted-injection`) merged into `dev` at `e30a1b7`; a single shared `includeConflicted` opt-in now gates every prompt-serving read path (shown wider still by the build-out: tiered context, FTS/gate, vector, engine passthrough, muse pool/lenses all inherit or take the flag); the golden recall fixture was deliberately untouched — the frozen corpus carries zero conflicted entries, verified, so no regen was required; cryptic-suite delta +7 tests (1408/0); Fresh Critic 9.5/10 with a mutation-verified overfetch test.
+- [x] T-406 · LOW · [#314](https://github.com/harshsinghmp/musememory/issues/314) · `memory health --project P` matches the project name case-sensitively, so `--project ALPHA` against a store holding `alpha` returns an empty report whose label still reads `ALPHA`. Exact-match is honest but silent. Needs either a case-insensitive match or an explicit "no memories for project X" line · cli/health · U — **LANDED 2026-10-24**: PR #322 (`fix/T-406-case-sensitive-project`) merged into `dev` at `d3a8f6b`; new `src/health/resolve.ts` owns the resolution (`resolveProjectName`: exact wins → unique case-insensitive → loud unresolved), wired on CLI (exit 1 + available list, `--json` stdout kept pure), MCP `muse_health` (isError) and Studio `/api/health` (404 + JSON); the gate stays a pure exact-canonical reporter (scope-case tests untouched); +8 tests (1408/0); Fresh Critic 9/10.
 - [x] T-105b · landed Wave 2 — Syntax-only promotion rule: enforce AST/schema verification before candidate confirmation · promotion · branch: feat/wave-2-trust-gates · F
 
 ## Realigned In-Line Execution Sequence
@@ -542,12 +550,97 @@ Canonical detailed artifact: `.agents/artifacts/audit-and-realigned-roadmap-2026
 19. **Wave 18: Ingestion, Suppression & Curation Gates** (`T-106`–`T-113`) — [x] Landed on dev
 20. **Wave 19: Scoring Refinements & Abstract Sidecars** (`T-118`–`T-125`) — [x] Landed on dev
 21. **Wave 20: Quality Telemetry, Honesty Gates & Retrieval Fault Signals** (`T-127`–`T-135`) — [x] Landed on dev
+22. **Wave 21: Invariant Mutation Safety & Constitutional Immunity** (`T-050`, `T-313`) — [x] Landed on dev
+23. **Wave 22: Failure Attribution & Negative Mining** (`T-144`, `T-314`, `T-315`) — [x] Landed on dev
+24. **Wave 23: Dashboard Overhaul, Terrain Maps & High-Speed Agent Hub** (`T-405`–`T-422`) — [ ] Active Roadmap
 
-## v12 Totals
+---
+
+# v13 — DASHBOARD OVERHAUL, TERRAIN MAPS & HIGH-SPEED AGENT HUB (WAVE 23, 2026-10-26)
+
+Source: Deep research on local Agent OS (Ryoku Rashin `http://127.0.0.1:3600`) and architectural design blueprint (`.agents/artifacts/2026-10-26-dashboard-rehaul-rashin-research-and-wave-23-tickets.md`).
+
+## PR 1 / Issue #1: Left-Rail Cyber-Minimalist Shell, Typography & Dual-Scope Switcher
+- [ ] T-405 · UI Shell: Fixed 76px vertical left rail with clean brand mark, numbered sections (`01 OVERVIEW`..`06 ABOUT`), warm-dark aesthetic, JetBrains Mono & Archivo Black typography (English-only, zero kanji) · src/ui.ts · F
+- [ ] T-406 · Dual-Scope Memory Switcher: Header segment toggle `[ Local Project Scope (./.memory) | Global User Scope (~/.memory) | Cross-Project Mesh ]` with instant live refetch · src/ui.ts, src/store.ts, src/root.ts · F
+- [ ] T-407 · Sub-10ms UI Route Architecture: Split single embedded HTML into modular static cached templates with ETag headers and pre-compressed buffers · src/ui.ts · F
+
+## PR 2 / Issue #2: Memory Studio 2.0: Instant Graph/List View Toggle, Physics Settling & Activity Heatmap
+- [ ] T-408 · Graph vs List Toggle Switch: Instant segment toggle between interactive Canvas Graph and filterable/sortable data table with live 100ms debounced search · src/ui.ts · F
+- [ ] T-409 · Energy-Settling Canvas Physics Engine: Ring-seeded 60fps force-directed graph with auto-settling kinetic loop (`energy < SETTLE` halts rAF) and pointer capture · src/ui.ts · F
+- [ ] T-410 · Activity Calendar Heatmap & Agent Sessions Card: 52-week activity commit-style calendar for memory mutations + agent session log cards with model tags, timestamps, message counts · src/ui.ts, src/audit.ts · F
+
+## PR 3 / Issue #3: Workspace Terrain Vault: Auto-Generated Context Maps & Split Markdown Reader
+- [ ] T-411 · Workspace Terrain Generator Engine: Compile deterministic workspace maps: `stack.md`, `habits.md`, `ownership.md`, `packages.md`, `repo.md`, `logs.md` · src/vault/index.ts, src/cli.ts · F
+- [ ] T-412 · Terrain Vault Split-Pane UI: Left file tree with `GEN` badges and right rendered markdown viewer with scanline animation on `REINDEX` · src/ui.ts · F
+- [ ] T-413 · Terrain Token-Efficiency Test & Benchmark: Test suite verifying deterministic generation, zero secret leaks, and token savings · test/vault_terrain.test.ts · F
+
+## PR 4 / Issue #4: Universal Agents Hub: Detection, 1-Click MCP Wiring & Prompt Snippets
+- [ ] T-414 · Coding Agent Auto-Discovery: Detect installed agents (Antigravity, OpenCode, Claude Code, Cursor, Copilot CLI, Hermes, Crush, Goose, Aider, Codex) with `WIRED`/`UNWIRED`/`ABSENT` status · src/connect.ts, src/ui.ts · F
+- [ ] T-415 · 1-Click Wire / Unwire API: `POST /api/agents/wire` and `POST /api/agents/unwire` writing safe native MCP configs with backup protection · src/ui.ts, src/connect.ts · F
+- [ ] T-416 · "Point Any Agent" Manifest & One-Click Copy Snippet: Display exposed filesystem paths, MCP endpoints, and one-click copyable system prompt snippet for custom LLMs · src/ui.ts · F
+
+## PR 5 / Issue #5: About & Cognitive Mission Control: Architecture Specs, Quick Start & CLI Cheatsheet
+- [ ] T-417 · Poster-Style About Panel: Architectural poster with WHAT (mission), THE PIECES live facts table (SQLite, Scope, Constraints, Tools, Wiki, Audit), and PRIVACY zero-cloud guarantee · src/ui.ts · F
+- [ ] T-418 · Quick-Start Interactive Onboarding: Multi-step interactive setup cards for leading agents (Antigravity, OpenCode, Claude Code, Cursor) with copyable commands · src/ui.ts · F
+- [ ] T-419 · "Go Deeper" Interactive Command Deck: Searchable CLI command palette with copyable one-liners (`muse recall`, `muse capture`, `muse current`, `muse brief`, `muse doctor`, `muse adr`, `muse sync`) · src/ui.ts · F
+
+## PR 6 / Issue #6: System Speed, In-Memory Caching & Performance Hardening
+- [ ] T-420 · In-Memory SQLite Read Projection Cache: Cache UI list and graph responses in memory, invalidated automatically on write transactions · src/ui.ts, src/cache.ts · F
+- [ ] T-421 · Fast-Exit & Visibility Sensors: Document `visibilitychange` listeners to stop all background polling intervals and animation frames when browser tab is inactive · src/ui.ts · F
+- [ ] T-422 · Automated UI Performance Benchmark Suite: Headless benchmark asserting sub-10ms UI responses, 60fps graph rendering, and zero memory leaks · test/ui_performance.test.ts · F
+
+---
+
+# v14 — STRATEGIC HORIZONS & SOVEREIGN LIFEOS RETIREMENT (WAVES 24–29, 2026-10-26)
+
+Source: Strategic roadmaps, developer experience assets, R17–R20 tri-cognitive horizons, and LifeOS sovereignty audit.
+
+## Wave 24: Showcase, Interactive Playground & DX Assets
+- [ ] T-423 · Terminal Showreel & GIF Recording: Script and record high-fidelity terminal demo (`showreel.mp4`, `muse-memory-demo.gif`) on v3.0.0 highlighting failure attribution, negative mining, and HOT.md compounding · assets/, docs/ · N
+- [ ] T-424 · Interactive WASM/SQLite Web Playground: In-browser memory studio preview on `apps/website` with zero backend server dependencies · apps/website · F
+- [ ] T-425 · Competitive Benchmark Showcase: Real-time latency, recall accuracy, and token-cost comparison matrix vs Mem0, Zep, and Letta · apps/website, docs/ · N
+- [ ] T-426 · Multi-Agent Interactive Demos: Interactive agent switcher in website docs demonstrating context injection across Antigravity, OpenCode, Claude Code, and Cursor · apps/website · N
+
+## Wave 25: R17 Tri-Cognitive Playbooks & Episodic Narrative Horizon
+- [ ] T-427 · Procedural Playbook Engine (`ProceduralMemory`): Model and persist executable step trajectories, pre-conditions, verification assertions, and rollback recipes · src/cognition/playbooks.ts · F
+- [ ] T-428 · Episodic Causal Narrative Horizon: Group linear observations into causal episodes (`Goal ➔ Hypothesis ➔ Trajectory ➔ Verification ➔ Retrospective`) · src/cognition/episodes.ts · F
+- [ ] T-429 · Bi-Temporal Validity Windows: Stored dual timestamps (`asserted_at` vs `valid_from`/`valid_until`) allowing historical queries without clobbering active state · src/schema.ts, src/store.ts · F
+- [ ] T-430 · Ebbinghaus Utility-Reinforced Cognitive Forgetting Curve: Exponential decay for unverified candidate notes; reinforcement for green test executions · src/quality/decay.ts · F
+- [ ] T-431 · CLI & MCP Playbook Commands: Wire `memory playbook --run <id>`, `memory playbook --list`, and `muse_playbook_recall` / `muse_playbook_record` MCP tools · src/cli/playbook.ts, src/mcp.ts · F
+
+## Wave 26: R18 AST Associative Callgraph Retrieval & Speculative Pre-Flight
+- [ ] T-432 · Recursive SQLite CTE Associative Expansion (Zero-Daemon HippoRAG): 2-hop associative graph traversal using in-process SQLite recursive CTEs (`WITH RECURSIVE call_tree AS (...)`) · src/sqlite.ts, src/retrieval/ · F
+- [ ] T-433 · Speculative Pre-Flight Context Push: Git and editor hooks pre-calculating token-budgeted memory knapsacks on file opening or branch switching · src/hooks/preflight.ts · F
+- [ ] T-434 · Cross-File Symbol Blast-Radius Risk Scoring: AST identifier cross-reference scoring to rate modification risk for proposed code changes · src/anchors/blast_radius.ts · F
+- [ ] T-435 · AST-Anchored Invariant Auto-Recall: Bind exported symbols and route interfaces directly to governing ADRs and architectural invariants · src/retrieval/anchors.ts · F
+
+## Wave 27: R19 Git-Branchable Memories & Multi-Tenant Agency Enclaves
+- [ ] T-436 · Branchable Memory Overlays (`memory branch` / `branch-merge`): Branch-isolated memory layers tracking git feature branch lifecycles · src/store/branch.ts · F
+- [ ] T-437 · Multi-Tenant Agency Enclaves (`scope: client`): Cryptographically segregated client vaults across Council divisions (Sol, Jasper, Crew, Nexus) · src/store/enclaves.ts · F
+- [ ] T-438 · Zero-Knowledge Memory Attestation: Cryptographic SHA-256 signing of SyncPackets with tamper-evident audit chains for client handoffs · src/sync/attestation.ts · F
+- [ ] T-439 · Semantic Contradiction Merge Resolver: Interactive 3-way semantic conflict resolution on branch merge into `main` · src/quality/branch_merge.ts · F
+
+## Wave 28: R20 Test-Driven Reinforcement & Regression Sentry
+- [ ] T-440 · Automated CI / Test Harness Integration: Bind memory utility directly to real test outcomes (`bun test`, `vitest`, `cargo test`); increment ROI on green, decay on red · src/quality/test_feedback.ts · F
+- [ ] T-441 · Negative Anti-Pattern Regression Sentry: Proactive watchdog matching test failures against `BUG_PRONE_PATTERN` and `DO_NOT_USE` records · src/cognition/sentry.ts · F
+- [ ] T-442 · Flaky Test & Environment Drift Detector: Correlate test flakiness and failure bursts with dependency updates and environmental churn · src/doctor/flaky.ts · F
+- [ ] T-443 · Autonomous Remediation Playbook Generator: Automatically synthesize recurring test fix sequences into verified reusable playbooks · src/cognition/remediation.ts · F
+
+## Wave 29: Sovereign Ecosystem Migration & Decommissioning
+- [x] T-444 · Sovereign Persona & Memory Ingestion: Synthesize user persona into `~/.memory/USER.md` and SQLite memory store; legacy import tool permanently removed from source · F
+- [x] T-445 · Native Vibeguard CLI (`memory scan-secrets`): Standalone secret scanning binary in `musememory` with zero external dependencies · src/cli/secrets.ts · F
+- [x] T-446 · Machine Terrain Collector in `src/vault/`: Incorporate hardware, toolchain, and package scans into unified workspace maps (`memory terrain`) · src/vault/system.ts · F
+- [x] T-447 · Global Governance De-LifeOSification: Remove all legacy imports and rewrite governance directives to point purely to Muse Memory and Muse Skills · ~/.agents/AGENTS.md · N
+- [x] T-448 · Sovereign Ecosystem Decommissioning Gate: Verification audit confirming zero dangling runtime dependencies and legacy tool removal · test/sovereignty_gate.test.ts · F
+
+## v14 Totals
 | Section | Tickets |
 |---|---|
-| Total Tracked Tickets | 290 |
-| Landed on dev | 212 |
-| Active Remaining | 78 |
+| Total Tracked Tickets | 334 |
+| Landed on dev | 222 |
+| Active Remaining | 112 |
+
+
 
 

package/.agents/skills/muse-health/SKILL.md

@@ -20,6 +20,32 @@ Call the `muse_health` MCP tool (or execute `memory health`):
 }
 ```
 
+To scope the report to a single memory project, pass `project`:
+
+```json
+{
+  "dir": ".",
+  "project": "my-app"
+}
+```
+
+**Read `scope` before trusting the number.** The report states exactly what it
+covered: `scope.filter` (the requested project, or `null` for the whole store),
+`scope.projects` (every project whose memories were considered), and
+`scope.entry_count`. The `project` field is the requested filter, the sole
+project present in the store, or `"all"` — it is never a guess. Code-side
+metrics (the technical-debt scan, the documentation/code drift audit) always
+cover the whole workspace, because source code is shared between projects and
+cannot be attributed to one of them; `scope.code_scope` records this.
+
+**The same filter works on every audit surface.** `muse_tech_debt`,
+`muse_bug_clusters`, `memory_anchor_audit` and `memory_drift_audit` all take
+`project`, and so do the studio's `/api/health`, `/api/drift`,
+`/api/cognition/clusters` and `/api/cognition/debt` endpoints
+(`?project=my-app`). The Cognitive Studio's **Project Scope** control in the
+header drives all of them and keeps the value in the URL, so a scoped view is
+shareable and survives a reload.
+
 ### Step 2: Evaluate 5-Pillar Scorecard
 The engine evaluates 5 distinct hardening dimensions, outputting an overall letter grade (**A–F**) and a gate status (**PASS**, **WARN**, or **FAIL**):
 
@@ -48,6 +74,9 @@ If the gate status is **WARN** or **FAIL**, the engine outputs an ordered remedi
 # Full terminal health dashboard
 memory health
 
+# Scope the report to one memory project
+memory health --project my-app
+
 # Output raw JSON for CI/CD gating (exits 1 on FAIL)
 memory health --json
 

package/.agents/standards/README.md

@@ -16,6 +16,7 @@
 | [`system-design.md`](./system-design.md) | Domain modelling, resilience, migration rehearsal, schemas. |
 | [`workflows.md`](./workflows.md) | Scaled tiers, the 5-phase pipeline, PR-per-feature and the post-merge sequence. |
 | [`git-workflow.md`](./git-workflow.md) | Branch lifecycle, commit standards, SemVer. |
+| [`landing-gate.md`](./landing-gate.md) | The delivery contract: a commit is not a delivery. `bun run check:landed` proves work reached the remote before *landed* may be used. |
 | [`dox-hierarchy.md`](./dox-hierarchy.md) | Reading order, child document shape, the closeout checklist, the pruning loop. |
 | [`council-roles.md`](./council-roles.md) | Muse / Sol / Jasper / Crew / Nexus responsibilities and subagent dispatch policy. |
 | [`memory-context.md`](./memory-context.md) | Context hygiene, the `.memory` store lifecycle, durable proposals. |