Skip to content

v0.9.0 execution board: lane order, dependencies, and agent protocol (canonical packet) #4092

Description

@Hmbown

v0.8.68 execution board (canonical agent packet)

This is the single entry point for any agent working the v0.8.68 milestone. It replaces the July 7 triage packet (preserved in this issue's edit history). Every open milestone issue now carries exactly one lane-* label, so lanes are queryable directly.

Ground rules (read before touching code)

  1. main is the implementation source of truth. Branch every fix from main as codex/v0868-fix-<issue>. PR 0.8.68 train: workflow correctness, TUI stability, modes & permissions, security hardening #4099 (quick-win cutover) is already merged.
  2. codex/0868-next is a stale reference only. Never develop on it. Cherry-pick a specific commit from it only when an issue explicitly needs one.
  3. Defer v0.8.69 refactors unless they directly unblock a stopship issue (v0.9.0 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).
  4. Guard issue v0.9.0 guard: preserve verified active modules and DEEPSEEK env names #4172 applies to every lane: preserve verified active modules and DEEPSEEK* env var names. Check it before deleting or renaming anything.
  5. Do not push to main, tag, release, force-push, or close issues without explicit approval. Close issues only after the fixing PR is merged (Fixes #N in the PR body).
  6. Preserve contributor credit on harvested work (Co-authored-by for humans only, per .github/AUTHOR_MAP; note agent assistance in plain commit body).
  7. Run the verification gate before opening any PR (commands at the bottom).

How to pick work (agent protocol)

  1. Query ready work: gh issue list -R Hmbown/CodeWhale --label agent-ready --state open — optionally add your lane label, e.g. --label lane-catalog.
  2. agent-ready means unblocked now. Issues without it are blocked on a start condition (see lane table) — do not start them.
  3. When you start an issue: gh issue edit <N> --add-label agent-in-progress --remove-label agent-ready. One issue per agent at a time; skip anything already agent-in-progress.
  4. Work the lane checklists below top to bottom — the order encodes dependencies.
  5. Open a PR per issue (or per small coherent batch within one lane), referencing Fixes #<N>.
  6. When you stop, comment on this issue with: branch, HEAD, issues touched, tests run, anything left local-only.

Lanes

Lane Label Start condition Workflow file
Stopship lane-stopship Active now (agents in flight — do not double-assign) workflows/v0868_stopship_lane.workflow.js
Catalog / Models.dev lane-catalog Ready now — file-disjoint from stopship workflows/v0868_catalog_lane.workflow.js
Transcript copy polish lane-copy Ready now — copy/strings; scout transcript/sidebar overlap with #4094 first workflows/v0868_tui_copy_lane.workflow.js
Fleet / AgentProfile lane-fleet After #4093 merges (same Fleet setup surface) per-issue workflow
Workflow runtime + UI lane-workflow After stopship green (overlaps #4094 surfaces) workflows/v0868_workflow_ui_lane.workflow.js
Turn Inspector lane-inspector After #4094 merges (shares ui.rs/detail panel code) per-issue workflow
Performance lane-perf After stopship green (mechanical edits across hot paths — rebase hazard) per-issue workflow
Setup / onboarding lane-setup After stopship green per-issue workflow
Meta / guards lane-meta Always in effect

When a lane's start condition is met, promote its issues by adding agent-ready (top-of-checklist first).

Lane order and dependencies

Stopship (lane-stopship) — ACTIVE, agents already assigned

Catalog / Models.dev (lane-catalog) — ready now, work in this order

Foundation (Models.dev as source of truth, umbrella #4184):

Picker wiring (after #4187):

Plumbing and closeout:

Transcript copy polish (lane-copy) — ready now, work in this order

Items marked ⚠ touch transcript/sidebar rendering — check the open #4094 PR before starting; rebase after it merges.

Fleet / AgentProfile (lane-fleet) — start after #4093 merges

Workflow runtime + UI (lane-workflow) — start after stopship green

Architecture phases first (canonical tracker #4175 — Fleet=WHO, Workflow=WHAT ORDER, Lane=INSTANCE, Runtime=WHERE):

Then UI/eventing (umbrellas #4110, #4038):

Turn Inspector (lane-inspector) — start after #4094 merges

Performance (lane-perf) — start after stopship green; mechanical, one PR per issue

Setup / onboarding (lane-setup) — start after stopship green

PR harvest lane (parallel to all waves — review, don't reimplement)

PR Issue Notes
#4088 #4026 Mergeable; terminal selection highlight — review Windows CI hunks, then merge
#4087 #4082 Draft refactor; finish review
#4084 #4065 Draft Fleet alias cleanup; land before/with lane-fleet
#3761 #3757 Conflicting; harvest/cherry-pick for the lane-perf startup issue
#3969 #3965 Conflicting; align with #4065 + lane-fleet contract first — do not brute-force merge

Verification gate (run before every PR)

cargo fmt --all --check
cargo clippy --workspace --all-features --locked -D warnings \
  -A clippy::uninlined_format_args -A clippy::too_many_arguments \
  -A clippy::unnecessary_map_or -A clippy::collapsible_if -A clippy::assertions_on_constants
cargo test --workspace --locked
cargo build --release -p codewhale-tui

Full playbook: docs/AGENT_WORKFLOWS_0868.md. Architecture vocabulary: #4175. Guard: #4172.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationlane-metareliabilityReliability, flaky behavior, retries, fallbacks, and robustnesssubagentsSub-agent orchestration, lifecycle, and completion handlingtuiTerminal UI behavior, rendering, or interactionv0.9.0Targeting v0.9.0workflow-runtimeWorkflow IR, executor, control flow, and replay runtime

    Projects

    Status
    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions