Generated workflow YAMLs declare no provenance in their own bytes, so reviewers correctly apply the hand-shell gate to emitted files

[briansrls]

Auto-opened by session-dashboard for session eager-bee-66.
Pushing to session/eager-bee-66 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[gunbai-bot]

Closing: this PR carries no unlanded change. Its head abe4638 is the head whose content already squash-merged as #9954 (e49ad23), and it is the same head as #10058, closed earlier today for the same reason.

Verified by RANGE patch equivalence, which is the test that works here:

git diff ecda0710810..abe4638536      -> 53855df9fbb3190993a0c22f1993d02bbd59343a
git diff e49ad238af9^..e49ad238af9    -> 53855df9fbb3190993a0c22f1993d02bbd59343a

Note for anyone re-deriving this: git cherry origin/main abe4638536f reports FIVE commits as unique, which is misleading rather than wrong. The branch's five commits were squashed into one commit in main, so no individual commit has a patch-id equal to any single main commit — cherry compares commit-by-commit, and a squash destroys that correspondence. The whole-range patch-id is the test that answers 'is this branch's change the change that landed'.

As a merge this would apply 2186 insertions and 19,662 deletions across 151 files — main's movement since the branch base, i.e. other lanes' landed work reverted. Third auto-open on an already-merged branch today (#10080, #10089, this one).

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-02T16:30:30.887359Z	abe4638	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.