Conversation
added 3 commits
September 21, 2026 22:57
Adapt composer and regression coverage from upstream PR kunchenguid#4946, head 942089e, including implementation commit 10bffd4 by cangele. The upstream PR remains unmerged; no upstream machine-specific verification claims are imported.
Require a current single-row agent composer and adjacent structured Muse model/effort footer before preferring glyph classification over an idle or done Pi binding. Keep blocked/working Pi, actual pending input, missing structure, and dead-shell cases conservative. Exercise original escalated inbox recovery without re-enqueue or ladder resets; acknowledgement remains the only delivery proof.
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.
Summary
Recognize Muse 1.3's titled composer separator and idle hint rows without treating footer furniture as an unsubmitted draft.
Disambiguate stale idle/done Pi identity only when a single current prompt row and adjacent structured Muse model/effort footer establish the Muse composer shape.
Keep actual input, working/blocked Pi, unknown footer layouts, and shell prompts protected.
Add regression coverage for retrying the original escalated steering-inbox record without re-enqueueing or resetting its delivery budget; acknowledgement remains the delivery proof.
The Muse composer adaptation credits cangele's upstream implementation in the retained commit message.
Rebasing required combining the Muse titled-rule handling with upstream's newly landed footer-zone glyph tracking; both protections are retained.
Verification documentation preserves existing upstream observations and the earlier Muse capture/startup limitations rather than claiming a fresh live pass.
Evidence and limitations
Based on upstream
aec043c718ef186a1d28c607fd5852b041e24435.The combined rebase head tested was
2488fe310400082c3dd088f56c1592313f814131; this PR isolates only the composer/inbox changes, without the terminal reclamation or transport changes.The isolated PR branch has not received a separate full-suite run.
On the combined head,
fm-composer-lib.test.shpassed in 34.9s andfm-composer-ghost.test.shpassed in 7.7s.The attempted repository run was:
It was interrupted at the 3600-second execution limit, after 50 completed script records, and is NOT a full-suite pass.
Real Herdr tests were excluded because no authorized isolated Herdr lab was supplied.
The composer-matrix live test gate-skipped, so this run does not establish a current installed-harness matrix pass.
Exactly the three failing scripts were then run on pristine upstream, serially with the same 900-second per-script bound:
fm-captain-hold-lifecycle.test.shfm-ci-workflow.test.shfm-composer-codex-idle-live-e2e.test.shNo missing cursor-tool dependency was established; the observed fact is the cursorless classifier result, not a proven explanation.
There is no claim that all remaining tests ran or passed.
Contribution process
Published directly under explicit contributor instruction, without running no-mistakes.
This PR has no no-mistakes attestation and does not claim compliance with CONTRIBUTING's required pipeline; maintainers may require it before review or merge.
No running installation was updated, and no local default branch was moved.