fix(composer): normalize Claude NBSP padding in the shared verdict - #2092
Closed
haroarthur wants to merge 3 commits into
Closed
haroarthur wants to merge 3 commits into
haroarthur wants to merge 3 commits into
Conversation
haroarthur
force-pushed
the
fm/contribute-composer-nbsp-upstream
branch
from
August 11, 2026 02:02
b5d494d to
d1dc339
Compare
Contributor
Author
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
This contribution consolidates, rather than supersedes, #2029. Claude renders its empty composer as ❯ followed by U+00A0. POSIX [:space:] does not trim that byte, so the shared composer classifier can misread an idle composer as pending on tmux, Herdr, Orca, and bordered cmux. Normalize only the observed U+00A0 at the shared verdict boundary, preserving real-text and dead-shell verdicts.
The false pending verdict caused a measured 10h31m away-mode wedge. The incident chronology belongs here rather than in regression-test comments.
What Changed
Validation
Raised through no-mistakes (cross-fork). The change and its focused regression tests are clean. The mandatory checks - the full test suite and the pinned ShellCheck 0.11.0 lint - run on this repository's CI and are the authoritative gate. They have not executed yet: the workflow is pending maintainer approval. The required checks are therefore not yet green; they run once approved. (Correcting an earlier draft that implied full validation had completed - it had not.)
Pipeline
Updates from git push no-mistakes