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/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.