test(spec): re-measure the two declared test budgets over 11 executed hourly runs (#23937)

Part of #23180
Clause-②: no

The census reads two declared test budgets over their lines, and the
refresh lane lists both files again. This PR re-measures them and raises
each `// test-budget:` header line under ruling record `6181973363` item
2: the measured CI reading x 1.25, rounded up to the next 10 s. #23180
stays open for its other rows. This PR covers only these two
declarations.

## Re-measure

The window is the 25 newest hourly scheduled `ci.yml` runs,
`38731551915` (2026-10-15 12:01Z) to `38897680323` (2026-10-16 12:01Z).
Each run's `Test Core` aggregator job log has a "Slowest 20 test files"
table. Both files appear in it in all 25 runs.

- **Executed runs (11).** Both files are "measured here", and
`@objectstack/spec` is in the executed-package list: `38731551915`,
`38798542648`, `38806610561`, `38820912723`, `38833767749`,
`38838260718`, `38848429828`, `38858901527`, `38865071010`,
`38877591164` and `38891051243`.
- **Replayed runs (14).** Both rows are "replayed log", and spec is in
the cache-replayed line. `windowFiles` excludes replayed rows, so they
are not used here. Every replayed reading is below the executed maximum
anyway.

| file | declared | executed readings (11 runs) | window max (run) | x
1.25 | new line |
|:--|--:|:--|--:|--:|--:|
| `scripts/build-schemas-check-mode.test.ts` | 940 | 602.13 to 983.27 s
| 983.27 s (`38798542648`) | 1229.09 | **1230** |
| `scripts/liveness/check-liveness.test.ts` | 410 | 268.30 to 425.63 s |
425.63 s (`38798542648`) | 532.04 | **540** |

Per executed run (bscm / liveness / spec package, s):
- `38731551915`: 925.47 / 402.21 / 1472.49
- `38798542648`: 983.27 / 425.63 / 1560.24
- `38806610561`: 931.76 / 391.73 / 1479.72
- `38820912723`: 952.11 / 415.31 / 1519.43
- `38833767749`: 862.23 / 364.91 / 1354.93
- `38838260718`: 880.76 / 373.74 / 1390.17
- `38848429828`: 931.96 / 408.38 / 1480.63
- `38858901527`: 602.13 / 268.30 / 969.79
- `38865071010`: 934.23 / 400.05 / 1482.89
- `38877591164`: 682.05 / 287.41 / 1070.92
- `38891051243`: 938.80 / 396.15 / 1490.03

## Why a raise and not a fix (Zone 2 hypothesis 2)

The growth is not repeated work, and no fixture was added:

- `build-schemas-check-mode.test.ts`, its producer `build-schemas.ts`,
and `liveness/check-liveness.mts` have no commit between the budget's
landing (`af255525c`) and `origin/main` `0744f9436`.
- `check-liveness.test.ts` has one commit in that range: `23d0bc78`
(#23776, 2026-10-16 03:14Z). It makes one existing case run the gate
twice instead of once. That commit landed **after** the over-budget
reading (run `38798542648`, head `9e0945cf`, 2026-10-15 20:01Z). Of the
executed readings after it, the highest is 408.38 s, which is under the
old 410 line.
- The file's wall follows the run's load. Across the 11 executed runs,
bscm is 0.62 to 0.64 of the spec package wall (969.79 to 1560.24 s),
which moves with how much of the workspace the run executes. The old
lines came from **three** executed runs (`38636949152`, `38651452634`,
`38657693085`; PR #23613). This window has eleven, and the busiest of
them reads above the old lines.
- The earlier measurements on this card (report `6176173059`) found the
floors. bscm's floor is about 96 real generator runs at about 9 s each.
Liveness already has the per-run read memo from PR #23535. Neither file
repeats a cause another case already covers.

Each new line names the runs, the reading and why it rose, as item 2
requires.

## Verification

At `1c32e6be`:

- The refresh's own reader, `declaredBudgetInTree('@objectstack/spec',
FILE)` from `scripts/measure-test-shard-timings.mjs`, exits 0 and
returns `seconds: 1230` and `seconds: 540`, the class `spawns the real
producer once per single-cause fixture`, at `line: 2`. A malformed line
would refuse the whole weekly `--diff`, so both lines were read locally.
- `check-liveness.test.ts`, run as one file under `os-verify-lock`:
71/71 passed, 220.19 s, `VERDICT command-exit 0`. That wall is from a
shared box and is not a CI reading.
- `build-schemas-check-mode.test.ts` was **not run locally**. It takes
about 900 s and this PR changes only a comment line. CI runs it.
- No ablation: no tested behaviour changed (comment line only).
- Gates: the local subset from `dispatch-gates --commands` is in the dev
report on #23180.

## Acceptance notes

- Only the two header lines change. Every `expect` is byte-identical.
Nothing is deleted, no timeout is raised and no project is moved.
- Publish: `@objectstack/spec`'s `files[]` (read at `1c32e6be`) lists
`dist`, `json-schema`, `liveness`, `prompts`, `src/**/*.zod.ts` and
top-level docs. It has no `scripts` entry, so both files ship in no
tarball (PR #23613's `npm pack --dry-run` showed 0 files under
`scripts/`). `skip-changeset` applies.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01VBiW3UCZSxPyRLHAMTnHHD)_

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: objectstack-fleet[bot] <332303061+objectstack-fleet[bot]@users.noreply.github.com>

Author: objectstack-fleet[bot]

packages/spec/scripts/build-schemas-check-mode.test.ts

@@ -1,5 +1,5 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
-// test-budget: 940 — spawns the real producer once per single-cause fixture: every case runs the real schema generator (build-schemas.ts --check) in its own sandbox git tree, one fixture per cause; slowest CI reading 749.9 s (hourly run 38657693085) x 1.25, rounded up
+// test-budget: 1230 — spawns the real producer once per single-cause fixture: every case runs the real schema generator (build-schemas.ts --check) in its own sandbox git tree, one fixture per cause; re-measured 2026-10-16 over the 11 hourly runs that executed it (38731551915 to 38891051243): slowest CI reading 983.3 s (run 38798542648) x 1.25, rounded up; rose from 940, which rested on 3 executed runs, with the file unchanged: its wall tracks the run's load (spec package 969.8 to 1560.2 s in the same runs)
 //
 // Pins that `build-schemas.ts --check` — the script behind
 // `check:authorable-surface`, one of the eight generated-artifact gates

packages/spec/scripts/liveness/check-liveness.test.ts

@@ -1,5 +1,5 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
-// test-budget: 410 — spawns the real producer once per single-cause fixture: each case spawns the real liveness gate (check-liveness.mts) on a ledger copy with exactly one cause for its verdict; slowest CI reading 320.4 s (hourly run 38657693085) x 1.25, rounded up
+// test-budget: 540 — spawns the real producer once per single-cause fixture: each case spawns the real liveness gate (check-liveness.mts) on a ledger copy with exactly one cause for its verdict; re-measured 2026-10-16 over the 11 hourly runs that executed it (38731551915 to 38891051243): slowest CI reading 425.6 s (run 38798542648) x 1.25, rounded up; rose from 410, which rested on 3 executed runs, with the file unchanged before that reading: its wall tracks the run's load (spec package 969.8 to 1560.2 s in the same runs)
 //
 // Self-test for the liveness gate's EVIDENCE guard (#5623).
 //