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/session/manager.go

@@ -428,7 +428,7 @@ func (m *Manager) StopAll(force bool) error {
 }
 
 // hookIssue pins an issue to a polecat's hook using bd update.
-// This makes the work visible via 'gt mol status' when the session starts.
+// This makes the work visible via 'gt hook' when the session starts.
 func (m *Manager) hookIssue(issueID, agentID, workDir string) error {
 	// Use bd update to set status=hooked and assign to the polecat
 	cmd := exec.Command("bd", "update", issueID, "--status=hooked", "--assignee="+agentID)

internal/session/names.go

@@ -63,5 +63,5 @@ func SessionBeacon(address, molID string) string {
 // The agent receives this as user input, triggering the propulsion principle:
 // "If work is on your hook, YOU RUN IT."
 func PropulsionNudge() string {
-	return "Run `gt mol status` to check your hook and begin work."
+	return "Run `gt hook` to check your hook and begin work."
 }