Repository navigation
Drop the scratch NuGet.Config digest from the MessagePack relock receipt (#1178 GPT read, P3) - #1196
Merged
seathatflowsinourveins merged 1 commit intoOct 16, 2026
Conversation
…ipt (#1178 GPT read, P3) The GPT full read of #1178 (P3): build_environment.nuget_config in evidence/receipts/osv-alpaca-messagepack-relock-20261015.json published the sha256 of a task-scratch NuGet.Config that no repository file holds, so nobody can check the digest from the repository (correction #161's custody rule: docs/decisions/2026-10-12-harbor-parallel-runtimes.md, "Custody of the run originals"). The key does not end in _sha256, so tests.test_receipt_sha256_key_custody never reached it. - The value now describes the file and carries no digest: "Task-owned public-only NuGet.Config: a cleared packageSources list plus the single nuget.org v3 source, passed with --configfile to every restore". - manifests/evidence.json: the receipt's row re-hashed. The command center's 20:58Z ruling keeps this fold in its own commit, after the mcp relock. Checks: validate.py passed (12148 hashed files); evidence_manifest.py --check passed; git diff --check is clean; under TZ=UTC, tests.test_receipt_sha256_key_custody, tests.test_provenance_digest_custody and the 32 tests/test_local_pages*.py modules ran 578 tests, OK. No other tracked file carries the removed digest (git grep). Co-Authored-By: Claude Opus 5.5 <[email protected]>
seathatflowsinourveins
added
the
lane:trading
seathatflowsinourveins
marked this pull request as ready for review
October 16, 2026 01:02
seathatflowsinourveins
deleted the
claude/api-actions-nuget-digest-receipt-20261015
branch
October 16, 2026 01:15
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.
Scope
evidence/receipts/osv-alpaca-messagepack-relock-20261015.json(fix(trading): relock the LEAN Alpaca adapter onto MessagePack 3.1.9 (GHSA-qhrr-8q5h-9q3h) #1178).build_environment.nuget_configstated the sha256 of the task's scratch NuGet.Config, a file no repository path holds; it now describes the configuration without a digest. The receipt'smanifests/evidence.jsonrow is re-hashed.1dedf90d3(main after Relock the OpenHands recipe onto mcp 1.30.0 (GHSA-84m7-p3x7-pcfv) #1191).lane:trading, as fix(trading): relock the LEAN Alpaca adapter onto MessagePack 3.1.9 (GHSA-qhrr-8q5h-9q3h) #1178.191f6c6f(P3) and again on Relock the OpenHands recipe onto mcp 1.30.0 (GHSA-84m7-p3x7-pcfv) #1191 (P3-1); the command center's ruling kept fix(trading): relock the LEAN Alpaca adapter onto MessagePack 3.1.9 (GHSA-qhrr-8q5h-9q3h) #1178 and Relock the OpenHands recipe onto mcp 1.30.0 (GHSA-84m7-p3x7-pcfv) #1191 unchanged and sent this fix to its own pull request.SOTA sources
tests/test_receipt_sha256_key_custody.pyat1dedf90d3(module docstring) anddocs/decisions/2026-10-12-harbor-parallel-runtimes.md("Custody of the run originals") apply it: a published digest binds only bytes anyone can check, a tracked file or a named public artifact. The scratch configuration was neither, so its digest is removed rather than its bytes published; the receipt keeps a description of what the configuration contained.Evidence-class table
local_integrationpython3 -m unittest tests.test_receipt_sha256_key_custody tests.test_provenance_digest_custody: OKlocal_integrationtests.test_local_pages_architecture_landscape_exclusions,tests.test_local_pages_policy_grants: OKlocal_integrationpython3 scripts/validate.pyexit 0;python3 scripts/evidence_manifest.py --checkexit 0 (12148 files);git diff --checkexit 0Fail-first evidence
tests.test_receipt_sha256_key_custodychecks only keys ending in_sha256, and this digest sat inside a free-text field, so no existing test failed on the old receipt (the GPT read of this PR, P3). The repository's free-text checker,scripts/check_text_digests.py(correction #161), discriminates it:The only finding present before and absent after is line 59's unresolved 64-hex run, the
nuget_configdigest. The other 23 findings are identical in both runs: public upstream commit identities (for example the pinned LEAN and Alpaca commits) that the checker's Git-index identity list does not include, so the checker is not a pass/fail gate for this receipt. No regression test is added: a receipt-wide free-text digest test would need the identity list to cover upstream commits first (PROPOSAL, for the R5 survey of upstream citation checkers).Decision record
None; a one-field receipt correction.
Checklist
🤖 Generated with Claude Code