fix: allow away supervisors to relaunch in-flight tasks by peterOC26 · Pull Request #27 · peterOC26/firstmate

peterOC26 · 2026-10-05T08:41:48Z

Intent

"q294y", answering this question: "Y = start a small firstmate fix job for this: the second check accepts relaunches, with a test, opened as a PR to your firstmate copy for your merge".

Earlier, on the problem: "can this be fixed?", about this report: while the captain was away with the words "you can move to other stages", a job's finished plan waited about 6.5 hours because the away supervisor could not restart the job for its next stage (the plan review on another model); on 2026-10-02 the same refusal cost about 2 hours.

Context the ask refers to. Moving a job to its next stage is bin/fm-control.sh <id> relaunch, which re-enters bin/fm-spawn.sh with RELAUNCH=1. bin/fm-spawn.sh has two away-posture checks for the supervision branch actor: spawn_require_relocated_queued_work (around line 1571) returns early for a relaunch, but the later backlog preflight (around line 3492, if [ "$spawn_preflight_actor" = branch ] && fm_lease_away_relocated; then if [ "$BACKLOG_ROW_STATE" != "queued no no" ]) has no relaunch exemption, and a relaunched task's backlog item is always In flight, so every away relaunch is refused with "spawn refused - the supervision branch under the away-posture record may dispatch only queued unblocked work ...". Evidence: state/branch-outcomes.jsonl seq 2654, 2663 and 3037; fleet issue https://github.com/peterOC26/fleet/issues/221.

What Changed

Exempt relaunches from the away supervisor’s queued-only backlog preflight so existing In-flight tasks can continue to their next stage.
Add regression coverage for relaunching at the spend cap while preserving task identity, rejecting fresh In-flight spawns, and rejecting held relaunches.
Document the separate fresh-spawn and relaunch rules and link the AFK skill to the authority contract.

Risk Assessment

✅ Low: The change only adds a relaunch exemption to the second away-posture check, matching the exemptions every other away check already has (lines 1535, 1540, 1573); relaunches still go through the general dispatchable-state check (fm_backlog_row_dispatchable accepts only in_flight no no / queued no no), so held or blocked items are still refused, branch relaunches must still go through fm-control's control lock, and fresh away spawns keep the queued-only rule.

Testing

The broader test-file attempt hit a fixture-location restriction; focused checks passed and the base reproduced the bug. After correcting lab setup, all three real Codex/tmux scenarios passed. CLI evidence was saved and disposable resources were removed.

Live validation: ✅ go - 3 of 3 scenarios driven live against the product

Scenario	Result	Live	Evidence
Away supervisor relaunches an existing In-flight worker at the spend cap while preserving its work	✅ pass	live	live-away-relaunch.log: successful relaunch, phase=complete, preserved endpoint, working copy, unfinished file, HEAD, and In-flight row; worker-after-response.txt
Fresh away dispatch refuses an In-flight item without creating a worker	✅ pass	live	live-away-relaunch.log: queued-work refusal, unchanged endpoint inventory and backlog row, no new task record
Away relaunch refuses a captain-held In-flight item	✅ pass	live	live-away-relaunch.log: refusal for state in_flight yes no, preserved task record and unfinished work

Evidence: Live relaunch, guard refusals, persisted records, and cleanup

Source: Live relaunch, guard refusals, persisted records, and cleanup

$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-lab-home.sh create ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y
~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y

exit=0
$ tmux -L fm-lab new-session -d -x 120 -y 40 -s primary -c ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY -e FM_HOME=~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y 'codex --disable hooks --dangerously-bypass-approvals-and-sandbox'

exit=0
$ tmux -L fm-lab display-message -p -t primary '#{socket_path},#{pid},0'
~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/tmux/tmux-1000/fm-lab,2731655,0

