Repository navigation
Hold ambiguous program input for explicit recovery - #514
Draft
raiseCatError wants to merge 1 commit into
Draft
raiseCatError wants to merge 1 commit into
raiseCatError wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
An echo-visible ownership lookup can replay an immediate answer and Enter into command approval before a macOS line reader is recognizable. Keep ambiguous program submissions in an ownership hold with an explicit recovery choice. Echo controls presentation; it does not authorize sending.
Refs #473. Separate from test-only PR #513, whose exact head and failed comprehensive gate remain untouched. No automatic merge or release.
Validation: full
npm run verifypassed locally with the intended truecolor profile and shortest compliant T7 test root. Fixed two-round/two-worker real-PTY stress passed with no lifecycle leftovers. Deterministic coverage includes unknown/older lookups, late likely/hidden inference, completion, cancellation, native handover, editor actions and ordering. Exact-head hosted CI: normal PR run40630119387 PASSED; single comprehensive run40630147755 FAILED macOS1/3 inbrowserConsoleChrome.test.ts:106. Its Mermaid-render result was neither success nor syntax; the actual code/reason was not logged, so causation remains unconfirmed. Other test/platform/timing/Fedora gates passed; aggregate checks correctly failed. No retry. This PR stays draft/unmerged until that independent blocker is understood and the required gate is satisfied. Controlled old/current-dev source fails both immediate/delayed approval-enqueue assertions; corrected source retains the real read and recovers exactly once after explicit Ctrl+S. Independent review findings are addressed. Physical Ghostty/Zed QA remains NOT RUN.Manual validation on Ghostty and Zed: run a prompt-less zsh read and type an immediate answer; when held, Ctrl+S should deliver it once without queueing. Check hidden reads show no answer; sleep plus Enter remains held; Ctrl+Q reviews for queueing; Tab does not submit; Esc/Ctrl+C cancel; completion keeps review-only typing; Fish/native and fullscreen handover receive only their own new input.
Do not integrate #513 yet: preserve its exact head and failed comprehensive evidence. After this gate is understood/corrected, use a separately pinned integration candidate containing current dev, the reviewed correction and exact #513 head, then run the unchanged comprehensive gate once. A normal green rerun does not clear either failure.
Deferred resource investigation plan preserves all prior performance benefits, CPU/RSS costs and measurement limits; no memory optimization was started.