feat(context): close long-lived incremental local context service (#682) - #750
Conversation
…682 Add process locking, incremental rebuilds, CLI/MCP service ops, session-scoped queries, and UAT-INDEX coverage so agents can share a fresh local index without stale evidence or network binds.
CodeDecay PR CheckLead catch: Test appears to copy implementation logic — packages/knowledge/test/context-service-uat.test.ts:24-26 matches executable logic from packages/knowledge/src/service-runtime.ts:17-19: const builder = createDefaultContextServiceBuild(); | const service = new LocalContextService({ | rootDir,. This can make tests pass without protecting real behavior. Risk: High · Merge 100/100 · Decay 54/100 · Security 0/100 Full CodeDecay reportCodeDecay ReportOverall risk: High
Changed Files
Likely Impacted Areas
Normalized Impact GraphGraph artifact:
Symbol Impact EvidenceGraph artifact:
Language And Parser Coverage
Merge Risk Breakdown
Top contributors:
Notes:
Decay Risk Breakdown
Top contributors:
Dampeners:
Notes:
Security Risk Breakdown
Security Matcher Coverage
Test Evidence
Changed Path Test Proof
Untrusted Memory Context
High Risk Findings
Medium Risk Findings
Low Risk Findings
Recommended Checks
NotesCodeDecay is deterministic and local-first. This report was generated without telemetry, API keys, LLMs, or model calls. Found by CodeDecay - deterministic, local-first, no telemetry. |
Summary
codedecay context serve|health|query|rebuild|reset|stopand MCPcontext_serviceTest plan
vitestcontext-service + UAT-INDEX + CLI parser + MCP context_servicetsc -p tsconfig.base.json --noEmitcontext health --format jsonCloses #682
Made with Cursor