fix(bin): read aged holds via backlog-json, not contribution-input - #6
Merged
Merged
Conversation
The hold re-verify sweep only needs canonical backlog rows; contribution-input also walks every task meta for merge-authority resolution, which took ~96s at this fleet size and always exceeded the five-second projection bound. Add fm-fleet-snapshot.sh --backlog-json for that narrower read and point the sweep at it so failures stay loud without raising the timeout. Co-authored-by: Cursor <cursoragent@cursor.com>
Sort aged captain holds oldest-first before the per-sweep cap, let FM_HOLD_REVERIFY_BUDGET_SECS govern the backlog projection bound, clamp forge probes to remaining budget, skip probes for predetermined not-a-decision rows, drop the classify subcommand, and document --backlog-json. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Adds the toolbelt row and prose alignment from the failed run's document step without rebasing onto upstream main. Co-authored-by: Cursor <cursoragent@cursor.com>
Apply captain inbox 006 on the fork publication branch without rebasing onto upstream main.
keenvc
marked this pull request as ready for review
September 28, 2026 19:14
This was referenced Sep 30, 2026
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
1 participant
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.
Summary
fm-fleet-snapshot.sh --backlog-jsonfor consumers that only need the canonical backlog projection.fm-hold-reverify.shat that mode instead of--contribution-input, which spent ~96s on per-task merge-authority work this sweep never reads and always exceeded the five-second projection bound.Evidence (before / after)
Methodology:
FM_HOME=/home/azureuser/firstmate FM_HOLD_REVERIFY_INTERVAL=0 FM_SNAPSHOT_NOW=2026-09-28T00:00:00Z bin/fm-hold-reverify.sh checkon the captain home (432 backlog rows, 227 task metas).fm/fm-recurring-hold-reconcile, contribution-input + 5s bound)hold re-verify: could not read the aged-hold projectionhold re-verify: … among 12 aged captain holds (35 deferred); docket state/hold-reverify/docket.jsonin ~1.4sNarrow-read timing:
bin/fm-fleet-snapshot.sh --backlog-jsonon the same home completes in ~0.75s vs contribution-input failing withArgument list too long/ multi-minute task-meta walks.Test plan
bash tests/fm-hold-reverify.test.shMade with Cursor