Inventory dead code and dead dependency candidates for 0.12.0 #2233

Summary

Create the initial inventory and triage report for dead code and dead dependency candidates across the 0.12.0 module.

Scope

• Run and compare dead-code/dependency tools across the monorepo and each workspace package.
• Inventory candidates by package/package family rather than creating one issue per symbol.
• Include production-vs-test-only classification.
• Identify false-positive patterns that must not be removed blindly.

Suggested analysis inputs

• npm run typecheck and npm run lint baseline.
• Knip for files, exports, types, class members, enum members, dependencies, and devDependencies.
• ts-prune for unused exports.
• depcheck for declared dependencies, treated as advisory.
• Import graph/orphan module tooling such as madge or dependency-cruiser.
• Targeted TypeScript reference analysis for suspicious methods or class members.

Deliverable

Produce an inventory that groups findings into at least these buckets:

• definitely dead and safe to remove
• test-only usage
• public API or exported surface requiring explicit decision
• dynamic/registry/config-driven usage requiring manual validation
• dependency cleanup candidates
• confirmed false positives

Acceptance criteria

• Inventory covers all packages under packages/* and notes any packages intentionally deferred.
• Inventory is grouped into manageable cleanup slices for follow-up PRs.
• The parent issue is updated with links to the inventory and recommended cleanup order.
• No production code is changed in this issue except optional analysis tooling/config if explicitly justified.