chore(deps): take the 17.4.0 @objectstack/* line - #8783
Merged
Conversation
Float all seven `@objectstack/*` entries from 17.3.0 to 17.4.0 as one line: client, core, formula, lint, sdui-parser, spec, types. `package.json` is untouched — every declared range is a caret inside major 17 (`^17.0.0`, `^17.1.0`, `^17.2.0`, `^17.3.0`), all of which already admit 17.4.0. This is a lockfile refresh only. The re-resolve is pinned so the diff carries nothing but the seven identities. A plain `pnpm update -r "@objectstack/*"` also floats `zod ^4.4.3 -> 4.5.4`, which forks `ai@7.0.65`'s peer context and yields two physical copies each of spec, formula and lint — the objectui#8326 / #8333 defect class that `scripts/check-lockfile-integrity.mjs` exists to catch. That float is not caused by this bump: `@objectstack/spec` and `@objectstack/core` declare the identical `zod: ^4.4.3` at 17.3.0 and 17.4.0. It is `pnpm update` re-resolving an already-satisfied range. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
Both are mechanically coupled to the family move in the previous commit, and
each carries its own prescription for exactly this event.
`e2e/live/ci/backend.env` — `OBJECTSTACK_VERSION` 17.3.0 -> 17.4.0. The file's
own header states the rule ("bump this in the same PR that bumps the console's
@objectstack pins"), `content/docs/guide/ci-cd-pipeline.md` repeats it, and
`scripts/__tests__/ci-cd-pipeline-doc.test.ts` enforces equality with the
version `pnpm-lock.yaml` resolves. A mismatched pair makes the live-e2e lane
carry no information either way (objectui#7689).
`scripts/__tests__/check-lockfile-integrity.test.ts` — its two samples are
transformations OF the real lockfile, anchored on the current pin, and the
assertion that broke says so itself: "the spec snapshot key moved — rebuild
this sample before trusting it". Only the anchor moves; the simulated
downgrade target (17.2.0) and every assertion are unchanged, so both samples
still reproduce objectui#8326 and objectui#8333 as before.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
…ectstack-17-4-0-line
…e sample The previous commit rewrote the sample anchor from 17.3.0 to 17.4.0 and lost one backslash level in the process. The pattern is built through `new RegExp(...)` from a template literal, so `17\.4\.0` reaches the constructor as `17.4.0` and both dots become "any character" — matching, but by accident. `no-useless-escape` caught it. Restored to `17\\.4\\.0`, which is byte-identical to the base line apart from the version digit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
This was referenced Sep 9, 2026
….shape (objectui#7845) objectstack#15469 closed `GanttConfigSchema` and declared the ten keys plugin-gantt used to read through its `.passthrough()` window. objectui carried its own copy of those ten in two places; with the spec declaring them, the copies became duplicates and `ObjectGantt.blockPrecedence.test.tsx`'s no-duplicates pin measured it (40 keys, 30 unique). Retired both copies: - `GANTT_CONFIG_EXTENSION_KEYS` (`plugin-gantt/src/ObjectGantt.tsx`) — the flat key list is now `GanttConfigSchema.shape` plus the `dependencyField` alias. - `GanttConfigExtensionFields` (`types/src/zod/objectql.zod.ts`) — the flat face takes all ten from `SpecGanttConfigSchema.shape` by reference like its other members, and the nested `gantt` block is the spec schema itself rather than the spec schema extended with the local map. Compared member for member before deleting, as the card required: the spec's declarations cover the same ten keys, the same `interactions` (move/resize/progress/link) and `timeSegments` (dayStart/bands/showMidnight) sub-shapes and the same band members, with strictly fuller describes. The local copy carried no describe, alias or member the spec's lacks, so there is no difference to file. Also corrected the prose that still called the spec loose: `types/objectql.ts` said `timeSegments` was "the one key the spec genuinely does not model" and that `GanttConfigSchema` is `$loose` upstream — both false, and the first read as an invitation to write undeclared sub-keys that the `strictObject` now refuses by name. `zod/objectql.zod.ts` justified its own local `.passthrough()` by pointing at the spec's gantt/tree windows, which no longer exist; the local reason (and the measurement that `swimlaneField` / `endField` are still spec-undeclared) replaces it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
…g the spec rename (objectui#7783) @objectstack/spec 17.4.0 renamed the dashboard's auto-refresh key (objectstack#15680, ruling B on objectstack#14478: a duration-shaped number carries its unit in the key name, not only in the describe prose) and left a `retiredKey` tombstone behind the old spelling. objectui's zod `DashboardComponentSchema` takes its spec-owned half from `SpecDashboardFields` by reference, so that face moved on its own the moment the lockfile did. What did NOT move was the TypeScript twin, and the pair's drift ledger caught it: `zod-mirror-parity.test.ts` refused to compile with `complex.zod.ts#DashboardComponentSchema` gaining `refreshInterval`. Moved here: the TS declaration; the four reader sites, keeping the `* 1000` arithmetic identical (the value is still seconds — the multiply is exactly the tell the rename exists to remove, and it now sits under a key that says so); the published registration input; the metadata-admin zh overlay key; the config panel's field key and the `DashboardConfig` model behind it; and the fixtures and pins that spell the key. ⛔ Deliberately NOT renamed, measured rather than swept: - `plugin-report` / `types` `reports.ts` / `reports.zod.ts` — the report component's own key, excluded by the card. - `DataBinding.refreshInterval` (`types/src/data.ts`) and `AIInsightsSchema.refreshInterval` (`types/src/ai.ts`). The card lists both among "the TS types" for this rename; they are not. Neither has a zod mirror or a `@objectstack/spec` counterpart (spec/ui exports nothing matching either name), so there is no producer behind a rename — and `DataBinding`'s is documented in MILLISECONDS, which makes `refreshIntervalSeconds` the wrong name for it outright. `content/docs/api/schema-reference.md` documented this key as milliseconds with a `30000` sample. It was never milliseconds; corrected with the rename. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
…Rule array arm (objectui#7663)
objectstack#14406 converged `ComponentPropsMap['element:record_picker'].filter`
from the MongoDB-style `FilterConditionSchema` record onto
`z.array(ViewFilterRuleSchema)` — the last record-form `filter` in the map,
closing the maintainer's 2026-08-25 ruling that the platform carries one filter
orthography (objectui#6206-B). @objectstack/spec 17.4.0 ships it, so the
declaration here now teaches a shape the save gate refuses and a JSX page
writing the legal array form draws a false `type-mismatch`.
Measured at the installed spec before flipping: the record form is refused by
KIND at `filter` (`invalid_type`, expected array), a bare tuple is refused at
`filter.0` (expected object), and `[{ field, operator, value }]` is accepted —
with `operator: 'eq'` normalised to `'equals'` on parse, which is why the
fixture spells the canonical form.
- `inputs.filter` flips `type: 'object'` to `'array'` and its description is
rewritten around `[{ field, operator, value }, …]`. The PRECEDENCE paragraph
is kept verbatim in substance: `dataSource.filter ?? filter` did not change.
- The two parity pins swap sides — the record form is now the refused shape,
the rule array the accepted one — and the refusals are asserted as an
envelope (issue code plus path), so a parse that failed for an unrelated
reason cannot stand in for the contract refusing the record form.
- The coarse-type agreement test moves with them, and now states WHERE the
agreement ends: `'array'` has no member arm, so a tuple list passes the
manifest check and is refused only by the spec. That gap is named rather than
papered over — the description carries what the coarse type cannot say.
No renderer change: `filter?: unknown` passes through to `$filter` and `find()`
already lowers the array form. The console parity test's `element:record_picker`
arm goes green by derivation once the declaration moves; only its MEMBER_PINS
prose is edited, to describe the arm that is actually pinned.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
… declares it (objectui#8172) objectui#8172 was filed because four faces taught `limit` on an `object-kanban` — the renderer sending `$top: schema.limit ?? DEFAULT_KANBAN_LIMIT`, both `@object-ui/types` faces, and a documented section — while the strict `ComponentPropsMap` refused it BY NAME, so an author following this repo's own docs wrote a node the save gate rejected. The maintainer ruled option A (the contract catches up, 2026-09-07 「同意」), objectstack#16503 landed as objectstack#16562, and @objectstack/spec 17.4.0 ships `limit: z.number().int().positive().optional()`. ⭐ All three of the card's disagreeing faces were RE-MEASURED at this pin rather than assumed, as the card asked: - renderer — `ObjectKanban.tsx` still sends `$top: schema.limit ?? DEFAULT_KANBAN_LIMIT`, with `schema.limit` in the effect deps. Unchanged. - `@object-ui/types` — BOTH faces declare `limit` now (`objectql.ts` and the zod mirror `objectql.zod.ts`).⚠️ This falsifies the reading recorded on the card by the spec seat, which measured only the plugin's own `KanbanSchema` declaring it at pin `a472b07`; objectui's shared faces have since caught up, so there was no missing declaration to add. - docs — `plugin-kanban.mdx` teaches it correctly. Its one loose sentence is tightened here, because the key is now published with a precedence-bearing description and the two must agree: the binding's own `limit` wins outright, a named view's `pagination.pageSize` fills the cap only when the board leaves `limit` unset. Verified against `ElementDataSourceGate`'s `readLimit(base) === undefined` branch, not restated from the spec's describe. So the only face still out of step was this repo's registration, and that is what moves. ⛔ The declaration carries NO default: a materialised `limit` would defeat that same `readLimit(base) === undefined` branch and a bound view's `pageSize` would then never fill it — the spec seat's explicit warning. The `object-kanban::limit@spec` ledger row in `block-config-schema-parity-8216` is deleted, which is the ratchet working: a row that no longer describes a violation is as red there as a violation with no row. Its self-deleting probe went with it, so the spec-face ledger is now empty — and an empty probe list is indistinguishable from a broken oracle lookup, so a live control replaces it: the former violation must now parse clean AND an undeclared sibling must still be refused by name. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
…this repo asserted against (objectui#8785)
Each was measured against BOTH spec versions before being repaired, so
"changed in 17.4.0" is a reading rather than an inference.
1. `job.timeout` retired in favour of `timeoutMs`. The preview sample carried
`timeout: 600000` and a comment arguing for that spelling ("the unit is
already milliseconds"). The spec now refuses the key with a tombstone making
the opposite argument — the unit belongs in the name, since the sibling
`retryPolicy.backoffMs` already spelled its own and one surface was teaching
two conventions. Same ruling family as objectui#7783. The SAMPLE moves; the
value is unchanged. Measured: `timeoutMs: 600000` parses clean through
`ObjectStackSchema`, `timeout: 600000` is refused at `jobs.0.timeout`.
2. The flow end-node `outcome` enum narrowed to `completed | refused`. The
sample's `outcome: 'success'` is no longer a member. It becomes `'completed'`
— ⛔ NOT `'refused'`, which the spec additionally requires a `message` beside
(measured: `refused` with no message fails at `config.message`), and which
would in any case describe the wrong ending for this sample.
3. The dashboard `gap` help text. The pin asserted that the ENGLISH producer
copy still says "Tailwind"; 17.4.0 rewrote it to "Space between widgets, in
steps of 0.25rem (4 = 1rem)".
That leg is a non-vacuity control, not the subject: without it, "the zh copy
does not say Tailwind" would pass just as well on copy that never said it.
Re-pointing it at the new sentence buys exactly one release — this repo does
not own that text. So the control now asserts the PROPERTY the overlay exists
for: the producer's copy reaches for developer vocabulary (a framework name,
or digits welded to a CSS unit) and the zh overlay carries none of it. Still
non-vacuous, no wording pinned, and if the spec ever writes this hint in
plain author language the control reddens and someone re-reads the overlay —
which is correct, since the overlay would then have nothing left to do here.
⚠️ `\brem\b` does not work for this: the boundary before `rem` never matches
in `0.25rem`, because `5` is a word character. Measured both ways against
both spec versions' copy before landing.
⛔ None of the three is patched green by relaxing an assertion: in all three the
spec is the producer and it moved deliberately.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
Neither has an open objectui card. Both are tests that predicted this exact
event in their own prose and said what to do when it fired, so the repair is the
one each prescribes — not a new decision.
`MetadataService.specKeyReference.test.ts` — the VERSION SKEW row. Until 17.3.0
the spec's `reference` emptiness test was an equality against `''`, so `' '`
parsed green while this writer refused it: a real divergence, declared rather
than hidden, with the spec half written as a tripwire for the day
objectstack#16920 reached the pin ("this line reddens when the pin reaches it —
at which point the reading becomes `false` and nothing else here moves").
17.4.0 carries the fix. Measured: `' '`, `''` and an absent target are now all
refused under the same `custom` issue at the same `reference` path the writer
names, while `'account'` and `' account '` still parse — the trim is for the
TEST only, which is what the writer's own pass-it-through row depends on. The
verdict flips and is asserted as an envelope (code plus path), because "refused"
and "refused AS a blank target" are separable claims. `MetadataService.ts` is
untouched, exactly as the note predicted. Closes the divergence objectui#8621
recorded; objectstack#16920 is the other repo's card and is not touched.
`toolLabels-locale-parity-7481.test.ts` — `AHEAD_OF_PIN`, the hand-held list of
tools the cloud runtime registers ahead of the spec snapshot. All five names it
carried are in `PLATFORM_TOOLS_BY_PACKAGE` at 17.4.0, and the file's own rule is
that a caught-up name must be REMOVED so the list never becomes a second
registry. Emptied, ⛔ not deleted: the next tool registered ahead of a snapshot
needs the same hatch.
⚠️ Emptying it turns three guards into tautologies — `[].filter(…)` is `[]`,
`arrayContaining([])` passes on anything — including the one whose comment says
it exists to stop the suite going vacuously green if the spec export disappears.
So they are re-anchored: a `GRADUATED` constant records the five names and
asserts they ARE in the registry, and the coverage floor is read off the
registry rather than off the emptied list. If the registry ever stops listing
one of them, that is now what reddens, and the repair is to put the name back on
`AHEAD_OF_PIN`.
⛔ objectui#7481 is CLOSED (completed via PR #7710) and is not reopened.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
Both surfaced in the full suite, both caused by edits in this branch and neither by a spec change: - `check-doc-example-types.mjs`'s `UNGATED_EXAMPLES` is keyed by `path:line symbol`, and the gantt prose corrections in `packages/types/src/objectql.ts` added six lines above `ObjectFormSchema`'s `@example`. Re-anchored 1607 to 1613; verified by reading the `@example` line at both revisions. - `doc-version-claims` refuses a version literal on a doc surface that nothing in this repo can re-check. The `refreshIntervalSeconds` row added to `schema-reference.md` carried "@objectstack/spec 17.4.0". Taken out rather than added to `KNOWN_CLAIMS`, which is the remedy the gate itself prefers: the sentence needs the RENAME, not the release it shipped in, and the card number already points at the full account. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
…ectstack-17-4-0-line # Conflicts: # scripts/check-doc-example-types.mjs
…ollows `node scripts/check-changeset-presence.mjs` refused without one: 26 of the changed files are published source of a package the release covers. Scored `minor` across the eight packages whose `src/` moved — never `major`, because this repo's fixed group tracks the @objectstack major (AGENTS.md §版本号策略, enforced by scripts/check-changeset-no-major.mjs). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
github-actions
Bot
added
documentation
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
…ectstack-17-4-0-line
Contributor
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8772
Fixes #7783
Fixes #7663
Fixes #8172
Fixes #7845
Fixes #8785
Moves the
@objectstack/*family from 17.3.0 to 17.4.0 as one line, and answers everycontract that move flipped. ⛔ No red is patched green by relaxing an assertion: in each
one the spec is the producer and it moved deliberately, so the pin is re-pointed at the
truth or the local duplication is deleted.
Why one PR and not six. Each repair alone still leaves this branch red on the other
fifteen, so none could merge on its own. The bump and every pin it flips by design are
one queue position.
What moved in the dependency line
pnpm-lock.yaml— all seven, together:client,core,formula,lint,sdui-parser,spec,types.package.jsonis untouched, as the card predicted. Every declared range is a caretinside major 17 (
^17.0.0,^17.1.0,^17.2.0,^17.3.0) and all of them alreadyadmit 17.4.0. All seven were verified present on npm before the line moved.
Two other files move because they are pinned to the lockfile by this repo's own rules,
and each names this exact event:
e2e/live/ci/backend.env—OBJECTSTACK_VERSION17.3.0 to 17.4.0. Its header,content/docs/guide/ci-cd-pipeline.md, andscripts/__tests__/ci-cd-pipeline-doc.test.tsall require it to equal the spec version the lockfile resolves; a mismatched pair makes
the live-e2e lane carry no information either way (objectui#7689).
scripts/__tests__/check-lockfile-integrity.test.ts— its two samples aretransformations OF the real lockfile, anchored on the current pin. The assertion that
broke says so itself: "the spec snapshot key moved — rebuild this sample before trusting
it". Only the anchor moved; the simulated downgrade target (17.2.0) and every assertion
are unchanged, so both samples still reproduce objectui#8326 and objectui#8333.
The lockfile diff is confined to the seven, deliberately
A plain
pnpm update -r "@objectstack/*"is not what landed here. It does two thingsthis card must not do:
package.jsonfiles (ranges to^17.4.0, plus unrelated indentation),which the card forbids.
zod ^4.4.3to 4.5.4. That forksai@7.0.65's peer context and yieldstwo physical copies each of
spec,formulaandlint— precisely theobjectui#8326 / objectui#8333 defect class
scripts/check-lockfile-integrity.mjsexists to catch. It also drifted
serovaland@mongodb-js/saslprep.That float is not caused by this bump:
@objectstack/specand@objectstack/coredeclarethe identical
zod: ^4.4.3at both 17.3.0 and 17.4.0. It ispnpm updatere-resolvingan already-satisfied range. The re-resolve was therefore run with those four pinned through
a temporary root
pnpm.overridesblock, the manifests restored, and the lockfile settledwith a plain
pnpm install.Result: every changed line in
pnpm-lock.yamlis an@objectstack/*identity or itsintegrity hash.
zod,seroval,seroval-pluginsand@mongodb-js/saslpreparebyte-identical to base. Resolution count 1822 to 1822.
The sixteen reds, answered
typestype-check:zod-mirror-parity.test.ts—DashboardComponentSchemadrift gainedrefreshIntervalplugin-dashboard/__tests__/dashboardAuthoredInputs.test.tsx— spec refusesrefreshIntervalby tombstoneapp-shellmetadata-form-i18n.test.ts— the 自动刷新 label, key gonecomponents/__tests__/record-picker-inputs-spec-parity.test.ts(2 tests)consoleregistry-inputs-spec-parity.test.ts—element:record_pickerarmconsoleregistry-inputs-spec-parity.test.ts—object-kanbannow declareslimitblock-config-schema-parity-8216.test.ts(2 tests) — ledger rowobject-kanban::limit@specstaleplugin-ganttObjectGantt.blockPrecedence.test.tsx— 40 keys, 30 uniqueplugin-chatbottoolLabels-locale-parity-7481.test.ts—AHEAD_OF_PINcaught upapp-shellMetadataService.specKeyReference.test.ts— the pin reached the trimconsolepreview-samples-spec-valid.test.ts— job sample,jobs.0.timeoutconsolepreview-samples-spec-valid.test.ts— flow sample,nodes.13.config.outcomeapp-shellmetadata-form-i18n.test.ts— thegap"Tailwind" controlci-cd-pipeline-doc.test.ts,check-lockfile-integrity.test.ts⛔ Two of these have no open objectui card and are repaired here without opening one:
objectui#7481 is CLOSED (completed via PR #7710) and is not reopened, and
objectstack#16920 lives in the other repo and is not touched.
What each card's repair actually was
#7845 — gantt: the deletion the card prescribes
GANTT_CONFIG_EXTENSION_KEYS(plugin-gantt) andGanttConfigExtensionFields(
@object-ui/types) were objectui's copy of the ten keys it read throughGanttConfigSchema's.passthrough()window. objectstack#15469 closed the window anddeclared all ten, so the copies became duplicates — which is exactly what the
no-duplicates pin measured (40 keys, 30 unique). Both are retired; the flat face takes all
ten from
SpecGanttConfigSchema.shapeby reference like its other members, and the nestedganttblock is the spec schema itself.⭐ Compared member for member before deleting, as the card required: the spec's declarations
cover the same ten keys, the same
interactions(move/resize/progress/link) andtimeSegments(dayStart/bands/showMidnight) sub-shapes and the same band members, withstrictly fuller describes. The local copy carried no describe, alias or member the spec's
lacks, so there is no difference to file.
The card's item 3 (prose that still calls the spec loose) is done, and one of its three
sites was premise-false:
normalize-list-view.test.ts's "the configs are.passthrough()for" needs no change. Measured — that test assertskanban.swimlaneFieldand
timeline.endFieldsurvive normalization, and both are still absent from the spec'sKanbanConfigSchema/TimelineConfigSchema; the passthrough carrying them is objectui'sown local schema, not the spec's. What was false is the note in
zod/objectql.zod.tsjustifying that local
.passthrough()"for the same reason the spec puts it onGanttConfigSchema/TreeConfigSchema" — that precedent is gone, and only the local reasonsurvives.
#7783 — dashboard
refreshInterval→refreshIntervalSecondsobjectui's zod
DashboardComponentSchematakes its spec-owned half fromSpecDashboardFieldsby reference, so that face moved on its own the moment thelockfile did. What did not move was the TypeScript twin, and the pair's drift ledger is
what caught it. Moved here: the TS declaration, the four reader sites (the
* 1000arithmetic is identical — the value is still seconds, and the multiply is exactly the tell
the rename exists to remove), the published registration input, the metadata-admin zh
overlay key, the config panel's field key and the
DashboardConfigmodel behind it, andthe fixtures and pins that spell the key.
card lists
types/src/data.tsandtypes/src/ai.tsamong "the TS types" for the rename.They are
DataBinding.refreshIntervalandAIInsightsSchema.refreshInterval: neither hasa zod mirror, and
@objectstack/spec/uiexports nothing matching either name, so there isno producer behind a rename.
DataBinding's is documented in milliseconds, which makesrefreshIntervalSecondsthe wrong name for it outright. Both left alone — this is thesame trap the card itself flagged for the report component.
content/docs/api/schema-reference.mddocumented this key as milliseconds with a30000sample. It was never milliseconds; corrected with the rename.
#7663 —
element:record_picker.filtertakes the array armMeasured at the installed spec before flipping: the record form is refused by KIND at
filter(invalid_type, expected array), a bare tuple is refused atfilter.0(expectedobject), and
[{ field, operator, value }]is accepted — withoperator: 'eq'normalisedto
'equals'on parse, which is why the fixture spells the canonical form.type: 'object'becomes
'array', the description is rewritten around the rule array (the PRECEDENCEparagraph is unchanged in substance —
dataSource.filter ?? filterdid not move), and thetwo parity pins swap sides with the refusals asserted as an envelope rather than a bare
success === false. No renderer change. The console arm goes green by derivation.'array'has no memberarm, so a tuple list passes the manifest check and is refused only by the spec. Named
rather than papered over.
#8172 —
object-kanbanpublisheslimit⭐ All three of the card's disagreeing faces were re-measured at this pin, not assumed —
the card's explicit instruction:
$top: schema.limit ?? DEFAULT_KANBAN_LIMIT,schema.limitin the effect deps. Unchanged.@object-ui/typeslimit—objectql.tsand the zod mirror.KanbanSchemaat pina472b07.plugin-kanban.mdxteaches it correctly. One loose sentence tightened, because the key is now published with a precedence-bearing description and the two must agree.ComponentPropsMap['object-kanban']declareslimitas of objectstack#16503.So the only face still out of step was this repo's registration. ⛔ The declaration carries
no default: a materialised
limitwould defeatElementDataSourceGate'sreadLimit(base) === undefinedbranch and a bound view'spagination.pageSizewould thennever fill it — the spec seat's explicit warning. Precedence verified against that branch
directly, not restated from the spec's describe.
The stale
object-kanban::limit@specledger row is deleted, which is the ratchet working.Its self-deleting probe went with it, leaving the spec-face ledger empty — and an empty
probe list is indistinguishable from a broken oracle lookup, so a live control replaces it.
#8785 — the three unannounced changes
Each measured against both spec versions.
job.timeout→timeoutMs. The sample carried a comment arguing for the old spelling("the unit is already milliseconds"); the spec's tombstone makes the opposite argument,
the same ruling family as dashboard
refreshInterval→refreshIntervalSeconds: two declarations and six reader sites to move when the spec rename ships #7783. The sample moves; the value is unchanged.outcomeenum narrowed tocompleted | refused.'success'becomes'completed'— ⛔ not'refused', which the spec additionally requires amessagebeside (measured: it fails at
config.message) and which describes the wrong ending.gaphelp text. That assertion is a non-vacuity control, not thesubject, and this repo does not own the sentence — re-pointing it at the new wording buys
one release. It now asserts the property the overlay exists for: the producer's copy
reaches for developer vocabulary (a framework name, or digits welded to a CSS unit) and
the zh overlay carries none of it.
\brem\bdoes not work for this — the boundarybefore
remnever matches in0.25rem, because5is a word character. Both legs weremeasured against both versions' copy.
The two uncarded tripwires
Both are tests that predicted this exact event in their own prose and said what to do.
MetadataService.specKeyReference.test.ts— the VERSION SKEW row. objectstack#16920 nowtrims before the emptiness test, so
' ',''and an absent target are all refusedunder the same
customissue at the samereferencepath the writer names, while'account'and' account 'still parse. The verdict flips and is asserted as anenvelope.
MetadataService.tsis untouched, exactly as the note predicted.toolLabels-locale-parity-7481.test.ts—AHEAD_OF_PINemptied, ⛔ not deleted: the nexttool registered ahead of a snapshot needs the same hatch.
guards into tautologies (
[].filter(…)is[]), including the one whose comment says itexists to stop the suite going vacuously green. They are re-anchored on a
GRADUATEDconstant asserted to be in the registry.
Verification
All readings are on the merged head
5f90b36, taken afterorigin/main(42ddd7f) wasmerged and
pnpm installre-run. Exit codes were captured to a file before any pipe.pnpm buildpnpm type-checkpnpm vitest runover the nine touched packages +scriptspnpm test(the WHOLE suite, run to completion on an earlier head)pnpm exec eslint --no-inline-configover this PR's 28 changed TS/JS filesno-explicit-any, counted file-wide)check:*gate scriptscheck-governed-queue-guard --testover the 36 changed pathsThe 25 gates:
lockfile-integrity·control-bytes·spec-symbols·sdui-registration-pins·element-data-source-declaration·designer-field-key-parity·handler-key-reads·i18n-keys·i18n-drift·i18n-dead-keys·i18n-designer-parity·self-import·unreferenced-sources·readme-exports·side-effects-array·phantom-deps·icon-record-names·action-forward-parity·doc-fences·shell-escape-residue·vi-mock-specifiers·vi-mock-inherit· the three changeset gates.⭐
check:i18n-designer-parityis new onmainsince this branch opened (objectui#8834)and it reads the metadata-admin designer string tables this PR edits, so it was picked up
from the merged tree rather than from the gate list this branch started with. It passes.
pnpm testwas run to completion once and then narrowed, on each re-merge, tothe nine packages this PR touches plus
scripts. The two merges brought 45 commits ofother people's already-CI-green work and produced exactly one conflict — a
line-number-keyed ledger row both sides had shifted, resolved by measuring the merged
tree rather than by arithmetic. CI runs the full farm on the merged head.
pnpm lintrepo-wide is CI-owned; eslint here is narrowed to this PR's own changedfiles. That narrowing is sound rather than convenient:
eslint.config.jsdeclares noparserOptions.project, noprojectServiceand no*TypeCheckedpreset (measured: zerooccurrences of
parserOptions), so linting is per-file and type-unaware and this diffcannot move the verdict on a file it does not touch.
check-published-dist-toolingexits 1 on 10dist/tsconfig.tsbuildinfobuild records —the known objectui#7003 class. Eight of the ten packages are untouched by this PR, the
records are produced by running a local build at all, and
published-dist-gate.ymlrunsnightly and on changes to its own wiring, never on an ordinary pull request. Not caused
here and not repaired here.
The lockfile, re-verified after each merge
Neither merge touched
pnpm-lock.yaml, and the two manifestsmaindid move(
packages/plugin-ai/package.json, the rootpackage.json) each added ascriptsentry,not a dependency. Nothing was hand-resolved and nothing was regenerated. Measured against
the merge base by the gate itself:
All seven
@objectstack/*resolve at 17.4.0;zod,seroval,seroval-pluginsand@mongodb-js/saslprepare byte-identical to base. Every one of the 132 changed lockfilelines is an
@objectstack/*identity, its integrity hash, or aversion: 17.3.0 → 17.4.0line for one of the seven — the residue after excluding those three classes is empty.
pnpm installafter the merge changed nothing.Changeset
.changeset/8772-objectstack-17-4-0-line.md, measured not assumed:node scripts/check-changeset-presence.mjsread "34 file(s) changed, 26 of them publishedsource of a package the release covers" and refused until one was added. Scored
minoracross the eight packages whose
src/moved — ⛔ nevermajor, because this repo's fixedgroup tracks the
@objectstackmajor (AGENTS.md §版本号策略,scripts/check-changeset-no-major.mjs). The pending.changeset/dashboard-declare-honoured-inputs.mdnamesrefreshIntervalin prosedescribing a key this PR renames before either ships, so its one token is corrected too.
Acceptance note, out of scope
e2e/live/ci/backend.envsays to retireBETTER_AUTH_VERSIONande2e/live/ci/better-auth-pin.mjs"in the PR that bumps OBJECTSTACK_VERSION past theupstream fix" (objectstack#16186). That condition now appears met:
@objectstack/plugin-authpins the whole better-auth family exactly at 17.4.0 (
1.7.2, caret dropped) where17.3.0 declared
^1.7.2. Not acted on here — retiring the pin changes the live-e2e lane'sbehaviour and adds a verification surface this PR cannot exercise.
#7267does not fire on this bump, contrary to the card starred on #8772:LocationField.optionalKeys.test.tsxruns and all 12 tests pass. The repair already landedunder the 17.3.0 pin. Already routed to
pm:retriage; ⛔ not folded in here.#7716and#7707were checked and are also not this family.🤖 Generated with Claude Code
https://claude.ai/code/session_019wtfW1ZxGnP1XKGc9uZVms
Generated by Claude Code
Generated by Claude Code