test(code-graph): run the real codebase-memory-mcp against a fresh clone and a helper root
test_code_graph_real.py runs only with KVB_CODE_GRAPH_INTEGRATION=1 and a permanent daemon, from the operator's command line: a fresh clone is indexed once by the hook's helper and reused by a second hook call, and an additional root indexed by the helper is checked for a watch that outlives the helper. The second test fails on 0.12.1, which drops the watch when the helper's session closes; 009 decision 12 keeps that criterion open until an upstream release after 0.12.1 (operator 2026-11-17). 🎯 Fix: 90 % 💥 Break: 1 % 💸 Tokens: 100 % ⏱️ Velocity: 100 % 🛡️ Security: 100 % 🏆 Score: 89 🚦 Gate: ✅ 90/5, tokens and velocity <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5e00a79fdc
commit
416a838cc8
2 files changed
+166
No files matched your search
@@ -103,6 +103,17 @@ tokens.
|
||||
`allowWrite`; opening `_config.db` read-only works there. Checks read the
|
||||
setting read-only or ask the daemon (`index_status`), never through
|
||||
`config get` from the sandbox.
|
||||
12. **Watch after the helper waits for upstream (operator-confirmed
|
||||
2026-11-17)**: the real test measured that codebase-memory-mcp 0.12.1,
|
||||
the newest release (2026-10-16), drops a root's watch when the helper's
|
||||
session closes, even under `daemon start` (`watcher.watch` then
|
||||
`watcher.unwatch` in `cbm-daemon.log`); the code that keeps it on a
|
||||
permanent daemon exists only on upstream main. The watch criterion of
|
||||
Other repositories and `test_code_graph_helper_watch` stay open until a
|
||||
release after 0.12.1; meanwhile a session root stays watched by its own
|
||||
MCP session. Rejected: the hook re-indexing on a moved HEAD, a
|
||||
supervisor holding one idle session per root (both workarounds), an
|
||||
unreleased upstream build.
|
||||
|
||||
## Approach
|
||||
|
||||
|
||||
Reference in new issue
Block a user