# Mobile API Reconciliation

Source compared against implementation:

- `mobile-backend-api-specification.md`

## Result

The current mobile v2 surface is implemented behind the unified gateway and validated live in `dev`.

That includes:

- auth session routes
- client dashboard, billing, coverage, hubs, vendor lookup, managers, team members, orders, and reports
- client order, hub, coverage review, and invoice write flows
- staff dashboard, availability, payments, shifts, profile sections, documents, attire, certificates, bank accounts, benefits, privacy, and frequently asked questions
- staff availability, tax forms, emergency contacts, bank account, shift decision, clock-in/out, and swap write flows
- upload and verification flows for profile photo, government document, attire, and certificates
- attendance policy enforcement, geofence incident review, background location-stream ingest, and queued manager alerts

## What was validated live

The live smoke executed successfully against:

- `https://krow-api-v2-e3g6witsvq-uc.a.run.app`
- Firebase demo users
- `krow-sql-v2`
- `krow-core-api-v2`
- `krow-command-api-v2`
- `krow-query-api-v2`

The validation script is:

```bash
node backend/unified-api/scripts/live-smoke-v2-unified.mjs
```

## Remaining work

The remaining items are not blockers for current mobile frontend migration.

They are follow-up items:

- extend the same unified pattern to new screens added after the current mobile specification
- add stronger contract automation around the unified route surface
- add a device-token registry and dispatch worker on top of `notification_outbox`
- keep refining reporting and financial read models as product scope expands
