Repository navigation
Correct catalog freshness receipt trigger wording - #616
seathatflowsinourveins merged 7 commits into
Conversation
…egistry plus the owned rows) Co-Authored-By: Claude Opus 5.5 <[email protected]>
…fore the final hot-file commit Co-Authored-By: Claude Opus 5.5 <[email protected]>
… (hot-file protocol: every hot-file edit in the last commit) Co-Authored-By: Claude Opus 5.5 <[email protected]>
GPT-6.1 Sol repair round 616-p2 through the packaged SDK worker; acceptance in the round's result. Co-Authored-By: Claude Opus 5.5 <[email protected]>
…fore the final hot-file commit Co-Authored-By: Claude Opus 5.5 <[email protected]>
… (hot-file protocol: every hot-file edit in the last commit) Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
Claude session native-agent-stack-5f: landing at head Observed main Required checks at this head: 8 pass . Unresolved review threads: 0. |
|
Claude session native-agent-stack-5f: post-merge observation. Landed as |
Scope
Catalog freshness receipts currently claim a scheduled run even when
workflow_dispatchproduced the evidence. Use trigger-neutral wording for both supported entry points, keeping the producing run URL and all evidence limitations.56473e4b840f0e6940c031801d866e7e9bf29baf.lane:foundation.scripts/freshness_propose.py, one string change.SOTA sources
GitHub's workflow event reference distinguishes
schedulefromworkflow_dispatch. Both are selected in the maintained workflow at base564. The implementation follows its existing receipt builder, preserving the receipt schema and report-only claim boundaries.The native API identifies producing run37068599328 as
workflow_dispatch; its original generated receipt is retained in PR527's original219 head. The separate PR527 metadata correction remains independently qualified.Evidence-class table
Local commands run
Original stdout/stderr and hashes are retained in the coordinator's scoped private checkpoint. An optional Ruff executable probe failed to resolve in the current PATH; it is not a lint pass. No runtime route, pin, permission or receipt schema changed. (2026-10-04 custody repair:
tests/test_catalog_freshness_propose.pyBuildReceiptTests now pins the wording; see below.)Decision record
Observed trigger mismatch is recorded in the coordinator's dated correction checkpoint and pre-integration notice384#5962642947. Trigger-neutral wording handles the existing workflow modes without inventing a new event field.
Host evidence
No host evidence files change. Before the 2026-10-04 repair, none of these checks could detect the wording.
Checklist
Custody repair, 2026-10-04
4865bbb8returned ACCEPT with one P2: no test pinned the trigger-neutral wording.25c2538ce: BuildReceiptTests asserts the exactCatalog-freshness run (<run url>) rebuilt the SOTA-convergence manifest andprefix, and thatScheduleddoes not occur. Against the old wording, a scratch copy fails (exit 1); at this head, the module passes (84 tests).681d7632:scripts/validate.pyexit 0,scripts/evidence_manifest.py --checkexit 0, registry in the last commit. The coordinator's read of the delta: ACCEPT.