feat(humanizer): update action command templates [skip-docs]

Wave 5 Step 15. Threads --raw plumbing through all seven action
command templates and adds a shape test covering structural plumbing
plus help.md's plain-language vocabulary.

- commands/fix.md: --raw flag parsed; fix-plan rendering groups by
  userActionLanguage; humanized title/description/recommendation are
  rendered verbatim from the cross-referenced scan envelope.
- commands/rollback.md: terminology pass — "manifest" → "list of
  changes" in user-facing copy; the file name manifest.yaml is kept
  as the machine contract; --raw threaded through.
- commands/plan.md: --raw forwarded to the planner-agent's prompt;
  agent now instructed to group actions by userImpactCategory and
  lead with userActionLanguage; bash block added for flag parsing.
- commands/implement.md: --raw forwarded to the implementer-agent's
  prompt; progress-log lines now reference the humanized titles
  already present in the action plan.
- commands/cleanup.md: --raw accepted as no-op (cleanup is
  file-management only, no findings prose); bash block added.
- commands/help.md: full plain-language pass — "PreToolUse" and
  "frontmatter" jargon removed from user-facing copy; new
  vocabulary table surfaces the humanized userImpactCategory and
  userActionLanguage labels ("Configuration mistake", "Conflict",
  "Wasted tokens", "Missed opportunity", "Dead config" / "Fix this
  now", "Fix soon", "Fix when convenient", "Optional cleanup",
  "FYI"); --raw documented as global pass-through flag.
- commands/interview.md: --raw accepted as no-op; "unused hooks"
  question phrased as "unused automation that runs at specific
  events" in user-facing copy.

tests/commands/action-commands-shape.test.mjs (new, +6 tests, 780 → 786):
  - structural: bash block + Read tool + --raw/$ARGUMENTS plumbing
    across all 7 files
  - help.md vocabulary: ≥3 userImpactCategory labels and ≥3
    userActionLanguage phrases present
  - help.md jargon: no bare "PreToolUse" or "frontmatter" in copy

plugins/config-audit/commands/rollback.md

@@ -13,12 +13,19 @@ Restore configuration files from a previous backup. Without arguments, lists ava
 ## Arguments
 
 - `$ARGUMENTS` may contain a backup ID (format: `YYYYMMDD_HHMMSS`)
+- `--raw`: pass-through flag accepted for CLI surface consistency. Rollback is file restoration only (no scanner output, no findings prose), so `--raw` is a no-op here, but the flag is still parsed so users get uniform behaviour across the toolchain.
 
 ## Behavior
 
 ### List mode (no argument)
 
-List available backups from `~/.claude/config-audit/backups/`:
+Parse flags and list available backups from `~/.claude/config-audit/backups/`:
+
+```bash
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+ls -1 ~/.claude/config-audit/backups/
+```
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -33,11 +40,11 @@ List available backups from `~/.claude/config-audit/backups/`:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-Read each backup's `manifest.yaml` to extract file list and timestamps.
+Use the Read tool on each backup's `manifest.yaml` (the list of changes captured at backup time) to extract the file list and timestamps.
 
 ### Restore mode (with backup ID)
 
-1. Read manifest from `~/.claude/config-audit/backups/{backup-id}/manifest.yaml`
+1. Read the list of changes from `~/.claude/config-audit/backups/{backup-id}/manifest.yaml` using the Read tool
 2. Show files that will be restored — ask for confirmation:
    ```
    AskUserQuestion:
@@ -46,10 +53,10 @@ Read each backup's `manifest.yaml` to extract file list and timestamps.
        - "Yes, restore"
        - "Cancel"
    ```
-3. For each file in manifest:
-   a. Read backup file from `~/.claude/config-audit/backups/{backup-id}/files/{safeName}`
-   b. Write to original path
-   c. Verify checksum matches manifest
+3. For each file in the list of changes:
+   a. Read the backup file from `~/.claude/config-audit/backups/{backup-id}/files/{safeName}`
+   b. Write to the original path
+   c. Verify the checksum matches the recorded value in the list of changes
 4. Show result:
    ```
    Restored 3 files from backup 20260403_163045