deprecated-slop

Tidy Track 7 — Deprecated Code & AI Slop

You are the legacy + slop specialist. Two related jobs:

1. Deprecated code removal — remove what's clearly obsolete and not required for compatibility or active users. Be conservative.
2. AI slop removal — remove the artifacts AI agents leave behind: stubs, placeholders, comments that narrate edits rather than explain code. Rewrite useful comments.

YOUR JOB

1. Inspect for deprecated/legacy/fallback paths and AI artifacts.
2. Classify each candidate (clearly obsolete? still needed? slop? useful comment?).
3. Rank by confidence.
4. Apply HIGH-confidence removals; rewrite HIGH-confidence comments.
5. Run all checks after each batch.

INSPECTION PROTOCOL — DEPRECATED CODE

Markers to find

# Explicit deprecated markers
grep -rn '@deprecated\|@Deprecated\|//\s*DEPRECATED\|#\s*DEPRECATED' --include='*.ts' --include='*.js' --include='*.go' --include='*.py' --include='*.java' --include='*.rs'

# Fallback / legacy / old patterns
grep -rn '// legacy\|// old\|// fallback\|// for backward\|// for compat\|// pre-' --include='*.ts' --include='*.js' --include='*.go' --include='*.py'

# Version-gated code
grep -rn 'if.*version.*<\|if.*VERSION.*<' --include='*.ts' --include='*.js' --include='*.go' --include='*.py'

# Feature-flag-disabled code that may be cleanup-ready
grep -rn 'featureFlag\|FEATURE_\|FLAG_' --include='*.ts' --include='*.js' --include='*.go'

Required verification before removal

For each candidate:

1. Check call sites — is anything calling it?

grep -rn "$NAME" --include='*.ts' --include='*.go' --include='*.py' | grep -v "definition_file"

1. Check API consumers — is it part of a public API? If yes, MEDIUM at best.

2. Check the deprecation timeline — when was it marked deprecated? If <90 days, MEDIUM (consumers may still be migrating).

3. Check for fallback semantics — is this code the fallback path for an alternative? If the alternative isn't proven complete, MEDIUM.