Repository navigation
Tests grow 2.5 times faster than source: measure the per-fix test weight and the #25911 pilot, then roll the shared-setup merge out to the heaviest components or retire it #29469
Description
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
Ruled: 6583487846 · Q1 A · Q2 A · 2026-11-02T17:17Z
Filing gate ③, a task the maintainer set. After the director's project assessment reported test lines growing 2.5 times faster than source lines, the maintainer answered 「同意」 to filing this card. ⛔ Not a claim. Reader who acts: the domain:devx seat. Follows #25911 (closed), whose own plan said 「先量 setup 与断言的占比再决定推广」.
Measured (origin/main, 2026-10-26 → 11-02, git log --numstat over packages and ui)
| class of file | added | removed | net |
|---|---|---|---|
test files (.test., .spec., __tests__, test/, e2e) |
352,859 | 43,250 | +309,609 |
| source | 236,290 | 114,716 | +121,574 |
| generated, JSON, fixtures | 8,155 | 3,789 | +4,366 |
- tests: 56.5% of spec files are per-issue pins costing 52.5% of suite time — pilot a shared-setup consolidation on the 95 StudioDesignSurface files and split cli-bin.test.ts (74.6 s) #25911 (2026-10-24): 3,263 of 5,773 spec files (56.5 %) were per-issue pins, 52.5 % of measured suite time; the pilot folded
StudioDesignSurface.*pins into shared files (PR test(app-shell): fold the other five Interfaces rail label pins onto the shared railLabels harness #26309) and splitcli-bin.test.ts(PR test(cli): split cli-bin into two files that share one build behind a lock directory #26333). - Slowest
Test Coreshard on five recent successfulpull_requestCI runs (ci.yml, 2026-11-02): 13 min 45 s, 18 min 28 s, 13 min 53 s, 12 min 22 s, 20 min 58 s. ci(test-shards): Test Core's two slowest shards set every core PR's wall clock at ~28 min (5.6 min dependency build + ~20 min tests) while the other six finish in 7–17 — re-derive the cli slicing and shard balance on post-merge readings #25870's fix brought it down from ~28 min; at a net 300,000 test lines a week the suite will grow back. - Example of the per-fix weight: PR fix(app-shell): interface list toolbar honours the userActions spec defaults — Filter, Row height, Group and Hide Fields are on unless written false #29299 changes 20 source lines and adds a 191-line test file.
Ask
- Measure, on the last 7 days' merged
fix(PRs: test lines added per source line changed (median and p90), and how many new test files each adds. - Measure the tests: 56.5% of spec files are per-issue pins costing 52.5% of suite time — pilot a shared-setup consolidation on the 95 StudioDesignSurface files and split cli-bin.test.ts (74.6 s) #25911 pilot: suite time of the folded
StudioDesignSurface.*files before and after. - Report both on this card. If the pilot saved time without losing a pin, roll the shared-setup merge out to the next four components tests: 56.5% of spec files are per-issue pins costing 52.5% of suite time — pilot a shared-setup consolidation on the 95 StudioDesignSurface files and split cli-bin.test.ts (74.6 s) #25911 named (
ListView*,ObjectView*,RecordDetailView*,ObjectGantt*), one PR each; if it did not, close the pattern and say so. - ⛔ No new gate and no ratio ceiling in CI: a guidance line in the test discipline of
AGENTS.mdis the most this card may propose, and it goes to the maintainer as a proposal, not a change.
Done when
The two measurements are on this card with their commands, and either the four rollout PRs have merged or the card records why the pattern stops.
Activity
objectstack-fleet commentedon Nov 2, 2026
triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U
Path: none
Triage: p2 ·
domain:devx·pm:queue· 2026-11-02T15:57Z⛔ Not a claim.
domain:devxas filed. p2.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
Claim: maintainer-directed dispatch · director seat · 2026-11-02T16:30Z
Session:
session_01WGufzg12BtjFc5rHp7YD1JAccount:
os-support-ai(the seat's linked user asGET /useranswers it; the card's assignee)Branch:
claude/issue-29469-test-weight-censusWorktree:
objectstack-issue-29469Domain:
domain:devxSeat:
director#1(the director seat dispatching under the maintainer's direct order; it holds nodomain:devxseat)File surface: none in phase 1 — measurement only, results reported as a comment on this card; ⛔ no source, test or workflow edit in this dispatch (stop on breach; explain in the report)
Container & model:
S (measurement, no build of the product),mode:subagent,model: default tier(dispatch-gates.mjs --tier: 「The tier stays the PM's per-card judgment call (floor sonnet · default opus · ceiling fable)」; no path-derived mandate, no file surface),effort: highClause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card
Thread-read: 6581713880
Premise: holds (the card's figures were measured by this seat at 2026-11-02T15:20Z on
origin/main; the dev re-measures them as part of the work)Serial constraints cleared: none — the dispatch edits no file
Provenance (three pieces): the maintainer, in the director session (
session_01WGufzg12BtjFc5rHp7YD1J, claude.ai), verbatim: 「普查测试的卡你现在就可以派发」, after 「同意」 to filing it. The director seat reads 「普查测试的卡」 as this card. The pm-dispatch rule that the director seat never claims backlog yields to the maintainer's order (SKILL.md 〈优先级〉: 维护者裁决 > … > 红线). Triage's first touch 6581713880 (p2,domain:devx,pm:queue) is respected;pm:queue→pm:dispatchedin one label write, read back.Scope of this dispatch: the card's Ask items 1 and 2 (the two measurements) and item 3's verdict, reported on this card. The rollout PRs that item 3 may call for are dispatched afterwards, one per component, by the lane that owns the files (
ui/**→domain:ui), each its own claim.objectstack-fleet commentedon Nov 2, 2026
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
Results: per-fix test weight, the #25911 pilot, and the verdict (Ask 1, 2, 3)
Read at 2026-11-02T16:37Z on
objectstack-ai/objectstackat94d3e2543(theorigin/maintip, committed 2026-11-02T16:10:12Z). Window: first-parent commits on that tip since 2026-10-26T15:20:00Z. That is 1,656 commits, all squash (0 merges). The history is proven present bynode scripts/pm/git-history.mjs ensure --since=2026-10-20(floor 2026-10-17, no fetch needed). Measurement only: no file, PR or label was written.0. The card's table, re-measured
Same path regexes as the card, with the test class taking precedence over generated, over
packages/andui/:The removed column matches the card exactly. The added column is 2 % (test) and 9 % (source) higher. I did not chase this; the tip moved after the card was read.
The classification moves the multiplier but not the conclusion. The card's "source" includes 22,029 added and 54,985 removed lines that are not code:
CHANGELOG.md+16,484 (written by the release tooling),.mdx−23,284,.md−21,705,LICENSE+3,051, and.sh. With source limited to code files (.ts .tsx .js .jsx .mjs .mts .cjs .cts) it is +234,824 / −87,894 / net +146,930. Test against source is then 2.15× on net lines (the card says 2.5×; the raw table gives 2.77×) and 1.53× on added lines. Tests still outgrow source by about 2 to 1.1. Per-fix test weight (Ask 1)
Population: the 816 first-parent commits in the window whose subject starts
fix((2 more startfix:orfix!and are not counted). Each file is classified as: test (card regex), generated (card regex), prose (.md,.mdx,.txt,LICENSE*, which includes.changeset/), or source (everything else, any path). Source lines changed = added + removed.fix(commits wrote 52.5 % of every test line added in the window (189,425 of 360,886, repo-wide).2. The pilot (Ask 2)
Instruments and their radius
ui/scripts/test-shard-timings.json. This is the per-file vitest module diagnostic (environment + prepare + setup + import + run) from CI, median of 6 full-battery runs on 2026-10-19T06:37:09Z, keyed bypathKey()(sha1 of the ui-relative path, first 16 hex). To check the keying:cli-bin.test.tsreads 74.12 s, which is the 74.1 s test(cli): split cli-bin into two files that share one build behind a lock directory #26333 cites.vitest run packages/app-shell/src/views/studio-design/StudioDesignSurface --maxWorkers=2), shared-box seconds. I did not re-run it, because this dispatch is a no-build container.ui/was imported (see the comment aboveRun the ui testsinci.yml), and the dataset has not been refreshed since 2026-10-19T06:37:09Z. No CI per-file reading exists after the fold.StudioDesignSurface.*family, local (b)The CI before (70.5 s) and the local before (76.6 s) agree within 9 %, so the local scale holds. Each folded file saved about 6.5 s of fixed cost, and the folded file's own fixed cost stayed about 7.5 s.
No pin lost (my own check, from git only). The ten original files, read at the parent of each fold (
697a307a2^and3249e204a^), hold 50it/testtitles and 153expect(calls.StudioDesignSurface.railLabels.test.tsxat3249e204aholds the same 50 titles as an identical set, and 153expect(calls. At the tip it holds 54 titles and 172expect(calls, and 0 of the original titles are missing. The 4 extra titles came from later commits that appended to the shared file (for example #27039 and #28825).The cli-bin split (#26333) is a split, not a fold. The heaviest file went from 87.2 s to 57.5 s cold wall, the spawn CPU is unchanged, and CI CPU rises by one build when the two files land on different legs. It is not evidence for or against the shared-setup merge.
Inflow after the pilot.
StudioDesignSurface.*test files: 95 before, 86 after #26309, 116 at the tip. That is 30 new per-issue pin files in the 7 days since, and 0 deleted. At about 6.5 s of fixed cost each, that is roughly 195 s, about 3× the 67 s the fold saved.The four components #25911 named, counted by test-file basename
COMPONENT.*.test.ts(x):f143cd88(pilot base)StudioDesignSurfaceListViewObjectViewRecordDetailViewObjectGantt3. Verdict (Ask 3): roll out, and land new pins in the shared file
Roll out. The pilot cut its ten pins from 76.6 s to 13.8 s of CPU (the family by 6.6 %) and kept 50 of 50 titles and 153 of 153
expect(calls, which meets the card's bar.Folding alone does not keep up with the inflow. The same family gained 30 new pin files in the following week, about 3× the time the fold saved, and 78.8 % of fix test lines go into new files. A rollout PR pays off only if later pins for that component go into its shared file.
So, under Ask 4 (a proposal to the maintainer, not a change, and no gate or ceiling): add one guidance line to the test discipline in
AGENTS.md: "A new pin for a component that already has a shared harness file goes in as a top-leveldescribein that file, not as a new file." The four rollout PRs (ListView*,ObjectView*,RecordDetailView*,ObjectGantt*) are for the owning lane (domain:ui) to dispatch.The rollout has no CI after-reading until the per-file timings reporter and its refresh workflow are ported into
ci.yml. Today each rollout PR can only cite a local A/B like #26309's.Exact commands (scripts are in the dev's scratchpad, read-only over git)
objectstack-fleet commentedon Nov 2, 2026
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
os-dev-report
{
"issue": 29469,
"status": "done",
"branch": "claude/issue-29469-test-weight-census",
"pr": null,
"session": "session_01WGufzg12BtjFc5rHp7YD1J",
"premise_still_valid": true,
"summary": "Measurement only, results comment 6582607393 on #29469. Ask 1: 816 fix( commits; test lines added / source lines changed median 2.28, p90 7.47; new test files per fix median 1, p90 2 (69.7% add one; 78.8% of fix test lines land in new files). Ask 2: the ten folded pins went 76.6 s to 13.8 s CPU (local A/B from PR #26255/#26309 bodies; CI before 70.5 s from ui/scripts/test-shard-timings.json; CI after NOT MEASURED, per-file reporter not ported), family -6.6% CPU, 50/50 titles and 153/153 expect( kept. Verdict: roll out, with a proposed AGENTS.md guidance line that new pins land in the shared file, because StudioDesignSurface.* gained 30 pin files in the week after the fold (about 3x the saving). Card table re-measured: code-only net test:source is 2.15x, not 2.5x (card's source class carries CHANGELOG/md/mdx/LICENSE). Writes: 2 comments via post-stamped relay; mcp_calls 0.",
"tests": "No product test run (no-build dispatch). Measurements: git log TIP --first-parent --since=SINCE --numstat parsed in Python at 94d3e25 (1,656 commits, 0 merges); history proven by git-history.mjs ensure --since=2026-10-20 (exit 0, floor 2026-10-17). Pin-kept check: 10 originals at 697a307^/3249e204a^ = 50 titles, 153 expect(; folded file at 3249e20 = same 50-title set, 153 expect(; at tip 54/172, 0 originals missing. CI-dataset keying control: cli-bin.test.ts = 74.12 s, matching the 74.1 s #26333 cites. No ablation: no tested behaviour changed.",
"gates": "No diff, so no derived gate family and no PR check-runs; dispatch-gates.mjs not run (nothing to derive from). post-stamped dry-run exit 2 once (MIXED stamp refusal on a bare --since stamp in the commands block), fixed to a SINCE variable, dry-run exit 0, post exit 0 with byte-identical read-back (8668 bytes).",
"dogfood_battery": "n/a — no PR, no
!title and no (narrowing) arm","mcp_calls": "0",
"api_writes": "2 — both through scripts/pm/post-stamped.mjs on the fleet-write relay (repository_dispatch then POST /repos//issues/29469/comments): the results comment 6582607393 and this os-dev-report comment. No git push (no edit, so no empty-branch probe), no PR, no label.",
"open_questions": [
{
"question": "Accept the AGENTS.md test-discipline guidance line proposed under Ask 4 (a new pin for a component that already has a shared harness file goes in as a top-level describe in that file, not a new file)?",
"options": [
"A propose it to the maintainer as written, as a separate docs PR after the ruling",
"B roll out the four folds without the line"
],
"recommendation": "A, because the StudioDesignSurface family gained 30 pin files in the 7 days after the fold, about 3x the CPU the fold saved, so folds without the landing rule are outrun within a week."
},
{
"question": "Port the ui per-file timings reporter and its refresh workflow into ci.yml so a rollout has a CI after-reading?",
"options": [
"A file it as a devx card before the rollout PRs",
"B let each rollout PR cite a local A/B like #26309"
],
"recommendation": "A, because no CI per-file reading has existed since the ui/ import, so neither the pilot nor the rollout can be checked in CI."
}
],
"security_findings": "none",
"out_of_scope_findings": [
"carrier: PM (director#1) · the ui per-file timings reporter was not ported with the ui/ import (ci.yml comment above Run the ui tests says so), so ui/scripts/test-shard-timings.json is frozen at its 2026-10-19 measurement; observation, noted and not filed · dedupe words: test-file-timings reporter, shard timings refresh, ui per-file timings, test-shard-timings.json stale"
]
}
objectstack-fleet commentedon Nov 2, 2026
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
Collected and accepted · measurement dispatch (claim 6582445213) · 2026-11-02T16:41Z
mcp_calls0: the dispatch's shape held.fix(first-parent subjects onorigin/main2026-10-26T15:20Z → 2026-11-02 15:20 UTC = 811 (the dev's 816 runs to the 16:10Z tip); net test lines ÷ net code-source lines (.ts/.tsx/.js/.mjs/.cjs/.jsx, generated and fixtures excluded) overpackages+ui= 313,791 ÷ 145,358 = 2.16 (the dev: 2.15). The body's "2.5 times" counted CHANGELOG and prose lines as source; the corrected figure is about 2.15. The conclusion stands.ListView*,ObjectView*,RecordDetailView*,ObjectGantt*(pilot: the ten folded pins 76.6 s → 13.8 s CPU, local A/B; no title orexpect(lost). The rollout PRs aredomain:uiwork and are not dispatched until the two questions below are ruled, because the first decides whether a fold stays folded.Two questions for the maintainer (the dev's
open_questions, analysed by this seat)Q1 — a test-discipline line in
AGENTS.md: 「a new pin for a component that already has a shared harness file goes in as a top-leveldescribein that file, not as a new file.」 Reading behind it:StudioDesignSurface.*went 95 → 86 files with the fold, then 116 at the tip — 30 new per-issue pin files in 7 days, about 3× what the fold saved. 78.8 % of fix test lines land in new files.Q2 — the
ui/per-file timings reporter, not ported whenui/was imported:ui/scripts/test-shard-timings.jsonhas been frozen since 2026-10-19, so neither the pilot nor a rollout can be read in CI, and Test UI shard balancing runs on week-old data.domain:devxcard to port the reporter and its refresh intoci.yml(Tier H, your approval) before the rollout. B each rollout PR cites a local A/B as test(app-shell): fold the other five Interfaces rail label pins onto the shared railLabels harness #26309 did.四轴分析
os-decision-facets
Prior rulings read: "per-issue pin" "shared harness" "test-shard-timings" → tests: 56.5% of spec files are per-issue pins costing 52.5% of suite time — pilot a shared-setup consolidation on the 95 StudioDesignSurface files and split cli-bin.test.ts (74.6 s) #25911 (pilot), ci(test-shards): Test Core's two slowest shards set every core PR's wall clock at ~28 min (5.6 min dependency build + ~20 min tests) while the other six finish in 7–17 — re-derive the cli slicing and shard balance on post-merge readings #25870 (Test Core shards, on hold); AGENTS.md test discipline: no file-placement rule; thread: none
自检:只看①选 Q1 A、Q2 A;②③④ 是否翻转:否。
推荐:Q1 A,Q2 A。 Q1 B 不取:实测一周内长回 3 倍。Q2 B 不取:本地 A/B 不能复查,也不喂分片均衡。置信缺口: 报告器移植的工作量未测(原实现在 objectui 仓,导入时未带过来)。
Analysis-tier:
claude-opus-5-5(served at analysis; notCONTRACT_REVIEW_TIER).State: the measurement claim is released.
pm:dispatched→needs-user-decisionin one label write, assignee cleared; this card is the anchor for the ruling. After the ruling: Q1 A → one docs PR in the skills lane quoting it; Q2 A → onedomain:devxcard; then the four rollout cards indomain:ui.objectstack-fleet commentedon Nov 2, 2026
director#1 · os-support-ai · session_01WGufzg12BtjFc5rHp7YD1J
Brief-claimed-by: session_01WGufzg12BtjFc5rHp7YD1J · batch #458 · 2026-11-02T17:11Z
⛔ Not a claim on the work. The two questions in 6582704041 are batch #458 item 1, presented in the director session.
39 remaining items
objectstack-fleet commentedon Nov 6, 2026
domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf
Claim: PM loop round 3 · 2026-11-06T07:01Z
Session:
session_01L9qibxkcTyv8QYYuvpzAFL(card thread, dev) · seatsession_01L9qibw7DekEe3wx5f3zphfAccount:
os-teslaBranch:
claude/project-thread-siynsc(a cloud card thread can push only its designated branch)Worktree:
objectstack-issue-29469Domain:
domain:uiSeat:
domain:ui#2File surface: the ObjectView family's test files (
__tests__ofui/packages/plugin-viewand the app-shell views that testObjectView), one harness file per package; source files ⛔Container & model: M,
mode:thread,model: default tier(test-only),effort: highClause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card
Thread-read: 6679162337
Premise: holds (ruling 6583487846 + seat amendment 2 6672694520: at most two PRs per family; ObjectView not started)
Serial constraints cleared: none (no in-flight claim declares plugin-view or app-shell
__tests__for ObjectView; #30786 PR #30858 touchesviews/metadata-admin/tests only)Resume-from:
main@e603385f25e8d639518ca3aeee76f5196c7c452fScope this claim: ObjectView family, slice 3a; the PR says
Part of #29469.objectstack-fleet commentedon Nov 6, 2026
domain:ui#2 · os-tesla · session_01L9qibxkcTyv8QYYuvpzAFL
os-dev-report
{ "issue": 29469, "status": "done", "branch": "claude/project-thread-siynsc", "pr": "https://github.com/objectstack-ai/objectstack/pull/30872", "session": "session_01L9qibxkcTyv8QYYuvpzAFL", "premise_still_valid": true, "summary": "Family 3 (ObjectView), slice 3a, the first of two ObjectView PRs under amendment 2 (6672694520), cut from main e603385f per claim 6679217795. The largest same-setup cluster is in plugin-view/src/__tests__: 31 of 54 per-issue ObjectView pins (7,367 lines) declare the same three mocks (@object-ui/react SchemaRenderer + fresh SchemaRendererContext + no-op data bus, plugin-grid ObjectGrid, plugin-form ObjectForm) and differ only in their stand-ins. Nine of them (calendarInitialDate-28102, tableSortKey-10664, kanbanDeclaredLanes-28211, namedViewEditInlineFold-5144, formLabelsI18nLabel-10993, refreshSignal, timelineBinding-7070, readersRetired-6152, filterSources), the smallest of the 12 with no spies, stubs, timers, own hoisted/globalThis slots, side-effect imports, dom-heavy entry or other file naming them, fold into a new ObjectView.harness.test.tsx: the three mocks are declared once and read vi.hoisted slots, each block installs its own stand-ins (copied verbatim) in a beforeEach and opens with restoreAfterBlock() (ListView's helper plus the slots). The probe measured the leaks the helper removes: formLabelsI18nLabel-10993 leaves html lang=zh / dir=ltr, and stand-ins carried across blocks. One harness file in one package: the app-shell ObjectView pins test a different component over 40+ mock sets and are left for slice 3b with the unfolded list.", "tests": "Per former file, TypeScript AST count at e603385f vs its describe at head 0ec2ac43: it 47 = 47, expect( 97 = 97, sorted describe>it titles identical for all nine; line-multiset check finds only license headers, imports, vi.mock wrappers and stand-in first lines missing. Harness 55/55 (47 it calls, it.each rows) in declaration order and under --sequence.shuffle.tests seeds 11, 222, 3333. Block-boundary probe (registry renderer+meta, localStorage descriptor, both storage lengths, html lang/dir, react-i18next getI18n, three slots, body, new globals) identical at all 9 block starts in all four orders; without the helper body: lang/dir leak after formLabelsI18nLabel and slots carried. vitest run packages/plugin-view/ --maxWorkers=2 from ui/ under os-verify-lock VERDICT command-exit 0: 71 files, 720 tests passed. Local A/B under os-verify-lock, all ObjectView.* in plugin-view/src/__tests__, runs B1 B2 A1 A2 B3: the 9 files 40.4/38.6/37.9 s CPU -> harness 5.9/6.1 s (-85 %); family 269.8/258.7/256.2 s -> 226.5/228.5 s (-13.0 %), wall 137.1 -> 119.0 s avg; 507 passed both legs. CI after: NOT MEASURED, per-file timings upload on main full-battery runs only. No ablation: no tested behaviour changed.", "gates": "dispatch-gates --commands: 26 derived (10 paths vs merge base e603385f, 2589 changed lines), 26 run at 0ec2ac43 with stdin from /dev/null, each exit 0 captured before any pipe (pnpm --dir ui exec vitest run scripts/ under os-verify-lock VERDICT command-exit 0: 170 passed 2 skipped, 4979 tests passed 2 skipped; node scripts/check-sdui-manifest.mjs exit 0 and --self-test exit 0). --ran reconciliation: 26 derived, 26 run, 0 NOT-MEASURED, 0 UNRUN. Also: plugin-view pnpm run type-check exit 0 (0 error TS, harness in the tsconfig.test.json program by --listFilesOnly); eslint on the harness exit 0, 0 errors, 47 no-explicit-any warnings, the same 47 the nine former files give at e603385f; pnpm check:new-line-citations exit 0, 0 new. PR check-runs: not concluded at report time; the seat reads them.", "dogfood_battery": "n/a — no ! in the PR title and no (narrowing) arm", "mcp_calls": "5 — mcp__github__issue_read get x1, issue_read get_comments x1, pull_request_read get x2 (#30769, #30872 read-back), list_pull_requests x1; all reads, 0 writes", "api_writes": "3 — git push of claude/project-thread-siynsc (two WIP commits, head 0ec2ac43); fleet-write relay pr_create with labels [skip-changeset] (request fw-20261106T080138Z-fbc544, run 42184759384, #30872, 14529 bytes sent = stored, label read back on the PR, no assignees); this os-dev-report comment via post-stamped.mjs", "deviations": "Branch not re-merged with origin/main before the PR: main moved e603385f -> cf478ea3, none of those commits touching ui/packages/plugin-view, ui/vitest.config.mts or ui/vitest.setup.*; stated in the PR body. The session harness asks to set the PR assignee and reviewer after creation; the frame and os-dev rule 2 reserve both for the seat, so neither was set. First A/B attempt ran its after legs without the harness (a relative path in the restore trap); those two runs were discarded and the after legs re-run, the before legs kept. Two commits are WIP-titled; the squash takes the PR title.", "line_budget": "2589 changed lines (+1272 / -1317), 10 files, under 3000", "files_changed": "ui/packages/plugin-view/src/__tests__/ObjectView.harness.test.tsx (added); 9 pin files deleted: ObjectView.calendarInitialDate-28102, tableSortKey-10664, kanbanDeclaredLanes-28211, namedViewEditInlineFold-5144, formLabelsI18nLabel-10993, refreshSignal, timelineBinding-7070, readersRetired-6152, filterSources (.test.tsx)", "open_questions": [], "security_findings": "none", "out_of_scope_findings": [ "carrier: PR #30872 · ObjectView.contractEnvelope-6726 is named by path in scripts/check-vi-mock-inherit.mjs (a ledger outside __tests__), so it cannot fold without touching that ledger · noted, not filed", "carrier: seat (domain:ui#2) · slice 3b candidates: 3 more clean trio pins (tableColumnsForwarding 298, strayGroupByLane-9242 313, canonicalTableKeys 470) plus named-by trio pins whose naming comments are in test files; app-shell ObjectView pins need their own harness in @object-ui/app-shell · noted, not filed" ] }objectstack-fleet commentedon Nov 6, 2026
domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf
ACCEPT → PR #30872 comment 6680692515 · 2026-11-06T08:32Z · head
0ec2ac43(ObjectView slice 3a, test-only, 2,589 lines, Tier S path). Landing through the merge queue.objectstack-fleet commentedon Nov 6, 2026
domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf
Landed (ObjectView slice 3a) at 2026-11-06T08:59Z: PR #30872 merged as
8b9cc712ab(seat ACCEPT 6680692515 on head0ec2ac43). The PR saidPart of #29469, so the card stays open.git grep -c "^describe(" origin/main -- ui/packages/plugin-view/src/__tests__/ObjectView.harness.test.tsxgit ls-tree origin/main ui/packages/plugin-view/src/__tests__/ObjectView.refreshSignal.test.tsxRelease:
session_01L9qibw7DekEe3wx5f3zphf(domain:ui#2, claim 6679217795) · because slice 3a has landed · back topm:queue, assignee cleared in this stroke.Resume-from:
main@8b9cc712ab81193b4a914e38e81731198decb84dRemainder: ObjectView slice 3b, the family's last plugin-view PR: the other 3 clean trio pins (
tableColumnsForwarding,strayGroupByLane-9242,canonicalTableKeys), the trio pins another test file names, and the app-shell ObjectView pins (a second harness in@object-ui/app-shell). Then the RecordDetailView family, whose PR is the card's last (Fixes #29469); it waits for #30595's successor (#30511) and #30652.objectstack-fleet commentedon Nov 6, 2026
domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf
Claim: PM loop round 4 · 2026-11-06T09:02Z
Session:
session_01L9qibxkcTyv8QYYuvpzAFL(card thread, dev) · seatsession_01L9qibw7DekEe3wx5f3zphfAccount:
os-teslaBranch:
claude/project-thread-siynsc(a cloud card thread can push only its designated branch)Worktree:
objectstack-issue-29469Domain:
domain:uiSeat:
domain:ui#2File surface: the ObjectView family's test files (
__tests__ofui/packages/plugin-viewand the app-shell views that testObjectView), one harness file per package; source files ⛔Container & model: M,
mode:thread,model: default tier(test-only),effort: highClause-②: no
Metadata-protocol: none
Responsibility: n/a — not a defect card
Thread-read: 6681150482
Premise: holds (ruling 6583487846 + seat amendment 2 6672694520: at most two PRs per family; ObjectView slice 3a landed as PR #30872, this is its second and last)
Serial constraints cleared: #30859 (this seat, claim 6680196179) declares
views/studio-design/**andEmbeddedItemEditor.tsxtests, not ObjectView pins; no other in-flight claim declares plugin-view or app-shell__tests__for ObjectViewResume-from:
main@8b9cc712ab81193b4a914e38e81731198decb84d(branch restarted from main; slice 3a is merged)Scope this claim: ObjectView family, slice 3b: the 3 clean trio pins left, the trio pins another test file names, and the app-shell ObjectView pins (second harness in
@object-ui/app-shell); the PR saysPart of #29469(RecordDetailView family remains).