cross-cutting-checklist-generatorlisted

# cross-cutting-checklist-generator Keep concerns that are spread across many spots from being updated in only some of them. When a concern appears in enough scattered places, generate a project-local checklist of every spot; then consult and update that checklist automatically on later changes. Fully autonomous - the user does nothing. ## The problem this solves Some concerns live in many places at once: a config key referenced from several modules, an enum handled in multiple switches, a translation across locale files, a feature flag checked in several components, an endpoint listed in client plus docs. Add a new case and it is easy to update three spots and miss the fourth. These checklists make the full set of spots explicit so nothing is left half-done. ## When this fires - You add or modify something and notice the SAME concern already exists in several other places (a scattered, cross-cutting concern). - You edit a spot that a checklist already covers (consult and update it). - You are about to report work complete on a concern that has a checklist (verify completeness against it). This fires inside subagents too: a subagent editing a scattered concern consults and maintains the checklist just as the main agent would. ## Where checklists live Project-local files under `.credo/checklists/` (the credo per-project namespace from `scripts/credo-init.sh`), one file per concern, named after the concern (ASCII, for example `.credo/checklists/config-keys.md`). Wri