test(lint): compute the SYSTEM_FIELDS live census once per file, under its own hook timeout

[objectstack-fleet]

Fixes #19807

Clause-②: no

What is red and why

The hourly full run on main (run 35829772446, Test Core (2/6) on de4ed33f) failed on exactly one test: packages/lint/src/system-fields-consumers.test.ts:586 (the #8999 SYSTEM_FIELDS consumer census, 「the live population › is anchored to a real export…」) — Error: Test timed out in 5000ms. The shard then stopped and six scheduled packages never ran. The same failure, same shard, same test, is the only red in the last 100 hourly runs (09-21 04:01Z, 09-21 16:00Z, 09-23 07:03Z); no commit between the last green run (fae870352) and the red head touches packages/lint/**, and the file is green on PR shards, where @objectstack/lint runs with few neighbours.

Cause, read from the file: liveSources() reads every .ts under packages/lint/src (201 files) and censusUnionConsumers parses each with the TypeScript compiler (setParentNodes: true); the six live tests each recomputed that whole census under vitest's default 5,000 ms per-test wall, and the cold run crossed it on a loaded full-battery shard (13 packages, --concurrency=4 on 4 vCPUs).

What changed

One file, test-only: the live census is computed ONCE per file in a beforeAll that carries its own explicit timeout (60,000 ms, sized from the measured cold run of ~1 s on a quiet box with headroom for a contended shard), and the six live tests read that one result. censusUnionConsumers, liveSources(), the LEDGER rows, the PROVENANCE_API pin and every assertion are unchanged; no walk is narrowed, no test skipped, no file-wide or package-wide testTimeout raised.

Verification

• Branch pushed by the dispatched dev (session_01XPUwWGnmky4PXPofNsf2w7); its report with the measured before/after durations follows on hourly full run: red on main (CI) #19807.
• CI on this head is the judge: Test Core shards (the @objectstack/lint package suite), Lint & Repo Gates, type checks.
• Not governed (packages/lint/src/** is on no register surface); ordinary queue landing after the dispatching seat's ACCEPT.

Related, not changed here: #16465 / #16468 (shard-duration alarm and per-package suite-duration ratchet, pm:queue in domain:devx), and ten other test files that walk directories or parse with the TypeScript compiler under the default wall (cli ×5, spec ×4, service-analytics ×1) — none has gone red; the same one-computation shape applies if one does.

🤖 Generated with Claude Code

https://claude.ai/code/session_0129ZpnaBcYZZ51rCvQiXg6C

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 0 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 0 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 502f179cc70f82c5a5c54783100736e7d4da8d44 → packageMentionDocs.