Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 21, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 21, 2026
10 of 14 tasks
This branch was successfully 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.
Native question choices and text disappear when switching threads because the card unmounts. Keep pending drafts in window memory scoped to their thread and request, and clear them on resolution, withdrawal, thread removal or retirement. Secret drafts never enter persisted composer recovery.
Related to #276 and tracker #273; retains the landed request broker, native approval policies and disabled preview gate.
Validation: the navigation regression failed before the fix and all three question E2E tests pass after it. After merging current main with the landed keyboard race fix #352, root build, typecheck and unit tests pass (1,907 passed, 16 skipped). Full E2E passes: 373 desktop tests (6 skipped), including all eight keyboard-answer tests, and 7 site tests.
The first CI attempt could not acquire hosted macOS runners. The second passed iPhone and unit coverage but hit the known Jump to latest race (371 desktop passed, 3 skipped, 1 failed). Bringing in #352 fixes that dependency; CI must pass on the updated head before the protected merge queue lands it.
A real Codex 0.163.0 question was answered through the app with the opt-in
default_mode_request_user_inputflag, and the model confirmed Blue. Default-mode async questions use a distinct form and remain unsupported by this broker. Human keyboard-only/VoiceOver acceptance remains unclaimed. Results and limitations are indocs/reviews/2026-10-20-cf3-drafts.md.Commits are signed with the user-approved SSH signing key registered on GitHub. No approval policy or preview-gate default changed.
CI passed on
1847e0c(375 desktop tests, 3 skipped; 7 site tests; iPhone passed). While it ran, #351/#353 landed and conflicted only with the status entry. Current main was merged, both entries retained, and the full local checks rerun successfully on the combined branch. The new head must pass CI and merge-queue validation.