Inbox
The canonical fleet Emails, Requests and Chats surface (09 §3.9).
The canonical fleet Inbox is not available here
This route is the fleet Emails, Requests and Chats surface, and it is deliberately not reimplemented. It needs the canonical package (BK-02) and real inbound mail routing (BK-11).
Why nothing is drawn here
BK-02 is the canonical fleet console package: it owns the Inbox UI, its integration and the guards that sit in front of it. BK-11 is the apex catch-all and DNS cutover, without which no real message can arrive at all.
A local thread list would be a replacement mail interface, which 19 §6 forbids, and an empty one would report zero requests for sources that are simply not connected.
What it will carry
Apex catch-all and named mail, and the PostgreSQL-backed landing, support and enquiry requests with status, assignment, private notes and permitted replies. Restricted billing, privacy and security records do not inherit project-wide visibility. There is no raw one-time-code archive, no duplicate intake, no automatic lead resale and no newsletter enrolment. Homeowner follow-up drafts arrive with their guardrail verdicts, and auto-send stays off until the operator edit rate is measured.