fix(autofix): carry the raised repair bounds through sibling prose

Author: qwen-code-dev-bot

.github/scripts/run-autofix-review-verification.sh

@@ -119,7 +119,7 @@ reject_fix() {
   if [[ "${preexisting}" == 'true' ]]; then
     # NOT retryable: the repair agent is only allowed to amend this round's
     # fix, and a failure that exists without the fix is outside that boundary
-    # by definition — the 18-minute repair budget cannot reach it. The remedy
+    # by definition — the 45-minute repair budget cannot reach it. The remedy
     # is a base update (merge main into the branch), not a repair.
     echo "preexisting=true" >> "${GITHUB_OUTPUT}"
   elif [[ "${retryable}" == 'true' ]]; then
@@ -1047,7 +1047,7 @@ fi
 # a DEFECT-CLAIM round only when resolved-comments.txt marks a finding
 # resolved-in-code whose thread is Critical-tagged or belongs to a
 # CHANGES_REQUESTED review (matched in rc.json/rv.json). Those rounds get a
-# non-retryable rejection on all-green — the 18-minute repair pass cannot
+# non-retryable rejection on all-green — the 45-minute repair pass cannot
 # make a nonexistent defect reproduce; the next full round re-reads the
 # feedback with the evidence in LAST_REJECTION and can decline or escalate
 # instead. Every OTHER src+test round (a refactor pinning existing

.github/workflows/qwen-autofix.yml

@@ -2173,7 +2173,7 @@ jobs:
     # Keep the predicate as narrow as the job's own `if:` — concurrency is
     # evaluated BEFORE it, so without the do_review conjunct a dispatch with
     # `phase: issue` + `pr_number: N` (route emits pr_number unconditionally)
-    # would park this skipped job in that PR's shared slot behind a 300-minute
+    # would park this skipped job in that PR's shared slot behind a 330-minute
     # address round, stalling the issue phase that `needs` it.
     concurrency:
       group: "qwen-pr-head-write-${{ needs.route.outputs.do_review == 'true' && needs.route.outputs.pr_number || github.run_id }}"
@@ -2776,7 +2776,7 @@ jobs:
             # The dispatch-pending marker is exempted by context: it is this
             # loop's own StatusContext busy signal (no .workflowName/.name, so
             # it passes the filters above) and its dedicated TTL check above is
-            # the authority on it — the 330-minute horizon here would keep a
+            # the authority on it — the 360-minute horizon here would keep a
             # stranded marker blocking long past its TTL.
             HAS_PENDING_CHECKS="$(jq -r --arg cut "${PENDING_CUTOFF}" \
               --argjson nonblocking "${NON_BLOCKING_CHECKS}" \
@@ -3888,7 +3888,7 @@ jobs:
               ;;
           esac
           # The label routing pins ecs-qwen, but a mis-labelled registration
-          # must not silently claim a PAT-bearing 300-minute job — assert the
+          # must not silently claim a PAT-bearing 330-minute job — assert the
           # pool by name on the self-hosted branch too.
           if [[ "${RUNNER_ENVIRONMENT}" == 'self-hosted' ]]; then
             case "${RUNNER_NAME}" in

scripts/tests/qwen-autofix-workflow.test.js

@@ -4144,7 +4144,7 @@ describe('qwen-autofix workflow', () => {
     // No rollup entries → dispatchable.
     expect(runMarkerCheck([])).toBe('pass');
 
-    // A stranded marker must NOT keep blocking through the 330-minute
+    // A stranded marker must NOT keep blocking through the 360-minute
     // HAS_PENDING_CHECKS gate after its TTL expired: replay the gate's jq
     // over fixture rollups.
     const pendingGate = reviewScanJob.match(
@@ -4194,7 +4194,7 @@ describe('qwen-autofix workflow', () => {
         checkRun('build', 'IN_PROGRESS', '2026-08-17T07:50:00Z'),
       ]),
     ).toBe('true');
-    // ...a check stuck past the 330-minute horizon is aged out...
+    // ...a check stuck past the 360-minute horizon is aged out...
     expect(
       runPendingGate([
         checkRun('build', 'IN_PROGRESS', '2026-08-17T01:00:00Z'),