feat(prime): Add crew auto-continue for attached work (gt-9g82)

Updates crew worker startup to detect and auto-continue attached molecules:

- prime.go: Add outputCrewAttachmentStatus() that detects pinned beads
  with attached molecules and outputs "AUTO-CONTINUE MODE" directive
- prime.go: Update startup directive to explain the auto-continue pattern
- crew.md: Add "Session Wisp Model" section documenting autonomous work

Key insight: if attached work exists, continue without awaiting input.
This enables overnight autonomous work on long molecules.

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

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

internal/cmd/prime.go

@@ -92,6 +92,9 @@ func runPrime(cmd *cobra.Command, args []string) error {
 	// Output handoff content if present
 	outputHandoffContent(ctx)
 
+	// Output crew attachment status (for autonomous work detection)
+	outputCrewAttachmentStatus(ctx)
+
 	// Output molecule context if working on a molecule step
 	outputMoleculeContext(ctx)
 
@@ -452,7 +455,9 @@ func outputStartupDirective(ctx RoleContext) {
 		fmt.Printf("1. Announce: \"%s Crew %s, checking in.\"\n", ctx.Rig, ctx.Polecat)
 		fmt.Println("2. Check mail: `gt mail inbox`")
 		fmt.Println("3. If there's a 🤝 HANDOFF message, read it and continue the work")
-		fmt.Println("4. If no mail, await user instruction")
+		fmt.Println("4. Check for attached work: `gt mol status`")
+		fmt.Println("   - If attachment found → **AUTO-CONTINUE** (no human input needed)")
+		fmt.Println("   - If no attachment → await user instruction")
 	case RoleDeacon:
 		fmt.Println()
 		fmt.Println("---")
@@ -492,6 +497,50 @@ func runMailCheckInject(workDir string) {
 	}
 }
 
+// outputCrewAttachmentStatus checks for attached work molecule and outputs status.
+// This is key for the autonomous overnight work pattern.
+func outputCrewAttachmentStatus(ctx RoleContext) {
+	if ctx.Role != RoleCrew {
+		return
+	}
+
+	// Check for pinned beads with attachments
+	b := beads.New(ctx.WorkDir)
+
+	// Build assignee string for crew worker
+	assignee := fmt.Sprintf("%s/crew/%s", ctx.Rig, ctx.Polecat)
+
+	// Find pinned beads for this agent
+	pinnedBeads, err := b.List(beads.ListOptions{
+		Status:   beads.StatusPinned,
+		Assignee: assignee,
+		Priority: -1,
+	})
+	if err != nil || len(pinnedBeads) == 0 {
+		// No pinned beads - interactive mode
+		return
+	}
+
+	// Check first pinned bead for attachment
+	attachment := beads.ParseAttachmentFields(pinnedBeads[0])
+	if attachment == nil || attachment.AttachedMolecule == "" {
+		// No attachment - interactive mode
+		return
+	}
+
+	// Has attached work - output prominently
+	fmt.Println()
+	fmt.Printf("%s\n\n", style.Bold.Render("## 🎯 ATTACHED WORK DETECTED"))
+	fmt.Printf("Pinned bead: %s\n", pinnedBeads[0].ID)
+	fmt.Printf("Attached molecule: %s\n", attachment.AttachedMolecule)
+	if attachment.AttachedAt != "" {
+		fmt.Printf("Attached at: %s\n", attachment.AttachedAt)
+	}
+	fmt.Println()
+	fmt.Println(style.Bold.Render("→ AUTO-CONTINUE MODE: Proceed with attached work immediately."))
+	fmt.Println("  No human input needed. Continue from where predecessor left off.")
+}
+
 // outputMoleculeContext checks if the agent is working on a molecule step and shows progress.
 func outputMoleculeContext(ctx RoleContext) {
 	// Applies to polecats, crew workers, and deacon

prompts/roles/crew.md

@@ -142,6 +142,51 @@ Without beads, track your work through:
 - Direct communication with the overseer
 {{ /unless }}
 
+## Session Wisp Model (Autonomous Work)
+
+Crew workers use a **session wisp** pattern for long-running molecules:
+
+### The Auto-Continue Pattern
+
+When you start a session:
+1. Check for attached work: `gt mol status`
+2. **If attachment found** → Continue immediately (no human input needed)
+3. **If no attachment** → Await user instruction
+
+This enables **overnight autonomous work** on long molecules.
+
+### Working on Attached Molecules
+
+```bash
+# Check what's attached
+gt mol status
+
+# Find next ready step in the attached work
+bd ready --parent=<work-mol-root>
+
+# Work the step
+bd update <step> --status=in_progress
+# ... do the work ...
+bd close <step>
+```
+
+### Attaching Work (for the overseer)
+
+To enable autonomous work, attach a molecule:
+
+```bash
+# Find or create a work issue
+bd create --type=epic --title="Long feature work"
+
+# Pin it to the crew worker
+bd update <issue-id> --assignee={{ rig }}/crew/{{ name }} --pinned
+
+# Attach the molecule
+gt mol attach <issue-id> mol-engineer-in-box
+```
+
+Now the crew worker will continue this work across sessions.
+
 ## Session End Checklist
 
 Before ending your session:
@@ -152,7 +197,7 @@ Before ending your session:
 [ ] 3. bd sync                 (sync beads if configured)
 [ ] 4. Check inbox             (any messages needing response?)
 [ ] 5. HANDOFF if incomplete:
-        gt mail send {{ rig }}/{{ name }} -s "HANDOFF: ..." -m "..."
+        gt mail send {{ rig }}/{{ name }} -s "🤝 HANDOFF: ..." -m "..."
 ```
 
 ## Tips