test(spec): the second ui/ file group's test titles state each cited decision in words instead of a tracker number (stage 21)

[objectstack-fleet]

Part of #20749
Clause-②: no

Stage 21 of this card: the next area of class (e), the test strings shipped under packages/spec/src, as ruled in 5902360492 on #20513. This stage takes the second name-ordered ui/ group: the test files directly under packages/spec/src/ui/ from component-record-blocks.test.ts to dashboard.test.ts. Those files carried 103 messages and 109 tracker-shaped ids, citing 58 records. 105 of those ids now either state what their record decided, in words (form D), or are dropped where the title already says it. Four stay: they are CSS colour literals in two widget fixtures, not citations (below). Text only: no assertion, identifier, test count or code comment changes, and no file is renamed.

Census at the base (1e18a0735c)

Instruments: census10.cjs (md5 9d08602ab972b4b8643c90d64d40fa41), census.cjs (md5 6e42a45a926d375013c32d62f16a296e), census-wide.cjs (md5 c98410a19529c439adb0afbfb00026a2) and dirtable.cjs (md5 dda605c54745b4a60cc14c9a686e4eff), byte-identical to the copies stages 10 to 20 used. A literal counts as a test title when its folded message is argument 0 of a describe / it / test call, .each / .skip / .only chains included. Everything else is an "other" string.

The base is 1e18a0735c, stage 20's landing and the claim's base. Both instruments read 764 messages / 807 ids in 159 files, the seat's reading and stage 20's head reading.

directory	files	messages / ids	titles	other
ui/ (this PR: 7 of the 53 files)	53	300 / 318	284 / 302	16 / 16
api/	40	189 / 201	181 / 193	8 / 8
system/	34	154 / 165	128 / 138	26 / 27
(files directly in src/)	30	118 / 120	117 / 119	1 / 1
ai/	1	2 / 2	0	2 / 2
contracts/	1	1 / 1	0	1 / 1
total	159	764 / 807	710 / 752	54 / 55

The group reads 103 messages / 109 ids in 7 files, the seat's figures file for file:

file (under ui/)	messages / ids	titles	other
component-record-blocks.test.ts	6 / 6	6 / 6	0
component-reference-rail.test.ts	2 / 2	2 / 2	0
component-type-vocabulary.test.ts	3 / 3	3 / 3	0
component.test.ts	65 / 70	65 / 70	0
dashboard-chart-structure-refusal.test.ts	2 / 2	0	2 / 2
dashboard-compareto.test.ts	5 / 5	5 / 5	0
dashboard.test.ts	20 / 21	17 / 18	3 / 3
7 files	103 / 109	98 / 104	5 / 5

component-report-items-action-members-typed.pin.test.ts sits in the same name range and carries no id. The five "other" strings are the four colour literals and dashboard.test.ts:205.

