Post-deploy verification anomalies for #388 epic

[dcellison]

Findings

• Compare Kai memory stack to stock Mem0 baseline #468: Open issue body proposes comparing the memory stack against stock Mem0; it directly references memory-stack machinery added in the merged work, including write-side dedup, two-stage extraction, and provenance-weighted retrieval.
• Update /help text to match current command surface #425: Open issue body references the /memory surface and the removed tag-browse and forget behaviors, which are part of the merged memory UI cleanup.
• /memory: prev/next navigation on fact and episode detail screens #423: Open issue body references fact and episode detail navigation inside /memory, another merged surface.
• Memory quality: replace write-time string filters with structural controls #436: Open issue body discusses write-time filtering, retrieval-time weighting, and the memory quality epic tied to the merged memory surfaces.
• Memory: janitor pass for unretrieved-fact decay #466: Open issue body describes a janitor pass for unretrieved facts and retrieval-count logging, which depends on the merged memory stack.

Suggested follow-up

Review whether these are intended forward-looking follow-ups or whether any should be retitled or re-scoped to avoid looking like post-deploy fallout from the merged epic.

[dcellison]

Triage by Kai

Triage summary: This issue flags several open follow-up issues that reference memory-stack work from epic #388 and asks whether they are intentional next steps or should be retitled/re-scoped to avoid appearing like post-deploy regressions. It is a triage and issue-hygiene review rather than a report of a specific broken behavior.

Priority: low
Labels applied: question
Related issues: #388, #468, #425, #423, #436, #466