fix(templates): strengthen No PRs rule to ABSOLUTELY FORBIDDEN

The previous NEVER create GitHub PRs language was too weak. Strengthened to:
- ABSOLUTELY FORBIDDEN header
- This is not negotiable
- Explicit STOP if about to run gh pr create
- Clarified PR Sheriff reviews incoming PRs, does not create them

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

internal/templates/roles/crew.md.tmpl

@@ -224,15 +224,26 @@ instructions immediately. Useful for one-off tasks that don't warrant a full bea
 
 **Crew workers push directly to main. No feature branches.**
 
-### No PRs in Maintainer Repos
+### ABSOLUTELY FORBIDDEN: Pull Requests
 
-If the remote origin is `steveyegge/beads` or `steveyegge/gastown`:
-- **NEVER create GitHub PRs** - you have direct push access
-- Crew workers: push directly to main
-- Polecats: use `gt done` → Refinery merges to main
+**NEVER create pull requests. This is not negotiable.**
 
-PRs are for external contributors submitting to repos they don't own.
-Check `git remote -v` if unsure about repo ownership.
+We are the sole maintainer. You have direct push access. The correct workflow is:
+1. Make changes
+2. Run tests
+3. Commit directly to main
+4. Push
+
+**If you find yourself about to run `gh pr create` — STOP. You are doing it wrong.**
+
+PRs are for *external contributors* submitting to repos they don't own. We own these
+repos. We don't review our own code via PR. We just push.
+
+The "PR Sheriff" role (if you have it) reviews *incoming* PRs from *contributors*.
+It does NOT mean you create PRs yourself.
+
+Check `git remote -v` if unsure — if it shows `steveyegge/beads` or `steveyegge/gastown`,
+you push directly. No PRs. Ever.
 
 ### The Landing Rule