v0.8.68: Stopship workflow as fleet-backed lane (dogfood #4090/#4093/#4094)

[Hmbown]

Parent: #4175

Purpose

End-to-end dogfood of the Fleet/Workflow/Lane/Runtime model against active stopship issues. This is the concrete reference lane — not a new priority above #4090, #4093, #4094.

Target invocation

codewhale workflow run stopship \
  --issue 4090 \
  --fleet v0868-stopship \
  --runtime tmux

codewhale lane list
codewhale lane attach <lane-id>
codewhale lane logs <lane-id>

Fleet: v0868-stopship

Named roster binding roles → AgentProfiles (configured under CODEWHALE_HOME):

Role	Profile intent
scout	Read-only recon on issue + codebase
implementer	Minimal fix branch from main
reviewer	Diff review, regression focus
verifier	cargo test, clippy, fmt gate
release_lead	Stopship checklist + PR draft

Fleet resolves roles only — does not spawn tmux or manage worktrees.

Workflow: stopship

Role-sequenced workflow (see #4177) covering #4090, #4093, #4094 with gates (#4179):

1. scout ×3 (parallel read-only scouts per issue)
2. implementer (sequential fixes, separate branches)
3. reviewer + verifier gates before PR
4. release_lead handoff artifact for v0.8.68 execution board: lane order, dependencies, and agent protocol (canonical packet) #4092

Update workflows/v0868_stopship_lane.workflow.js after Phase 2 lands.

Runtime: tmux

• One lane per stopship batch (or per issue — configurable)
• stream-json logs under lane registry
• worktree per implementer branch
• attach for human oversight

Acceptance criteria

• v0868-stopship fleet file exists and resolves all five roles.
• stopship workflow runs via CLI with --fleet and --runtime tmux.
• Lane registry shows running/completed stopship lanes with issue bindings.
• Dogfood run produces PR-ready branches for v0.8.68 TUI: repeated Ctrl+C re-prompts instead of exiting in PTY/raw-mode path #4090/Fleet setup modal is provider-scoped instead of a role/profile roster editor #4093/Sub-agent detail panel is empty and can freeze the TUI during active work #4094 without manual tmux wiring.
• Does not close v0.8.68 TUI: repeated Ctrl+C re-prompts instead of exiting in PTY/raw-mode path #4090/Fleet setup modal is provider-scoped instead of a role/profile roster editor #4093/Sub-agent detail panel is empty and can freeze the TUI during active work #4094 until human-verified on main.

Related

• v0.8.68 TUI: repeated Ctrl+C re-prompts instead of exiting in PTY/raw-mode path #4090, Fleet setup modal is provider-scoped instead of a role/profile roster editor #4093, Sub-agent detail panel is empty and can freeze the TUI during active work #4094 — Active stopship (priority unchanged)
• v0.8.68 Phase 1: Lane CLI + Runtime backends (tmux, worktrees, stream-json logs) #4176 — Phase 1: Lane CLI + Runtime
• v0.8.68 Phase 2: Workflow steps reference Fleet roles (not raw prompts/profiles) #4177 — Phase 2: Workflow role resolution
• v0.8.68 Phase 3: Workflow gates and handoffs between Fleet roles #4179 — Phase 3: Gates + handoffs
• feat(workflows): v0.8.68 agent execution lanes and milestone sync #4163, docs/AGENT_WORKFLOWS_0868.md — Current playbook (migrate to new CLI)
• v0.8.68 execution board: lane order, dependencies, and agent protocol (canonical packet) #4092 — Triage handoff notes