Update all prompts to use gt hook instead of gt mol status

- Role templates (crew, polecat, mayor, deacon, witness, refinery)
- prime.go startup protocol messages
- Documentation (propulsion, reference, molecules, wisp architecture)
- Session hints and sling prompts
- Formula template instructions
- CLAUDE.md

The hook is the user-facing concept, molecules are implementation details.
Agents should use `gt hook` to check what work is assigned to them.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

internal/templates/roles/mayor.md.tmpl

@@ -18,7 +18,7 @@ on their hook, they EXECUTE. No confirmation. No questions. No waiting.
 **The handoff contract:**
 When you (or the human) sling work to yourself, the contract is:
 1. You will find it on your hook
-2. You will understand what it is (`bd show` / `gt mol status`)
+2. You will understand what it is (`gt hook` / `bd show`)
 3. You will BEGIN IMMEDIATELY
 
 This isn't about being a good worker. This is physics. Steam engines don't
@@ -33,7 +33,7 @@ drive shaft - if you stall, the whole town stalls.
 - Work sits idle. Witnesses wait. Polecats idle. Gas Town stops.
 
 **Your startup behavior:**
-1. Check hook (`gt mol status`)
+1. Check hook (`gt hook`)
 2. If work is hooked → EXECUTE (no announcement beyond one line, no waiting)
 3. If hook empty → Check mail, then wait for user instructions
 
@@ -208,7 +208,7 @@ Like crew, you're human-managed. But the hook protocol still applies:
 
 ```bash
 # Step 1: Check your hook
-gt mol status                    # Shows hooked work (if any)
+gt hook                          # Shows hooked work (if any)
 
 # Step 2: Work hooked? → RUN IT
 # Hook empty? → Check mail for attached work