Skip to content

fix(bin): merge upstream main to stop reporting untouched shared-captain copies as drift - #61

Merged
jazz127 merged 3 commits into
housefrom
fm/firstmate-house-upstream-merge-r5
Sep 27, 2026
Merged

jazz127 merged 3 commits into
housefrom
fm/firstmate-house-upstream-merge-r5

Conversation

@jazz127

@jazz127 jazz127 commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

Summary

Merge upstream main at 30ef650d7ee93cbaaf2ce63c6cac9b1a7890d81e into fork house from 2150207c74c105a89942cf4f4202dc603df5b92b with a real merge commit.
The two upstream commits are 62d643c7 (remote secondmate e2e watcher cleanup) and 30ef650d (shared-captain inherited-generation tracking).
There were no merge conflicts and no house behavior was dropped.
The house declared-wait watcher and its triage tests have identical trees to origin/house.

House feature reconciliation

The upstream commit file list in the evidence artifact contains only the secondmate provisioning skill, shared-captain inheritance scripts and test, and the remote lifecycle e2e test.
The commits do not implement any feature below; each row records the result for that feature.

House feature Coverage by either new upstream commit
Configured runtime branch Neither
Spawn pool refresh from runtime remote Neither
Clone sync on runtime branch Neither
Endpoint-free legacy record retirement Neither
Luna Codex dispatch seat Neither
Fork house workflow guide Neither
Fork default branch and main mirror guide Neither
Durable house feature workflow docs Neither
Delivered open PR declared wait Neither
Quota-axi fleet tab and frame fix Neither
Automated reviewer intake Neither
PR poll relaunch survival Neither
Evidence provenance gate Neither
Bookkeeping-only supervision silence Neither
Routine supervision outcome silence Neither
House feature board Neither
Branch contribution safety Neither
Focused house CI Neither
Stale published attestation refusal Neither
Duplicate remote worker and stale readiness fix Neither
Host-backed supervision and branch dispatch Neither
Pi watcher rejected-confirmation recovery Neither
CLAUDE.md pointer conversion scope Neither
PR evidence body preflight Neither
Closed-row ownership for upstream contributions Neither
Branch report wake row Neither
Branch routine outcome rules Neither
Branch report receipt locking Neither
Contradictory evidence claim refusal Neither
Dock-local Codex credential homes Neither
Scratch-file publication guard and follow-up Neither
Published intent evidence enforcement Neither
Evidence validation at every reporting boundary Neither
Dispatch profile Codex quota seats Neither
Automatic no-mistakes handoff Neither
Secondmate restart Pi composer readiness Neither
House board paged comparison and N/A On House Neither
Merge method from base branch Neither
Herdr project spaces Neither
Prior-art check for upstream PRs Neither
Housefeature automatic branch cut Neither
Codex seat home order Neither
Declared-wait cadence for every liveness verdict Neither
Ready-session timeout Neither
House test fixtures for PR-files and authority Neither
Prior-art PR summary Neither
Captain's Call pane Neither
Housefeature branch delivery Neither

Focused validation

bin/fm-lint.sh passed, including ShellCheck for changed bin scripts.
tests/fm-shared-captain-inheritance.test.sh passed.
tests/fm-remote-secondmate-lifecycle-e2e.test.sh passed (589.958 seconds).
The full suite was not run before the merge.

evidence-artifact: /tmp/fm-firstmate-house-upstream-merge-r5/upstream-commits.txt
evidence-command: git log --format=fuller --name-status 5700baa..30ef650 > /tmp/fm-firstmate-house-upstream-merge-r5/upstream-commits.txt
evidence-captured: 2026-09-27T00:31:47Z

Pipeline

Review, Test, Document, Lint, and Push completed through no-mistakes; CI is running.
The pipeline Test step used disposable lab homes and fake SSH fixtures, so those checks are synthetic/offline built-CLI validation with no real-account or real remote-host claim.
The generated attestation comment is preserved verbatim.

aminry and others added 3 commits September 26, 2026 15:24
…kunchenguid#5845)

* test: stop the leaked unreachable watcher before remote e2e cleanup

The remote secondmate lifecycle e2e backgrounded fm-watch.sh through the
remote_env shell function, so $! named the function's subshell rather than
the watcher. Killing that subshell left the unreachable-leg watcher running,
and its one-second liveness probe kept invoking the fake ssh, which rewrites
ssh.count in the temp root. When a probe landed while the EXIT trap was
removing the root, rm failed with "Directory not empty" after every
assertion had passed.

Exec the watcher from the backgrounded function so the recorded pid is the
watcher itself, and assert the stopped watcher stops probing and writing its
state. Cleanup also stops a watcher left running by a failed assertion and
removes the root through fm_test_remove_tree, so a run that fails before
retirement does not strand the read-only spawn hooks directory.

Closes kunchenguid#5836

* no-mistakes(review): Clear reaped watcher PIDs and restore plain temp-root removal

* no-mistakes(review): Let in-flight probe settle before stopped-watcher baseline
…nchenguid#4806)

* fix: stop quarantining ordinary shared-captain source updates

* no-mistakes(document): Rewrap remote inherit header so usage prints fully
@jazz127
jazz127 merged commit 21494bc into house Sep 27, 2026
1 check passed
@jazz127
jazz127 deleted the fm/firstmate-house-upstream-merge-r5 branch September 28, 2026 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants