mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-09 09:11:00 +08:00
Martin Vogel
b54eb3d0c1
The two questions the research says developers ask most and tooling answers worst: why is this code the way it is (rationale via change history and ownership), and does A reach B (LaToza reachability, asked ~9x/day). Plus the user-requested data-flow lens. - /api/trace: shortest A-to-B path over CALLS or DATA_FLOWS (BFS, depth-capped at 12), endpoints by id or qualified name; the flow cache gains a DATA_FLOWS CSR beside the CALLS one. - Symbol bundle: file_history (recent commits, commits/year, top author share from a bounded git log at metrics time, cached and honest - available:false when no history was parsed) and data_in/data_out with the stored edge detail. - Flows tab: trace bar with symbol pickers and a control/data toggle; the result path is clickable hop by hop. - Symbol tab: 'Recent changes to this file' and 'Data flows' panels with honest empty states. - Tests: trace reachability both modes + endpoint errors, symbol bundle data-flow/history shape, /api/trace route wiring, and a fetchTrace client test. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>