Skip to content

Correct catalog freshness receipt trigger wording - #616

Merged
seathatflowsinourveins merged 7 commits into
mainfrom
foundation/catalog-provenance-template-20261002
Oct 4, 2026
Merged

seathatflowsinourveins merged 7 commits into
mainfrom
foundation/catalog-provenance-template-20261002

Conversation

@seathatflowsinourveins

@seathatflowsinourveins seathatflowsinourveins commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

Scope

Catalog freshness receipts currently claim a scheduled run even when workflow_dispatch produced the evidence. Use trigger-neutral wording for both supported entry points, keeping the producing run URL and all evidence limitations.

  • Base commit: 56473e4b840f0e6940c031801d866e7e9bf29baf.
  • Lane: lane:foundation.
  • Owned path: scripts/freshness_propose.py, one string change.

SOTA sources

GitHub's workflow event reference distinguishes schedule from workflow_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

Claim Evidence class Command / receipt
Workflow supports both entry points; old builder hardcodes Scheduled source_review Exact base564 workflow and builder linked above
Manual producing event occurred native_proven Native Actions run API0, exact run37068599328/source0eb
Existing proposal behavior passes local fixtures local_integration Unchanged83 proposal tests, native0/53.397s
Repository integrity and scope pass local_integration validate.py0:69components/9317hashed files/4profiles/186receipts

Local commands run

rtk proxy python3 -m unittest discover -s tests -p test_catalog_freshness_propose.py
exit0;83 tests;OK
rtk proxy python3 scripts/validate.py
exit0;integrity/scope passed;no live provider or GPU execution
rtk proxy git diff --check
exit0

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.py BuildReceiptTests 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

  • Existing Actions pins and permissions are preserved.
  • No secret or new billing surface is introduced.
  • Peer-owned worktrees and uncommitted changes are preserved.

Custody repair, 2026-10-04

  • A Claude Opus cross-family read at 4865bbb8 returned ACCEPT with one P2: no test pinned the trigger-neutral wording.
  • GPT-6.1 Sol repair commit 25c2538ce: BuildReceiptTests asserts the exact Catalog-freshness run (<run url>) rebuilt the SOTA-convergence manifest and prefix, and that Scheduled does not occur. Against the old wording, a scratch copy fails (exit 1); at this head, the module passes (84 tests).
  • At 681d7632: scripts/validate.py exit 0, scripts/evidence_manifest.py --check exit 0, registry in the last commit. The coordinator's read of the delta: ACCEPT.

Scout and others added 6 commits October 4, 2026 15:20
…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]>
@seathatflowsinourveins
seathatflowsinourveins marked this pull request as ready for review October 4, 2026 20:08
@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Claude session native-agent-stack-5f: landing at head 681d763237162c05215da004a0ea74e8dade4e0b. The command center (wsl-architecture-design) gave its ACK at this exact head; under the user's 2026-10-04 decision it owns merges that touch the hot registry. The read-only cross-family review (GPT-6.1 Sol max, the packaged Codex SDK worker) returned ACCEPT at 4865bbb8bac3; this head is reached from it through recorded carry edges (equal owned patch-ids, or a cross-family delta read returning ACCEPT at the edge's target), with no P1 item.

Observed main 63348259aef76a5b3d7919cba7913e403ded0dbd. coordination/merge_tree_landing_check.py (sha256 a11649fcf2e5844c…) exit 0:

main 63348259aef76a5b3d7919cba7913e403ded0dbd head 681d763237162c05215da004a0ea74e8dade4e0b base 780bf5d0508760b2494995493d9246efd74d614d merged-tree 7a46cab0b20f5d01d5e253fa8d71350416c8cafc merge-tree-exit 0
ok   1: clean three-way merge
ok   2: merged-vs-main paths 3, outside PR-owned 0 []
ok   3: main drift 78 paths, overlap with PR-owned inputs (registry excluded) []
ok   4: registry foreign rows equal True, order preserved True, PR-owned rows 2, unowned top-level keys differing []
ok   5: merged files[] sorted by path with no duplicates: True (9929 rows)
LANDABLE
condition 5: merged files[] sorted and unique (tree 7a46cab0b20f5d01d5e253fa8d71350416c8cafc)

Required checks at this head: 8 pass . Unresolved review threads: 0.

@seathatflowsinourveins
seathatflowsinourveins merged commit 5358bb5 into main Oct 4, 2026
28 of 30 checks passed
@seathatflowsinourveins

Copy link
Copy Markdown
Collaborator Author

Claude session native-agent-stack-5f: post-merge observation. Landed as 5358bb564fc42edb54a1edf7b848bf07d7f0997a (parent 63348259aef76a5b3d7919cba7913e403ded0dbd), tree 7a46cab0b20f5d01d5e253fa8d71350416c8cafc. The landed tree equals the checked merged tree and the parent is the observed main.

@seathatflowsinourveins
seathatflowsinourveins deleted the foundation/catalog-provenance-template-20261002 branch October 4, 2026 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:foundation Foundation lane: Claude/Codex setup, hosts, memory, RAG, research, workers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant