Maintain a code-scans skill

A code-scans skill rots the moment the tree is refactored. It keeps naming retired directories, its enumerations lose members, it cites a gate that was removed, and it misses the contract corpus that AGENTS.md started protecting last month. A surveying agent that trusts it then searches the wrong roots and proposes deleting something settled. This skill is the upkeep loop for a skill generated by /create-code-scans-skill (or any project-local simplification-survey skill of the same shape). The unit of rigor is the claim: every path, every protected-surface entry, every corpus rule, every command the skill names either still holds or gets fixed.

Outcomes

Pick one, and say which:

• clean — every claim was checked, the live pass ran, nothing worth shipping. No branch, no PR.
• changed — one PR ships proven corrections to the skill.
• blocked — a check could not finish or a proven fix could not ship safely. Say exactly what blocked it.

Edit scope

Only edit the code-scans skill's own directory. Never edit product code, docs, or notes to make the repo match the skill: when they disagree, the repo is the truth and the skill is what changes. Simplification candidates the live pass turns up are a by-product: report them to the user in the shape the skill prescribes, but keep them out of this PR.

Pass

0. Locate the target. Find .agents/skills/code-scans-*/SKILL.md (with .claude/skills/code-scans-* symlinks pointing to the same directories). If none matches, look for an older project-local skill with the same shape (survey domains, corpus classification, prove-or-reject rules; often named *-find-simplifications) and confirm it with the user. Several candidates → ask which one; none → stop and point at /create-code-scans-skill instead of inventing a target.