Repository navigation
ci: inspect SES readiness without changing account settings - #94
Conversation
Add a separate confirmed inspection workflow with an account-bound read-only session and fixed public receipt. Exercise its actual scripts without credentials and include the policy and API controls in required CI. Refs: #93
Give the read-only inspection its own concurrency group so it cannot replace a pending setup run. Reject a restored collision using the actual workflow YAML.
@codex review for read-only SES execution, dispatch guards, account binding and fail-closed metadata |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Ready at This publishes the reviewed inspection path. The real account read is gated on its confirmed run from protected main; current live SES readiness is still unverified. |
Why
Mail rollout decisions need a current sending-readiness check that cannot change account settings.
What
Adds a confirmed, read-only inspection with a concise readiness and quota result to guide the remaining mail rollout.
Fixes #93