exit=0
$ tmux -L fm-lab capture-pane -p -t primary -S -80

  >_ OpenAI Codex (v0.160.0)
     ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY
  permissions: YOLO mode

  Shall we turn “what if” into something?





                                                       ⣀⣤⣤⣤⣀⣀
                                                    ⣠⣶⣿⣿⣿⣿⣿⣿⣿⣿⣦⣤⣤⣤⣤⣤⣤⡀
                                                  ⢀⣾⣿⣿⠿⠋⠉⠉⢉⣭⣿⣿⣿⣿⣿⠿⣿⣿⣿⣿⣷⣄
                                                 ⣀⣾⣿⣿⠃ ⣀⣴⣾⣿⣿⡿⠟⠋ ⣀⡀ ⠈⠙⢿⣿⣿⣧
                                              ⣀⣶⣿⣿⣿⣿⡇ ⢸⣿⣿⡿⠛⠉⢀⣠⣴⣿⣿⣿⣷⣦⣀⠈⢻⣿⣿⡇
                                             ⣰⣿⣿⡿⢿⣿⣿⡇ ⢸⣿⣿⢀⣤⣶⣿⣿⣿⠟⠛⠻⣿⣿⣿⣿⣮⣿⣿⡷
                                            ⢰⣿⣿⡟⠁⢸⣿⣿⡇ ⢸⣿⣿⣿⣿⠿⠿⣿⣿⣿⣦⣄⡀⠈⠛⠿⣿⣿⣿⣧⡀
                                            ⣾⣿⣿⠃ ⢸⣿⣿⡇ ⢸⣿⣿⠋⠁  ⠈⠙⢻⣿⣿⣿⣶⣤⡀ ⠹⢿⣿⣷⡄
                                            ⢸⣿⣿⣇ ⠸⣿⣿⣷⣦⣼⣿⣿      ⢸⣿⣿⠻⢿⣿⣿⡇ ⠘⣿⣿⣿
                                            ⠈⢿⣿⣿⣦⡀⠈⠛⠿⣿⣿⣿⣿⣄⡀  ⢀⣠⣼⣿⣿  ⣿⣿⡇  ⣿⣿⣿⠇
                                              ⢻⣿⣿⣿⣷⣦⣀⠈⠙⠻⣿⣿⣿⣶⣶⣿⣿⣿⣿⣿  ⣿⣿⡇ ⣠⣿⣿⣿
                                              ⢸⣿⣿⡿⢿⣿⣿⣿⣦⣠⣴⣿⣿⣿⡿⠟⠋⢸⣿⣿  ⣿⣿⣷⣴⣿⣿⣿⠃
                                              ⠘⣿⣿⣷ ⠈⠛⢿⣿⣿⣿⠿⠋⠉ ⣠⣴⣿⣿⣿  ⣿⣿⣿⣿⣿⠟⠁
                                               ⠻⣿⣿⣿⣤⣀ ⠈⠉ ⢀⣤⣶⣿⣿⣿⠿⠟⠁ ⣰⣿⣿⡟⠋⠁
                                                ⠈⠿⣿⣿⣿⣿⣶⣾⣿⣿⣿⣿⠟⠋⠁  ⣠⣼⣿⣿⡟
                                                   ⠙⠛⠛⠛⠻⠛⢿⣿⣿⣿⣿⣷⣾⣿⣿⣿⡿⠏
                                                          ⠈⠙⠛⠿⠿⠿⠿⠛⠉








› Ask Codex to do anything

  GPT-6.1-Sol low · ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY
  ? for shortcuts                                                                              ⚠ 1 warning · f2 to view

exit=0
$ git init -q ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/project

exit=0
$ git -C ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/project add seed.txt

exit=0
$ git -C ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/project -c 'user.name=Live Test' -c user.email=live-test@example.invalid commit -qm fixture

exit=0
$ git -C ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/project worktree add -qb fixture-worker ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh add awayfresh 'fresh In-flight row' --kind ship
ok: added awayfresh (ship) -> Queued
task:
  id: awayfresh
  title: fresh In-flight row
  state: queued
  blocked: no
  blocked_by: none
  held: no
  hold_reason: "-"
  hold_kind: "-"
  hold_until: "-"
  kind: ship
  repo: "-"
  priority: "-"
  created: 2026-10-05
  closed: "-"
  deps: none
  links: none
  body: ""
