Repository navigation
Clarify staging event availability and clear stale member status - #725
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Members can distinguish current free-event availability from stored signup history, and an uncertain refresh no longer leaves old active status or new-action controls visible.
Officer impact: Clear cancelled/closed/full/not-yet-open/ended messages and safe refresh/saved retry in the existing staging member page. No event/registration/refund policy changes.
Officer documentation:
docs/officers/STAGING_COMMUNITY.md,docs/officers/SYSTEM_MAPS.mdwith text alternative,SYSTEM_DESIGN.md,OPERATIONS_RUNBOOK.md,GITHUB_ISSUES.md. New procedure remains NOT AVAILABLE YET pending native acceptance.Deployment evidence: None for this change yet. Exact backend-first staging Function archive/settings/unchanged-profile/IAM/security, dependent Hosting and disposable native UI/failure/cleanup checks remain required under #724. No production/runmprc.com or real payment release.
Review
signupStatusenum. Old clients may ignore it; new UI fails closed on missing/unknown states. No stored schema or backfill.Checks
Refs #724. Do not auto-close before native acceptance and current handoff. Full backend goal stays active.