Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
1d43f9c
fix: reset per-task supervision markers at away-session boundaries (#…
kunchenguid Nov 11, 2026
9fbefb8
fix: surface herdr lab server failures and validate socket path lengt…
artburkart Nov 11, 2026
13271e2
fix(bin): let a continued Claude session take over the Stop auto-arm …
RibatTRW Nov 11, 2026
64254de
feat(bin): honor config/crew-exclude-tools on Claude workers (#8223)
dmealing Nov 11, 2026
bb3b2d6
feat(watch): add opt-in silent recheck for unchanged paused declarati…
Azd325 Nov 11, 2026
391f9d0
fix(bin): stop counting the no-mistakes gate mirror as reachable in t…
mikeastwoody Nov 11, 2026
6d56ea4
fix(bin): skip stale-grant reclaim in branch wake drains (#8310)
stuartmercer Nov 11, 2026
47df77f
fix(watch): surface paused waits superseded by gates or terminal runs…
Dematom1 Nov 11, 2026
a02b089
fix: close PR registration scan gaps (#8110)
Dematom1 Nov 12, 2026
afc5b76
feat(bin): add opt-in PR squash commit summaries (#8366)
Dematom1 Nov 12, 2026
cf7329b
test: observe Herdr fallback focus before restoration (#8378)
tiago-peixoto Nov 12, 2026
afa1859
feat: report and archive stale worker records (#8035)
Dematom1 Nov 12, 2026
488b232
fix: prevent false extension timeouts after suspension (#8380)
WTF-Am-ID Nov 12, 2026
09ca015
fix: recognize the bun-installed omp as a harness process (#8350)
fmaggi-cw Nov 12, 2026
a9ae3c0
feat(crew): park ship lanes while awaiting review (#7965)
Dematom1 Nov 12, 2026
bf0f346
feat(bootstrap): make Treehouse pool report opt-in (#8033)
Dematom1 Nov 12, 2026
42ec97f
fix: recover stale directory locks during session startup (#8381)
WTF-Am-ID Nov 12, 2026
ed7fbb8
fix(bin): keep home-summary collection inside its refresh deadline (#…
LifeBringer Nov 12, 2026
33809d3
test: accept jq's shortest spelling of the runner-up floor (#8304)
lockhartheavyindustries Nov 13, 2026
07409e7
fix: preserve login identity in remote job environments (#8383)
m-moravcik Nov 13, 2026
d44427a
fix: read Grok 1.0.77's Fast model composer as empty (#8418)
Azd325 Nov 13, 2026
34c77d5
feat(bin): settle declared captain holds from forge PR events (#8422)
tiago-peixoto Nov 13, 2026
427056c
fix(hermes): tolerate empty args under bash 3.2 set -u (#8399)
fmaggi-cw Nov 13, 2026
46b17a2
Merge upstream/main (427056c4) into fork
andrew-codes Nov 13, 2026
c11e683
Merge origin/main into upstream sync
andrew-codes Nov 15, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .agents/skills/afk/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -235,8 +235,9 @@ The single-line format makes submission unambiguous across harnesses; the carrie
### Stale-artifact lifecycle

Treat `state/.subsuper-escalations`, its `.since` sidecar, `state/.subsuper-inject-wedged`, and `state/.subsuper-unknown-acked` as session-scoped delivery artifacts, not as the durable work record.
Always enter through `bin/fm-afk-launch.sh`, which clears prior-session artifacts only for a fresh entry and preserves the current session's buffer on refresh.
Always exit through `bin/fm-afk-launch.sh stop`, which keeps `state/.afk` present through the daemon's shutdown flush, clears it, and archives the posture record last.
The per-task markers `state/.subsuper-stale-<task>`, `.subsuper-reported-stale-<task>`, `.subsuper-dialog-<task>`, `.subsuper-paused-<task>`, and `.subsuper-pause-until-due-<task>` are the same kind of session-scoped episode state: a still-true condition is re-derived fresh by the next session, and a declared wait spanning two away sessions restarts its recheck window at re-entry.
Always enter through `bin/fm-afk-launch.sh`, which clears prior-session artifacts and markers only for a fresh entry and preserves the current session's buffer on refresh.
Always exit through `bin/fm-afk-launch.sh stop`, which keeps `state/.afk` present through the daemon's shutdown flush, clears it with the session's per-task markers, and archives the posture record last.
`docs/herdr-backend.md` "Away-mode supervisor support" and `docs/t3code-backend.md` "Away mode" own the backend mechanisms, and `docs/verification/runtime-backends.md` "Away-mode transport" owns active evidence.

### Reliability properties
Expand Down
5 changes: 4 additions & 1 deletion .agents/skills/bootstrap-diagnostics/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
name: bootstrap-diagnostics
description: >-
Load when the session-start digest's bootstrap or network-checks section, or a standalone bin/fm-bootstrap.sh or bin/fm-startup-network.sh run, prints an actionable diagnostic line - MISSING, MISSING_MANUAL, OUTDATED, PRESENTATION_UNAVAILABLE, BACKEND_INVALID, NEEDS_GH_AUTH, TANGLE, STARTUP_MEMORY_BUDGET, CREW_DISPATCH invalid, FLEET_SYNC, NETWORK_CHECKS, HOME_SUMMARY, BACKLOG_RECONCILE, SECONDMATE_SYNC, SECONDMATE_LIVENESS, SECONDMATE_HANDOFF, NUDGE_SECONDMATES, or FMX - or reports that an interrupted backlog cleanup may have left an endpoint or local copy.
Load when the session-start digest's bootstrap or network-checks section, or a standalone bin/fm-bootstrap.sh or bin/fm-startup-network.sh run, prints an actionable diagnostic line - MISSING, MISSING_MANUAL, OUTDATED, PRESENTATION_UNAVAILABLE, BACKEND_INVALID, NEEDS_GH_AUTH, TANGLE, STARTUP_MEMORY_BUDGET, CREW_DISPATCH invalid, FLEET_SYNC, NETWORK_CHECKS, HOME_SUMMARY, BACKLOG_RECONCILE, SECONDMATE_SYNC, SECONDMATE_LIVENESS, SECONDMATE_HANDOFF, NUDGE_SECONDMATES, RECORD_HYGIENE, or FMX - or reports that an interrupted backlog cleanup may have left an endpoint or local copy.
A silent bootstrap section, or any other BOOTSTRAP_INFO fact, means no skill load.
user-invocable: false
metadata:
Expand Down Expand Up @@ -67,6 +67,9 @@ When any diagnostic needs captain attention, report the plain consequence and re
- `BACKLOG_RECONCILE: code-root <file> is not this home's <file>; ...` - a tasks-axi write addressed the code root instead of this home, so the queue has already forked and either copy may hold rows the other lacks; [`docs/configuration.md`](../../../docs/configuration.md) ("Backlog backend") owns why.
Neither copy is a safe winner: union-merge them into this home's file by task id, resolve each conflicting id to its most recent real transition, check this home's archive before treating a missing Done row as lost, and verify the merged id set equals the union of both inputs before installing it.
Then move the code-root file aside rather than deleting it, tell the captain which rows were recovered, and run every later backlog command through `bin/fm-tasks-axi.sh`; re-linking the code-root copy is never the fix, because the next cwd-relative tasks-axi write replaces the link again.
- `RECORD_HYGIENE: <record inconsistency found in this home>` - report the finding to the captain.
For an orphan status log, say whether it was archived to `data/<id>/status.log` by a mutating session start or only reported by a detect-only session start or heartbeat scan; `state/<id>.status` still existing means it was not archived.
Leave any further cleanup for an explicit instruction.
- `SECONDMATE_SYNC: secondmate <id>: skipped: <reason>` - secondmate convergence left a live home on its existing checkout because the home was dirty, diverged, unsafe, on the wrong branch, missing its placement-specific target commit, unreachable, or otherwise not fast-forwardable, or because inherited local-material propagation failed; bootstrap continued, but inspect the reason because the secondmate's tracked instructions, inherited settings, or shared captain preferences may be stale after a primary update.
- `SECONDMATE_LIVENESS: secondmate <id>: skipped: <reason>|respawn failed after <cause>: <reason>` - the session-start liveness sweep could not guarantee that the registered secondmate is running a real agent process.
Investigate the reason because that secondmate is not guaranteed live.
Expand Down
14 changes: 11 additions & 3 deletions .agents/skills/captain-hold-lifecycle/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,9 +28,17 @@ A completed investigation and an ended visual review use this same owner and com
Run the command in the originating work's authoritative `FM_HOME`; secondmate-owned work registers in that secondmate home's backlog, and a question already held anywhere is never re-registered as a second row.
Do not close a captain-held task merely because the originating investigation completed, its report was archived, its visual review ended, or its task was torn down.
Holding the work item the question gates is safe for exactly that reason: cleanup keeps such a row open with the finished work's deliverable recorded and returns it to the queue, so it still reads as the captain's own call.
Only `answer` with the captain's words or an evidence-backed `reconcile close` may resolve it.
Only `answer` with the captain's words, an evidence-backed `reconcile close`, or the declared PR settlement policy below may resolve it.

Never close anything the captain owns without recording what he actually said: `bin/fm-captain-hold.sh answer` writes his exact words into the task and closes a question-shaped call, while `--release` frees a captain-gated work item to proceed.
When [PR hold settlement](../../../docs/configuration.md#pr-hold-settlement-confighold-pr-settle) is enabled, declare a `pr-policy` only when its specified forge event answers the whole held question.
Use `close` only for a decision-only task, and `release` when the task still contains unfinished work.
A structured PR link alone never authorizes settlement.
The contribution observer records the event as evidence, not as a captain answer, and settles matching holds without a model turn.
An unmatched unmerged closure remains an open question and arrives as a contribution notification.
Read that fact before presenting the remaining choice, rather than asking whether to merge the closed PR.
The script's help owns policy registration, supported events, and retry mechanics.

When recording a captain answer, preserve what he actually said: `bin/fm-captain-hold.sh answer` writes his exact words into the task and closes a question-shaped call, while `--release` frees a captain-gated work item to proceed.
A merge approval uses that existing release path because approval permits the merge to proceed; cleanup closes the work only after it lands and records what shipped.
Closing a held row at merge approval instead records completion before landing, so the backlog claims completion before the work actually ships.
When the answer changes what a task must build, follow `AGENTS.md` section 7's mid-task ask rule to preserve the captain's words in the brief and steer the worker.
Expand Down Expand Up @@ -64,7 +72,7 @@ The absence of a routed work item is not a divergence and the guard never requir
3. Firstmate holds that task - or creates one captain-held task for the review's open questions - with a concise reason carrying the question and options.
4. Attest the full inventory for that review pass under the caller authority in Policy above.
5. Relay the choices to the captain as decisions from Bearings' Captain's Call section under `AGENTS.md` section 9; do not use the word hold in captain chat.
6. Close each call only through `answer` (or a channel that feeds `answers`), close a board-requested moot call through evidence-backed `reconcile close`, record a still-active reconciliation through `reconcile note`, use `--until` when the captain defers it, or confirm a channel already closed it.
6. Resolve each call through `answer`, board-requested reconciliation, or the declared PR settlement policy above, and use `--until` when the captain defers it.
7. Confirm Bearings reflects the outcome: answered or reconciled-moot calls leave Captain's Call, released work resumes, active reconciliations remain held, and deferred calls sit in Charted Next with their date.

`bin/fm-captain-hold.sh --help` owns command syntax, close modes, legacy-identity compatibility, completion attestation, retry behavior, and close ordering.
Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/harness-adapters/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Muse, Gemini, Devin, Command Code, Polytoken, Cortex, Kiro, and Hermes are verif
`../../../bin/fm-harness.sh` prints firstmate's own harness from verified environment markers and process ancestry, and owns how they combine.
A marker names its harness, but a structural ancestor of a different harness outranks it, because a marker is ordinary environment state a child or a multiplexer can retain while ancestry is what proves who owns the process tree.
Only `FM_PI_HARNESS=pi-signed` at the launch boundary together with `PI_CODING_AGENT=true` selects Pi-signed; shared unmarked launcher ancestry remains Pi.
omp publishes no marker of its own; `FM_OMP_HARNESS=omp` is Firstmate's launch marker and the anchored process name `omp` is its ancestry evidence, as `references/harness/omp.md` records.
omp publishes no marker of its own; `FM_OMP_HARNESS=omp` is Firstmate's launch marker and the anchored identity in `bin/fm-omp-process-lib.sh` (process name `omp`, or `bun` running the omp launcher) is its ancestry evidence, as `references/harness/omp.md` records.
`../../../bin/fm-spawn.sh` owns worker marker establishment, while the README launch command owns the signed-primary boundary.
`../../../bin/fm-harness.sh crew` resolves `config/crew-harness`, where absent or `default` means firstmate's own harness.
[`docs/configuration.md`](../../../docs/configuration.md#choose-the-secondmate-harness) owns secondmate pin resolution, including per-mate overrides; [`bin/fm-harness.sh`](../../../bin/fm-harness.sh) owns the resolver commands.
Expand Down
6 changes: 3 additions & 3 deletions .agents/skills/harness-adapters/references/harness/omp.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Cross-harness provider and credential identity is owned by `references/common/mo
| Model flag | `--model <provider>/<id>` (fuzzy patterns are accepted by omp but bypass Firstmate's pre-launch check). |
| Effort flag | `--thinking <off\|minimal\|low\|medium\|high\|xhigh\|max\|auto>`, a superset of the shared vocabulary, so every level including `max` maps straight across. |
| Model discovery | `omp models [--json]` lists built-in and auto-discovered providers only; extension-registered providers such as `claude-bridge` never appear, so those models pass through the spawn unvalidated with a stderr notice. `omp usage` shows provider windows; `quota-axi` covers the `claude` provider when the bridge is in use. |
| Marker | None of omp's own (verified: `PI_CODING_AGENT` absent from the binary, no `PI_CODING_AGENT_DIR` or `OMP_PROFILE` in the default profile). `FM_OMP_HARNESS=omp` is Firstmate's launch marker; ancestry matches the exact process name `omp`. |
| Marker | None of omp's own (verified: `PI_CODING_AGENT` absent from the binary, no `PI_CODING_AGENT_DIR` or `OMP_PROFILE` in the default profile). `FM_OMP_HARNESS=omp` is Firstmate's launch marker; ancestry matches the exact process name `omp` or bun running the package's `omp` launcher. |
| Composer | Pinned to `composer.shape: borderless` by the overlay, a bare `❯` (U+276F) row the shared classifier already reads; busy text is `Working…` (U+2026), the only spelling the omp busy regex accepts (the three-dot form its headless `-p` mode writes never reaches a supervised pane), with the status row's braille spinner plus elapsed cell as the second signal. |
| Autonomy | `--auto-approve` owns approval (omp forces `tools.approvalMode: yolo` for the session under it); the overlay pins `plan.defaultOnStartup: false`, `prewalk.enabled: false`, `retry.usageReservePolicy: auto`. |
| Trust | No project-trust gate at all; a fresh profile shows a provider-login wizard instead, suppressed by `OMP_SKIP_SETUP=1`. |
Expand All @@ -29,9 +29,9 @@ omp cold start is roughly twenty seconds to the first agent turn, paid once per

## Detection

`../../../bin/fm-harness.sh` tests `FM_OMP_HARNESS=omp` before `CLAUDECODE`, like Cursor's markers, and its ancestry walk matches the anchored process name `omp` above the interpreter fallback.
`../../../bin/fm-harness.sh` tests `FM_OMP_HARNESS=omp` before `CLAUDECODE`, like Cursor's markers, and its ancestry walk matches the anchored identity from `../../../bin/fm-omp-process-lib.sh` (the exact process name `omp`, or `bun` whose next argument is a script named exactly `omp`) above the interpreter fallback.
The omp template in `../../../bin/fm-spawn.sh` clears every foreign marker at its own launch boundary, and `FM_OMP_HARNESS=omp` counts only under a real `omp` ancestor, so the marker inherited by any other launch is inert: an omp secondmate's workers keep their own identity and an inherited `CLAUDECODE` cannot outrank a worker that omp launched.
`../../../bin/fm-session-lock-lib.sh` matches the same anchored name for session-lock ownership, and `../../../bin/backends/tmux.sh` classifies it `agent` for liveness.
`../../../bin/fm-session-lock-lib.sh` uses the same `fm_omp_process_matches` identity for session-lock ownership, while `../../../bin/backends/tmux.sh` classifies only the exact name `omp` as `agent` for liveness.
The optional claude-bridge extension runs a nested executable literally named `claude` as a sibling of tool execution, never an ancestor of it, so omp's own tool calls detect as omp; that subtree is never walked by a Firstmate script.

## Worker posture overlay
Expand Down
4 changes: 4 additions & 0 deletions .agents/skills/operational-home-layout/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ config/fleet-ledger optional presence flag opting this home in to the default-o
config/firstmate-role optional LOCAL, gitignored firstmate-repository publication role; see docs/configuration.md "Firstmate role" for operator opt-in and secondmate inheritance
config/wait-no-turns optional presence flag opting this home into default-off waiting-worker behavior (brief waiting section, foreground pipeline drive, pending-reply hold, one fire-and-forget retry ring); LOCAL, gitignored, and not inherited; see docs/configuration.md "Waiting worker spends no turns"
config/pr-health-monitor optional presence flag opting this home into the default-off monitor of its owned PRs; LOCAL, gitignored, and not inherited; see docs/configuration.md "PR health monitor"
config/park-on-review config/auto-land optional presence flags: the first opts this home into default-off parking of idle ship lanes whose PR only awaits human review, the second opts this home into merge-time cleanup of unparked ship lanes; LOCAL, gitignored, and not inherited; see docs/configuration.md "Park on review"
config/hold-pr-settle optional presence flag opting this home into default-off settlement of captain holds that declare a PR policy; LOCAL, gitignored, and not inherited; see docs/configuration.md "PR hold settlement"
config/contribution-review-bots optional exact GitHub-login allowlist for review-bot signals on owned pull requests; LOCAL, gitignored, and not inherited; see docs/configuration.md "Contribution review bots"
config/pipeline-spend optional presence flag opting this home in to default-off per-task no-mistakes spend recording in data/pipeline-spend.jsonl; LOCAL, gitignored, and not inherited; see docs/configuration.md "No-mistakes pipeline spend"
config/nm-home-resolver optional one-line absolute path of a site-provided executable that maps a task copy to its no-mistakes home for host-side reads when NM_HOME is unset; LOCAL, gitignored, and not inherited; see docs/configuration.md "No-mistakes home resolver"
Expand All @@ -67,6 +69,7 @@ config/wedge-defer-parked-gate optional presence flag opting this home into the
config/wedge-evidence-guards optional list of absolute operator guard executable paths, one per line, consulted by the watcher before a wedge escalation where a `CRITICAL` answer defers a bounded run of windows; absent means off; LOCAL, gitignored, and not inherited; see docs/configuration.md "Wedge evidence guards"
config/wedge-defer-worker-wait optional presence flag opting this home into the default-off deferral of a wedge escalation for a lane whose newest status line is its own still-open blocked: or needs-decision: line; LOCAL, gitignored, and not inherited; see docs/configuration.md "Worker-declared wait deferral"
config/wedge-defer-validating optional presence flag opting this home into the default-off deferral of a wedge escalation for a lane whose attributed no-mistakes run is validating (running) or validating (fixing); LOCAL, gitignored, and not inherited; see docs/configuration.md "Validating-run deferral"
config/paused-wait-supersession optional presence flag opting this home into the default-off wake that surfaces a declared `paused:` wait ahead of its recheck cadence once its run is parked at an unreported human-owed gate or terminal; LOCAL, gitignored, and not inherited; see docs/configuration.md "Superseded declared-wait wake"
config/spawn-base-primary-checkout optional presence flag opting this home into the default-off spawn base that starts a fresh local-only ship or scout from the primary checkout's default branch when it strictly contains origin's tip; LOCAL, gitignored, and not inherited; see docs/configuration.md "Spawn base from the primary checkout"
config/cmux-socket-password optional cmux control-socket password; LOCAL, gitignored; read fresh on every cmux CLI call and passed through without ever overriding an operator's own ambient CMUX_SOCKET_PASSWORD when absent (docs/cmux-backend.md "Setup")
config/wedge-alarm optional away-mode wedge-alarm active-alert directives; LOCAL, gitignored; absent means auto (macOS Notification Center when available); see docs/wedge-alarm.md
Expand Down Expand Up @@ -112,6 +115,7 @@ state/ runtime records and signals; gitignored
<id>.herdr-presentation quarantinable attempt and restart-binding journal for Herdr's optional visual projection; never task or endpoint authority; see docs/herdr-backend.md "Presentation spaces"
<id>.check.sh authenticated slow poll; the watcher dispatches validated PR data and the byte-identified Relay shim through trusted repository scripts, runs registered custom checks from hash-validated private snapshots, and rejects every other state check without execution
<id>.check-trust private content binding created by fm-check-register.sh for an intentional custom check
Review-park records (`<id>.review-park` and `<id>.review-park-land`), locks, reports, and tick handoff files are owned by `bin/fm-park.sh`; see [Park on review](../../../docs/configuration.md#park-on-review) for the behavior contract.
<id>.pr-poll private validated data sidecar for the byte-static PR merge poll
<id>.pr-poll-registration private transactional provenance record binding the task, canonical metadata identity, sidecar, and static poll publication
<id>.pr-poll-retirement private identity-bound crash-recovery receipt for one exact validated merged result; removed after its poll artifacts retire
Expand Down
Loading
Loading