Repository navigation
Add private operations KB replay and Journey-3 history - #36
Merged
Merged
Conversation
gouhongshen
marked this pull request as ready for review
November 18, 2026 05:58
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.
Journey-3 adds 60 slow production-question replays to the existing 57 knowledge cases. Two standard Ubuntu runners execute concurrently, each with up to 10 isolated case processes.
cases (documents)runs J3-01–J3-57.cases (operations)runs J3-58–J3-117 for both operations agents. QA runs remain manual; PR CI only tests the framework offline.journey3_benchmark.results. Export history once after both case jobs finish and generate numeric charts, CSV and JSON. The history page overlays all cases by default, with Documents, Operations and individual case views. Each case version keeps a separate line and missing grades leave gaps.Validation:
insufficient_credit. Its trace/session and 29 events were captured; report, QA archive/history and metrics-only publication completed with harness exit 0. No successful new model-quality evaluation is claimed.Readiness limitations: the public-cloud replica still lacks five MCP tools and a dependent custom skill because QA does not expose the required MCP exports. It is blocked rather than scored as an equivalent replica. Model credit must be available for real answer-quality measurements. No shared QA feature flags, MOI/SDK code, production settings or schedules were changed.