Repository navigation
Recover outage knowledge and reconcile reviewed source events - #326
Merged
Merged
Conversation
…ix merged sources
tzhouam
marked this pull request as ready for review
October 6, 2026 11:13
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
The service suspension left retained source changes unpublished or prematurely marked
no rules, including major model and streaming features. Recover the 103 retained vLLM-Omni changes, one blocked Jiuwen change, and six earlier events required to close a shared failed batch. Review the original merged source and substantive discussion, then correct or union executable rules at their model and component owners. The QR-image-only change has an explicit no-rule disposition.Add owner-reviewed event settlement after the knowledge has merged with green checks and become the exact active snapshot. Signed plans and immutable receipts bind the original source payload, explicit coverage, owner merge and installed snapshot. Historical records without a merge ID receive a fresh upstream GitHub attestation; their original payload is preserved. Original
done/no rulesdecisions and failed model verdicts remain in history. Whole-batch and publication safeguards stay enforced, and these event receipts confer no knowledge-history trust.Expose public SDK helpers for active source-citing rule proof and installed package bytes so the review bot can verify corrected knowledge without importing private service internals. Retained original exports are handled by a separate reviewed-coverage overlay, rather than being represented as unchanged activated patches.
Validation: complete source coverage and canonical active-rule citation proof; both knowledge validators; committed-baseline vLLM-Omni release audit; focused reconciliation, event-settlement and public SDK tests; repository CI. No upstream release baseline or deployment admission flags change.