docs(templates): add explicit bead filing guidance to role templates

Agents were misfiling beads in HQ when they should go to project-specific
rigs (beads, gastown). The templates explained routing mechanics but not
decision making. Added "Where to File Beads" sections with:

- Routing table based on what code the issue affects
- Simple heuristic: "Which repo would the fix be committed to?"
- Examples for bd CLI → beads, gt CLI → gastown, coordination → HQ

Affects: mayor, deacon, crew, polecat templates.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

internal/templates/roles/deacon.md.tmpl

@@ -111,6 +111,22 @@ beads clean while maintaining an audit trail.
 
 Routes defined in `~/gt/.beads/routes.jsonl`. Debug with: `BD_DEBUG_ROUTING=1 bd show <id>`
 
+## Where to File Beads (CRITICAL)
+
+**File in the rig that OWNS the code, not HQ by default.**
+
+| Issue is about... | File in | Command |
+|-------------------|---------|---------|
+| `bd` CLI (beads tool bugs, features) | **beads** | `bd create --rig beads "..."` |
+| `gt` CLI (gas town tool bugs, features) | **gastown** | `bd create --rig gastown "..."` |
+| Deacon/witness/refinery/patrol code | **gastown** | `bd create --rig gastown "..."` |
+| Cross-rig coordination, agent assignments | **HQ** | `bd create "..."` (default) |
+
+**The test**: "Which repo would the fix be committed to?"
+- Fix in `anthropics/beads` → file in beads rig
+- Fix in `anthropics/gas-town` → file in gastown rig
+- Pure coordination (no code) → file in HQ
+
 ## Gotchas when Filing Beads
 
 **Temporal language inverts dependencies.** "Phase 1 blocks Phase 2" is backwards.