Skip to content

Implement staging-only membership and free-event signup/cancellation - #708

Merged
daliu merged 4 commits into
mainfrom
codex/staging-community-lifecycle
Oct 11, 2026
Merged

daliu merged 4 commits into
mainfrom
codex/staging-community-lifecycle

Conversation

@daliu

@daliu daliu commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

Refs #707; does not close until hosted acceptance. Officer impact: A staging-only screen submits pending membership requests/withdrawal and paid-term cancellation intent, and manages free-event signup/cancel. Signup never activates dues or claims. Officer documentation: docs/officers/STAGING_COMMUNITY.md plus entrypoints/maps/cost guide and engineering roots. Deployment evidence: not yet hosted; production and real payments excluded. One isolated communityActions callable/entrypoint; native Auth/App Check, verified mutation account, explicit UID context binding, closed inputs, transactional capacity and saved command/revision fences. No payment/email/role/admin/schedule/dependency change; no legacy migration. Dedicated staging runtime created with exactly four Firestore transaction/get/create/update permissions (project scope, not collection scope); profile IAM unchanged. Fixed owner-only release/Hosting scripts require exact main and six green CI jobs, explicit identities, archive readback, bounded resources and staging-only public configuration. Profile release can inspect but never deploy the one new service. Local evidence: backend7640 pass/66 skipped, frontend1356 pass plus new event UI regression, Rules424 pass, real emulator 20-way final-seat and concurrent cancel plus membership retries/exact expiry, native SDK denials, release guard20 cases, successful diagnostic TypeScript/build and staging artifact verification. Lint snapshot adds four files but no new findings; existing113 errors/6 warnings unchanged. Backup-officer review: clear staging banner/actions/stops, no terminal or secret/data workaround; specialist still supplies/removes fixtures. Hosted browser/race/ownership/source/IAM/cleanup evidence remains required. Rollback is staging-only owner removal/revert of this service; no production operation.

@netlify

netlify Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for luminous-fox-7c393f ready!

Name Link
🔨 Latest commit f6c521c
🔍 Latest deploy log https://app.netlify.com/projects/luminous-fox-7c393f/deploys/6acc202b947c950008ab3e09
😎 Deploy Preview https://deploy-preview-708--luminous-fox-7c393f.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@daliu

daliu commented Oct 11, 2026

Copy link
Copy Markdown
Contributor Author

Self-review completed under Dave’s explicit sole-maintainer review/merge override. Reviewed exact head f6c521c: native Auth/App Check, verified mutations and own-account binding, closed typed inputs, transaction read-before-write/capacity, revision and immutable retry receipts, expiry/evidence preservation, no browser writes/roster, bounded reads/rates/resources, redacted failures, fixed source bundle and staging-only owner/quota/runtime/build/Hosting path. Fixed non-string event identifiers and explicit staging quota routing. All six exact-head CI jobs and their steps pass in run38185624900; root safety suite158 passed locally before the quota test, then affected34 passed; no new lint finding/dependency. Production release manifest remains inactive. Officer impact: disposable staging actions only; no paid activation/refund. Officer documentation: STAGING_COMMUNITY.md and listed roots/maps. Deployment evidence: source/CI only at this point; staged native archive, UI and cleanup still required. No production/payment operation authorized.

@daliu
daliu merged commit 7e3dc45 into main Oct 11, 2026
10 checks passed
@daliu
daliu deleted the codex/staging-community-lifecycle branch October 11, 2026 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant