docs(jangar): record control plane release verification

[gregkonush]

Summary

• Adds the Jangar control-plane release verification audit for 2026-05-05.
• Records the merged selected PRs, the current open PR inventory, the blocked feat(jangar): surface failure-domain lease holdbacks #5454 Codex review gate, and adjacent Torghut gate state.
• Documents live rollout evidence for the fix(jangar): reconcile swarms from agentrun events #5521/chore(jangar): promote image a1b55322 #5525 Jangar path, including pod readiness, /health, residual DB warnings, Kubernetes API 429s, and RBAC limits.
• Captures rollback guidance for reverting chore(jangar): promote image a1b55322 #5525 image promotion if the app becomes unready again.

Related Issues

None.

Testing

• bunx oxfmt --check docs/agents/rollouts/2026-05-05-jangar-control-plane-verify.md - pass
• git diff --check - pass
• gh pr checks 5454 -R proompteng/lab - pass/skipped checks only, but merge blocked by missing Codex review
• kubectl get pods -n jangar -o wide - Jangar pod Ready with app restart count stable at 3 during the 18:55Z recheck
• kubectl get pod -n jangar jangar-584d75f4f6-zt9b2 -o jsonpath=... - live image is tag a1b55322 digest sha256:cf398e6ab1dd7cc9df5a99bac655a90678d5acaace5ec7ba5b908ff9ee3d1478, pod conditions Ready
• curl -fsS --max-time 10 http://jangar.jangar.svc.cluster.local/health - returned ok
• kubectl get events -n jangar --field-selector type=Warning --sort-by=.lastTimestamp - residual Jangar backoff/readiness and jangar-db-1 readiness 500 warnings observed
• kubectl logs -n jangar pod/jangar-584d75f4f6-zt9b2 -c app --since=10m --tail=80 - residual Kubernetes API 429s, unresolved worktree snapshot refresh failures, and ClickHouse freshness query timeouts observed

Screenshots (if applicable)

N/A.

Breaking Changes

None.

Checklist

• Testing section documents the exact validation performed (or N/A with justification).
• Screenshots and Breaking Changes sections are handled appropriately (removed or filled in).
• Documentation, release notes, and follow-ups are updated or tracked.

[gregkonush]

Status: audit PR merged as of 2026-05-05T19:05Z. #5532 was squash-merged at 2026-05-05T19:00:09Z as 4f4e37372f7b1dc8144ad273b331b76c1ea8a421 after the refreshed head checks were green.

• PR inventory: fix(torghut): restore live jangar dependency quorum #5376, ci: stabilize agents and jangar checks #5364, fix(torghut): restore rollout readiness #5387, fix(jangar): reconcile swarms from agentrun events #5521, chore(jangar): promote image a1b55322 #5525, chore(jangar): promote image 919848c1 #5538, and docs(jangar): record control plane release verification #5532 are merged with pass/skipped final check rollups; feat(jangar): surface failure-domain lease holdbacks #5454 is open, clean, green, and blocked by the required >1,000-line Codex review; adjacent feat(torghut): add renewal bond profit escrow #5412 is blocked by the same review gate; adjacent revert(torghut): roll back image 7e2fb9ce #5537 is now merged.
• feat(jangar): surface failure-domain lease holdbacks #5454 gate: GitHub reports MERGEABLE/CLEAN, 1,538 additions and 4 deletions, no review threads, no posted reviews, and connector usage-limit responses to Codex review requests.
• Live Jangar evidence: after chore(jangar): promote image 919848c1 #5538, pod jangar-847d6d7f8d-zx5sq is 2/2 Running, app restart count stayed at 0 through the 19:05Z stability recheck, image tag 919848c1 digest sha256:8651851a0b5baef46b9a10f933a56473313f3028658d41e1b68a73289cc9fd57, pod conditions Ready, and /health returns ok.
• Residual rollout risk: this runner is RBAC-forbidden from Argo CD Application and Deployment rollout reads; warning events still include a recent jangar-db-1 readiness HTTP 500 and the initial chore(jangar): promote image 919848c1 #5538 pod readiness miss before it became Ready; app logs were quiet for the two minutes before 19:05Z.
• Local validation: bunx oxfmt --check docs/agents/rollouts/2026-05-05-jangar-control-plane-verify.md passed, and git diff --check passed.

Gate decision: #5532 is merged and the latest Jangar workload rollout is healthy by pod and HTTP evidence. The broader Jangar release gate remains no-go until #5454 receives a Codex review with all threads resolved or a maintainer explicitly waives the large-diff review gate; full GitOps sync certification also requires Argo/Deployment read RBAC.