Ilia Denisov
7cac910de4
Add the mail, notifications, and broadcast pages over the mail, notification,
and diplomail services (no new business logic), completing the operator console.
- GET /_gm/mail deliveries (paginated) + dead-letters
- GET /_gm/mail/deliveries/{id} delivery detail + attempts
- POST /_gm/mail/deliveries/{id}/resend re-enqueue a non-sent delivery
- GET /_gm/notifications notifications + dead-letters + malformed
- GET/POST /_gm/broadcast multi-game admin diplomatic broadcast
Console depends on MailAdmin / NotificationAdmin / DiplomailAdmin interfaces
(satisfied by the concrete services); pages render in tests without a database.
Delivery detail and dead-letters live under /_gm/mail/deliveries/* and
/_gm/mail/... static segments to avoid a param/static route conflict. Resend
and broadcast flow through the CSRF guard.
Tests: mail page, delivery detail (+ not-found), resend (+ bad-CSRF),
notifications overview, broadcast form + send (input assertions) + bad game
ids, and unavailable. Plus an integration test that drives /_gm end to end
through the real gateway → backend (401 challenge + authenticated dashboard).
Docs: backend/docs/admin-console.md page inventory completed.
Backend Service Docs
This directory keeps service-local documentation that is too detailed for the workspace-level architecture document and too diagram-heavy for the module README.
Sections:
- Runtime and components
- Domain and protocol flows
- Operator runbook
- Configuration and contract examples
Primary references:
../README.md— service scope, contracts, configuration, operational behaviour.../openapi.yaml— REST contract.../PLAN.md— historical staged build-up; kept for archaeology, not as a source of truth.../../docs/ARCHITECTURE.md— workspace-level architecture.