feat(runtime): close local telemetry evidence (#685) - #752
Conversation
…ge for #685 Add downstream/budget correlation, cited investigation tasks, historical non-proof semantics, MCP runtime_evidence, and local-only provider defaults without network calls.
CodeDecay PR CheckLead catch: No direct high-signal catch found CodeDecay did not find a strong direct regression or weak-test signal in this run. Risk: Medium · Merge 39/100 · Decay 54/100 · Security 0/100 This score is conservative pending stronger direct evidence. Treat structural-only signals as review guidance, not proof of a regression. Full CodeDecay reportCodeDecay ReportOverall risk: Medium
Changed Files
Likely Impacted Areas
Normalized Impact GraphGraph artifact:
Symbol Impact EvidenceGraph artifact:
Language And Parser Coverage
Merge Risk Breakdown
Top contributors:
Dampeners:
Notes:
Decay Risk Breakdown
Top contributors:
Dampeners:
Notes:
Security Risk Breakdown
Security Matcher Coverage
Test Evidence
Changed Path Test Proof
Untrusted Memory Context
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
canProveCurrentTree: falseruntime_evidence, persist redacted.codedecay/local/runtime-evidence.json, document can/cannot prove indocs/runtime.mdTest plan
vitestruntime-evidence + CLI runtime + MCP runtime_evidencetsc -p tsconfig.base.json --noEmitruntime --helpCloses #685
Made with Cursor