Docs: pin GitHub acceptance ref identity

[BigSimmo]

Status

The original controlled GitHub write test did not prove publication of the expected ref:

• expected branch: codex/github-connector-write-test-20260802
• expected full SHA: 2f1a09b5d0ceb3e8ae2ea689f1d96ef8efe6a185
• actual branch: codex/test-github-integration-after-reconnection
• actual initial SHA: ef644b72f6e838820888eb6723d47309afdcdc92

Change

The acceptance task now requires a task to record its expected branch and full HEAD SHA, publish that exact existing ref without reconstruction, and report whether the published ref matches exactly. It also retains conditional links for successful writes and explicit failure/no-link reporting.

Verification

• npm run verify:pr-local -- --dry-run --files docs/codex-cloud.md
• npm run verify:pr-local -- --files docs/codex-cloud.md
• npm run format
• git diff --check

The current Cloud environment validation remains read-only and independent of this documentation change.

---

Original Codex task

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

📝 Walkthrough

Walkthrough

The GitHub acceptance instructions now require published branch and draft PR links as write-verification evidence before cleanup approval.

Changes

Acceptance Guidance

Layer / File(s)	Summary
Write-verification evidence docs/codex-cloud.md	The acceptance task now requires reporting published branch and draft PR links before removing them.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BigSimmo/Database#1447: Updates the same GitHub write-verification guidance.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the documentation change that pins the GitHub acceptance reference identity.
Description check	✅ Passed	The description explains the change and lists verification commands; the missing template headings do not prevent understanding of this documentation-only change.

---

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/codex-cloud.md`:
- Around line 154-155: Update the write-verification requirements in the
documented workflow so branch and draft PR links are required only when their
respective publication or creation operations succeed; when either operation
fails, require its failure reason and explicitly state that no link is
available.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: edd7ddd7-5bc2-4807-8bc8-1a96ff1d92ae

📥 Commits

Reviewing files that changed from the base of the PR and between dd7b65e and ef644b7.

📒 Files selected for processing (1)

• docs/codex-cloud.md

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9af4d85bee

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