chore: make Codex Cloud setup reproducible

[BigSimmo]

Summary

• Add reproducible Codex Cloud setup, maintenance, and static/runtime acceptance for the repository's Node, npm, Deno, Python/OCR, and Playwright toolchain.
• Harden prompt-perfector repository isolation for Windows task-start output, clean Cloud checkouts, and content-level dirty-state drift.
• Add the provider-free RAG extraction work-order prompt without changing retrieval code.
• Preserve current-main CI, upload-parity, issue-ledger, and Playwright-preflight changes.

RAG impact: no retrieval behaviour change — Cloud tooling, isolation checks, and prompt documentation only.

Verification

• npm run check:codex-cloud — static Cloud contracts pass.
• npm run check:skills — 33 canonical skills and 8 aliases valid.
• Prompt-perfector isolation self-test — 14/14 passed.
• Docs links (1,413 refs), docs scripts (403 refs), maintainability budgets, outstanding-issues, branch-review-ledger, changed-file Prettier, and git diff --check passed.
• Focused Vitest rerun was attempted but the repository coordinator was occupied by an exclusive Playwright run in another worktree; exact-head hosted CI is the final executable gate.
• Local Bash syntax/runtime acceptance was not rerun because the installed Bash cannot address these Windows worktrees; hosted Linux CI owns that final check.
• No provider-backed workflow or live service check was dispatched; none is required for this provider-free scope.

Risk

• Risk is limited to Cloud setup portability and future toolchain drift. Static contracts and the 14-case isolation self-test cover the intended boundaries; hosted Linux CI remains merge-blocking.
• Rollback is a normal revert. No deployment, production data, provider credential, or clinical behavior changes are included.

[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]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 11 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a51efe23-0555-49de-a579-07ad2b440be3

📥 Commits

Reviewing files that changed from the base of the PR and between d8b034c and c30049f.

📒 Files selected for processing (17)

• .agents/skills/prompt-perfector/SKILL.md
• .agents/skills/prompt-perfector/agents/openai.yaml
• .agents/skills/prompt-perfector/references/repository-workflow.md
• .agents/skills/prompt-perfector/scripts/verify-repository-isolation.mjs
• .gitignore
• AGENTS.md
• README.md
• docs/README.md
• docs/branch-review-ledger.md
• docs/codex-cloud.md
• docs/prompts/rag-coverage-gate-extraction.md
• docs/scripts-index.md
• scripts/check-codex-cloud-setup.mjs
• scripts/maintain-codex-cloud.sh
• scripts/setup-codex-cloud.sh
• tests/codex-cloud-setup.test.ts
• tests/database-skills.test.ts

---

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

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #6895 (cancelled).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9f7f5a607

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

[BigSimmo]

@codex resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: e9f7f5a607

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

[BigSimmo]

@cursoragent resolve merge conflict

[cursor]

Merge conflict on PR #1434 is resolved and pushed.

• Merged origin/main into codex/cloud-readiness-consolidation-20260730
• Resolved conflicts in AGENTS.md and docs/codex-cloud.md by keeping this PR’s Cloud setup contract and folding in main’s GitHub connector routing guidance
• Also fixed the Static PR TypeScript failures in tests/codex-cloud-setup.test.ts / helper JSDoc
• git merge-tree is clean; GitHub reports mergeable: MERGEABLE

Head: 93b2e87d — #1434