codebase-memory-mcp

mirror of https://github.com/DeusData/codebase-memory-mcp.git synced 2026-11-11 09:25:35 +08:00

Files

T

Martin Vogel 617a4b1495 feat(ui): change impact — who can reach this symbol, and what to retest

/api/impact answers the strongest-demand developer question in the
information-needs literature: if I change this, what breaks and what
must I retest. A reverse CALLS adjacency joins the flow cache (built in
the same edge pass); a distance-labelled BFS from any symbol reports
reachers per hop, a region rollup, and — separately — the test
functions that reach the symbol, nearest first: the tests to run.
Honest caps (depth 10, 50k visits, both flagged) and a stated basis:
static CALLS only, so every count is a floor.

The symbol page grows an 'If you change this' card: headline sentence,
cumulative hop tiers, region chips, run-these-first test list with an
explicit warning when no test reaches the symbol, and the floor
footnote. Question family F3 flips to answered (7/8/3); the
blast-radius wiki entry now names its caps.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>

2026-08-27 14:29:51 +02:00

@/components/ui

Replace vmem with mimalloc global allocator, add extraction-phase prescan, fix __init__.py QN collision

2026-03-17 22:05:57 +01:00

src

feat(ui): change impact — who can reach this symbol, and what to retest

2026-08-27 14:29:51 +02:00

components.json

Replace vmem with mimalloc global allocator, add extraction-phase prescan, fix __init__.py QN collision

2026-03-17 22:05:57 +01:00

index.html

feat(ui): the Atlas graphite design system + trust repairs (Field Guide D1)