Harden CodexUI runtime and long-thread rendering - #48
Merged
Conversation
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
1 participant
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.
This narrowly fixes the reviewed CodexUI runtime defects without replacing the current architecture.\n\nIt bounds Qt IPC retention and notifier work, makes framing and dispatch failures terminal, completes pending operations exactly once, enforces frontend/provider generations, reconciles thread reads without stale rollback, acknowledges and drains shutdown, and avoids repeated full-text rebuilds while long responses stream.\n\nCI now builds and tests against pinned SNode.C and the exact paired AISuite PR revision.\n\nVerification:\n- 6/6 CodexUI tests pass\n- 26/26 paired AISuite Codex tests pass\n- CodexUI was built against the installed paired AISuite artifact\n\nOnly essential behavioral coverage was added; no generated-value redesign, retention subsystem, or replacement UI architecture is included.