Conversation
added 8 commits
September 8, 2026 15:22
… consumer regressions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Intent
Le capitaine demande d enchaîner les tâches restantes en les regroupant en lots cohérents plutôt que de produire des dizaines de petites PR. Il autorise maintenant deux ou trois ouvriers supplémentaires, avec un maximum de deux sessions Grok, tout en surveillant la charge de la machine.
Ce lot regroupe cinq défauts déjà mesurés de la supervision Firstmate :
Ce brief est en français, ta livraison ne l est pas.
Ajout du capitaine pendant l exécution : « il reste 97% sur grok si ca coupe tu changes switch ». Cette autorisation vise les ouvriers Grok actuellement lancés : si Grok interrompt réellement cette tâche, Firstmate la relancera sur GPT-5.6 Sol en effort élevé sans redemander, dans la même copie et sans perdre le travail.
What Changed
Risk Assessment
Testing
Six focused test scripts and additional executable evidence scenarios passed without skips, demonstrating all five supervision fixes using real CLI subprocesses with isolated homes and mocked backends. Captured CLI transcripts, snapshot JSON, and durable state; no live fleet, full-suite, lint, or delivery phases were run.
Evidence: Shell-without-agent reconciliation preserves reasons but rejects stale working
Source: Shell-without-agent reconciliation preserves reasons but rejects stale working
Evidence: Clean watcher exit receives a healthy successor
Source: Clean watcher exit receives a healthy successor
Evidence: Terminal deduplication and recurring blocker presentation
Source: Terminal deduplication and recurring blocker presentation
Evidence: Fleet snapshot under a foreign ambient override
Source: Fleet snapshot under a foreign ambient override
Evidence: Voluntary-wait suppression, invalid-record alarms, and heartbeat recovery
Source: Voluntary-wait suppression, invalid-record alarms, and heartbeat recovery
Pipeline
Updates from git push no-mistakes
✅ **intent** - passed
✅ No issues found.
✅ **Rebase** - passed
✅ No issues found.
🔧 **Review** - 2 issues found → auto-fixed ✅
bin/fm-crew-state.sh:164- A newly spawned worker can have metadata and a busy agent before writing its first status event. snapshot_capture_optional intentionally creates no capture when that optional log is absent, but prefetch_task_observations still passes the capture pathname. This new validation immediately emits unknown, bypassing both authoritative run lookup and live-agent classification. Direct crew-state reads still work, so the fleet snapshot silently mislabels that worker. Preserve the captured absence as an empty status observation rather than treating it as an invalid capture, while retaining rejection of genuinely invalid overrides.bin/fm-control.sh:479- The approved decision requires: "Centralize the voluntary-exit record grammar in one shared fm_voluntary_exit_record_valid helper used by control and watcher." The target still introduces independent validators here and in fm-watch.sh:1176; fm-pr-lib.sh has no shared helper, and the requested shared valid/invalid corpus is absent. Remove the duplicate grammar and implement the already-approved shared validator and consumer regressions.🔧 Fix: Centralize voluntary-exit validation with shared consumer regressions
✅ Re-checked - no issues remain.
✅ **Test** - passed
✅ No issues found.
bash bin/fm-test-run.sh --jobs 1 --per-script-timeout-secs 300 tests/fm-busy-state.test.sh tests/fm-crew-state.test.sh tests/fm-fleet-snapshot-view.test.sh tests/fm-wake-drain-outcome-backstop.test.sh tests/fm-watch-arm.test.sh tests/fm-control.test.shbash ~/.no-mistakes/evidence/01M20Y4BVJS67Y30T1QYD7T8AW/targeted-watcher.sh: shared valid/invalid record corpus, voluntary-exit alarm throttling, and heartbeat deduplication with a buried new result.Executed evidence driverscrew-evidence.sh,snapshot-evidence.sh,drain-evidence.sh, andcontinuity-evidence.shfrom the evidence directory; captured actual CLI responses, snapshot JSON, and persisted watcher records.git status --short: confirmed no worktree changes or leftover generated artifacts.✅ **Document** - passed
✅ No issues found.
✅ **Lint** - passed
✅ No issues found.
✅ **Push** - passed
✅ No issues found.