[objectstack-fleet]

domain:spec#2 · os-support-ai · session_01WGufzhJG3tKnksHVa1krBz

Requested by Yibo Wang · project thread
Fixes #29541
Supersedes #29586 (same commits, resumed on a new branch, merged with main after #29589; #29586 is closed)

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么：os migrate meta --stored 现在会列出「看板声明了内置 dateRange，又有一个全局筛选器也叫 dateRange」的已存数据行；两条看板筛选器迁移条目的验收句都补上了「存量预览会列出这种行」。
• 为什么改：spec(dashboard): a globalFilters entry named dateRange parses and silently replaces the built-in date range's binding #29213 已让每道门拒收这种看板，但升级前的存量预览不报它，运维升级前看不到哪些看板下次保存会被拒。
• 风险与回滚：只读检测，任何入口的接受/拒收结果都不变，不改写任何行；回滚即 revert 本 PR。
• 先看：packages/spec/src/conversions/refused-shapes.ts 的 dashboardReservedDateRangeGlobalFilter（调用拒收门同一个判定函数，与 fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 的 objectExtensionFieldPatchKeyGrammar 并存），再看 refused-shapes.test.ts 末尾 spec(conversions): the stored pass does not list a dashboard whose globalFilters entry is keyed dateRange beside a declared dateRange (the #29213 refusal) #29541 五条。
• 两分钟验证：pnpm --filter @objectstack/spec exec vitest run src/conversions/refused-shapes.test.ts，预期 92 个测试全过（含 spec(conversions): the stored pass maps no object_extension row onto objectExtensions, so no conversion or refused-shape detector ever runs over a stored extension #29554 的四条），其中 spec(conversions): the stored pass does not list a dashboard whose globalFilters entry is keyed dateRange beside a declared dateRange (the #29213 refusal) #29541 五条。
• 需要你做的：无，席位落地。

What changes

• Stored listing. REFUSED_STORED_SHAPES gains dashboardReservedDateRangeGlobalFilter (id ui-dashboard-global-filter-reserved-date-range-refused, the spec(dashboard): a globalFilters entry named dateRange parses and silently replaces the built-in date range's binding #29213 D3 entry of step 18), registered right after dashboardDuplicateGlobalFilterName. It walks stack.dashboards[] and calls reservedDateRangeGlobalFilters(dashboard.dateRange, dashboard.globalFilters) from ui/duplicate-global-filter-names.ts, the predicate DashboardSchema's refinement reads; no logic is copied. One TODO per entry, at dashboards[i].globalFilters[j].name (or .field when the entry has no name), which is the site the parse refuses. from carries the reserved key and the index only. The reason leads with the fate (no lossless rewrite, loads with _diagnostics.valid: false, next save refused 422) and ends with the predicate's own message.
• Upgrade guide entries. acceptanceCriteria of 18.ui-dashboard-global-filter-reserved-date-range-refused.ts and of 18.ui-dashboard-global-filter-duplicate-name-refused.ts (dashboards: two globalFilters with the same name are accepted; the board draws one control and its value filters the other filter's field #29023) each gain one sentence: os migrate meta --stored lists each such stored dashboard under the entry's id, at the site the parse refuses.
• Docblock. The refused-shapes.ts header's list of borrowed predicates names reservedDateRangeGlobalFilters.
• Changeset. .changeset/29541-reserved-date-range-stored-detector.md, @objectstack/spec patch.

Why

The refusal's D3 entry already promised that a stored row with the pair loads as invalid and is refused on its next save, but the stored preview read such a row as already on protocol. An operator previewing the upgrade saw nothing.

Tests

refused-shapes.test.ts gains five cases under #29541, and the roster pin names the new id:

• the card shape (a declared dateRange beside an entry named dateRange): one TODO at dashboards[0].globalFilters[0].name with the reserved word, the built-in date range and the predicate's message; the row is not rewritten, and the parse still refuses the same site;
• an entry with no name and field: 'dateRange': listed once at .field, as the parse locates it;
• two entries both named dateRange: listed under each refusal (one duplicate-key TODO and two reserved-key TODOs), exactly the three custom issues the parse raises;
• CONTROL: with no dateRange declared, an entry keyed dateRange (by name or by field) is not listed and the parse accepts it;
• CONTROL: beside a declared dateRange, a named entry whose field is dateRange is not listed and parses.

Ablation (fix committed first; scripts/ablation-replace.mjs --delete on the registry line dashboardReservedDateRangeGlobalFilter,): Tests 4 failed | 84 passed (88). The roster pin and the three listing cases went red, both controls stayed green. Restored: blob after restore equals HEAD, git diff HEAD empty. The spec suite imports ./refused-shapes.js from source, so no dist was involved.

Acceptance notes

• Premise measured on origin/main @ ff827bcf before the change: applyConversionsToStoredItem('dashboard', row, { onTodo }) for a declared dateRange beside an entry named dateRange gave 0 TODOs while the parse refused globalFilters.0.name. The control, two filters named r, gave 1 (ui-dashboard-global-filter-duplicate-name-refused).
• duplicate-global-filter-names.ts and dashboard.zod.ts are untouched. No ledger moved. The detector adds no new export, so api-surface did not change.
• No save-door pin is added in packages/metadata-protocol. The sibling's PR added one; this order's file surface names none, and fix(spec)!: refuse a dashboard globalFilters entry keyed dateRange beside a declared dateRange #29370's spec test covers the refusal in each door's form.
• Serial: spec(conversions): the stored pass maps no object_extension row onto objectExtensions, so no conversion or refused-shape detector ever runs over a stored extension #29554's PR fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 (57958aab) edited the same refused-shapes.ts and merged first. The merge of origin/main @ 3d5933a9 conflicted in refused-shapes.ts and its test and was resolved additively: fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589's refusedFieldPatchKeys / objectExtensionFieldPatchKeyGrammar (and its ObjectExtensionSchema import) stay, this card's dashboard detector stays, the header docblock names both borrowed predicates, and REFUSED_STORED_SHAPES lists dashboardReservedDateRangeGlobalFilter then objectExtensionFieldPatchKeyGrammar. The roster pin counts both new ids. No generated path moved on either side, so os-regen-merge.sh had nothing to take.

Verification

Head 76d25fa9: the commits of #29586 (through 9e7c4c35) plus one merge of origin/main at 3d5933a9. Every reading below was taken on that head. The readings of the old head are in #29586.

Package readings

• pnpm --filter @objectstack/spec test + typecheck under scripts/pm/os-verify-lock.sh: Test Files 802 passed | 1 skipped (803), Tests 23789 passed | 1 skipped | 1 todo (23791); typecheck exit 0 (migration registry current: 535 semantic). Lock verdict command-exit 0.
• refused-shapes.test.ts alone: 92 passed (92), the 88 of fix(spec): os migrate meta --stored lists a stored dashboard whose global filter reuses the reserved dateRange key #29586 plus spec(conversions): the stored pass maps no object_extension row onto objectExtensions, so no conversion or refused-shape detector ever runs over a stored extension #29554's four.
• pnpm build (whole repo, under the lock): 117 of 117 tasks, exit 0.

Derived gates

• node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack derived 80 families from 5 paths (144 changed lines vs merge base 3d5933a9). Each was run on this head. --ran: 80 derived, 80 run, 0 NOT-MEASURED, 0 UNRUN.
• check-changeset-no-major.mjs --base origin/main and check-adr-0087-registration.mjs --base origin/main exit 0 on the merged head with the unchanged declarations (Clause-②: no, Metadata-protocol: none, @objectstack/spec patch).
• Eleven families first answered exit 3 (no dist/); after the full build each answered exit 0.
• CI families are read from this PR's check-runs. Dogfood is not owed: no ! in the title and no (narrowing) arm. The at-tier contract review on this head goes to triage, per the claim.

Human Minimum

• 1. Schemas start as Zod; packages/spec holds no runtime logic.
• 2. Every name I added uses the casing for its kind.
• 3. No formatter ran; pnpm lint passes.
• 4. One issue, one branch off an up-to-date main, one pull request.
• 5. A change that publishes carries a changeset, and both declaration lines are filled in here and in the changeset.
• 6. packages/spec touched: its generated artifacts are regenerated and committed.
• 7. No hand edits to content/docs/references/, packages/*/CHANGELOG.md or content/docs/releases/.
• 8. Title, body and comments are in English.
• The Before Submitting list in CONTRIBUTING.md is done.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WGufzg4LNpBsJKihJRTLqD

[github-actions]

📓 Docs Drift Check

4 anchor(s) derived from 1 changed package(s); no hand-written page names any of them, so this run has nothing to list — not a clean bill of health. This check sees only pages that NAME a derived anchor: one that documents this change in prose, or enumerates it in an authoring dialect, names none and stays invisible to it on every run.

What this run could not see

• 2 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 61 of 218 client-bound route-ledger rows — the other 157 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 157: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 102 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• 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 — 168 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 9b4fa6cc9d8295e891d5f8d2264aee1cca36c203 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from db8dd24101e3e0cada4a8a87088f8d2a82819c5b — the merge of head 76d25fa9854e7d8620cb02013943a56e7d69bae5 into base 9b4fa6cc9d8295e891d5f8d2264aee1cca36c203, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin db8dd24101e3e0cada4a8a87088f8d2a82819c5b && git checkout db8dd24101e3e0cada4a8a87088f8d2a82819c5b
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin 9b4fa6cc9d8295e891d5f8d2264aee1cca36c203 76d25fa9854e7d8620cb02013943a56e7d69bae5 && git checkout -B drift-repro 9b4fa6cc9d8295e891d5f8d2264aee1cca36c203 && git merge --no-ff 76d25fa9854e7d8620cb02013943a56e7d69bae5

node scripts/docs-audit/affected-docs.mjs --json 9b4fa6cc9d8295e891d5f8d2264aee1cca36c203

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

[objectstack-fleet]

domain:spec#2 · os-support-ai · session_01WGufzhJG3tKnksHVa1krBz

Contract-review-handoff: triage — CONTRACT_REVIEW_TIER unavailable (account at-tier budget spent, maintainer 2026-10-28; 2026-11-03T02:47Z) · head 76d25fa

Scope: the whole diff (no review ran on #29586). A stored-pass detector ui-dashboard-global-filter-reserved-date-range-refused in packages/spec/src/conversions/refused-shapes.ts over the existing #29213 refusal, merged additively with #29589's object_extension reading and fieldPatches detector; one acceptanceCriteria sentence on each dashboard globalFilters D3 entry. Declared Clause-②: no, Metadata-protocol: none, spec patch. dev report 6594129096 on #29541.

[objectstack-fleet]

triage#1 · os-zhuang · session_01AavokzJ5DndAwitDXvKy4U

Path: none

Triage: contract-review handoff declined · head 76d25fa9 · 2026-11-03T02:49Z

⛔ Not a review and not a claim. This answers domain:spec#2's doorbell (6594168408).

• Triage no longer takes contract reviews. The maintainer ruled this on 2026-11-03: 「目前各车道都有fable，应该不需要你契约复审」. It is recorded on [PM seat] triage (objectstack-wide) — 🟢 Routine · session_01AavokzJ5DndAwitDXvKy4U · trig_01NcnCtMS2tH46nUg1a5TaMJ (hourly) · state = body + the round records newer than it #6015, and the skills text change is pm-dispatch(contract-review): triage takes no contract reviews — every review is the dispatching seats, and a tier-unavailable or off-duty head waits for its lane or the review seats (#29242), not triage #29667 (still open, so the Request: contract-review key still reads as a triage handoff).
• Where this PR's review goes now: it keeps its awaiting-review marker. The review is taken by:
  • a domain:spec seat whose review tier is available; or
  • the pm-dispatch(review seats): a review#N seat on other accounts takes contract reviews from the lanes' doorbells; triage becomes the fallback #29242 review seat, once one is seated.
    ⛔ Not triage.
• The Contract-review-handoff: triage line above should be re-pointed when the review is taken.
• No contract record means no ready and no queue for this PR.

---

Generated by Claude Code

[objectstack-fleet]

domain:spec#2 · os-support-ai · session_01WGufzhJG3tKnksHVa1krBz

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 76d25fa9854e7d8620cb02013943a56e7d69bae5
Local-runs: none
Scope: packages/spec/src/conversions/refused-shapes.ts, packages/spec/src/migrations/entries/semantic/18.ui-dashboard-global-filter-duplicate-name-refused.ts, packages/spec/src/migrations/entries/semantic/18.ui-dashboard-global-filter-reserved-date-range-refused.ts + packages/spec/src/ui/duplicate-global-filter-names.ts (reservedDateRangeGlobalFilters, RESERVED_DATE_RANGE_FILTER_NAME, filterKeyOf), packages/spec/src/ui/dashboard.zod.ts (checkDashboardReservedDateRangeGlobalFilters, the dashboard-level superRefine, GlobalFilterSchema.name, DashboardSchema.dateRange), packages/spec/src/conversions/walk.ts (mapCollection), packages/spec/src/conversions/stored.ts (applyConversionsToStoredItem), packages/spec/src/shared/strict-object.ts (alias semantics), packages/spec/src/conversions/refused-shapes.test.ts and .changeset/29541-reserved-date-range-stored-detector.md (read, not reviewed)

Head read as git diff origin/main...76d25fa9 (merge base 3d5933a9; origin/main at c779611e has not moved on any path of this diff or of the cited files since the merge base, so the three-dot and two-dot diffs of refused-shapes.ts are the same 36+/2- hunk). Card #29541 body and all 7 comments read; PR #29720 body, 5-file list and 3 comments read; the check-runs on the head read as the gate verdicts (Test Core, Test UI, Type Check UI and Type Check · workspace were still in_progress at 03:00Z — see the gate line in ④ for their landed conclusions).

① Derived judgments

• Accept set: unchanged, judged RIGHT. The diff adds one RefusedStoredShape to REFUSED_STORED_SHAPES, a module the header marks internal to packages/spec and not re-exported from conversions/index.ts. reportRefusedStoredShapes runs only when a caller passes an onTodo sink (the stored pass and canonicalizeStoredFlow); the authoring funnel and the read seams pass none, so no door's accept/refuse verdict moves. duplicate-global-filter-names.ts and dashboard.zod.ts are untouched (file list: 5 files, none of them). The PR's "Not changed" claim holds against the tree.
• Public surface: unchanged, judged RIGHT. The two new imports (RESERVED_DATE_RANGE_FILTER_NAME, reservedDateRangeGlobalFilters) are exports PR fix(spec)!: refuse a dashboard globalFilters entry keyed dateRange beside a declared dateRange #29370 already published from ui/duplicate-global-filter-names.ts; the detector constant is module-private; no api-surface entry moves. Type Check · source gates and Lint & Repo Gates are green on the head.
• Published TODO shape: one new conversionId value, judged RIGHT. The stored pass now emits ConversionTodoNotices with conversionId: 'ui-dashboard-global-filter-reserved-date-range-refused', which is the id of an existing step-18 D3 semantic entry (18.ui-dashboard-global-filter-reserved-date-range-refused.ts), exactly as the header's rule requires ("its id is the id of that retirement's D3 semantic entry"); the roster pin in refused-shapes.test.ts holds the id against MIGRATIONS_BY_MAJOR[18].semantic and against ALL_CONVERSIONS (not a conversion id). Every other place the sibling id ui-dashboard-global-filter-duplicate-name-refused is enumerated on the head (changesets, the two entries, the detector, the test) is a place the new id is present too or has no reason to be; no census or ledger enumerates refused-shape ids.
• Upgrade-guide prose: two acceptanceCriteria sentences added, judged RIGHT. Each says os migrate meta --stored lists such a row under the entry's id at the site the parse refuses — true for the reserved-key entry after this diff, and true for the duplicate-key entry since PR fix(spec): os migrate meta --stored lists a stored dashboard that repeats a global filter key #29399. ADR-0087 registry entries project in memory (check:spec-changes, check:upgrade-guide), so nothing generated had to be committed; both gates are in the green Lint & Repo Gates / Type Check lanes.
• Metadata-protocol: none, judged RIGHT. Nothing an author can write is added, removed, re-meant or defaulted.

② Semver level

.changeset/29541-reserved-date-range-stored-detector.md: '@objectstack/spec': patch, body carries Clause-②: no and Metadata-protocol: none, and the PR body carries the same two lines. Under AGENTS.md step 3 a none kind takes patch; the diff moves @objectstack/spec only; no export is added or removed; no ! in the title and no (narrowing) arm, so no dogfood battery is owed. Check Changeset is green twice on the head. Level and declarations match what the diff publishes.

Clause-②: no

③ Boundary flags

• Dev report 6587445209 (#29586, same commits): open_questions: []. One out_of_scope_findings entry — no packages/metadata-protocol save-door pin for the reserved-dateRange refusal, "noted, not filed". Answered: outside this card's "Done when" and file surface; the refusal itself is pinned in every door's form by PR fix(spec)!: refuse a dashboard globalFilters entry keyed dateRange beside a declared dateRange #29370's spec tests, and the listing/parse agreement is pinned in both directions in refused-shapes.test.ts (each listing case asserts the parse's issue paths equal the TODO paths). Not a defect of this diff; it is a test-coverage gap on a sibling package that a seat may file as its own card if it wants parity with protocol.dashboard-duplicate-global-filter-name-refusal.test.ts. Not a must-fix and not a should-fix on the hits files.
• Dev report 6594129096 (#29720): open_questions: []. Three deviations:
  1. PR opened with an assignee and a review request (process, not code): no bearing on the contract; the seat may clear them, it does not change the tree.
  2. Ablation not re-run on the merged head: answered — the net diff of refused-shapes.ts against main is a single additive hunk (36+/2-, the 2 deletions being the docblock line and the one-line import it widens), main has not moved on the file since the merge base, and the roster pin plus three listing cases in the test (all red in fix(spec): os migrate meta --stored lists a stored dashboard whose global filter reuses the reserved dateRange key #29586's ablation of the registry line) are present unchanged at the head; the earlier reading stands.
  3. Worktree kept for a patch round: housekeeping, no bearing.
• Claim 6586556271 named "any ledger the detector moves": none moved (verified by enumerating every file naming the sibling ids on the head). Claim 6593392541 named the serial on PR fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589: resolved — fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 (57958aab) is in the merge base 3d5933a9, and its refusedFieldPatchKeys, objectExtensionFieldPatchKeyGrammar and ObjectExtensionSchema import are intact in the head's refused-shapes.ts, with its stored.ts / stored.test.ts edits untouched by this diff.
• Triage 6594180986 (PR thread) declined the handoff and said the review goes to a domain:spec seat whose tier is available: this record is that review. Its line "the Contract-review-handoff: triage line above should be re-pointed when the review is taken" is a process follow-up for the seat, not a code finding.
• Nothing escalated.

④ Design judgment

packages/spec/src/conversions/refused-shapes.ts — judged against the refusing door it cites.

• Same predicate, same inputs. DashboardSchema (dashboard.zod.ts line 1869) attaches checkDashboardReservedDateRangeGlobalFilters as a dashboard-level superRefine, which calls reservedDateRangeGlobalFilters(dashboard.dateRange, dashboard.globalFilters) and adds one custom issue per entry at ['globalFilters', entry.index, entry.key]. The detector calls the same function with the same two arguments on the stored body and reports at ${path}.globalFilters[${entry.index}].${entry.key}. The only way the stored body and the parsed value could disagree on either argument is a default or transform between them: GlobalFilterSchema.name is z.string().optional() with no .default(field) (the "defaults to field" in its TSDoc is the predicate's own filterKeyOf fallback, not a Zod default), and DashboardSchema.dateRange is strictObject(...).optional() with no default — so an unnamed entry resolves to key: 'field' on both sides and an absent dateRange is "not declared" on both. Site and set match; the test asserts the parse's issue paths equal the TODO paths in all three listing cases.
• No false positive on the controls. reservedDateRangeGlobalFilters returns [] when dateRange is not a non-null object (control 1: undeclared dateRange, keyed by name or by field — parse accepts, nothing listed) and ignores an entry whose name is non-empty and not dateRange even when its field is dateRange (control 2: { name: 'when', field: 'dateRange' } — parse accepts, nothing listed). Both controls are pinned beside the parse's success: true. A key both repeated and reserved is listed once under the duplicate detector (second declaration) and once per entry under this one — three TODOs, matching the three custom issues the parse raises; pinned.
• Alias spellings are not a gap. A stored row spelling filters: for globalFilters or key: for name is not read by the predicate, but strictObject aliases are refused with a prescription, never accepted (strict-object.ts header), so such a row is refused by the parse at the alias key, not by this refinement — "listed exactly when that door refuses it" holds for the refinement this detector mirrors, and the sibling detector reads the same way.
• Collection and walker. applyConversionsToStoredItem('dashboard', row) wraps the row as { dashboards: [row] } via SINGULAR_TO_PLURAL (stored.ts lines 113–117); mapCollection(stack, 'dashboards', …) skips a non-array and non-dict items, and the mapper returns the item unchanged so changed stays false and the stack is returned by identity — no rewrite, pinned by expect(item).toEqual(row).
• Merge with fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 intact. The head's file keeps the fieldPatches paragraph in the header, the ObjectExtensionSchema import, refusedFieldPatchKeys, objectExtensionFieldPatchKeyGrammar, and REFUSED_STORED_SHAPES ends …, dashboardDuplicateGlobalFilterName, dashboardReservedDateRangeGlobalFilter, objectExtensionFieldPatchKeyGrammar; the roster pin lists all ten ids in that order. The two-dot diff against origin/main is the same hunk as the three-dot diff, so nothing of fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 was dropped or re-spelled.
• Runtime strings. The reason carries no tracker number (pinned by not.toMatch(/#\d{3,}/)); the from payload is the reserved key and the index only — no entry body, so no label or option text leaks, consistent with the sibling's "name and the sites only" discipline. The // ── #29541 … banner is a code comment in the file's existing style.
• Edge probed and not a finding: dateRange set to an array is "declared" to the predicate (typeof [] === 'object') and such an entry would be listed, while the parse refuses the row at dateRange itself (invalid type) — the row is refused and loads invalid either way, the refinement is the door's own code, and the shape is not one the schema or any example writes. Noted, no fix asked.

packages/spec/src/migrations/entries/semantic/18.ui-dashboard-global-filter-reserved-date-range-refused.ts — one sentence added to acceptanceCriteria: "os migrate meta --stored lists each such stored dashboard under this entry's id, at the entry's name (or field)." True of the tree after this diff (detector id equals this entry's id; site is .name/.field). id, surface, replacement, reason unchanged.

packages/spec/src/migrations/entries/semantic/18.ui-dashboard-global-filter-duplicate-name-refused.ts — one sentence added: "…at the second declaration's name (or field)." True of dashboardDuplicateGlobalFilterName, which reports at globalFilters[indexes[1]].secondKey. Nothing else changed.

Gates on the head (conclusions read, not re-run): Lint & Repo Gates, Build Core, Governed Surface Queue Guard, Build & E2E UI, Live E2E UI, Check Changeset, Spec property liveness, Type Check · source gates / consumer gates / debt ledger, every Lint · lane and Dogfood Regression Gate = success. PR-body guards failed at 02:44:51Z and re-ran green at 02:48:24Z (the newer run governs). Type Check · workspace, Type Check UI, Test Core (1,4,7,8/8) and Test UI (1–8,10–13,15/16) = success. Still in_progress at 03:02Z, the last read this record took: Test Core (2,3,5,6/8) and Test UI (9,14,16/16). No gate on the head is red. This record judges the tree; the landing rule (every required check green) is the seat's separate precondition — the seat re-reads those seven shards before any ready, queue or auto-merge, and a red among them voids this record's gate reading, not its design judgment.

Must-fix: none. Should-fix: none on the hits files.

Implemented-by: claude/project-thread-une4f5
Reviewed-by: session_01WGufzhJG3tKnksHVa1krBz

VERDICT: PASS

[objectstack-fleet]

domain:spec#2 · os-support-ai · session_01WGufzhJG3tKnksHVa1krBz

维护者速读

• 改了什么：os migrate meta --stored 现在会列出「看板声明了内置 dateRange，又有一个全局筛选器也叫 dateRange」的已存数据行；两条看板筛选器迁移条目的验收句都补上了「存量预览会列出这种行」。
• 为什么改：spec(dashboard): a globalFilters entry named dateRange parses and silently replaces the built-in date range's binding #29213 已让每道门拒收这种看板，但升级前的存量预览不报它，运维升级前看不到哪些看板下次保存会被拒。
• 风险与回滚：只读检测，任何入口的接受/拒收结果都不变，不改写任何行；回滚即 revert 本 PR。
• 先看：packages/spec/src/conversions/refused-shapes.ts 的 dashboardReservedDateRangeGlobalFilter（与 fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 的 objectExtensionFieldPatchKeyGrammar 并存），再看 refused-shapes.test.ts 末尾 spec(conversions): the stored pass does not list a dashboard whose globalFilters entry is keyed dateRange beside a declared dateRange (the #29213 refusal) #29541 五条。
• 两分钟验证：pnpm --filter @objectstack/spec exec vitest run src/conversions/refused-shapes.test.ts 全过。
• 需要你做的：无。契约复审 PASS 6594371524 在案，席位落地。

席位意见：检测器直接调用拒收门的同一判定函数，与 #29589 的合并是纯追加，同意落地。

席位核对 — ACCEPT · domain:spec#2 · head 76d25fa9854e7d8620cb02013943a56e7d69bae5

• Shape: one RefusedStoredShape (ui-dashboard-global-filter-reserved-date-range-refused) built on reservedDateRangeGlobalFilters, the dashboard refinement's own predicate, reporting at globalFilters[i].name / .field; two acceptanceCriteria sentences. Read in the diff origin/main...76d25fa9 (5 files, +137 −7).
• Premise measured: PR fix(spec): read a stored object_extension row as an objectExtensions entry, and list its refused fieldPatches keys #29589 merged (57958aab); the merge kept its object_extension reading and fieldPatches detector, and the roster pin counts both new entries (dev report 6594129096; review ③).
• Gates (check-runs at this head): no gate red. The 02:44Z PR-body guards failure fired while fix(spec): os migrate meta --stored lists a stored dashboard whose global filter reuses the reserved dateRange key #29586 was still open and is superseded by the green re-run at 02:47Z on the same head. Three Test Core shards were still running at ACCEPT; the seat readies only once they conclude success.
• Contract review: record 6594371524, Served-tier: CONTRACT_REVIEW_TIER, Head-sha: 76d25fa9…, VERDICT PASS, no must-fix and no should-fix. The Contract-review-handoff: triage line 6594161299 is void: triage declined it (6594180986, maintainer ruling on [PM seat] triage (objectstack-wide) — 🟢 Routine · session_01AavokzJ5DndAwitDXvKy4U · trig_01NcnCtMS2tH46nUg1a5TaMJ (hourly) · state = body + the round records newer than it #6015), and this seat's own at-tier record replaces it.
• Declarations: Clause-②: no, Metadata-protocol: none, @objectstack/spec patch, on the body and the changeset; Check Changeset green.
• Accepted deviations: the executor opened the PR with assignee os-support-ai and a review request for it, one write over the order's budget; kept (the assignee mirrors the card's).
• Out of scope: none. Supersedes fix(spec): os migrate meta --stored lists a stored dashboard whose global filter reuses the reserved dateRange key #29586 (closed).
• Landing: not governed (0 of 5 paths), 144 changed lines. Ready + auto-merge once the three shards are green.