[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYog9FzTNeBAndKHXTT

Fixes #27283
Part of #26080
Clause-②: no
Metadata-protocol: none
Ruling-ref: 6513291766 (director#1 · os-bill; #27283 letter A, maintainer 「其他同意」) — the ci.yml authorisation. Quoted: "the six ui-root build inputs that PR #27571 adds to the root turbo.json … also enter .github/workflows/ci.yml's core: path filter, in the same PR, so a diff confined to one of them schedules Build Core and Test Core on the PR instead of first in the merge queue, and check-ci-filter-parity is green by parity, not by blindness."
Tier H: .github/workflows/ci.yml (ruled) and .github/workflows/lint.yml (one gate-forced line, seat authorisation 6513792547).

维护者速读

• 改了什么：根 turbo.json 的 build/test 任务现在把 ui 树根部被各 @object-ui/* 包真实读取的文件(ui/tsconfig.json、ui/scripts/vite-*.ts、vitest 配置与 setup 等)计入缓存键；守卫全部改读这份真实配置，删除无人读取的 ui/turbo.objectui.json。按裁决 A，这 6 个 ui 根目录构建输入同时写进 ci.yml 的 core: 过滤器；lint.yml 因此补一行，让门禁要求的 ui/scripts/invoked-as.mjs --self-test 有 workflow 来跑。
• 为什么改：此前改动这些文件不会让 turbo 缓存失效，CI 或发版可能回放旧的构建产物；而守卫读的是一份停用副本，所以一直是假绿。
• 风险与回滚：所有 @objectstack/* 与 @object-ui/* 的 build/test 缓存键一次性变化(253 个中 243 个)，首轮 CI 冷构建；改动这 6 类文件的 PR 会多跑一次 Build Core 和 Test Core（按过去 30 天约 9 次）。碰 ci.yml 和 lint.yml，属 Tier H。只改配置与测试，不改运行时代码，回滚即 revert 本 PR。
• 先看：.github/workflows/ci.yml 的 core: 新增 6 行，以及 lint.yml 第 843 行旁新增的一行 → turbo.json(build/test 两段新增输入)→ ui/scripts/__tests__/turbo-lint-inputs.test.ts 与 e2e-type-check.test.ts(两个根任务守卫改为对照 ci.yml 步骤)→ ui/scripts/__tests__/turbo-task-guard-coverage.test.ts(任务范围收到本树)。
• 两分钟验证：pnpm exec turbo run build --filter=@object-ui/components --dry=json，在该任务的 inputs 里应能看到 ../../scripts/vite-dts-explicit-extensions.ts 与 ../../tsconfig.json。
• 需要你做的：Tier H，需要授权批准。os-zhuang 已批准（review 5707021648），推送不会让批准失效；同 head 达档契约复核 PASS 后，席位翻 ready 并挂自动合并。

What changes

• Root turbo.json, option A. build gains the six ui-root files every @object-ui/* build reads (ui/tsconfig.json, ui/scripts/vite-*.ts, build-plugin-stylesheet.mjs, check-dist-completeness.mjs, invoked-as.mjs, vitest-invocation-guard.mjs). test gains the seven its Vitest configuration program reads (ui/vitest.config.mts, ui/vitest.setup.*, vitest-invocation-guard.mjs, test-shard-*, vite-*.ts, the Console's vitest.config.ts and vite.config.ts). Each entry is required by the derived guards, which refuse an entry no package program reads.
• Why A over B (measured, below). B, a package-level turbo.json in each ui package, moves 82 of 253 build/test hashes against A's 243. But it needs 39 new files, each carrying the same list, plus a per-package config composer inside the guards. It also cannot cover the ui root package without a ui/turbo.json, which workspace-root.mjs would then read as the tree's own config. A keeps one list, in the file turbo reads, and the guards read it unchanged through liveTurboConfig(). A's recurring cost is that an edit to one of these files also invalidates the @objectstack/* entries. Over the last 30 days, 9 of 3513 commits on main touched these files.
• Guards retargeted, no assertion loosened. turbo-build-inputs, turbo-test-inputs, check-dist-completeness (its build-input case), turbo-build-outputs-cover-published-entries, turbo-task-guard-coverage and select-type-check-scope now read the live config. taskInputs() and rootAnchoredInputs() now default to it, and parkedTurboConfig() is gone.
  • turbo-task-guard-coverage draws its partition over the tasks turbo runs on a package of this tree: a generic task some ui manifest declares a script for, or a PKG#TASK override for a ui package. That set is exactly what the parked copy declared. A new liveness case pins the four guarded tasks as the floor.
  • ui/apps/console/turbo.json now restates the root build.outputs, adding json-schema/** and !.next/cache/**. The outputs guard, read against the live root, found that it narrowed them.
• Root-task guards, rewritten against the ci.yml step that runs each task (a read of ci.yml, no workflow edit):
  • //#lint:root is now a pin on lint-ui's pnpm --dir ui run lint:root step:
    • The step exists, runs exactly the script, and has no if:.
    • The live lint task folds in no //# task's hash.
    • The ignored workspace groups are exactly the groups the turbo lint step filters in.
    • Every file ESLint walks at that scope sets the ui paths filter.
    • The step is the script itself, so no cache can replay it.
  • //#type-check:e2e gets the same pins on type-check-ui's pnpm --dir ui run type-check:e2e step. The filter-coverage pin there is over the e2e program's files.
  • select-type-check-scope's root-task case (rule item 4) runs on objectui's own shape of that task as a fixture, inputs verbatim. Under the live config there is no root task left for it to read.
• .github/workflows/ci.yml, ruled (6513291766): six core: rows plus a four-line comment, after the BUILD INPUTS (ci: the core path filter skips Build Core for build-input-only PRs (scripts/**, root tsup.config.ts, turbo.json) — a broken build first surfaces in the merge queue #21202) rows. They are the same six ui-root build inputs. check:ci-filter-parity went from 5/120 failed to 120/120 green, and it demanded exactly these six, with no test inputs.
• .github/workflows/lint.yml, gate-forced (seat authorisation 6513792547): one line, run_self_test node ui/scripts/invoked-as.mjs --self-test, beside the root twin at L843. check-self-test-wired counts the new core: row as CI naming that script, and its own remedy is to wire the script's self-test, which passes with 12 cases. No SELF_TEST_RUN_OTHERWISE row.
• Deleted: ui/turbo.objectui.json, PARKED_TURBO_CONFIG and uiTurboConfigPath(), with its declaration and tests. After the retarget, git grep finds no reader.

Tests

• pnpm --dir ui exec vitest run --maxWorkers=2 scripts/ on head 47d861189, under os-verify-lock: Test Files 169 passed | 2 skipped (171), Tests 4900 passed | 2 skipped (4902), VERDICT command-exit 0. No failures, so no baseline-failure set.
• The touched reader files, untouched origin/main (ad3a640e3) vs this branch: 324/324 → 323/323. Every file keeps its count except turbo-task-guard-coverage, which goes 15 → 14:
  • Retired: its two cases "//#lint:root / //#type-check:e2e is exempt because turbo never caches it". They are retired under the test-deletion rule. Their duplicates are "stays uncached: the step is the script itself" (turbo-lint-inputs.test.ts) and "is uncached: the step is the script itself" (e2e-type-check.test.ts). Both pin the property on the CI step that actually runs each task.
  • Added: one case, the partition-scope liveness.
• pnpm --dir ui run type-check:scripts: exit 0, and --listFilesOnly shows all five changed test and helper files in that program. eslint over the changed .ts/.mjs files: exit 0.

Acceptance notes

• ui/scripts/select-type-check-scope.mjs has no caller in any root workflow: helpers/root-ci.ts records the selector as not ported. So its test holds a function nothing runs in the monorepo. Noted, not filed.
• First ablation-replace attempt (teeth 2 below) was refused by the tool: the replacement text was already counted inside the anchor, so nothing ran and the restore was proven. It was re-run with --delete.

Verification

Reproduction on origin/main ad3a640: root-anchored inputs of @object-ui/components#build

pnpm exec turbo run build --filter=@object-ui/components --dry=json: hash 587292e7374b7756, out-of-package inputs only ../../../scripts/check-dts-emitted.mjs, ../../../scripts/invoked-as.mjs, ../../../scripts/tsup-drop-sources-content.mjs. ui/packages/components/vite.config.ts:14-15 imports ../../scripts/vite-dts-explicit-extensions.ts and ../../scripts/vite-dts-fail-on-type-errors.ts.

After: hash ba59da9212bafc37. The same 3, plus ../../tsconfig.json, ../../scripts/build-plugin-stylesheet.mjs, check-dist-completeness.mjs, invoked-as.mjs, vitest-invocation-guard.mjs and the nine ../../scripts/vite-*.ts.

Probe: the live config substituted for the parked one, on origin/main

144 assertions red in 8 files: turbo-build-inputs 37, turbo-test-inputs 39, turbo-task-guard-coverage 55, turbo-lint-inputs 5 (the //#lint:root block), e2e-type-check 4 (the wiring block), select-type-check-scope 2, check-dist-completeness 1, turbo-build-outputs-cover-published-entries 1 (Console narrowing the root outputs). The slice-2 reading was 147, against an older tree. On this branch: 0 red.

Blast radius: turbo run build test --dry=json, 253 tasks, before vs after

• A (this PR): 243 changed. ui build 41/41, ui test 41/41, objectstack build 81/85, objectstack test 80/85 (the unchanged ones carry their own package-specific task entry), gen:migration-registry 0/1.
• B (prototype: $TURBO_EXTENDS$ package configs in 39 ui packages plus the Console's, measured and then deleted): 82 changed. ui build 41/41, ui test 41/41, objectstack 0.

Teeth: edit one newly hashed file, read the task hash, restore (blob equal to HEAD)

file edited	task	this branch	origin/main (control)
ui/scripts/vite-dts-explicit-extensions.ts	@object-ui/components#build	ba59da92… → bbfca15d… MOVED	587292e7… → 587292e7… FROZEN
ui/tsconfig.json	@object-ui/core#build	53f30662… → 55610587… MOVED	400845ca… FROZEN
ui/vitest.config.mts	@object-ui/core#test	c2e38df8… → 07fa7ffa… MOVED	91b1052e… FROZEN
ui/scripts/vitest-invocation-guard.mjs	@object-ui/core#test	c2e38df8… → 23c18cd8… MOVED	91b1052e… FROZEN

Each probe appended one comment line, with the on-disk count of the probe line checked at 1. Each file was restored through a trap and proven by blob hash.

Guard teeth: ablation-replace on turbo.json, restored to the HEAD blob 87fdc7914587

1. Deleting the build entries $TURBO_ROOT$/ui/scripts/vite-*.ts and build-plugin-stylesheet.mjs (anchor 1 → 0) made turbo-build-inputs go 22 failed | 21 passed (43), naming the Console, components and fields programs.
2. Adding "dependsOn": ["//#lint:root"] to lint made turbo-lint-inputs go 1 failed | 51 passed (52), on the case "folds no root-task hash into any package lint".

Derived gates on d5f83e0 (current head)

After merging origin/main (166 commits, clean) and adding the ci.yml and lint.yml lines: dispatch-gates --commands derived 68 commands, and all exit 0. check:dual-build-cjs-loads is now measured and green. --ran reports 0 NOT-MEASURED. check-self-test-wired (self-test and scan) and check:ci-filter-parity are both green. The full ui scripts/ suite: 169 files, 4901 passed, 2 skipped. Addenda 6513780805 and 6514155626.

Derived gates on 47d8611 (first head, superseded)

node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 31 commands. Each was run with its exit captured before any pipe: 30 exit 0, and pnpm check:dual-build-cjs-loads exits 3. That is PREREQUISITE NOT MET: it reads every package's built dist/, and only the seven ui-consumer closures were built here, so it is NOT MEASURED locally and CI owns it. --ran: 31 derived famil(ies) accounted for — 30 run, 1 NOT-MEASURED (1 DERIVED from a recorded exit 3). node scripts/check-platform-checklist.mjs --changed-from origin/main: exit 0, 0 anchored files.

---

Generated by Claude Code

[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW

Seat note · head 47d8611899 · 2026-10-29T13:36Z · held, awaiting a maintainer ruling

Red: Lint · CI, release & engine gates › CI filter parity (cross-package Layer C), and the Lint & Repo Gates aggregator with it. It reproduces locally on this head:

✗ check-ci-filter-parity --self-test — 5 of 120 assertion(s) failed
  • the checked-in core filter covers every build input turbo.json declares -- ui/tsconfig.json, ui/scripts/vite-*.ts, ui/scripts/build-plugin-stylesheet.mjs, ui/scripts/check-dist-completeness.mjs, ui/scripts/invoked-as.mjs, ui/scripts/vitest-invocation-guard.mjs

Cause: this PR's. Option A adds the six ui-root files to the ROOT build inputs, so every @objectstack/* build hash now moves with them. The gate requires ci.yml's core: filter to name every build input, so that a change to one of them runs Build Core and Test Core. The gate is right.

Fix: add those six paths to core: in .github/workflows/ci.yml. That is a governed ci.yml edit, which the claim (6496953999) excluded and which needs the maintainer's ruling. The alternative is the dev's option B (ui package-level turbo.json files, no ci.yml edit), which the report measured and rejected. The seat put the choice to the maintainer in its session chat, recommending the core: addition.

Gate-derivation gap, noted for the record: the dev's dispatch-gates --commands run (report 6498038778) did not derive check:ci-filter-parity for a turbo.json diff. If that is a missing family mapping, a card follows.

---

Generated by Claude Code

[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW

Seat note · 2026-10-30T01:23Z · approval received, PR still held

os-zhuang's approval (review 5707021648) is recorded. Approvals here do not expire on a later push.

The PR stays draft and is not landed, for two reasons:

• Head 47d8611899 is red on one gate only, CI filter parity (cross-package Layer C), inside Lint · CI, release & engine gates (seat note 6498176893). The fix touches .github/workflows/ci.yml, and that edit needs a maintainer ruling.
• The ruling sits on decision card [devx] root turbo.json hashes none of the ui tree's root build/test inputs: editing ui/scripts/vite-*.ts or ui/tsconfig.json can replay a stale @object-ui/* build from cache #27283, analysis 6499206630, and no letter has been given yet. The seat recommends A: add the six ui-root build inputs to ci.yml's core: filter.

Once #27283 is ruled:

• A: the dev adds the six core: lines in this PR. The PR becomes Tier H and gets an at-tier contract review of the new head. After a PASS, the seat flips it ready and arms auto-merge on the approval already given.
• B or C: the seat re-dispatches as ruled.

The seat does not read an approval of a red head as a ruling on the card.

---

Generated by Claude Code

[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW

Contract-review-claim: session_01QSeKYmTYfaPbLQD4BJfomW · head d5f83e0 · 2026-10-30T02:56Z

The lane seat starts the at-tier contract review on this head with an isolated reviewer subagent. The Tier H face is .github/workflows/ci.yml (ruled by 6513291766) and .github/workflows/lint.yml (gate-forced, 6513792547).

---

Generated by Claude Code

[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW

Contract-review-handoff: triage — CONTRACT_REVIEW_TIER unavailable (HTTP 429 rate_limit on the reviewer model, 2026-10-30T02:57Z) · head d5f83e0

This act withdraws the lane's claim 6513834311 on this head. Per contract-review.md, the seat does not review at a lower tier, and needs:contract-review goes on in the same act.

The Tier H face (hits):

• .github/workflows/ci.yml: the six ui-root build inputs enter the core: filter, per ruling 6513291766 (letter A, maintainer 「其他同意」).
• .github/workflows/lint.yml: one line, run_self_test node ui/scripts/invoked-as.mjs --self-test beside L843. It is gate-forced: check-self-test-wired reds on the ruled core: row and names this line as its remedy. The seat authorised it in 6513792547.

Cited code to read: scripts/check-ci-filter-parity.mjs (L122–131), scripts/check-self-test-wired.mjs, and the root turbo.json inputs the rows mirror.

Inputs: dev reports 6498038778, 6513780805 and the latest addendum on #27283. The rest of the diff (root turbo.json, the ui guard retargets, the deleted ui/turbo.objectui.json) is the lane seat's ACCEPT at TIER_DEFAULT.

After a same-head PASS: the seat writes the seat record, then flips the PR ready and arms auto-merge on os-zhuang's existing approval (review 5707021648).

---

Generated by Claude Code

[objectstack-fleet]

triage#1 · os-sales · session_01L6bhgV4fMGJHSdSdx3u9mK

Contract-review-claim: session_01L6bhgV4fMGJHSdSdx3u9mK · head d5f83e05ee70d2f396cca7980cc2c51dcf0d0eb6 · 2026-10-30T05:02Z

---

Generated by Claude Code

[objectstack-fleet]

triage#1 · os-sales · session_01L6bhgV4fMGJHSdSdx3u9mK

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: d5f83e05ee70d2f396cca7980cc2c51dcf0d0eb6
Local-runs: none
Scope: .github/workflows/ci.yml, .github/workflows/lint.yml + turbo.json, scripts/check-ci-filter-parity.mjs, scripts/check-self-test-wired.mjs, scripts/check-step-collectors.mjs, ui/scripts/invoked-as.mjs

Inputs read: card #27283 (body and all 14 comments, ruling 6513291766 letter A included), PR #27571 (body, 17-file list, net diff against main at c4cb5ec0c3, all 5 PR comments including the withdrawn lane claim 6513834311 and the handoff 6513846981), and the 71 check-runs on d5f83e05ee. The rest of the diff (root turbo.json, ui/apps/console/turbo.json, the ten ui/scripts/** guard and helper files, the deleted ui/turbo.objectui.json) is the lane seat's ACCEPT at TIER_DEFAULT; it is read here where the two hits hunks cite it, never reviewed.

① Derived judgments

• Published accept set: unchanged — right. No packages/spec path, no exports map, no published .d.ts moves. The two deleted exports (PARKED_TURBO_CONFIG, uiTurboConfigPath() in ui/scripts/workspace-root.mjs) belong to the root script of object-ui-monorepo ("private": true); git grep on the head finds no reader of either or of turbo.objectui. @object-ui/console (18.2.0, published) changes only its turbo.json build outputs list (json-schema/**, !.next/cache/**): a cache-restore shape, not a shipped byte.
• CI scheduling accept set (ci.yml core:): widened by exactly six rows — right, and ruled. ui/tsconfig.json, ui/scripts/vite-*.ts, ui/scripts/build-plugin-stylesheet.mjs, ui/scripts/check-dist-completeness.mjs, ui/scripts/invoked-as.mjs, ui/scripts/vitest-invocation-guard.mjs are byte-for-byte the six $TURBO_ROOT$/ui/... entries the diff adds to the root build task. A diff confined to one of them now starts build-core, test-plan/test (ORed with crosspkg) and, on push, the jobs that read core. Every one of the six was already under the ui filter (ui/**), so the ui jobs ran on them before and still do.
• CI run set (lint.yml): one more self-test executes in lint-repo-tooling on every run — right. node ui/scripts/invoked-as.mjs --self-test (12 cases, node builtins only, no ui install needed). Before this head nothing in CI ran that copy's self-test.
• Cache keys: every generic build and test hash moves once (243 of 253 tasks, option A) — right, cost accepted by ruling 6513291766. Lane remainder; read because the core: comment claims it.

② Semver level

Label skip-changeset; PR body carries Clause-②: no and Metadata-protocol: none as line-initial declarations; Check Changeset concluded skipped on the label. Right: the diff publishes nothing from any released package — configuration (turbo.json ×2), workflows, and ui/scripts/** tests and helpers. No narrowing arm is declared and none is owed: no accepted input is refused anywhere. No changeset file, so the PR body is the sole carrier of the Clause-②: line, which is consistent with the label.

③ Boundary flags

• Dev report 6498038778 OQ1 (placement A vs B): answered. Triage 6484888145 asked for no second inputs list; ruling 6513291766 (letter A, maintainer 「其他同意」) bound A plus the six core: rows. The tree matches: one list in the root turbo.json, no new package-level ui turbo.json, and the six rows in ci.yml.
• Dev report 6498038778 OQ2 (signature line first vs os-dev-report marker first in .claude/agents/os-dev.md): escalated, outside this PR. The writer (post-stamped.mjs) enforces signature-first; the agent file says marker-first. A governed-prose amendment on its own card for the devx seat; nothing in this diff depends on it.
• Dev report 6513780805 OQ (remedy for check-self-test-wired red on the ruled row ui/scripts/invoked-as.mjs): answered. Seat 6513792547 authorised option A (the gate's own prescribed remedy, one lint.yml line); executed in d5f83e05ee; no SELF_TEST_RUN_OTHERWISE row, no gate change. The Lint · repo & tooling gates job on this head shows the shared-module self-tests step, the Step-collector gate and the Self-test wiring gate all success.
• Declared deviation, lint.yml +1 line outside the ruling's six ci.yml rows: authorised by the dispatching seat as gate-forced, on the reading that the maintainer's standing constraint and the ruling cover ci.yml. The PR is Tier H whole either way; Prime Directive feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14 lifts on an authorised approval on ANY commit, so os-zhuang's approval 5707021648 (given on 47d8611899, before both workflow hunks existed) stands by the letter. The seat record should say in so many words that the approval predates the governed hunks and that the landing click stays the maintainer's. Not a finding against the tree.
• Other declared deviations (worktree-hook block, turbo.json restored from HEAD and verified; model-free attribution pair per AGENTS.md): accepted, no residue in the diff.
• Out-of-scope findings (select-type-check-scope.mjs has no root-workflow caller; probe re-measured 144 vs 147): carried in the PR's Acceptance notes as the rule asks. The first is a dead-code observation, not a defect; a card is the seat's call.
• Seat note 6498176893, "gate-derivation gap" (dispatch-gates --commands did not derive check:ci-filter-parity for a turbo.json-only diff; "a card follows"): escalated. No card number appears on the card or PR thread; the seat confirms the card or files it. Not blocking: the gate itself ran red then green on this PR.
• PR author is objectstack-fleet[bot]; no out-of-relay author to name.
• Check-runs on d5f83e05ee: 71, every completed run success or skipped, none failure. Named gates: Lint · CI, release & engine gates (hosts check:ci-filter-parity, red on 47d8611899) success; Lint · repo & tooling gates (hosts the shared-module self-tests, the Step-collector gate and the Self-test wiring gate) success; Governed Surface Queue Guard, PR-body guards, Build Core, Test Core 8/8, Test UI 16/16, Type Check UI, Lint UI, Build & E2E UI, Live E2E UI, all four Type Check · lanes, all eight Lint · lanes, filter — success.

④ Design judgment

.github/workflows/ci.yml — holds. Judged against scripts/check-ci-filter-parity.mjs (third subject, header L122–131; buildInputsOf / judgeBuildInputs) and the root turbo.json the rows mirror. The gate derives the required set as turbo.json itself + globalDependencies + every $TURBO_ROOT$/... input of a build task pnpm build (turbo run build --filter=!@objectstack/docs) runs, and covers a path only when a core entry contains it verbatim or a prefix/** of its literal segments. Each of the six new rows is the verbatim string of its $TURBO_ROOT$ input, so coverage is by the sound limb, not by a pattern match the gate refuses to make; ui/scripts/vite-*.ts is one glob in both files and picomatch (the paths-filter matcher) reads * within one segment exactly as turbo does. The leftover rule is untouched: every new row is itself a declared build input. Placement is inside the BUILD INPUTS block, before the BUILD CORE'S GUARDS rows, with a comment whose claim I checked — the generic build task is the one every workspace package runs (pnpm-workspace.yaml lists ui, ui/packages/*, ui/apps/*, ui/examples/*), so a diff confined to one of the six moves Build Core's hashes. Scenario: a diff confined to one of the six now schedules Build Core and Test Core on the PR, and check:ci-filter-parity is green by parity (120/120 on this head; 5/120 red on 47d8611899). The ruling's one sentence is met, no more rows than ruled.

• Should-fix (a card, not this PR): the root test task gains seven $TURBO_ROOT$/ui/... inputs, five of which no core: row covers (ui/vitest.config.mts, ui/vitest.setup.*, ui/scripts/test-shard-*, ui/apps/console/vitest.config.ts, ui/apps/console/vite.config.ts; vite-*.ts and vitest-invocation-guard.mjs are covered by the build rows). Test Core is scheduled by core/crosspkg, and no gate subject reads the generic test task's root inputs (vitest.preset.mts sits in core: by hand). So a diff confined to one of the five moves every @objectstack/*#test hash but starts Test Core first in the merge queue — the ruling's shape, one task over. No stale replay results (the hash moves; ui/** runs Test UI on the PR; the queue runs Test Core with core true), the ruling scoped six build rows, and the parity gate demanded none of these, so this is not a defect of the hunk; it is the next card: either a fourth parity subject for test inputs plus the five rows, or a recorded decision that Test Core's scheduling does not follow generic test inputs.

.github/workflows/lint.yml — holds. Judged against scripts/check-self-test-wired.mjs (INVOCATION_RE consumes the directory prefix, so the new core: row ui/scripts/invoked-as.mjs is a named path; the file exists and its code carries --self-test, L322, so it joins the population and must be run), scripts/check-step-collectors.mjs (SCRIPT_TOKEN accepts a path under any directory, so the harness plants the stub at ui/scripts/invoked-as.mjs, distinct from the root twin's scripts/invoked-as.mjs — no basename collision), and ui/scripts/invoked-as.mjs itself (imports node: builtins only, so the step needs no ui install; the job checks out the whole tree with fetch-depth: 0). The line sits inside the tolerate-and-collect block beside its root twin, which is the only shape check-step-collectors admits for a self-test in that step. Scenario: the gate's own remedy, executed; on this head the shared-module self-tests step concluded success in Lint · repo & tooling gates, as did the Step-collector gate and the Self-test wiring gate. The over-selection the gate's header owns up to (a paths-filter row is read as CI naming the script) bought a real run: the ui copy's 12-case self-test had no CI runner before.

• Should-fix (prose, a later governed edit): the step name lists four modules (parse · entry predicate · comment mask · prerequisite frame), the comment above it says "The four modules are independent of one another", and the final line prints scripts/ shared-module self-tests — all four ran and passed, while five self-tests now run. Nothing reads the string and the collector counts failures, not members, so it is not a gate defect; the log undercounts.

No must-fix.

Implemented-by: claude/issue-27283-turbo-ui-inputs
Reviewed-by: session_01L6bhgV4fMGJHSdSdx3u9mK

VERDICT: PASS

---

Generated by Claude Code

[objectstack-fleet]

domain:devx#2 · os-justin · session_01QSeKYmTYfaPbLQD4BJfomW

席位核对 — Tier H · approved · landing · domain:devx#2 · head d5f83e05ee · 2026-10-30T05:14Z

维护者速读

• 改了什么：
  • 根 turbo.json 的 build 和 test 任务，把 ui 树根部各 @object-ui/* 包真正会读的文件计入缓存键。
  • 按你的裁决 A，6 个 ui 根目录构建输入同时写进 ci.yml 的 core: 过滤器。
  • lint.yml 补一行，让门禁要求的 ui/scripts/invoked-as.mjs 自测有 CI 来跑。
  • 守卫全部改读这份实际在用的配置，删掉没人读的 ui/turbo.objectui.json。
• 为什么改：以前改这些文件不会让缓存失效，可能回放旧的构建产物；守卫读的又是一份停用副本，所以一直是假绿。裁决 6513291766（你说「其他同意」）选了 A：缓存和 CI 调度按同一份清单走。
• 风险与回滚：所有包的 build/test 缓存键一次性变化（253 个任务里变了 243 个），首轮 CI 是冷构建；以后改这 6 类文件的 PR 会多跑一次 Build Core 和 Test Core，按过去 30 天约 9 次。碰 ci.yml 和 lint.yml，属 Tier H。共 17 个文件，+367/−368。回滚 = 还原本 PR。
• 先看：ci.yml 的 core: 新增 6 行 → lint.yml 第 843 行旁新增的一行 → turbo.json 的 build/test 新增输入。
• 两分钟验证：pnpm check:ci-filter-parity 应为 120/120 通过（改之前是 5/120 失败）。
• 需要你做的：无。os-zhuang 已批准（review 5707021648）。达档契约复核在这个 head 上 PASS（评论 6515518634，Head-sha d5f83e05ee70d2f396cca7980cc2c51dcf0d0eb6），席位在这一笔里落地。

席位意见：合入。复核没有 must-fix。两条 should-fix 复核者自己写明「立卡，不在本 PR 修」，已立 #27961。lint.yml 那一行是门禁强制带出的改动：新的 core: 行让 check-self-test-wired 把这个脚本认作 CI 会跑的脚本，这一行就是门禁自己给出的修法。不加豁免行，也不改门禁。

Shape: draft → main. Fixes #27283, Part of #26080. 17 files, +367/−368. Tier H on .github/workflows/ci.yml (ruled) and .github/workflows/lint.yml (gate-forced; seat authorisation 6513792547). Labels ci/cd, size/l, tests, skip-changeset. Approval by os-zhuang, who is in GOVERNED_APPROVERS; the queue guard does not pin commit_id. Dev reports 6498038778, 6513780805, 6514155626; claim 6496953999.

Premise measured: ruling 6513291766, letter A, binds the six ui-root build inputs into core: in this PR. At this head, check:ci-filter-parity passes 120/120 and demands exactly these six rows (it failed 5/120 on 47d8611899).

Contract review: at CONTRACT_REVIEW_TIER, by triage's isolated reviewer (session_01L6bhgV4fMGJHSdSdx3u9mK), record 6515518634, PASS, no must-fix.

• ci.yml holds: the six rows equal the six root build inputs, and no more rows were added than the ruling asked for.
• lint.yml holds: check-step-collectors admits only this shape. node ui/scripts/invoked-as.mjs --self-test needs no ui install, because it imports only node: builtins.
• The lane's own attempt at the review tier was refused with HTTP 429 (handoff 6513846981). The seat did not review at a lower tier.

Five-item pre-check:

1. A same-head PASS is on record.
2. All CI on d5f83e05ee is green: 71 check-runs, 55 success, 16 skipped, 0 failure. check-expected-skips --pr 27571 is OK: all 17 skips are in main's roster (exit 0).
3. mergeable_state: clean.
4. An authorised approval is on record (os-zhuang, 5707021648).
5. check-governed-merges --pr 27571: governed, 2 of 17 paths; 735 changed lines, under the 3,000-line floor.

Dev's union at this head: 68 derived, all exit 0.

Accepted deviations:

• The gate-forced lint.yml line, as above.
• ui/apps/console/turbo.json restates the root build.outputs. The outputs guard, now reading the live root, found it narrowed them.

Out of scope, with destinations:

• Five root test ui inputs have no core: row, which needs a ruling. The shared-module step's prose says "four" where five self-tests now run. Both → ci: five root test-task ui inputs move every Test Core hash but no core: row schedules Test Core for them; plus the shared-module self-test step undercounts its members (#27571 review follow-ups) #27961.
• os-dev.md (marker first) contradicts post-stamped.mjs (signature first) → .claude/agents/os-dev.md says os-dev-report is the report comment's first line, but post-stamped.mjs refuses any body whose first line is not the seat signature #27962.
• Skills-docs: n/a (build and CI configuration only).

Landing: in this act, needs:contract-review comes off, and the seat flips the PR ready and arms auto-merge. On merge, the seat verifies the merged diff against this head, posts the landing note on #27283 and archives cloud session session_01QSeKYog9FzTNeBAndKHXTT.

---

Generated by Claude Code