Sam Valladares fc6dca6338 feat(dashboard): expose suppress + unsuppress HTTP endpoints + memories UI button ... Fixes the biggest UI gap flagged by the v2.0.7 audit: the `suppress` tool has shipped since v2.0.5 with full graph event handlers (MemorySuppressed, MemoryUnsuppressed, Rac1CascadeSwept) and violet implosion animations — but zero trigger from anywhere except the MCP layer. Dashboard users literally could not forget a memory without dropping to raw MCP calls. Backend (Axum): - `POST /api/memories/{id}/suppress` optionally accepts `{"reason": "..."}` and returns the full response payload (suppression_count, prior_count, retrieval_penalty, reversible_until, estimated_cascade_neighbors, labile_window_hours). Emits `MemorySuppressed` so the 3D graph plays the compounding violet implosion per the v2.0.6 event handlers. - `POST /api/memories/{id}/unsuppress` reverses within the 24h labile window. Returns `stillSuppressed: bool` so the UI can distinguish a full reversal from a compounded-down state. Emits `MemoryUnsuppressed` for the rainbow burst reversal animation. Frontend: - `api.memories.suppress(id, reason?)` and `api.memories.unsuppress(id)` wired through `apps/dashboard/src/lib/stores/api.ts`. - Two new TypeScript response types (`SuppressResult`, `UnsuppressResult`) in `lib/types/index.ts` mirroring the backend JSON shapes. - Memories page gets a third action button alongside Promote / Demote / Delete: violet "Suppress" with a hover-tooltip explaining "Top-down inhibition (Anderson 2025). Compounds. Reversible for 24h." The button ships `reason: "dashboard trigger"` so the audit log carries source attribution. Tests: 425 mcp + 366 core all pass, svelte-check 580 files 0 errors.		2026-04-19 20:31:44 -05:00
..
vestige-core	test(v2.0.7): cover the new behaviors the branch was shipping blind	2026-04-19 17:02:36 -05:00
vestige-mcp	feat(dashboard): expose suppress + unsuppress HTTP endpoints + memories UI button	2026-04-19 20:31:44 -05:00