2 Commits

Author	SHA1	Message	Date
Anto01	4c7075650c	fix(memory): Wave 1 — SQL-aggregate dashboard counts + memory write-path fixes ... Closes three live-affecting bugs surfaced by the 2026-04-29 Codex review, all in the memory write/read path. Pre-deploy on Dalidou the live discrepancy was dashboard.memories.active=315 vs integrity active=1091. 1. /admin/dashboard counts now SQL-aggregate (no sampling). New get_memory_count_summary() helper. Dashboard memories.{active, candidates,by_type,by_project,reinforced,by_status,total} all derive from full-table SQL, not a confidence-sorted limit=500 sample. Post deploy the dashboard active count must match the integrity panel. 2. PUT /memory/{id} accepts project; auto-triage now applies it. Added project to MemoryUpdateRequest and update_memory() with resolve_project_name canonicalization, before/after audit, and duplicate-active check scoped to the new project. scripts/auto_triage.py suggested-project correction now PUTs {"project": suggested} so misattribution flags actually retarget the memory. 3. POST /memory/{id}/invalidate uses direct id lookup. New get_memory(id) helper. Replaces the old _get_memories(status="active", limit=1) lookup, which only saw the highest-confidence active row. Active memories outside slot 0 no longer 404. Same status-guard structure applied to POST /memory/{id}/supersede so candidates can't silently flip to superseded. 14 regression tests added (572 -> 586 locally). Reviewed by Codex twice: verdict GO on tip 9604c3e. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 21:57:08 -04:00
Anto01	081c058f77	feat(api): invalidate + supersede for active entities and memories (Issue E) ... Public retraction path so mistakes can be corrected without SQL. Unblocks the correction workflows that the live AKC p05 session exposed. - engineering/service.py: invalidate_active_entity returns (ok, code) with codes invalidated/already_invalid/not_active/not_found for clean HTTP mapping. supersede_entity gains superseded_by + auto-creates the supersedes relationship (new SUPERSEDES old), rejects self-supersede - memory/service.py: invalidate_memory/supersede_memory accept reason string that lands in audit note - api/routes.py: POST /entities/{id}/invalidate, /supersede; POST /memory/{id}/invalidate, /supersede (all 4 behind /v1 aliases) - tests/test_invalidate_supersede.py: 15 tests (idempotency, 404/409, supersede relationship auto-creation, self-supersede rejection, missing-replacement rejection, v1 alias presence) - DEV-LEDGER.md: session log + test_count 494 -> 509 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-21 21:56:24 -04:00