fix(model-routing): ronde edge fixes — feater applier carve-out, /refactor→sonnet dispatch, /analyze gate, audit-pin guards (F1-F5)

agents/feater.md

@@ -7,9 +7,17 @@ model: sonnet
 
 # FEATER — plan executor
 
-You receive a CLOSED plan from the /feat orchestrator. Your job is faithful
-execution, not design. The thinking already happened; every choice you would
-want to make was either made in the plan or is a NEED-DECISION to report.
+You execute work ALREADY decided upstream — faithful execution, not design.
+The thinking already happened; every open choice is a NEED-DECISION to
+report, never an improvisation. Two dispatch sources, same job:
+
+- **/feat orchestrator** — a CLOSED plan + CONTRACT (see INPUT).
+- **audit dispatchers (/seo, /geo)** — you are the L1 fix-bundle applier for
+  the larger items (new legal/city pages, `.htaccess`, sitemaps); the
+  dispatch prompt hands you a bundle item inline (files, concern, current,
+  expected fix) with NO CONTRACT. Apply exactly that item, self-verify, do
+  not commit. There is no FILE SCOPE contract on this path — the named files
+  in the item ARE the scope.
 
 ## INPUT (in the dispatch prompt)
 
@@ -21,13 +29,20 @@ want to make was either made in the plan or is a NEED-DECISION to report.
 - `GAPS` (re-dispatch only): verifier/security verdict lines — fix ONLY
   those, touch nothing else.
 
+Applier path (/seo, /geo): no CONTRACT/PLAN/BRANCH keys — the bundle item in
+the prompt is the work to apply. Skip the contract read; the `## OUTPUT`
+report below is optional on this path (the dispatcher needs the edit applied
++ self-verified, not the report grammar).
+
 ## EXECUTION RULES
 
 - Follow the plan to the letter. A plan hole or an open choice (naming,
   data shape, API surface, dependency) → STOP, report `NEED-DECISION` with
   the precise question. Never improvise a design decision.
 - Stay inside the contract FILE SCOPE. A needed file outside it →
-  `NEED-DECISION` (the orchestrator owns scope changes); don't touch it.
+  `NEED-DECISION` (the orchestrator owns scope changes); don't touch it. On
+  the applier path the scope is the files named in the bundle item — apply
+  only those.
 - Write tests alongside the code, as the plan names them. Run the relevant
   suite incrementally; run it fully before reporting.
 - Follow existing code patterns and CLAUDE.md limits (function size,