Files

T

hamid 17a82832ab frontend phase 1: auth — phone-OTP login, role routing & session refresh

Replace the username/password stub with Balinyaar's real credential (phone-OTP)
and add the role router every authenticated screen sits behind.

- services/auth rewritten for OTP over the b2 contract: types/keys/constants,
  clientApi+mockApi behind a config'd seam, hooks (useRequestOtp/useVerifyOtp/
  useMe/useRefresh/useLogout/useSelectRole/useSessionRoleSync). Stub removed.
- A1/A2 customer login + B1/B2 nurse switch as one OTP flow at /login
  (PhoneStep/OtpStep: auto-verify, resend countdown, wrong/expired/lockout states).
- Role router: pure resolveRoleDestination + RoleRouter -> family / nurse /
  admin / select-role, with a splash while /me loads (no wrong-shell flash).
- SelectRole first-use screen at /select-role.
- Widened AuthState (roles via SessionUser), hydrated from /me by useSessionRoleSync.
- Fetch-layer silent token refresh (single-flight + one retry) + shared
  persistAuthTokens/clearAuthTokens; useRefresh as the on-demand path.
- auth i18n namespace in both locales; tests for routing branches, countdown,
  OtpStep state machine, RoleRouter branches; fixed jest @/ -> src alias.
- Docs: client/CLAUDE.md, frontend STATUS/report, for-backend REQ-002..004.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-02 11:58:52 +03:30

backend-phase-0-report.md

backend phase 0: foundation, cross-cutting seams & starter cleanup

2026-06-30 22:48:41 +03:30

backend-phase-1-report.md

backend phase 1: config, reference & platform signals

2026-07-02 01:18:00 +03:30

backend-phase-2-report.md

backend phase 2: identity — phone-OTP auth, sessions & roles (REST)

2026-07-02 02:34:11 +03:30

frontend-phase-0-report.md

frontend phase 0: app shells, design system & data/contract patterns

2026-07-02 01:19:21 +03:30

frontend-phase-1-report.md

frontend phase 1: auth — phone-OTP login, role routing & session refresh

2026-07-02 11:58:52 +03:30

mocks-registry.md

backend phase 2: identity — phone-OTP auth, sessions & roles (REST)

2026-07-02 02:34:11 +03:30

README.md

add build development phases

2026-06-28 21:59:59 +03:30

README.md

Phase reports — template

Every phase writes a report here when it finishes (operating-rules §7, Definition of Done). The report is the durable answer to "what did this phase do, what can I test now, and what's still fake?" — saved to a file, not left in chat.

File name: backend-phase-N-report.md or frontend-phase-N-bM-report.md.

# <Backend|Frontend> Phase N — <Title> — Report (<YYYY-MM-DD>)

## What was built
- Bullet list of concrete deliverables (entities/migrations/endpoints, or screens/services/components).

## What is now testable (and exactly how)
- Step-by-step for a human: e.g. "Swagger → POST /api/v1/auth/otp/request with {phone} → 200; the OTP is
  logged to the console; POST /api/v1/auth/otp/verify with that code → returns access+refresh tokens."
- For the frontend: which screen, which route, what to click, expected result, how mock data shows up.

## What is mocked / waiting on a real service
- Each seam touched: interface + file, what's faked, and a link to its entry in `mocks-registry.md`.

## Contracts
- Produced (backend): which `contracts/domains/*.md` + openapi snapshot.
- Consumed (frontend): which contract/version; any request filed in `frontend/requests/for-backend.md`.

## Docs updated
- Which CLAUDE.md / product doc / conventions were updated and why.

## Follow-ups for later phases
- Anything intentionally deferred, with the phase that should pick it up.