Repository navigation
BUZZ-269: Cover community-ban entry points - #8239
Draft
bradseiler wants to merge 11 commits into
Draft
bradseiler wants to merge 11 commits into
bradseiler wants to merge 11 commits into
Conversation
Signed-off-by: seiler <seiler@squareup.com> Co-authored-by: Codex <noreply@openai.com> (cherry picked from commit dcb83eaec669ed044ab2f16c8b7612bd54ed1d9c) Signed-off-by: Brad Seiler <seiler@squareup.com>
Signed-off-by: seiler <seiler@squareup.com> Co-authored-by: Codex <noreply@openai.com> (cherry picked from commit 5bbf2b64a82115c40fdadeb981dbfdf7122241f2) Signed-off-by: Brad Seiler <seiler@squareup.com>
Signed-off-by: seiler <seiler@squareup.com> Co-authored-by: Codex <noreply@openai.com> (cherry picked from commit 2374e1c05352db37eafa42d502a148b57dc21080) Signed-off-by: Brad Seiler <seiler@squareup.com>
Signed-off-by: seiler <seiler@squareup.com> Co-authored-by: Codex <noreply@openai.com> (cherry picked from commit 31968772ebe1b30c2862966e46b75a9ad4b967b6) Signed-off-by: Brad Seiler <seiler@squareup.com>
Keep invitation and webhook-owner gaps explicit until their implementations are integrated. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Complete the preserved 66663e19 remediation with a deterministic production-consumer regression, cancellation-safety documentation, and deadline diagnostics. Original recovered refs and their attribution remain unchanged. Co-authored-by: Codex <codex@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Co-authored-by: Codex <codex@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
Avoid comparing host and PostgreSQL clocks in the async enqueue guard regression. Assert strict lease ordering before releasing activation. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Brad Seiler <seiler@squareup.com>
This was referenced Oct 10, 2026
This branch has not been 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
Classify all 74 current relay HTTP routes and bind community-ban enforcement to a signed request matrix with allowed controls. Cover the new sidebar/read-state routes and classify operator routes explicitly. Fail the inventory guard when a new production route has no policy row.
Fix a mesh echo timeout by retaining the pending validated receive across housekeeping ticks. Add a deterministic production-consumer regression, cancellation-safety documentation, and diagnostics that retain the last scrape or error until the deadline. Enable the accessory API when CI runs its route matrix.
Invitation claim and webhook-owner coverage remain explicitly pending BUZZ-268 and BUZZ-272 in this standalone draft. Final integration must replace those rows with real tests, include BUZZ-271 revalidation regressions, and require zero pending coverage.
Related issue
BUZZ-269. Companion invitation implementation: #8237. Staging verification runbook: #8235.
Testing
Validated
893f81ffed0fa50048f786c7f698e9b8bf3a2ac6:just ciandjust testpassed; full DB/relay packages and doctests passed; the complete discovered PostgreSQL suite passed 940/940. Ordinary lanes retain configured infrastructure skips; the separate PostgreSQL run uses isolated services. Existing ACP pipe-test leak warnings were reported with passing exit status.The isolated signed route suite passes all three tests: HTTP matrix, root WebSocket refusal, and host-scoped bans. The inventory reports 23 HTTP behavior cases and 19 supporting regressions. Adding an unclassified route to the production router source makes the guard fail. Removing the mesh consumer fix makes its regression fail.
Independent agent review found no remaining blockers. Draft only: sibling integration and human testing remain outstanding.
Companion drafts
Live-session revalidation: BUZZ-271. Webhook owner policy: BUZZ-272.
Generated with Codex.