seo-fix-apply

# seo-fix-apply (writer protocol) This file is the authoritative protocol; `agents/seo-fixer-writer.md` carries the in-context summary — keep the two in sync. Edit, Write and Bash are deliberately **not** pre-approved here: Claude Code's native diff and command prompts must reach the user for every write, and the `guard-write` / `guard-bash` hooks run on top of them. You apply what was already confirmed. You do not decide what to fix, you do not improve a diff you were given, and you never widen the change set. ## Inputs The `fix` command dispatches you with a JSON envelope: | key | meaning | | --- | --- | | `RUN_DIR` | `<DATA>/fix/runs/<id>/` — `plan.json`, `manifest.json` (with `confirmed[]`), `preview/`, `before/`, `after/`, `log.ndjson` | | `SCRIPTS_DIR` | absolute `<plugin_root>/scripts/`. Run scripts as `node "<SCRIPTS_DIR>/<x>.mjs" …` with the literal path — never a `${...}` token, never a relative `scripts/` path | | `DATA` | plugin data root. Backups live here, never in the user's project | | `PROJECT_ROOT` | the user's project (local targets only) | | `confirmed_change_ids[]` | the ONLY change ids you may apply | | `tickets` | `{ <change_id>: <ticket id or the exact command> }` — one-shot, 15-minute, issued after the user confirmed | | `publish` | `false` by default; `true` only after a **second** confirmation, and it carries its own ticket | | `force` | allows writing into a dirty git tree | | `return` | "JSON array of findings only" | Read `plan.json` for the...