@@ -134,8 +134,37 @@ jobs:
           node-version: '22.x'
           cache: 'pnpm'
 
-      - name: Turbo Cache
-        uses: actions/cache@v6
+      # ── Cache bookkeeping cannot void a recorded verdict (objectui#7048) ──
+      # THE ORDERING, carried here from the type-check split in `ci.yml`
+      # (objectui#6577, PR #7047) because it is what a future reader needs in
+      # order to judge whether these steps may be touched: the verdict is
+      # recorded by the checking steps; everything after them is bookkeeping,
+      # and bookkeeping must never discard an answer the gate already produced.
+      #
+      # Why the SPLIT rather than a timeout on one step: combined
+      # `actions/cache` declares `main: dist/restore/index.js` plus
+      # `post: dist/save/index.js`, so its save is a step the RUNNER generates
+      # at job end (`Post Turbo Cache`). No workflow syntax attaches
+      # `timeout-minutes` or `continue-on-error` to a generated post step.
+      # Measured once, on `ci.yml`'s type-check cache: a 1-second save took
+      # 789s, ran that job into its ceiling, and the resulting `cancelled` —
+      # which the merge queue cannot tell from `failure` — ejected an all-green
+      # pull request (objectui#6577). `actions/cache`'s own `save-always`
+      # deprecation text points at this same split.
+      #
+      # ⚠️ This job declares NO `timeout-minutes`, so its ceiling is GitHub's
+      # default of 360 minutes, and `Bundle Analysis` is a required context
+      # (objectui#6245). A stalled save would therefore hold a required check
+      # open for up to six hours before reporting `cancelled`. ⛔ Adding a
+      # ceiling is NOT the fix and is not attempted here — it would change what
+      # this gate rejects. The bound below is on the bookkeeping step alone.
+      #
+      # The restore half is deliberately left UNBOUNDED: a restore stall fails
+      # BEFORE any verdict exists — a gate that did not run, which is honest —
+      # rather than a recorded verdict discarded.
+      - name: Restore Turbo Cache
+        id: turbo-cache
+        uses: actions/cache/restore@v6
         with:
           path: .turbo/cache
           key: turbo-${{ runner.os }}-${{ github.sha }}
@@ -470,3 +499,39 @@ jobs:
               core.warning(`Could not comment on PR: ${error.message}`);
               await core.summary.addRaw(body).write();
             }
+
+      # The bookkeeping half of the split documented at the restore step above,
+      # placed HERE — last in the job, after the budget verdict AND after the
+      # comment that reports it — because that is exactly where the post phase
+      # it replaces already ran. Nothing about which commits this gate accepts
+      # or rejects moves with it.
+      #
+      # `timeout-minutes: 5` is DERIVED FOR THIS SITE, and landing on the same
+      # number PR #7047 chose is a result rather than a copy — objectui#7048
+      # fences inheriting that 5, so here is this site's own arithmetic. This
+      # job's own save of this cache measured 1s on 2026-09-02 (`Post Turbo
+      # Cache`, job 100096569559); the whole job was 4m07s. 5 minutes is 300x
+      # the measured save — the same ratio #7047 sized its bound at, arrived at
+      # from this job's own number.
+      #
+      # `continue-on-error: true` is the other half, and without it the bound
+      # would only trade a `cancelled` gate for a red one. A cache that failed
+      # to upload costs the next run some time; it says nothing whatsoever
+      # about the bundle sizes under test, so it must not speak for them.
+      #
+      # Behaviour preserved, spelled out so the equivalence is checkable:
+      #   - `cache-hit != 'true'` reproduces the combined action's own "exact
+      #     hit on the primary key ⇒ do not save" skip. A `restore-keys` prefix
+      #     match leaves `cache-hit` false and the save still runs, exactly as
+      #     the combined action behaved.
+      #   - the condition names no status function, so the implicit `success()`
+      #     still applies — matching the combined action's `post-if: success()`.
+      #   - same `path` and same `key` as the restore step above.
+      - name: Save Turbo Cache
+        if: steps.turbo-cache.outputs.cache-hit != 'true'
+        uses: actions/cache/save@v6
+        timeout-minutes: 5
+        continue-on-error: true
+        with:
+          path: .turbo/cache
+          key: turbo-${{ runner.os }}-${{ github.sha }}