[AGENT] docs: clarify production auth smoke setup and renewal - #344
Conversation
|
[AGENT] Claude ReviewClaude review for commit This is not a current review or approval. |
|
Codex Review SummaryThis 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. |
PR verification reportAll configured preview and verification checks passed.
Changed visual baselines: none. Updated from Baseline Checks run 35908950512, attempt 1 for |
[AGENT] The production auth smoke runbooks still implied OAuth-only capture and automatic enablement after storing the secret. Document the explicit manual dispatch, complete Clerk cookie capture, fresh-browser verification after JWT expiry, and operator-owned session renewal.
Clarify that the smoke validates the signed-in account page, including possible identity-row initialization, without proving OAuth consent, provider linking, or profile writes.
Validation: markdownlint and the normal pre-commit hook passed. The dedicated account's exported session passed locally after JWT expiry, then the production workflow passed with its authenticated step executed.