Repository navigation
fix: recover DeepSeek acceptance while retaining unknown usage - #273
Merged
DavidHLP merged 2 commits intoOct 11, 2026
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Restore explicitly authorized DeepSeek acceptance under the cumulative USD200 cap while keeping V12 permanently halted. V13 retains the complete 39-source historical chain, all 988 historical attempts and all three unknown-usage liabilities; unknown receipts never become settled charges or fresh acceptance evidence.
The existing unknown-rollover verifier now supports the pinned V12 predecessor and checks its SQL/guard state, totals and dispatch/request binding. The unchanged V2 path remains supported. DEVELOPMENT documents the recovery contract and its corpus whole-file identity is synchronized without changing excerpt content.
Validation: remote new regressions reproduced 9 failures on the test-only predecessor; current targeted suite passed150 tests and full suite passed1669 tests/1 optionalQdrant skip in173.39s. Actual read-only historical verification passed39 source pins, retained3 unknown liabilities, unknown_released=false and acceptance_evidence=false. Two independent final-commit reviews approve. Exact-head CI38132308441 attempt2 completedSUCCESS after retrying the Auth image's temporary Maven404; AST-only graph update exited0 (122 SQL files lack parser coverage).
V13 is now active. Actual source+three citation model requests were replay-verified against canonical receipts, request/response hashes, provider usage and current prompts:4 known calls,697microUSD recorded at the budget rate,0 newunknown. The executor mistakenly invoked internal source_main without the public artifact claim; it published the complete raw record then exited1/KeyError. This original failure is retained, strict raw source proof passes, no paid source retry occurred, and subsequent stages use public entry points. First20-case development run is live. These preliminary results do not constitute fullU02/U03/U04 acceptance; parentPR231 remainsDraft.