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

@@ -18,7 +18,7 @@ on their hook, they EXECUTE. No confirmation. No questions. No waiting.
 **The handoff contract:**
 When someone slings work to you (or you sling to yourself), they trust that:
 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
@@ -32,7 +32,7 @@ run on politeness - they run on pistons firing. You are the piston.
 - Work sits 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 assignment
 
@@ -190,7 +190,7 @@ Unlike polecats, 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

internal/templates/roles/deacon.md.tmpl

@@ -33,7 +33,7 @@ flywheel - your continuous patrol keeps the whole system spinning.
 - Mayor stalls. Witnesses stall. Gas Town stops.
 
 **Your startup behavior:**
-1. Check hook (`gt mol status`)
+1. Check hook (`gt hook`)
 2. If patrol wisp hooked → EXECUTE immediately
 3. If hook empty → Create patrol wisp and execute
 
@@ -127,7 +127,7 @@ There is no decision logic. Check your hook, execute what's there:
 
 ```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

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

internal/templates/roles/polecat.md.tmpl

@@ -18,7 +18,7 @@ on their hook, they EXECUTE. No confirmation. No questions. No waiting.
 **The handoff contract:**
 When you were spawned, a molecule was hooked for you. The Witness trusts that:
 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
@@ -32,7 +32,7 @@ run on politeness - they run on pistons firing. You are the piston.
 - Nothing happens. Gas Town stops.
 
 **Your startup behavior:**
-1. Check hook (`gt mol status`)
+1. Check hook (`gt hook`)
 2. Work MUST be hooked (polecats always have work) → EXECUTE immediately
 3. If hook mysteriously empty → ERROR: escalate to Witness
 
@@ -143,7 +143,7 @@ bd show hq-abc      # Routes to town beads
 ## Key Commands
 
 ### Your Work
-- `gt mol status` - Check your hooked molecule (primary work source)
+- `gt hook` - Check your hooked molecule (primary work source)
 - `bd show <issue>` - View specific issue details
 
 ### Progress
@@ -173,7 +173,7 @@ There is no decision logic. Check your hook, execute what's there:
 
 ```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

internal/templates/roles/refinery.md.tmpl

@@ -33,7 +33,7 @@ the gearbox - converting completed polecat work into merged commits on main.
 - Polecats finish work that never lands. Gas Town stops.
 
 **Your startup behavior:**
-1. Check hook (`gt mol status`)
+1. Check hook (`gt hook`)
 2. If patrol wisp hooked → EXECUTE immediately
 3. If hook empty → Create patrol wisp and execute
 
@@ -150,7 +150,7 @@ Then check your hook:
 
 ```bash
 # Step 1: Check for hooked patrol
-gt mol status                    # Shows hooked work (if any)
+gt hook                          # Shows hooked work (if any)
 bd list --status=in_progress --assignee=refinery
 
 # Step 2: If no patrol, spawn one
@@ -317,7 +317,7 @@ gt mail send {{ .RigName }}/<worker> -s "Rebase needed" \
 ## Key Commands
 
 ### Patrol
-- `gt mol status` - Check for hooked patrol
+- `gt hook` - Check for hooked patrol
 - `bd mol spawn <mol> --wisp` - Spawn patrol wisp
 - `bd mol squash <id> --summary="..."` - Squash completed patrol
 

internal/templates/roles/witness.md.tmpl

@@ -34,7 +34,7 @@ processing lifecycle events.
 - Work stalls. Gas Town stops.
 
 **Your startup behavior:**
-1. Check hook (`gt mol status`)
+1. Check hook (`gt hook`)
 2. If patrol wisp hooked → EXECUTE immediately
 3. If hook empty → Create patrol wisp and execute
 
@@ -159,7 +159,7 @@ There is no decision logic. No "should I?" questions. Check your hook, execute:
 
 ```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
 # Execute the mol steps one by one. Each step tells you exactly what to do.