feat(runtime): ingest local telemetry evidence - #742
Conversation
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
codedecay runtimewith JSON and Markdown reportsWhy
CodeDecay needs runtime evidence to show which production paths are exercised or failing without turning historical or sampled telemetry into false proof that the current tree is safe. This first slice is local-only, performs no network calls or project command execution, and keeps source references inspectable.
Validation
pnpm run lintpnpm typecheckpnpm test(769 passed)pnpm buildpnpm --filter @submuxhq/codedecay pack --dry-runRemaining Issue Scope
This PR intentionally does not close the full issue. Provider adapter contracts, requirement and product-flow correlation, learning proposals, environment allowlists, and explicit live-provider query intent remain follow-up work.
Refs #685