Repository navigation
Preserve optional intake metadata in ledger verification - #3686
Open
roger-sato wants to merge 1 commit into
Open
roger-sato wants to merge 1 commit into
roger-sato wants to merge 1 commit into
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.
Summary
closure. The committed intake contains 24 such decisions: four inherit an explicit null from earlier family decisions, one new row records null in the ledger, and 19 new rows omit the field. The previous checker rejects all 24, includingKeyError: 'closure'on PR1365 in the existing Ubuntu tooling run.Canonical base:
20ecf2891d80b5acf18d980b2164fb44ea7faa90, priority revision 6. This is offline metadata integrity maintenance, not a scientific or live GitHub-state audit. Credit roife's PR704 for the original binding and rejection controls, Douglas R. Colkitt for the reconciliation infrastructure, and Dennis / antunishdPursuit's PR2026 and PR2859 for historical replay maintenance. Fresh open/closed PR and Discussion overlap checks found these predecessors, with no matching pending repair; this is not a novelty guarantee.Test plan
macOS 27 arm64, CPython 3.12.14: 24 focused tests pass normally and with optimized Python, including all 2,947 current authoritative projections, inherited receipts/nulls/completion evidence, explicit overwrite, missing mandatory fields, invented closures, boolean/integer confusion and companion review.
Independently reviewed the production diff and projection semantics. No registered live
SOURCES.json/VERIFY.jsonpin requires modification; historical PR704/721 coverage retains its original snapshot paths.Ran the actual
python3.12 -B scripts/replay_historical_check.py tooling-ledgeronce in a complete isolated checkout containing this checker plus the exact documentation-admission change from pending PR3648. The former closure failure is resolved. The command then rejects the unchanged canonical PR3107 starting-head mismatch; no metadata or validation bypass was added. The production checker tested is identical to this PR; PR3648's change is not included here.Ran the complete
test_pr_reconciliation.pymodule: 29 of 30 tests pass. The remainingAssertionSafetyRefresh.test_exact_accepted_successors_passfailure rejects the canonical liverun_isolated_tests.pysuccessor and also occurs on untouched base. That separate allowlist repair is now PR3688. This diff does not change the allowlist.In a disposable copy of this exact commit
932f3b1ef707733643b5e318c4bf134436ddd766plus only PR3688's two-file patch, all 31 reconciliation unit tests pass normally and under-O, both with-W error.Full tooling CI is not green: the fork push run stops at the existing documentation guard addressed by PR3648. Even with that admission and PR3688, the canonical starting-head inconsistency remains separate. No complete historical ledger replay success is claimed. Upstream Actions require maintainer approval.
Prepared with substantial OpenAI Codex assistance for investigation, implementation, regression controls, execution, independent agent review and writing. Apache-2.0.
Local integration follow-up (2026-10-19 JST): PR3692 repairs the initial-head mismatch using authenticated existing receipts. A disposable canonical-base tree combining its
af040ab4change with exact PR3648a0d88d68, PR3686932f3b1(checker and tests), and PR36883463ba61passes all 38 reconciliation tests normally and under-O, both with-W error, on macOS arm64 / CPython 3.12.14. One 600-second-cappedtooling-ledgerreplay passed the repaired boundaries and batch1047, then stopped after 29.76 seconds at the separate canonical PR1048 detailed-review/evidence mismatch against historical batch1099. The untouched canonical checker independently reproduces that mismatch. Ledger, intake and frozen evidence remain unchanged; full ledger/CI success is still not claimed.