feat(club-002): club PWA: join flow, digital card and installable shell
This commit is contained in:
22
work/artifacts/CLUB-002/documenter.md
Normal file
22
work/artifacts/CLUB-002/documenter.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# CLUB-002 — Documentation notes
|
||||
|
||||
## New storefront routes
|
||||
- `/club`
|
||||
- `/club/join`
|
||||
- `/club/card`
|
||||
- `/manifest.webmanifest`
|
||||
|
||||
## New same-origin proxy
|
||||
- `GET/POST/PATCH /api/club/[...path]`
|
||||
- Forwards Club requests to backend `/club/*`
|
||||
- Preserves incoming cookies and forwards backend `set-cookie`
|
||||
|
||||
## User-facing behavior
|
||||
- Customers can activate an anonymous Club identity from the storefront without a separate login flow.
|
||||
- After join, the browser keeps the `mdv_club` cookie and the Club card can be reopened later from the same device.
|
||||
- The Club card shows member code, current balance and recent ledger movements.
|
||||
- The storefront now exposes install metadata for a standalone Club PWA shell.
|
||||
|
||||
## Scope reminder
|
||||
- CLUB-002 is frontend/PWA only.
|
||||
- TPV scan semantics, recoveries and account linking stay in later Club phases.
|
||||
Reference in New Issue
Block a user