new-patch

# /new-patch <tag> Create the four files needed for a new patch, then hand off to the user. `$ARGUMENTS` is the patch tag. If the tag is missing, ask the user for tag, one-line purpose, and group. ## Files to create 1. **`src/patches/<tag>.ts`**: copy the structure from a similar existing patch in `src/patches/`. Import `traverse`, `@babel/types`, and helpers from `./ast-helpers.js`. Export a `Patch` with `tag`, `astPasses`, and `verify`; see `src/types.ts` for the interface. 2. **`src/patches/<tag>.test.ts`**: use `node:test` plus `node:assert/strict`. At minimum, assert the exported `tag` matches and add a placeholder for verify behavior. Mirror the shape of a sibling `*.test.ts`. 3. **`src/patches/index.ts`**: add the named `export ... from "./<tag>.js"`, add the import for the array, and append the patch to `allPatches`. 4. **`src/patch-metadata.ts`**: add a `BY_TAG["<tag>"]` record with `tag`, `label`, and `group`. ## After scaffolding Tell the user the four files are created. Do not implement the visitor or verifier; that is the user's design step. Remind them to follow `CLAUDE.md > Adding Patches`: - **Step 5**: if the patch changes exported live prompt guidance, update `src/verification/prompt-surface-rules.ts` and update `src/verification/prompt-policy-contract.ts` for shared policy. - **Step 6**: when the total patch count changes, keep the patch count in sync across the `README.md` intro and patch-count badge. Confirm the new total against `bun run cli --li...