Status: the third many-people round, and the join fix on its own

[renrenmimi]

Adds a section to STATUS.md for the third many-people round on 10-14:

• what the new races checked: a meetup cancelled, and a code revoked, while 200 people act on them;
• the contended join and its fix (Meetups: a join aborted by the crowd waits and tries again #321), deployed to production as a single function;
• the app showing a refused join in the phone's language (Meetups: a refused join reads in the phone's language #319);
• one small known flaw left as it is.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
pet-note	Ready	Preview	Oct 14, 2026 8:54pm UTC

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-14T20:59:18.829343Z	aa75672	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: aa75672fcd

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

Correct the 200-user concurrency claim

This heading says every listed scenario used 200 people simultaneously, but the invitation-revocation scenario in functions/scripts/scenario-many-users.mjs:718-724 selects exactly three redeemers with outsiders.slice(-4, -1), races only those requests against the revocation, and sends the fourth redemption after that race finishes. This provides four concurrent operations rather than a 200-person test, so the canonical status table materially overstates the coverage; either run the scenario with the intended crowd or report its actual concurrency.

Useful? React with 👍 / 👎.