docs: update templates with molecule navigation workflow (gt-lz13)

- Add bd mol current for orientation in polecat, crew, refinery, deacon
- Replace 3-command dance with bd close --continue (Propulsion Principle)
- Witness template unchanged (monitor role, no molecule execution)

prompts/roles/crew.md

@@ -146,18 +146,20 @@ This enables **overnight autonomous work** on long molecules.
 ### Working on Attached Molecules
 
 ```bash
-# Check what's attached
+# Check what's attached and see current step
 gt mol status
+bd mol current
 
-# Find next ready step in the attached work
-bd ready --parent=<work-mol-root>
-
-# Work the step
-bd update <step> --status=in_progress
+# Work the step (current step shown by bd mol current)
 # ... do the work ...
-bd close <step>
+
+# Close and auto-advance to next step
+bd close <step> --continue
 ```
 
+The `--continue` flag closes your step and automatically marks the next ready step
+as in_progress. This is the **Propulsion Principle** - seamless step transitions.
+
 ### Attaching Work (for the overseer)
 
 To enable autonomous work, attach a molecule:

prompts/roles/deacon.md

@@ -41,17 +41,17 @@ Your work is defined by the `mol-deacon-patrol` molecule with these steps:
               v
 ┌─────────────────────────────────────────┐
 │ 2. Execute current step                 │
-│    - Read step description              │
+│    - bd mol current (see your step)     │
 │    - Perform the work                   │
-│    - bd close <step-id>                 │
+│    - bd close <step-id> --continue      │
 └─────────────────────────────────────────┘
               │
               v
 ┌─────────────────────────────────────────┐
 │ 3. Next step?                           │
-│    - bd ready                           │
+│    - --continue auto-advances you       │
 │    - If more steps: go to 2             │
-│    - If done: go to 4                   │
+│    - If molecule done: go to 4          │
 └─────────────────────────────────────────┘
               │
               v

prompts/roles/polecat.md

@@ -30,25 +30,25 @@ steps and exit conditions. The molecule is your contract:
 
 Your molecule is attached to your handoff bead:
 ```bash
-# Find your pinned assignment
+# See your current molecule and step at a glance
+bd mol current
+
+# Or manually find your assignment
 bd list --pinned --assignee=$BEADS_AGENT_NAME
-
-# View your molecule and its steps
 bd show <mol-id>
-
-# Find your current step (first in_progress or next unblocked)
-bd ready --parent=<mol-id>
 ```
 
 ### Working Through Steps
 
 Steps have dependencies (`Needs: step1, step2`). Work in order:
 
-1. Find the next ready step: `bd ready --parent=<mol-id>`
-2. Mark it in_progress: `bd update <step-id> --status=in_progress`
-3. Do the work
-4. Mark complete: `bd close <step-id>`
-5. Repeat until exit-decision step
+1. Check your current step: `bd mol current`
+2. Do the work
+3. Close and auto-advance: `bd close <step-id> --continue`
+4. Repeat until exit-decision step
+
+The `--continue` flag closes your step and automatically marks the next ready step
+as in_progress. No friction, no forgetting. This is the **Propulsion Principle**.
 
 ### Exit Strategies
 

prompts/roles/refinery.md

@@ -73,9 +73,9 @@ GATE: Cannot proceed to merge without fix OR bead filed
               v
 ┌─────────────────────────────────────────┐
 │ 2. Execute current step                 │
-│    - Read step description              │
+│    - bd mol current (see your step)     │
 │    - Perform the work                   │
-│    - bd close <step-id>                 │
+│    - bd close <step-id> --continue      │
 └─────────────────────────────────────────┘
               │
               v