chore(jangar): promote image a4c52389

[gregkonush]

Summary

• Promoted the Jangar image built from a4c52389366f74e58e0adfaa68be2e2c70e0dbab into GitOps manifests.
• Updated the Jangar deployment image to tag a4c52389 with digest sha256:8cd77a9dad5d0d9654b0c6131e2def641d1081c206d8a48d72671b4b679da7c3.
• Updated the Agents control-plane image to tag a4c52389 with digest sha256:d47c8eac9c382605f6771818772e224a84259f6ea808098e37f56c5eb0d4209c.
• Updated rollout annotations so Argo CD reconciles the promoted images.

Related Issues

None.

Testing

• gh pr view 5587 -R proompteng/lab --json statusCheckRollup: argo-lint, kubeconform, semantic checks, and jangar-ci / lint-and-typecheck / run passed.
• gh run view 25408705343 -R proompteng/lab --json status,conclusion,jobs: jangar-post-deploy-verify passed for merge commit c3c5e7633f0d88b7b374174d345eae6f13f3129c.
• kubectl get application -n argocd jangar -o json: Jangar app Synced/Healthy at c3c5e7633f0d88b7b374174d345eae6f13f3129c.
• kubectl get application -n argocd agents -o json: Agents app Synced/Healthy at c3c5e7633f0d88b7b374174d345eae6f13f3129c.
• kubectl rollout status deploy/jangar -n jangar --timeout=180s: passed.
• kubectl rollout status deploy/agents -n agents --timeout=180s: passed.
• kubectl rollout status deploy/agents-controllers -n agents --timeout=180s: passed.
• curl -fsS --max-time 10 http://jangar.jangar.svc.cluster.local/health: returned status: ok.

Screenshots (if applicable)

N/A.

Breaking Changes

None.

Checklist

• Testing section documents the exact validation performed.
• Screenshots and Breaking Changes sections are handled appropriately.
• Documentation, release notes, and follow-ups are updated or tracked.

[gregkonush]

Marco release gate as of 2026-05-06T00:10Z: PR #5587 is merged and Jangar rollout-verified.

• Merge outcome: chore(jangar): promote image a4c52389 is merged to main at c3c5e7633f0d88b7b374174d345eae6f13f3129c. I did not initiate the merge; I verified the post-merge gate after it landed.
• Check state: post-merge argo-lint, kubeconform, and jangar-post-deploy-verify are green.
• Rollout evidence: jangar-post-deploy-verify reported Argo sync=Synced health=Healthy revision=c3c5e7633f0d88b7b374174d345eae6f13f3129c desired=c3c5e7633f0d88b7b374174d345eae6f13f3129c.
• Runtime evidence: the Jangar pod is Running with image registry.ide-newton.ts.net/lab/jangar:a4c52389@sha256:8cd77a9dad5d0d9654b0c6131e2def641d1081c206d8a48d72671b4b679da7c3, and /health returns status=ok.
• Rollback path: revert promotion commit c3c5e7633f0d88b7b374174d345eae6f13f3129c; if the source behavior regresses, revert feat(jangar): surface failure-domain lease holdbacks #5454 commit a4c52389366f74e58e0adfaa68be2e2c70e0dbab through the normal PR/GitOps path.