chore: MAINT-227 Dead-code deletion verification pass (go/no-go for T4–T10)#140
Merged
MP2EZ merged 1 commit intoJun 6, 2026
Merged
Conversation
…4–T10) Independent caller re-verification of the 2026-06-06 audit's bloat-agent "zero caller" claims, gating deletion tranches T4–T10. Read-only; no app code ships. 4 of 7 targets confirm clean GO; 3 are wrong/imprecise as written: - T5 performance optimizer: removable only as an atomic dead-chain cluster (the "live" callers are transitively dead via a zero-import demo file); deleting the optimizer alone breaks tsc. - T6 CrisisSecurityProtocol: initialize() is a live non-metrics caller (SecurityMonitoringService.ts:410) — "metrics-only" scope would break the build. But SecurityMonitoringService is itself dead (T9), so run T9 first and delete the file outright. - T10 FeatureGate: prod-dead but test-consumed (owner disposition); flows.ts/ stoic.ts are live files (sub-block scope only); path correction noted. Corrected scopes mirrored as comments on MAINT-237/238/245/247. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes MAINT-227
Independent read-only re-verification of the 2026-06-06 audit's bloat-agent "zero-caller" claims that gate deletion tranches T4–T10. No application code ships — deliverable is a go/no-go audit doc + corrected-scope comments on the downstream tickets.
Result: the gate paid off — 4 of 7 targets confirm clean GO; 3 are wrong or imprecise as written (following T5/T6 ACs verbatim would have broken
tsc):performance/optimizer → GO only as an atomic dead-chain cluster (the "live" callers are transitively dead via a zero-import demo file).CrisisSecurityProtocol→initialize()is a live non-metrics caller (SecurityMonitoringService.ts:410); but its consumer is itself dead (T9), so run T9 first → delete the whole file.FeatureGate→ prod-dead but test-consumed (owner disposition);flows.ts/stoic.tsare live files (sub-block scope only); Technical-Notes path corrected.Deliverable:
docs/development/audits/MAINT-227-dead-code-deletion-verification-2026-06-06.md. Corrected scopes mirrored as comments on MAINT-237/238/245/247.🤖 Generated with Claude Code