code-tidy

Run the tidy workflow on your recent diff: it applies the project's formatters and linters first, then structural rules, then an agent-level pass that removes dead code and slop. Every layer preserves behavior and public APIs, with tests run after each apply step.

Dead code removal follows a verification procedure: scanner reports are treated as candidates, then each symbol is checked for zero references, grep hits in strings and templates, and a never-dead list covering entry points, public APIs, and registry tables. Removals proceed in tiers with tests after each batch.

The tidy tool detects project engines such as Biome, Prettier, clang-format, rustfmt, and gofmt via a scan action that reports used and missing engines. It never invents a formatter config; projects keep their existing configuration files.

Yes. Asking to check, review, or just report keeps every layer in dry-run mode, and the final report lists what would change without applying edits. An explicit focus such as dead code only or efficiency restricts the agent layer to that lens.

The failing change is reverted and the next layer does not start until the baseline is green again. CAREFUL-tier edits are applied one file at a time with tests after each file, reverting that file on failure, and three failed attempts on one file stop the run with an escalation report.