Enable auth-service/api-gateway on production, build their images in CI

coordination/CLAUDE_PLAN_CICD_SAFETY_2026-08-18.md

@@ -6,10 +6,22 @@
 > outright on branch `agent/retire-compose-cicd`, not disabled. D1/D2/D3/D4 are
 > closed by deletion rather than by fixing the probe. `docs/operations.md`
 > Deploy/Rollback sections rewritten to describe the actual k3s/ArgoCD path.
-> Compose EC2 itself (`52.0.158.61`) is untouched pending an explicit stop/
-> terminate decision (PR D) — do not stop or terminate it without that go-ahead.
-> PR B (Helm hygiene) and PR C (rollback runbook, now mostly covered in
-> `docs/operations.md`) remain open.
+> PR #23 (both commits above) merged to `master` as `e804817`.
+>
+> **Update, same day, further into the session:** owner gave explicit go-ahead
+> and Compose EC2 `i-039fc8f6102467a54` was **stopped** (not terminated) via
+> `aws ec2 stop-instances`. Confirmed transition `running` → `stopping`. Root
+> EBS still carries `DeleteOnTermination=true`, so it is intact and
+> restartable, but it is no longer a live rollback target — `docs/operations.md`
+> Rollback section now documents this as the current state, including the
+> manual `start-instances` + compatibility-check steps needed before ever
+> trusting it as a DNS fallback again. Nothing else about the box (AMI, EBS,
+> tags, security group) was touched.
+>
+> PR B (Helm hygiene: drop the redundant `AWS_REGION` env block, add a
+> baseline render-diff to `helm-chart.yml`) and the remaining half of PR C
+> (an actual one-command k3s rollback script/workflow, not just the manual
+> runbook now in `docs/operations.md`) remain open.
 
 # Plan — make the CI/CD path safe after the k3s cutover (2026-08-18)