Repository navigation
Conversation
JJ27
force-pushed
the
JJ27/ug-orchestrator-ci-verification
branch
from
October 8, 2026 01:26
ae0f4fa to
14b8ba0
Compare
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.
What did you change, and why?
Keep temporary live verification separate from the integration changes in #996. This draft targets that PR's branch and changes only tests and their documentation.
Two real-agent journeys exercise Claude and Codex with
ENABLE_SMART_ROUTER_ORCHESTRATOR=1. Each requests a review of three source modules without asking for subagents, requires completed native child work and a root report containing values read from all three files, performs native/compact, and repeats with different files. Both reviews require fresh workflow context. Codex delivers its compact hook before the next model request, so the follow-up review checks that delivery.The journeys use the existing managed-config test lanes and real gateway and agent binaries. They check delegation and continuation, not the accuracy of review findings. There are no production-code or shared CUJ-fixture changes.
How do you know it works?
d4a505c. Codex hit model API 429 rate limits in both attempts, so its complete journey remains unverified. Results for the renamed revision are pending CI.This is a temporary validation PR, not intended for merge.