COOL IDEA: generate Code Dojo ratchet-candidate reports

[flyingrobots]

Idea

Add a code-dojo:candidates command that runs live analysis and prints the highest-yield next cleanup slices.

Shape

The command could emit:

• top files by ESLint finding count
• top directories/packages
• top rule/file pairs
• low-risk single-rule files
• estimated debt reduction per slice
• warnings for DOGFOOD localization or file/context tripwires

Why It Is Useful

WF-134 needed ad hoc scripts to discover that wizard.test.ts was a clean 44-finding require-await slice and that docs-preview tests were a high-yield cast cluster. That should be a repeatable tool.

Acceptance Sketch

• One command produces a deterministic Markdown or JSON report.
• The report can be pasted into PR descriptions or issue bodies.
• It distinguishes easy mechanical wins from risky product/DOGFOOD files.

[flyingrobots]

Backlog release triage: assigned to v8.2.0.

Reason: Code Dojo ratchet-candidate reports belong in the quality automation lane.

This keeps the GitHub issue tracker aligned with the expanded post-v8 release horizon instead of leaving active work in Beyond or without a milestone.