derot

Run a derot pass: find and fix rot — every place this repo's stated intent (comments, docs, CI infra, versions, dependency choices) has drifted from what the code/build actually is — without deleting knowledge that still holds.

Scope: $ARGUMENTS (empty → the whole repo; prioritise src/, .github/, *.md, build/config files).

Use the derot skill for the full methodology and the five rot dimensions. The pass:

1. Plan. Decide the scope; split it into areas (by directory / file-type).
2. Scout — parallel, read-only. For a non-trivial repo, fan out one rot-scout per area (Agent tool, or a Workflow when there are many areas — scouts are independent and read-only, so they parallelise cleanly). Each scout VERIFIES every candidate against ground truth before reporting it (open the referenced code; check Version.props / Directory.Packages.props / global.json for version claims; grep for symbol/ID/file existence; read the code under the comment). For dimension 5, dispatch the dep-analyst.
3. Synthesize. Collect findings into one ordered apply-list. Drop unverified; keep confirmed-rot, correct-keep-explanation, obsolete-delete. Sanity-check each against its stated evidence.
4. Apply. YOU — not the scouts — apply the verified edits. Correct beats delete: keep a useful why, fix only the wrong facts.
5. Verify. Build + test; for YAML/props-only changes, validate the file. Never claim done without running it.
6. Report + commit. Summarize each change with its one-line root-cause justification, plus a separate flagged, not changed list (secrets to delete, unverified candidates, dependency calls needing a human). Commit + push per the repo's hygiene conventions.

The discipline is non-negotiable (see the skill): never "fix" a comment to match a wrong assumption — fix whichever of {comment, code} is actually wrong, and chase it through every caller. Never assert a dependency succession from memory — cite the source or report it as unverified.