Customer Dashboard

Everything the customer dashboard draws, in one read (issue #4067; design docs/design/2026-10-07-customer-dashboard-handoff/): the customer, their contacts with each contact's own plan and billing, the orders, the payments, the tickets and the History, Rooster's one suggestion, and which actions THIS person may draw.

Live from Pigeonly and Recurly through the existing client; nothing is stored twice. Each section fails on its own ({"data": null, "error": {...}}) and the rest still answers: "Payments could not be reached" is a state of the page, not a 5xx. 404 when Pigeonly no longer has the customer. actions is the only thing the page uses to decide what to draw: an action the service cannot do, or the person may not do, is false (capabilities.py).