Repository navigation
Audit selected JSON locale failures without changing frozen sources - #6165
Merged
Mister-Meeseeks merged 1 commit intoOct 29, 2026
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.
The selected-result checker uses the locale codec for its record, certificate and source-manifest JSON. Complete UTF-8 fixtures fail on native Windows CPython 3.12.10 (cp1252): U+211D raises
UnicodeDecodeError, and a Unicode input filename becomes mojibake. This package reproduces the failure, verifiespython -X utf8on the unchanged checker, and tests a three-line explicit-encoding patch in private temporary copies.The checker is itself pinned by
frontier6030-source.json, so applying the patch directly would break the selected source closure. Onlyresearch/selected-json-utf8-replay/is added. The patch is reviewable evidence, not a modification to the selected checker. The current selected metadata passes its normal baseline; the failures use complete synthetic fixtures. No new kappa or mathematical claim.Evidence and reproduction
378985908c2138ee3ef33abd956b3cc07fcb8e2eequals the tested local tree. Full source-history preflight is unavailable in the shallow checkout. POSIX execution and full scientific cold replay are not claimed; hosted CI is separate.Current main, overlap and credit
Started from canonical main
721c03822c421b7f7fcbb2598993b947c4d88419, priority revision 8. Before publication on October 28, fetched canonical main3f0152a32eeebac0df11946dbd50cabe5a7f7839. Guidance, catalogue, selected record and audited source are unchanged. The changed upstream package runner was additionally executed read-only at its logical repository path against this package; both registered commands passed. The package retains its original provenance pins.The
portable-replaycard came from the verifier-engineering picker, nonce269949e813c9ca9d693f6a23b2d0d0c2; TASK.json records the refined scope and stop rule. Handoffs, active Discussions and bounded all-state PR searches were checked. The final targeted updated-PR search returned no matches. Remote helper coverage was unavailable without gh; sparse local note coverage was partial. No exhaustive novelty claim.This differs from #5973's invoice stdout repair. Credit Douglas Colkitt's selected-checker contract, Mihir Srivastava's baseline, and the codec precedents #2531, #1834 and #2554. Prepared for josecarlosgonzalezroque-design with substantial OpenAI Codex assistance, one agent, Apache-2.0.
Open next questions: choose a source-preserving integration policy for the explicit-read patch, and corroborate the same fixtures on native POSIX/another supported Windows interpreter. The five framework assumptions and selected frontier remain unchanged.