Organize dirty work: codex/config-reconciliation

[BigSimmo]

This PR organizes local dirty work for branch codex/config-reconciliation.

[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:18 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: 9e40bdff-3ba5-400c-8398-d920cf620f23

📥 Commits

Reviewing files that changed from the base of the PR and between 7f91d99 and e974355.

📒 Files selected for processing (4)

• .github/workflows/ops-digest.yml
• docs/operator-backlog.md
• scripts/check-env-parity.mjs
• tests/repo-hygiene.test.ts

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:e9743550f9

ℹ️ 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]

Keep examples out of the canonical consumer set

When a variable remains only in .env.example because its runtime/CI consumer was removed or misspelled, adding envExampleConfigNames to canonical makes both unknownExpected and unknownLive accept it, so check:env-parity can report success even though no application or CI code reads the variable. Keep the example names solely for the missingFromExample check and derive the canonical set from actual consumers; a focused test where OPENAI_API_KEY exists only in example text reproduces the false success.

Useful? React with 👍 / 👎.

[BigSimmo]

Reviewed at exact head e974355. Superseded by #1360. The valid ops preflight wording was retained; the conflicted environment rewrite was dropped. Source branch and worktree are preserved; this PR is closed only to remove the superseded review queue entry.