Outcome
Create a manual, auditable onboarding/offboarding procedure while provider APIs cannot manage the club communities.
Scope
- Map membership activation, renewal, lapse, suspension, reactivation, and account deletion to WhatsApp and Strava operator tasks.
- Name primary/backup admins and define claim, completion, stale-task escalation, periodic reconciliation, and provider-outage handling.
- Treat invite links as capabilities; never put them in logs, public issues, or broadly readable documents.
- Record only minimum actor/time/outcome/reason metadata, not provider rosters or Strava user data.
Acceptance criteria
- Every task must be claimed before execution and cannot be completed concurrently by two operators.
- Duplicate renewal, lapse/reactivation, wrong-account report, provider outage, and partial completion have deterministic procedures.
- Manual/stale provider state is clearly disclosed; no automation is implied.
- Opt-out and account deletion remove local link data and create the correct provider follow-up.
- Synthetic dry-run fixtures demonstrate the full workflow without contacting production providers.
Dependencies
#81 and #85. Align with Strava constraints in #88 and #89.
Coordination
Parent: #79
Do not begin implementation until dependencies are complete, this issue is assigned, and a timestamped CLAIMED comment naming the agent and branch is posted. Creation of this ticket is not a claim. Preserve the parallel agent work tracked by stable IDs in GITHUB_ISSUES.md.
Outcome
Create a manual, auditable onboarding/offboarding procedure while provider APIs cannot manage the club communities.
Scope
Acceptance criteria
Dependencies
#81 and #85. Align with Strava constraints in #88 and #89.
Coordination
Parent: #79
Do not begin implementation until dependencies are complete, this issue is assigned, and a timestamped CLAIMED comment naming the agent and branch is posted. Creation of this ticket is not a claim. Preserve the parallel agent work tracked by stable IDs in GITHUB_ISSUES.md.