Repository navigation
BUZZ-270: Prepare community access verification runbook - #8235
Open
bradseiler wants to merge 2 commits into
Open
bradseiler wants to merge 2 commits into
bradseiler wants to merge 2 commits into
Conversation
Add a repeatable staging runbook and versioned evidence template. Execution remains gated on deployed prerequisites and a disposable community owner. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
This was referenced Oct 10, 2026
Signed-off-by: Local Builder <1c476cb1127ea270cb900bdc3891060140bdd1173f91498030ee9b4db01c2f20@buzz.block.builderlab.xyz>
bradseiler
marked this pull request as ready for review
October 12, 2026 03:52
github-actions
Bot
added
the
codex-security-review-current
🔐 Codex Security Review
Review SummaryOverall Risk: NONE
FindingsNo concrete security, correctness, or reliability findings were identified. Notes
Generated by Codex Security Review | |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a repeatable community-access verification runbook and an evidence template for an exact deployed revision. The steps cover invitation revocation, bans and timeouts, existing root/audio sessions, tenant isolation, cross-pod limits, and webhook-owner policy.
Staging execution remains pending merged prerequisites, passing checks, a deployment owner, and an authorized disposable community. The template starts at NOT RUN and requires exact image/source versions, per-case outcomes, and cleanup confirmation.
Related issue
BUZZ-270. Merged source remediation: #8005. Prerequisites: invitation replacement #8237 and regression coverage #8239. Staging remains NOT RUN.
Testing
Verified all relative document links and the complete diff at
c15c77fd4085beb8f859a45959585d24413647f7. Independent review found no blockers. Commands were checked against the current CLI source. No staging execution or human verification is claimed.Companion drafts
Live-session revalidation: BUZZ-271. Webhook owner policy: BUZZ-272.
Already merged source prerequisites: #7706, #7828, #8128, #8130. Staging remains NOT RUN.
Generated with Codex
🤖 Documentation review correction
At
eb3b03afc3238de7a46916ca8d0d40a9fd6353da, local rehearsal requires an integrated candidate containing #8239 before using the route guard. The runbook now states the mandatoryBUZZ_POSTGRES_ADMIN_URL, PostgreSQL bootstrap variables/privileges, isolated Redis setup, and disposable-database requirement; default/shared services must not be reused. Exact-head content, local links/anchors, diff checks, and normal commit/push hooks passed. Application-test lanes skipped for this documentation-only delta. Staging is NOT RUN; deployment-owner authorization, prerequisites, and exact deployed revisions remain required.