Repository navigation
Compare Codex probe request shapes on the same candidate - #273
Merged
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
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.
Live borrowing results still vary between source candidates. Comparing different runs cannot distinguish a request-shape discrepancy from a different route or an upstream failure.
Add an optional
probe_contractscenario to the existing authenticated administrator diagnostic endpoint. It freezes one candidate and target request template, then compares the pinned ranxi body order without a tier, that body with the final tier, and the current body with the same tier. The selected real model never changes; Sol is explicitly identified as the downstream model extension. All pairs use the existing sender, independent per-shot legacy session IDs, fixed cookie, native identity, proxy and strict STATE criteria.Results are explicitly probe-only: they preserve both terminal outcomes, STATE lengths, exact shape and context/body fingerprints, but never publish a business qualification or overwrite real usage evidence. Source acquisition and all comparisons remain within the existing eight-request cap, and expiry or cancellation stops the fixed-candidate comparison. No configuration, account health, scheduling, billing or normal business behavior changes.
Validation: focused tests cover both real model names, reuse of a still-live candidate without early renewal, one-candidate identity retention, semantic tier versus body-order differences, continued comparison after a failed verdict, no qualification/usage writes, request budget, cancellation, candidate expiry, and effective tier policy (including no model calls when blocked). The existing native HTTP tool-continuation regression passes. Actual protocol conclusions remain pending the controlled live comparison; this diagnostic addition is not presented as a completed borrowing repair.