> **For client planning only:** This is an incomplete coverage/verification record, not a backend implementation guide or a release sign-off.

> **Current coverage warning:** Files have been consolidated in place. A route listing is not a complete endpoint contract. Full request/response coverage and runtime verification are still pending for multiple modules.

# Coverage and outstanding verification

This is a partial verified extraction, **not** the complete API handoff requested.

Repository route modules identified: Access, Accounts, Audit, AuditChain, BulkActions, Cart, Catalog, Chat, Core, Dashboards, Delivery, Devices, Disputes, FeatureFlags, Identity, Impersonation, ImportExport, Locations, Media, Notifications, Orders, Pages, Payments, Pricing, Push, Realtime, Reports, Reviews, Scheduler, Search, Settings, Support, Verification, Wallet; plus root `routes/api.php`.

## What must still be done

1. Parse every route file, including nested prefixes, middleware, permissions, and rate limits.
2. Read each referenced Controller action.
3. Read corresponding FormRequest rules to establish exact request fields, types, defaults and validation.
4. Read API Resources/serializers to establish exact success JSON schemas and nested objects.
5. Read exception handling and tests for documented error status codes and JSON examples.
6. Split the verified contracts by Flutter and Dashboard and create a complete endpoint index.

No unverified request/response example has been presented as a factual production contract.