• Controls. Lit: ui/view.test.ts, outside the group, reads 43 ids at the base and at the head. Dark: component.test.ts reads 0 at the head while 200 of its comment lines still carry a number. Planted in scratch copies of head files: an id put into a component-record-blocks.test.ts title reads 1 / 1, and an id put into a dashboard-compareto.test.ts comment reads 0.
• A wider pattern (any # plus digits) reads the same as the gate pattern in 6 of the 7 files at the base. component.test.ts reads one more: decision batch #77, a two-digit batch number the gate pattern does not count. It leaves with the id beside it, as stages 9, 13 and 15 did with theirs.
• At the head: 665 messages / 702 ids in 154 files. The 7 files read 4 / 4 (the four colour literals), ui/ reads 201 / 213, and no other file moved.

How the area was chosen

ui/ has no subdirectory test file with an id, so it is taken in name-ordered file groups near the ~100-id bound. Stage 20's re-cut named this group at 109 ids, and this census reads 109, so no re-cut was needed.

Named for the next stages (cut from the head census, 665 / 702):

• ui/ 213 ids. One is stage 20's kept component-props-unknown-members.pin.test.ts:322, four are this group's colour literals, and 208 sit in the 45 files after dashboard.test.ts. The next group nearest 100 runs from dataset-filter-nested-relation-list.test.ts to view-inline-object-binding.test.ts: 29 files, 96 messages / 102 ids, 7 of them "other". Cutting two files earlier gives 98. The last ui/ group is then the 16 files from view-item-config-type.test.ts to widget.test.ts: 100 messages / 106 ids, view.test.ts alone 43.
• api/ 201, two stages. system/ 165, two. The files directly in src/, 120, one.
• The three docblock needles plus the kept :322, one stage, with an at-tier review.

The five "other" strings: four kept, one rewritten

• '#111' / '#222' at dashboard-chart-structure-refusal.test.ts:94 and dashboard.test.ts:124 are kept. They are three-digit CSS hex colours, not placeholders for a record: colors: ['#111', '#222'] in a widget's chartConfig, and palette: ['#111', '#222'] inside the free-form options bag. They cite nothing. But they are not input and expected value at once, the case stage 12 dropped. Each is input that the schema under test reads (ChartConfigSchema.colors is a string-array or string-map union), and the assertions read other things: the first parse must succeed, the second asserts options.stacked. So by the claim's rule they stay, and are reported. They match the gate pattern only because a short hex colour can be all digits. They are the only four such literals in the whole census.
• dashboard.test.ts:205 is the label argument of the file's orderPin helper, which passes it to it(). So it is a test title one call down, and no assertion reads it. It is rewritten and declared to the text-only tool.

No string in the group is a needle (an id that is the expected value of an assertion over a docblock or another file's text). The three known needles are in ai/ and contracts/.

What each id became

• 21 literals (21 ids) now state a decision in words.
• 15 literals (15 ids) get their subject back in words, where the number stood for a thing, such as "the record:details sections: five more renderer-honoured keys remain undeclared by the strict section schema (title / defaultCollapsed / icon / description / headerColor) #11661 keys".
• 63 literals (69 ids) drop a number the title already explains.

Every cited record was read with its comments through REST: 54 answer 200 and 4 answer 404. Four citations are cross-repo: ui#6206 (also spelled ui#6206-B), ui#6207 and objectui#8221 were read from objectui and answer 200. framework#2501 was read under the repository's current name, as stage 18 read framework#2536. #5042 is a pull request, #4001 batch 14. The four 404s were read from what landed, through the commits the stage-5 comment sweep (#20576) re-anchored them to:

• element:record_picker 的 sort / limit 扁平简写:renderer 兑现、schema 未声明(#5775 实施中新测出,A 表之外的第 7 处) #6276: 78f0be872, which declares the record picker's flat sort / limit (maintainer ruling 2026-08-08, direction A).
• [finding] page:tabs items[].icon is the exact sibling of #9881 — live objectui reader, no .describe(), no accept-pin #9972: 60e0f900a, which records the live read point of page:tabs items[].icon and its accept pin.
• [Decision] Is sys_activity.type a closed platform vocabulary or an author-extensible one? Both readings are true of the code today #11507: 88b9d749a, which declares sys_activity.type an open, author-extensible vocabulary (maintainer ruling 2026-08-24, direction 4).
• record:activity's authorable types filter is a CLOSED enum over a vocabulary #11507 just ruled open #11658: 1a6a19c31, which opens RecordActivityProps.types to author-contributed kinds, executing that ruling.

Each of those titles already carried its decision, so the number is dropped. component.test.ts:3037 also gets its subject back: "the ruling" becomes "the open-vocabulary ruling".

Stated in words:

record	literal (under ui/)	now reads	the decision
#8744	component-record-blocks.test.ts:355	"the record:discussion / record:chatter pair — one shared row"	record:discussion is wired to the chatter row on purpose: one renderer, one accept face.
#7702	component.test.ts:63	"accepts a header without title — the synthesized shape, headed from the record"	Ruling A/B: title becomes optional, and an omitted title means the renderer derives the heading from the record.
#6776	component.test.ts:89, :262	"PageHeaderProps recordChrome / showStar / showCopyId — declared because the header renderer reads them"; "PageAccordionProps variant — declared because the accordion renderer reads it"	Route A: declare the five author keys objectui's renderer reads.
#6776	component.test.ts:235	"PageTabsProps tabStyle — renamed from type, which collides with the component type"	Route A: rename type to tabStyle, because in a flat node type is the component's own dispatch key.
#6946	component.test.ts:122	"PageHeaderProps icon is retired — no renderer reads it"	Maintainer ruling: retire three keys with zero renderer read points, this one among them.
#5775	component.test.ts:406, :2932	"… items[].value / items[].count — declared because the tabs renderer reads them"; "RecordPathProps stages[].terminal — declared because the path renderer reads it"	Ruling A: retire the dead keys and declare the keys the renderers honour.
#5775	component.test.ts:649	"PageContainerProps — page:section / page:footer / page:sidebar compose through children"	Same ruling: the three containers declare children as their one composition key, and body is not declared.
#11289	component.test.ts:768	"preserves the section presentation keys the renderer honours, verbatim"	Direction 1: declare hideEmpty / collapsible / showBorder; the renderer is unchanged.
#11661	component.test.ts:889	"still refuses title, deliberately withheld as a second spelling of label"	Three more renderer-honoured keys are declared; title stays out because label already names the heading slot.
#9220, #9249	component.test.ts:2078, :2142, :2899, :2908	"Interactive Elements — element:filter (retired, no renderer)", the same for element:form, and "… through the kept map row (retired, no renderer)" twice	Both elements are retired at element grain: no renderer or reader in any repository.
#4001	component.test.ts:3325	"batch A, unknown keys refused — the prescriptions, each backed by a measured producer"	Every authorable surface refuses unknown keys; spelled as stage 15 spelled #4001 batch D.
#7751	component.test.ts:3419	"object-* block props schemas — declared, so the props gate has a schema to dispatch"	Ruling A: the object-* block family enters ComponentPropsMap.
ui#6207	component.test.ts:3468	"object-grid data takes the ViewDataSchema provider object — the two spec authorities converged"	Option A: object-grid.data converges on ViewDataSchema, and the bare array is refused.
#19228	component.test.ts:4499	"row caps on the object-bound blocks — a bound view fills limit only when the authored one is not a usable cap"	Ruling D: one row bound per view; the component face keeps an undefaulted limit, which a bound view's page size fills whenever the authored one is not a usable cap (the gate's !isUsableRowLimit(authored)).
#4614	dashboard.test.ts:419	"date-range preset vocabulary — one source, in the spec"	Ruling A: the preset names move into the spec as their one source, and a date filter's default is checked against them.
#16458	dashboard.test.ts:850	"control — columns still declares no default … (the renderer infers it from widget spans)"	Item 4 was not landed: a .default(12) would retire the renderer's span inference and switch every auto-flow dashboard to the positioned grid.

Subject back in words (15 literals): "the #5068 gate" becomes "the props gate" (component-reference-rail.test.ts:34); "the three #18305 blocks" / "object blocks" become "object-map / object-gantt / object-tree" (component-type-vocabulary.test.ts:88, component.test.ts:4295); the four "#11661 keys" titles name defaultCollapsed / icon / description (component.test.ts:832, :848, :860, :875), because id-free sibling titles already say "the section presentation keys"; "#18639 scope fences" becomes "scope fences of the columns widening"; "the twin of the #14406 census pin" becomes "the twin of the census pin that no door refuses the rule array"; "the #7750 specimen shape" becomes "the my-work specimen shape"; the four #5011 — prefixes in dashboard-compareto.test.ts become compareTo — where the title needs a subject, and go where it already has one (:61); "the words #5042 measured" becomes "every word authors were measured spelling … reaches …".

Dropped where already stated (63 literals, 69 ids). A number goes only where the title already says its decision. Examples: "ComponentPropsMap["record:alert"] (#8744)"; "user:profile is not author-placeable (#14159, ruling B)"; "ai:chat_window is retired, refused by name (#21504)"; the six "(#6276)" picker titles, each already naming what the declaration does; "the four object-* sort doors — one sort orthography, the array (objectui#8221, decision batch #77, option B; #18305)"; the [#4876], [#5010], [#17779], [#20958] and [#21293] prefixes on dashboard.test.ts, each in front of the rule it names; "drill branch (#5022): …", whose sibling labels already read "… branch: …". 批 17 stays as a batch label in stage 18's form, and ADR-0021 / ADR-0049 style citations are untouched.

No file is renamed. None of the 7 file names carries a number.

Readers

• Test-name filters: none. No tracked script, workflow or package config passes -t / --testNamePattern (the hits are mapfile -t, docker build -t, type -t, lsof -t, and a preflight's option vocabulary).
• Snapshots: none. No __snapshots__ directory is tracked under packages/spec, and none of the 7 files calls a snapshot matcher.
• Projects: all 7 files run in the local project; packages/spec/vitest.repo-tests.json lists none of them.
• By substring: every old literal, its id-bearing fragment and a window around each id (301 needles) was searched with git grep at the base, across the tracked tree outside its own file. No gate, doc, filter, snapshot or scripts/check-*.mjs self-test reads one. The 6 hits:
  • a code comment in lint/src/validate-component-props.test.ts:540 ("the showcase my-work: the personal work queue authors filters: (plural) and no $filter ever reaches the wire — the grid lists every row #7750 specimen shape");
  • a QA checklist source entry, docs/qa/platform-checklist/areas/dashboards.json:406, which anchors on dashboard-compareto.test.ts#dashboard and describes it in its own words ("dashboard widget compareTo:三个声明分支在 ADR-0021 dataset 路径上全部无效(两个静默丢弃,一个抛错) #5011 — compareTo converged on …"). The checklist gate looks up the dashboard symbol, which this PR leaves in the file, and reads none of the titles. pnpm check:platform-checklist exits 0 at the head;
  • a sibling title in service-analytics (dataset-compare-dimension-resolution.test.ts:74, "dashboard widget compareTo:三个声明分支在 ADR-0021 dataset 路径上全部无效(两个静默丢弃,一个抛错) #5011 — …");
  • three hits on one same-id title in this card's later ui/ stage, ui/view.test.ts:4236, the visibility twin of the message-order describe, citing 三个手写 unrecognized_keys error map 绕过 strictUnknownKeyError,把说明句夹在「哪个键错了」与处方之间 —— #5955 的修法与 #5593 的迁移都够不到 #6416 / [spec] Fold the three hand-written unrecognized_keys error maps into strictObject guidance — requires a set-keyed guidance form, and closes the alias-integrity gate's blind spot (#6416 direction 2) #6619.

Text-only proof

Stage 10's scratch tool (textonly10.cjs, md5 d5e4801dbb4329ab1984da91e92fc47c) compares base and head file by file on three legs:

1. Skeleton: the full AST, with string pieces masked. It must be identical.
2. Comments: every comment, byte-equal.
3. Strings: each changed string leaf must sit in a test-call title position or on a declared line, must carry a tracker id before, and must carry no # plus digits after. This stage declares one line, dashboard.test.ts:205.

• Result: 7 of 7 files SAME on all three legs, with the per-file counts predicted in writing before the run.
• Totals: 99 changed string leaves in 99 literals: 98 titles and 1 declared. The diff's + and - lines are exactly the 99 planned lines as multisets, and every file keeps its line count. dashboard-chart-structure-refusal.test.ts is untouched.
• Controls (13 of 13 as predicted, on scratch copies, each anchor hit once): identifier rename DIFF; numeric literal DIFF; comment edit COMMENT DIFF; a non-title string given an id VIOLATION; a rewritten title given a new id VIOLATION; a title that was id-free at base edited VIOLATION; one title reverted to base SAME; an it.each row given an id VIOLATION; an undeclared orderPin label changed VIOLATION; a title re-split into a + chain DIFF; the declared label reverted to base SAME; the declared label given a new id VIOLATION; a kept colour literal edited VIOLATION. The first run predicted VIOLATION for the declared-label revert: putting (#5022) back where it was reproduces the base text exactly, so SAME is the right answer, and a control that gives the label a new id was added. That run read 11 of 12.
• Templates and tables: no .each title, %s / $name placeholder or table row changes.

Test counts: the 7 files were run at the base, in a separate base worktree, and at the head, with --project local --project repo. Both sides read 677 tests in 7 files, all passed, with the same count and status sequence per file in 7 of 7. 469 full test names change, and each changed name equals the base name with the planned replacements applied (0 mismatches). One full name repeats 5 times on both sides: an it.each row in dashboard.test.ts whose printed name is cut at the same point for 5 rows. Only its describe prefix changed.

Changeset: skip-changeset

Measured, not assumed:

• npm pack --dry-run of @objectstack/spec lists 2068 files. 0 of the 6 touched files are in it, and no *.test.ts at all. The controls src/ui/component.zod.ts and dist/index.mjs are in it.
• In the built dist/, a new phrase and an old literal each read in 0 files. The control Unrecognized key reads in 42.

So this PR publishes nothing, and no changeset is added.

Verification (at ec96327761)

• pnpm turbo run build over all packages: 71 / 71, through the shared verify lock (VERDICT command-exit 0).
• @objectstack/spec:
  • vitest run --project local: 618 files, 18450 passed, 1 todo.
  • typecheck: exit 0, including check:test-typecheck (52 files / 246 errors / 135 pinned signatures held). Its program holds all 7 group files, counted with tsc --listFilesOnly -p tsconfig.test.json.
  • check:generated: all 15 generated artifacts up to date, against the dist/ the build above wrote.
• Gates: dispatch-gates --commands derived 79 families, the same set as stage 20, and all 79 exit 0. --ran reconciles: 79 derived, 79 run, 0 NOT-MEASURED, 0 UNRUN, every family with its exit code recorded. The five roster families whose rosters sit under a touched directory were also run, and each exits 0: check:meta-url-spelling, check:spec-changes, check:authz-resolver, check:error-code-casing and check:filter-alias-parity. So does check:platform-checklist, for the checklist entry above.
• ESLint, a proven narrowing: --no-inline-config over the 7 files reads 0 errors and 0 warnings. The population comes from ESLint's own config: 7 configured, 0 ignored. No file sets parserOptions.project or projectService, so no untouched file's verdict can move.
• check-governed-merges --test: NOT governed, 198 changed lines (+99 / -99).
• A control-byte scan over the 6 changed files finds none.
• Review round 1, at 69ea423302: two titles reworded, one line each: the row-cap describe (component.test.ts:4499) now states the gate's guard, and the offset-alias title (dashboard-compareto.test.ts:160) reads straight. Text-only proof against the base: 7 of 7 SAME, 99 changed leaves (98 title, 1 declared). The 7 files at base and head: 677 / 677 passed, count and status sequence identical in 7 of 7, 469 changed full names, 0 mismatches against the plan. ESLint over the 7 files: 0 errors, 0 warnings. The group census still reads 4 / 4. typecheck exit 0, and check:nul-bytes OK. The derived gate set is the same 79 families; they were not re-run for a two-literal change.

main since the base

Re-fetched just before this PR opened, origin/main was four commits past the base (cab6396715: #21875, #21896, #21893, #21900). None touches any of the 7 files. #21893 touches 8 packages/spec files under automation/ and migrations/, and the census over packages/spec/src at 866683f96f (after #21893) still reads 764 / 807 with no file moved, so the merged tree reads this PR's 665 / 702. #21900 touches two more packages/spec files, both non-test migration entries, which this census does not count. So main was not merged. git merge-tree onto cab6396715 is clean.

Acceptance notes

• The four colour literals stay, as above. They are the only digit-only hex colours in the census, so the card's end state will read them unless a later stage changes the fixture values, which would be a fixture change rather than a text change.
• Same-id test titles in this card's later stages go with those stages: 21 lines in packages/spec/src, for example system/i18n-resolver.test.ts:1982 ("(spec(ui): walkAddressedPageComponents skips page:card's properties.footer as a back-compat spelling, but PageCardProps.footer is a declared, rendered slot, so nodes there go unjudged; the three platform page walks disagree on positions #20940)"), ui/page.test.ts:696 ("(ui#6206-B, finding(spec): ElementDataSourceSchema.filter (page.zod.ts) still declares the MongoDB-style FilterConditionSchema — the binding-level sibling of #14406 outside ComponentPropsMap, while objectui's composition seam lowers three shapes and its own pins author the tuple array #15442)"), ui/view-strictness-batch18.test.ts:91 ("未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 批 18 — …"), ui/view.test.ts:4236 ("(三个手写 unrecognized_keys error map 绕过 strictUnknownKeyError,把说明句夹在「哪个键错了」与处方之间 —— #5955 的修法与 #5593 的迁移都够不到 #6416 / [spec] Fold the three hand-written unrecognized_keys error maps into strictObject guidance — requires a set-keyed guidance form, and closes the alias-integrity gate's blind spot (#6416 direction 2) #6619)") and ui/view.test.ts:4793 ("(spec(ui): the new per-kind view limit and the base pagination.pageSize are two authorable row bounds with no declared precedence — and an APPLIED default makes the react tier's own "fills it only when unset" arm unreachable #19228)").
• Same-id test titles in other packages are their lanes' test-string shares. A search of describe / it / test lines outside packages/spec/src finds 40 lines citing ids this PR handled, in 10 packages: lint 25 (8 files), service-analytics 3 (1), cli 2 (1), platform-objects 2 (1), plugin-audit 2 (2), plugin-security 2 (2), and one each in plugin-sharing, rest, service-automation and spec/scripts. Examples: lint/src/validate-component-props.test.ts:783 ("… are dispatched (spec: record:alert / record:quick_actions / record:history have no ComponentPropsMap row — same silent no-op mechanism #8691 closed for the rail #8744)"), service-analytics/src/__tests__/dataset-compare-dimension-resolution.test.ts:74 ("dashboard widget compareTo:三个声明分支在 ADR-0021 dataset 路径上全部无效(两个静默丢弃,一个抛错) #5011 — …"), rest/src/meta-types-schema-titles.test.ts:131 ("spec: the dashboard authoring form has no channel for ITEM-level property names — header.actions[] columns render as raw keys in every locale, and columns documents a default it never declares #16458 — …"). The two [#6206] hits in plugin-security and plugin-sharing cite objectstack#6206, a different record from ui#6206.
• Code comments still carry ids in these files and their sources, for example the #9198 tombstone comment in component.test.ts, the #19228 header above component.test.ts:4499, and the #6416 / #5955 docblock above dashboard.test.ts:163. Comments are not this card's share, and none is touched here.

---

Generated by Claude Code

[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 e6dc7a240617eaeef9a64e788bf6e5561c107f1b → packageMentionDocs.