diff --git a/docs/titan_20_21_22_capacity_optimization.md b/docs/titan_20_21_22_capacity_optimization.md
index 41a219ed..524a6a24 100644
--- a/docs/titan_20_21_22_capacity_optimization.md
+++ b/docs/titan_20_21_22_capacity_optimization.md
@@ -2,25 +2,32 @@
 
 Status: evidence-led audit + guardrails shipped. **No workload was relocated
 onto titan-22 by this card/PR.** Between this audit's first pass and this
-revision, Brad independently placed three workloads (Jenkins, VictoriaMetrics,
-Wger) onto titan-22 via direct commits to `main` (outside this card's PR),
-implementing almost exactly the Option B pattern this document recommends.
-§4a documents that live change and the fresh evidence validating it. This
-document is the durable record for Kanban card `t_26da4c88`.
+revision, Brad independently placed four workloads (Jenkins, VictoriaMetrics,
+Wger, SonarQube) onto titan-22 via five direct commits to `main` (outside
+this card's PR), implementing almost exactly the Option B pattern this
+document recommends. §4a documents that live change and the fresh evidence
+validating it. This document is the durable record for Kanban card
+`t_26da4c88`.
 
-Evidence collected in two passes:
+Evidence collected in three passes, each triggered by discovering `main`
+had moved again mid-audit:
 - **First pass** 2026-08-23 13:00-13:30 UTC, at `origin/main@a019ecd55`,
   covering a trailing-24h VictoriaMetrics window ending ~13:15Z (the longest
   valid window since titan-22's return to service — node manifests show the
   current `jellyfin` restore commit reconciling from 2026-08-23T01:11Z).
 - **Revalidation pass** 2026-08-23 ~14:40-14:45 UTC, after `git fetch
   --no-tags origin main` showed this branch was 4 commits behind a
-  fast-moving `main` (`origin/main@42795f3d6`); the branch was rebased onto
-  it (clean, no file overlap with the audit's own commit). This pass queried
-  VictoriaMetrics directly (`victoria-metrics-single-server.monitoring.svc.cluster.local:8428`,
-  in-cluster) for current + trailing-3h data, since 3 of the 4 new commits
-  changed placement for Jenkins/VictoriaMetrics/Wger only ~1-3h before this
+  fast-moving `main`; rebased cleanly (no file overlap with the audit's own
+  commit) onto `origin/main@42795f3d6`. Queried VictoriaMetrics directly
+  (`victoria-metrics-single-server.monitoring.svc.cluster.local:8428`,
+  in-cluster) for current + trailing-3h data, since 3 of the commits
+  changed placement for Jenkins/VictoriaMetrics/Wger only 1-3h before this
   pass — see §4a.
+- **Final pass** 2026-08-23 ~14:56 UTC: `main` advanced once more
+  (`17c5f5093`, a 4th direct placement commit moving SonarQube onto
+  titan-22) while this document was mid-revision; rebased again (clean) and
+  folded in as a 4th row in §2/§4a rather than shipping a report that was
+  already stale at open time.
 
 Both passes used `kubectl` as `system:serviceaccount:hermes:hermes-agent`
 (per-namespace `get/list/watch` on pods/deployments/statefulsets/daemonsets;