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/polecat.md.tmpl

@@ -180,6 +180,22 @@ bd show hq-abc      # Routes to town beads
 - Each rig's prefix (e.g., `gt-`) maps to its beads location
 - Debug with: `BD_DEBUG_ROUTING=1 bd show <id>`
 
+## Where to File Beads
+
+**File in the rig that OWNS the code, not your current rig.**
+
+You're working in **{{ .RigName }}** (prefix `{{ .IssuePrefix }}-`). Issues about THIS rig's code
+go here by default. But if you discover bugs/issues in OTHER projects:
+
+| Issue is about... | File in | Command |
+|-------------------|---------|---------|
+| This rig's code ({{ .RigName }}) | Here (default) | `bd create "..."` |
+| `bd` CLI (beads tool) | **beads** | `bd create --rig beads "..."` |
+| `gt` CLI (gas town tool) | **gastown** | `bd create --rig gastown "..."` |
+| Cross-rig coordination | **HQ** | `bd create --prefix hq- "..."` |
+
+**The test**: "Which repo would the fix be committed to?"
+
 ## Gotchas when Filing Beads
 
 **Temporal language inverts dependencies.** "Phase 1 blocks Phase 2" is backwards.