Adopt proof-pr v0.2.1

[saagpatel]

Summary

• updates the proof-pr reusable workflow pin to v0.2.1
• updates the installed proof_pr_ref to v0.2.1

Proof Bundle

Risk: T3
Receipt: proof-pr.v1 for cd18c056b4964a01fa95b63a7e9316e23c6c0e60
Decision: ready_with_operator_awareness

Evidence:

• release-available: v0.2.1 release exists with validated receipt asset -> passed.
• workflow-update: reusable workflow and install ref both pin v0.2.1 -> passed.
• metadata-gate: not_applicable (legacy repo history is not noreply-clean yet; keep adoption advisory-only.)
• github-workflow-dispatch: passed (manual workflow passed on PR Adopt proof-pr v0.2.1 #69.)
• rollback: documented (revert this PR or pin back to v0.2.0.)

Known gaps:

• This updates the workflow pin only; historical dogfood receipt text remains historical. The public metadata gate remains deferred until repo history/tag hygiene is handled separately.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c231322f1f

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Disable the metadata gate until history is private

With this enabled, the manual proof-pr workflow will fail in this repository: v0.2.1's reusable workflow runs proof-pr check-public-git-metadata --ref "$PUBLIC_METADATA_REF" --ref 'refs/tags/v*', and that command uses git log <ref>, so the default github.sha scan covers the full reachable history. I checked this commit locally and the scan reports 187 non-noreply author/committer emails, including 8183b5b itself as codex@openai.com and earlier Gmail-authored commits, so the proof bundle cannot be produced until the history is rewritten or the gate is left off/narrowed.

Useful? React with 👍 / 👎.