docker-buildlisted

# Purpose Build and push Docker images for the project's services to the cloud container registry (`.claude/project.json` → `cloud.provider`): multi-arch builds (ARM64 edge, AMD64 web), tagging conventions, registry authentication. Image creation only — rollout belongs to the project's infra pack skills. Placeholders `<mainApp>` and `<device>` come from project.json. # Rules (never violate) - Never pass `NEXT_PUBLIC_*` as `--build-arg` — client config comes through the `window.__ENV__` runtime bridge (12-factor). - Registry URLs use `$IMAGE_REGISTRY` — never a hardcoded cloud project ID. - Tags are a git short hash (dev) or semver (release) — never `latest`; flag base images pinned to `:latest`. - A push writes to the shared registry immediately and irreversibly — confirm tag and target first; never push to production from a local machine (CI only). - Stop and ask when tests have not passed for the code being built, or on a platform mismatch. - Verify every push via the registry describe command; attach a confidence label (LOW if unverified). # Resources - Read `resources/build-procedure.md` when building — the procedure with commands, per-service build parameters, output template, and self-check. - Read `resources/troubleshooting-and-examples.md` when diagnosing — DO-NOT patterns, escalation conditions, two full examples, failure modes. # How to use ## What it does Builds Docker images for your services and, when asked, pushes them to your cloud container registry. I