help[2]:
  - Run `tasks-axi start awayfresh` to move it to in flight
  - Run `tasks-axi block awayfresh --by <other>` to record a dependency

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh start awayfresh
ok: start awayfresh -> In flight
help[1]:
  - Run `tasks-axi done awayfresh --pr <url>` when it ships

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-afk-contract.sh enter --spend 1 --words 'you can move to other stages'
Away posture recorded at 2026-10-05T08:35:34Z: hold-for-return only. No phone channel is configured; anything that needs you waits for your return. Your away instructions are recorded verbatim; the away session will carry them out where it can, and anything it is unsure of, or that needs you, waits for your return. Destructive, irreversible, and security-sensitive actions are never pre-authorizable, whatever the words say. Expected return: not given. Spend cap: 1 concurrent workers.
Away posture (recorded):
  entered: 2026-10-05T08:35:34Z
  expected return: not given
  spend cap: 1 concurrent workers
  reach: hold-for-return only. No phone channel is configured; anything that needs you waits for your return.
  your words (verbatim):
    you can move to other stages

exit=0
$ tmux -L fm-lab list-windows -t primary -F '#{window_id}:#{window_name}'
@0:node

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-spawn.sh awayfresh ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/project --harness codex --mode no-mistakes --yolo off
fm-gate-refuse: gate agent lifecycle permitted only against lab home ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y
note: new-task spawn (fm-spawn) proceeds for the supervision branch under the away-posture record: main is parked and its standing authority is relocated; this script's own gate still applies (docs/pi-supervision-branch.md "Postures")
note: new-task spawn (fm-spawn) proceeds for the supervision branch under the away-posture record: main is parked and its standing authority is relocated; this script's own gate still applies (docs/pi-supervision-branch.md "Postures")
error: spawn refused - the supervision branch under the away-posture record may dispatch only queued unblocked work (already queued, or filed by the branch from the captain's away words); task awayfresh has no dispatchable backlog item in this home

exit=1
$ tmux -L fm-lab list-windows -t primary -F '#{window_id}:#{window_name}'
@0:node

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh show awayfresh
task:
  id: awayfresh
  title: fresh In-flight row
  state: in_flight
  blocked: no
  blocked_by: none
  held: no
  hold_reason: "-"
  hold_kind: "-"
  hold_until: "-"
  kind: ship
  repo: "-"
  priority: "-"
  created: 2026-10-05
  closed: "-"
  deps: none
  links: none
  body: ""

exit=0
SCENARIO {"name": "Fresh away dispatch refuses an In-flight row without creating a worker", "result": "pass", "live": true, "detail": "Queue-only refusal, unchanged endpoint inventory and In-flight row"}
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh add awaylive-p44zn0_y 'existing stage worker' --kind ship
ok: added awaylive-p44zn0_y (ship) -> Queued
task:
  id: awaylive-p44zn0_y
  title: existing stage worker
  state: queued
  blocked: no
  blocked_by: none
  held: no
  hold_reason: "-"
  hold_kind: "-"
  hold_until: "-"
  kind: ship
  repo: "-"
  priority: "-"
  created: 2026-10-05
  closed: "-"
  deps: none
  links: none
  body: ""
help[2]:
  - Run `tasks-axi start awaylive-p44zn0_y` to move it to in flight
  - Ru

... [8305 bytes truncated] ...

worker\n"}
$ tmux -L fm-lab capture-pane -p -t primary:fm-awaylive-p44zn0_y -S -80

  ## Progress note (2026-10-05T08:35:48Z)

  This task was relaunched. Continue from here; the local copy and every
  uncommitted change are exactly as the previous worker left them.

  First, check your instruction inbox: list ~/.no-mistakes/
  worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/state/awaylive-p44zn0_y.inbox/*.msg, act on
  each message in numeric order, then mv each handled file into
  ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/state/awaylive-p44zn0_y.inbox/
  handled/. A steer sent before the relaunch survives there.

  Continue the next stage by replying exactly AFTER_AWAY_RELAUNCH. Do not call tools or change files.

  # Current no-mistakes intent contract
  This section supersedes every earlier brief instruction about constructing `--intent`, but not later clarifications
  actually supplied by the captain.
  Use everything under `## Captain intent authorized for --intent` through the end of this brief, including any nested
  subheadings but excluding that heading, plus any later words the captain actually supplied as `--intent`; never
  include Firstmate specification or other mixed Task content.
  Preserve those words without adding speaker labels or direct address.
  Firstmate-authored constraints, acceptance criteria, implementation details, decisions, and tradeoffs are
  specification, not captain intent.
  The Definition of done's rule that `--intent` must be self-sufficient still governs the string you pass: resolve any
  report, decision, or PR the intent below refers to into its substance rather than passing the pointer.

  ## Captain intent authorized for --intent
  Reply exactly AFTER_AWAY_RELAUNCH and wait for further input. Do not edit any files, run tools, start validation, or
  create a PR.


• AFTER_AWAY_RELAUNCH

  Worked for 3s • 10:36


› Ask Codex to do anything

  GPT-6.1-Sol low · ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker · ⠧
  ? for shortcuts                                                                              ⚠ 1 warning · f2 to view

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh hold awaylive-p44zn0_y --reason 'decision pending' --kind captain
ok: hold awaylive-p44zn0_y -> held (captain)
task:
  id: awaylive-p44zn0_y
  title: existing stage worker
  state: in_flight
  blocked: no
  blocked_by: none
  held: yes
  hold_reason: decision pending
  hold_kind: captain
  hold_until: "-"
  kind: ship
  repo: "-"
  priority: "-"
  created: 2026-10-05
  closed: "-"
  deps: none
  links: none
  body: ""
help[2]:
  - Run `tasks-axi unhold awaylive-p44zn0_y` to resume dispatch
  - Run `tasks-axi ready --include-held` to review paused work

exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-control.sh awaylive-p44zn0_y relaunch --note 'Attempt the held next stage'
fm-gate-refuse: gate agent lifecycle permitted only against lab home ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y
fm-gate-refuse: gate agent lifecycle permitted only against lab home ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y
warning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/data/awaylive-p44zn0_y/launch-brief.md records no ship branch; defaulting to legacy branch fm/awaylive-p44zn0_y
warning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/data/awaylive-p44zn0_y/launch-brief.md records no delivery contract line (scaffolded before ship briefs recorded one); launching on the explicit --mode no-mistakes - confirm its definition of done matches
error: this home's backlog item awaylive-p44zn0_y is not dispatchable in state in_flight yes no; refusing before creating its endpoint or local copy
error: the replacement agent for awaylive-p44zn0_y could not be launched on codex
error: awaylive-p44zn0_y's agent was stopped but the replacement did not launch; no agent is running, and its work plus the recorded progress note are preserved at ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker

exit=1
$ tmux -L fm-lab capture-pane -p -t primary:fm-awaylive-p44zn0_y -S -80
bash-5.2$ codex --disable hooks --dangerously-bypass-approvals-and-sandbox 'Reply exactly BEFORE_AWAY_RELAUNCH and wait.
 Do not call any tools.'
WARNING: proceeding, even though we could not create PATH aliases: Refusing to create helper binaries under temporary di
r "~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y" (codex_home: AbsolutePathBuf("/
home/zabi/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/codex"))
Token usage: total=2,950 input=2,939 (+ 12,160 cached) output=11
To continue this session, run:
  codex resume 01a10b34-4947-7c23-aa1a-44a238015e7f
Or run codex resume and select Prepare away relaunch response.
bash-5.2$ cd -- '~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker'
bash-5.2$ export GOTMPDIR=/tmp/fm-awaylive-p44zn0_y/gotmp
bash-5.2$ export COMPACT_ADVISER_DISABLE=1
bash-5.2$ export FM_TASK_ID=awaylive-p44zn0_y
bash-5.2$ . '/tmp/fm-awaylive-p44zn0_y+4384d60aa32ca2d74eee4235bd2458f39cc3b683fd2386734f9990c7ecf369f3/launch.s17911893
55.2745179.8998.sh'
WARNING: proceeding, even though we could not create PATH aliases: Refusing to create helper binaries under temporary di
r "~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y" (codex_home: AbsolutePathBuf("/
home/zabi/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/codex"))
Token usage: total=3,725 input=3,714 (+ 12,160 cached) output=11
To continue this session, run:
  codex resume 01a10b34-9916-7003-8ecc-579d5c5dcc03
bash-5.2$



















exit=0
$ ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/bin/fm-tasks-axi.sh show awaylive-p44zn0_y
task:
  id: awaylive-p44zn0_y
  title: existing stage worker
  state: in_flight
  blocked: no
  blocked_by: none
  held: yes
  hold_reason: decision pending
  hold_kind: captain
  hold_until: "-"
  kind: ship
  repo: "-"
  priority: "-"
  created: 2026-10-05
  closed: "-"
  deps: none
  links: none
  body: ""

exit=0
SCENARIO {"name": "Away relaunch refuses a captain-held In-flight row", "result": "pass", "live": true, "detail": "fm-gate-refuse: gate agent lifecycle permitted only against lab home ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y\nfm-gate-refuse: gate agent lifecycle permitted only against lab home ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y\nwarning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/data/awaylive-p44zn0_y/launch-brief.md records no ship branch; defaulting to legacy branch fm/awaylive-p44zn0_y\nwarning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/data/awaylive-p44zn0_y/launch-brief.md records no delivery contract line (scaffolded before ship briefs recorded one); launching on the explicit --mode no-mistakes - confirm its definition of done matches\nerror: this home's backlog item awaylive-p44zn0_y is not dispatchable in state in_flight yes no; refusing before creating its endpoint or local copy\nerror: the replacement agent for awaylive-p44zn0_y could not be launched on codex\nerror: awaylive-p44zn0_y's agent was stopped but the replacement did not launch; no agent is running, and its work plus the recorded progress note are preserved at ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker\n"}
$ tmux -L fm-lab kill-server

exit=0
Cleanup correction: product-created hook directories are read-only. Restored owner write access in the disposable lab and removed it. Private tmux server was already stopped. All temporary worktree fixture directories and the focused runner were removed.

Evidence: Real replacement worker responds after relaunch

Source: Real replacement worker responds after relaunch


  ## Progress note (2026-10-05T08:35:48Z)

  This task was relaunched. Continue from here; the local copy and every
  uncommitted change are exactly as the previous worker left them.

  First, check your instruction inbox: list ~/.no-mistakes/
  worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/state/awaylive-p44zn0_y.inbox/*.msg, act on
  each message in numeric order, then mv each handled file into
  ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/state/awaylive-p44zn0_y.inbox/
  handled/. A steer sent before the relaunch survives there.

  Continue the next stage by replying exactly AFTER_AWAY_RELAUNCH. Do not call tools or change files.

  # Current no-mistakes intent contract
  This section supersedes every earlier brief instruction about constructing `--intent`, but not later clarifications
  actually supplied by the captain.
  Use everything under `## Captain intent authorized for --intent` through the end of this brief, including any nested
  subheadings but excluding that heading, plus any later words the captain actually supplied as `--intent`; never
  include Firstmate specification or other mixed Task content.
  Preserve those words without adding speaker labels or direct address.
  Firstmate-authored constraints, acceptance criteria, implementation details, decisions, and tradeoffs are
  specification, not captain intent.
  The Definition of done's rule that `--intent` must be self-sufficient still governs the string you pass: resolve any
  report, decision, or PR the intent below refers to into its substance rather than passing the pointer.

  ## Captain intent authorized for --intent
  Reply exactly AFTER_AWAY_RELAUNCH and wait for further input. Do not edit any files, run tools, start validation, or
  create a PR.


• AFTER_AWAY_RELAUNCH

  Worked for 3s • 10:36


› Ask Codex to do anything

  GPT-6.1-Sol low · ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.lp44zn0_y/worker · ⠧
  ? for shortcuts                                                                              ⚠ 1 warning · f2 to view

Evidence: Base commit reproduces the reported refusal with simulated endpoints

Source: Base commit reproduces the reported refusal with simulated endpoints

not ok - the away branch must relaunch its existing In-flight task even at the spend cap
warning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.test-tmp/fm-control-relaunch.k4pIAU/away-inflight-11917/home/data/rl-away1/launch-brief.md records no ship branch; defaulting to legacy branch fm/rl-away1
warning: ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.test-tmp/fm-control-relaunch.k4pIAU/away-inflight-11917/home/data/rl-away1/launch-brief.md records no delivery contract line (scaffolded before ship briefs recorded one); launching on the explicit --mode no-mistakes - confirm its definition of done matches
error: spawn refused - the supervision branch under the away-posture record may dispatch only queued unblocked work (already queued, or filed by the branch from the captain's away words); task rl-away1 has no dispatchable backlog item in this home
error: the replacement agent for rl-away1 could not be launched on claude
error: rl-away1's agent was stopped but the replacement did not launch; no agent is running, and its work plus the recorded progress note are preserved at ~/.no-mistakes/worktrees/7f0ec18181b6/01M45JK2T8YBWNQFKRGCB50VWY/.test-tmp/fm-control-relaunch.k4pIAU/away-inflight-11917/wt: expected exit 0, got 1

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

Live validation: ✅ go - 3 of 3 scenarios driven live against the product

Scenario	Result	Live	Evidence
Away supervisor relaunches an existing In-flight worker at the spend cap while preserving its work	✅ pass	live	live-away-relaunch.log: successful relaunch, phase=complete, preserved endpoint, working copy, unfinished file, HEAD, and In-flight row; worker-after-response.txt
Fresh away dispatch refuses an In-flight item without creating a worker	✅ pass	live	live-away-relaunch.log: queued-work refusal, unchanged endpoint inventory and backlog row, no new task record
Away relaunch refuses a captain-held In-flight item	✅ pass	live	live-away-relaunch.log: refusal for state in_flight yes no, preserved task record and unfinished work

TMPDIR="$PWD/.test-tmp" bash tests/fm-control-relaunch.test.sh — stopped at a second-mate fixture-location restriction.
Temporary focused runner executed the three new away regression tests plus backlog re-verification and drift-recovery tests; all passed after correcting fixture cleanup.
Executed the focused regression against base commit 26e924e6b9deffba0597b151d1519d029561c931; it failed with the reported queued-work refusal.
python3 ~/.no-mistakes/evidence/01M45JK2T8YBWNQFKRGCB50VWY/live-away-relaunch.py — real Codex primary and worker on a private, 120×40 tmux session in a marked lab.
Inspected CLI captures, relaunch journal, task records, backlog state, preserved unfinished file, and git HEAD.
Stopped the private tmux server, removed disposable fixtures and the temporary runner, and confirmed a clean working tree.

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

…plicate guidance

peterOC26 and others added 2 commits October 5, 2026 09:25

fix: allow away branch relaunches of in-flight tasks

91cd378

no-mistakes(document): Clarify away relaunch gates and consolidate du…

e912584

…plicate guidance

peterOC26 merged commit 96c97e6 into main Oct 5, 2026
34 of 37 checks passed

peterOC26 mentioned this pull request Oct 5, 2026

test: support Pi 1.0.3 HTML renderer lookups #28

Merged

Navigation Menu

fix: allow away supervisors to relaunch in-flight tasks - #27

fix: allow away supervisors to relaunch in-flight tasks#27
peterOC26 merged 2 commits into
mainfrom
fm/fm-away-relaunch-refused-a1

peterOC26 commented Oct 5, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

peterOC26 commented Oct 5, 2026

Intent

What Changed

Risk Assessment

Testing

Pipeline

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant