diff --git a/scripts/ci/contextual_orchestrator_review_sidecar.sh b/scripts/ci/contextual_orchestrator_review_sidecar.sh
index e4984f643b..fc5686cf26 100755
--- a/scripts/ci/contextual_orchestrator_review_sidecar.sh
+++ b/scripts/ci/contextual_orchestrator_review_sidecar.sh
@@ -428,9 +428,16 @@ printf '{"model":"%s","messages":[{"role":"system","content":"You are a helpful
 # in 18s, then this identical request against that same healthy route being
 # cut off by curl's own timeout at exactly 30.0s -- "gateway preflight
 # request could not reach the local sidecar" is this curl failure, not an
-# actual connectivity problem. This required-workflow job already budgets
-# 120 minutes (see timeout-minutes in strix.yml/noema-review.yml), and the
-# org's own stated policy accepts multi-hour central review latency in
+# actual connectivity problem. The calling job's own outer bound already
+# gives multi-hour headroom for this required-workflow job regardless of
+# which caller invokes this script: strix.yml's job-level timeout-minutes
+# is 200; noema-review.yml's `noema-review` job and pr-review-autofix.yml's
+# job that runs this script both set no job-level timeout-minutes at all,
+# so their outer bound is GitHub Actions' own 360-minute default. Do not
+# assume this list of callers or their timeout values is exhaustive or
+# durable -- check each caller workflow directly rather than trusting this
+# comment if it matters at the time of reading. Either way, the org's own
+# stated policy accepts multi-hour central review latency in
 # favor of accuracy over speed -- a 30s bound on one preflight self-check
 # contradicted that policy and rejected a route the routing probe had just
 # proven healthy. 120s keeps this a bounded, fail-closed check while giving