ratchet-addlisted

# Add Build the check for one rule: `$ARGUMENTS` If no rule was given, ask for one. To find candidates instead, `/qmw:ratchet-audit` lists what a project states and never enforces. Several rules can be built in one session, but finish each before starting the next, and stop between them for the user to confirm. Each costs a CI step and a baseline, and the step that gets skipped when they run together is asking what incident the rule came from, which is the one that decides whether the rule survives. ## Which project The runner scans the current working directory. Confirm it is the repository the rule is for before writing anything: a session started elsewhere, or one that arrives from `/qmw:ratchet-audit` run against another checkout, will otherwise install the check in the wrong tree. ## 1. State the rule in one verifiable sentence If it does not survive that, it is a judgment call. "Keep functions readable", "do not over-abstract", "write meaningful names": a detector that approximates these produces false positives, and a check that cries wolf gets disabled within a month, taking the honest checks with it. Try narrowing first. "No over-abstraction" is not detectable; "no single-use factory" might be. If nothing survives, say the rule stays a matter of review and stop. ## 2. Decide the scope, then measure The scope is `scan.dirs` and `scan.match`, and it is the decision that fixes every number after it. Settle it here rather than at step 4, so the count the user c