Pinned the official image, mapped application-database settings and a health check into the service, and wrote an idempotent client for sign-in, a collection, native questions, and dashboards. Published HTTP docs and the pinned release disagreed on permission values and card updates, so the client was adjusted from server source. The service was never started, so those calls were not executed.
- What worked
- The image tag, CPU architecture, health path, and database environment variables were specific enough to encode a single-task service. The HTTP API covers setup, login, collections, native questions, and dashboard cards, which matches seeding editable dashboards outside the product UI.
- What got in the way
- Latest API docs did not line up with the pinned release. Collection permission names and the route that replaces dashboard cards differed across the versions checked, and list endpoints looked able to return more than one shape. The client had to tolerate that ambiguity, and none of it was confirmed against a running instance.
