Repository navigation
Verify the complete CARES journey and prepare the Member launch #564
Description
Part of #276; delivery plan: #558.
Outcome
Produce evidence that CARES registration, activity, re-confirmation and liaison reporting work together, then make an explicit launch decision. Keep the admin-only registry gate until this checklist is satisfied and the release decision is recorded.
Acceptance criteria
- Reconcile the implemented registration, profile, fry-sharing and browser/coverage features with [Feature] Member CARES profile section #279 and [Feature] CARES species browser filter #285; close or split their remaining requirements only on evidence. Do not rebuild existing featu 8000 res from stale checklists.
- Verify registration with a photo, duplicate handling, collection-independent registrations, profile/seals, internal and external fry sharing, article submission, Annual re-confirmation/lapse/reactivation and the liaison export against the same data.
- Verify that the opt-in BAP prompt reaches the correct registration, never auto-registers, and leaves BAP's CARES bonus independent of registration.
- Resolve and record historical confirmation handling, reporting period semantics and any outstanding PDF storage/access policy. Preserve the previously documented March 31 renewal grace period unless explicitly superseded.
- Exercise owner, other Member, signed-out and admin access; check private collection data and liaison contact fields remain appropriately restricted.
- Run the end-to-end review on public staging with chikin-farm, including mobile upload/forms and failure/retry cases. Exercise intended Member access in a controlled staging configuration; do not loosen production access to perform the test.
- Record the liaison/maintainer release decision, Member navigation/help, operational owner and rollback procedure. Only then open Member access; verify the released behavior and ensure rollback can restore the gate without losing data.
Blocked by
#281 (articles), #283 (Annual re-confirmation), #284 (report export), #282 (BAP opt-in prompt).
Scope
Launch integration and rollout, not a second implementation of those features. CARES standings #286 are optional follow-up, not a launch requirement.
Activity