Push Report Writer server to prod

Objective

• Ship the Report Writer server to production and widen access to a broader test build so daily development is less dependent on juggling multiple repos locally—especially while near-complete front-end and mobile MVP work continues in parallel.

Background

• May 15 feature sync (Chris): Front-end and mobile MVP are close; the server still needs a prod push and a test build that more people can hit without fragile local orchestration.
• Chris: Treat prod deployment as a distinct milestone from finishing the last MVP UI polish.

Scope

Infrastructure / release

• Decision needed: target hosting, environment matrix (staging vs prod), secrets, DB migrations, and rollback plan for the Report Writer API.
• Decision needed: how the test build is distributed (TestFlight, internal APK, web preview URL) and who is on the allowlist.

Backend alignment

• Coordinates with ATT-1672 when schemas and routes are owned by Attik backend versus an interim service—Decision needed which service receives prod traffic first.

Monorepo / local dev ergonomics

• Document (in the owning repo’s README or runbook) the minimal commands to run server + clients—Decision needed whether Docker compose, remote dev env, or shared staging replaces multi-clone setups.

Codebase audit note

• attik-backend in this workspace is the general Attik API surface; no ReportWriter-named routes appeared in the quick audit—confirm the actual deployable artifact name and repository before wiring CI.

References

• ATT-1672 (schema / backend migration).
• Sibling feature tickets under Attik Report Writer (e.g. ATT-1673–ATT-1677) assume a reachable server for integration testing once this lands.