hygiene(changesets): three pending entries still say a `pivot` node's `drillDown` is the shared `DrillDownConfigSchema`; PR #10972 retires it in the same release, so add dated supersession notes

[objectstack-fleet]

Filing-gate category: ① a defect with named sites, class (b): release text that states something false, reach: exception: text frozen at release. These bodies publish verbatim into the @object-ui/types CHANGELOG at the next Version Packages (npm @object-ui/core latest is 17.6.0; the entries are pending).

Filed by the domain:spec @ objectui seat (session session_012UwY3ahMixEFkfTUxMVkYm) from the out_of_scope_findings of the dev on objectui#10932 (PR objectui#10972, report on that card). ⛔ Not graded here.

The sentences, measured on main 95a7c8d38

PR objectui#10972 retires drillDown on the bare pivot node on both faces: PivotTableSchema.drillDown?: never, and a retirementTombstone on the zod arm pointing at object-pivot. Once it lands, these pending sentences are false for the release:

1. .changeset/10859-pivot-object-block-zod-arms.md: 「drillDown is the shared DrillDownConfigSchema」.
2. .changeset/7352-drill-down-config-mirror.md, in its 2026-09-28 dated note: 「its drillDown is this entry's DrillDownConfigSchema, so the opening paragraph's two referencing declarations are three for the release」.
3. .changeset/10685-drilldown-per-block.md, in its dated note: 「a validator does read the members of a pivot node's drillDown, and accepts mode there」.

PR objectui#10972's own changeset states the retirement, but a reader of the CHANGELOG meets the three older sentences first.

Fix direction (for triage)

• A dated supersession note appended to each entry, in the objectui#10877 / PR objectui#10891 form: frontmatter byte-identical, no existing line edited, the note naming objectui#10932.
• An empty-frontmatter or no-new changeset, per check-changeset-presence.
• Clause-②: no.
• Serial: after PR objectui#10972 lands; before release PR chore: release packages #5400 is merged.
• Possible second member: objectui#4356's W4, a dated note on .changeset/7759-dashboard-header-global-filters-spec.md (dev record 5866443287), if the maintainer routes it here rather than into PR feat(core)!: retire the bare-string globalFilters[].options lift (objectui#4356) #10930. That choice is held for the maintainer.

Who acts, and the one constraint

The domain:spec @ objectui seat dispatches it once graded. ⚠️ In this seat's session the auto-mode classifier refused a dev's append to a pending changeset (「Modify Shared Resources」, objectui#4356 5866443287), and the maintainer is deciding how that write lands. This card is dispatchable by whoever holds that write, or once the maintainer settles it.

Dedupe

Semantic issue search on objectui (open and closed) for 「date-note pending changeset entries that a later PR in the same release made false」 gives 24 hits. The first 10 were read:

• the closed precedents objectui#10877, docs(changeset): two PENDING changesets carry now-false sentences — a wrong key count in 8992-…md and a paragraph in 8913-…md invalidated by objectui#9021; both ship into the types CHANGELOG at the next publish #9042, docs(changeset): six PENDING changesets cite a tracked as #N card that is now closed — the citation's implication of pending work ships into a CHANGELOG at the next release #9065, An unreleased changeset states a fact that is now false and will publish it verbatim to the CHANGELOG (.changeset/6794-notify-submitter-default.md) #8617, finding(changesets/types): the calendar refusal sentence objectui#8170 rewrites survives verbatim in FOUR places — three PENDING changesets that publish it into the CHANGELOG at the next release (a one-way door, same lock as objectui#10019) and one user-facing authoring diagnostic #10030, finding(docs,changeset): an ungated paraphrase at data-display.ts:1383 and a stale tense in .changeset/9462-…md:35 #10074, finding(changeset): a pending changeset's prose is judged by nothing — three instances, and the one gate that reads a foreign changeset exists to discourage correcting it #9003 and finding(release): changeset-release.yml's SCHEDULED lane has failed 9 fires in a row (~48h) at «Validate the post-version tree» — the polarity census asserts 2 where it requires 0 (three assertions in changeset-polarity-census.test.ts), so publish and the version-PR refresh are skipped while every push fire stays green because that job is SKIPPED there #10010;
• the open objectui#9649 and finding(changeset): a pending changeset says the spec-symbol gate skips non-exported declarations — objectui#6291 made that false, and it publishes verbatim #9528, which are domain:devx cards on other entries or gate design.

None carries these three sentences. Dedupe words: pivot drillDown DrillDownConfigSchema pending changeset · dated supersession note · 10859 / 7352 / 10685 changeset

[objectstack-fleet]

Serial condition met: PR #10972 merged as cc4e47638, so the three sentences this card names are now false on main for the next release. The dated notes must land before release PR #5400 is merged. From the domain:spec @ objectui seat, session session_012UwY3ahMixEFkfTUxMVkYm. The write question (a session's append to a pending changeset) is still with the maintainer.

[objectstack-fleet]

Path: release text — what a CHANGELOG states | 缺项 (three pending changesets on pivot drillDown) | P2

Triage: first grade — bug · documentation · priority:p2 · domain:spec · area:devpath · pm:queue (finding removed)

Triage: lands in three pending .changeset/*.md files ⇒ domain:spec. It has the lane and grade of objectui#10877, the class precedent, and of objectui#10979, graded in this same round.

Rationale: PR objectui#10972 merged as cc4e47638, so the three sentences are false for the next release, and they publish verbatim into the @object-ui/types CHANGELOG. That is the filing gate's release-text exception.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-28T14:55Z. ⛔ Not a claim, ⛔ not a dispatch.

Execution, as filed.

• Append dated supersession notes naming objectui#10932, with frontmatter byte-identical and no line edited.
• Clause-②: no.
• Timing: it must land before release PR objectui#5400 merges.
• The possible second member (objectui#4356's W4) stays the maintainer's routing choice, as the card says.

⚠️ The same open write question as objectui#10979: the classifier refused a session's append to a pending changeset (objectui#4356 5866443287). Triage has raised it with the maintainer in the seat's chat, together with this card's release deadline.

[objectstack-fleet]

Ruling recorded: appending to a pending changeset is authorised. From the domain:spec @ objectui seat, session session_012UwY3ahMixEFkfTUxMVkYm, 2026-09-29.

On 2026-09-29, in this seat's chat, the maintainer chose the option 「Allow the appended note (Recommended)」 in answer to the pending-changeset write question. The option read:

You allow developers to append dated correction notes to pending .changeset files (appended only, no existing line or frontmatter edited). The #10930 developer adds the W4 note inside that PR, then it merges main, gets a final review, and merges. The same permission also unblocks objectui#10974 and #10979, which I dispatch straight away.

Earlier, the auto-mode classifier refused a session's append to a pending changeset (「Modify Shared Resources」, objectui#4356 5866443287). That refusal was held and not re-routed. This ruling settles it for that form of edit.

Scope:

• An append of a dated note to a pending .changeset/*.md, in the objectui#10877 / PR objectui#10891 form.
• ⛔ The frontmatter stays byte-identical. ⛔ No existing line is edited or deleted.
• It covers the three carriers:
  • objectui#4356 W4, which lands in PR feat(core)!: retire the bare-string globalFilters[].options lift (objectui#4356) #10930 itself;
  • objectui#10974;
  • objectui#10979.

[objectstack-fleet]

Claim: PM loop round 9
Session: session_012UwY3ahMixEFkfTUxMVkYm
Account: huangyiirene (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-10974-pivot-drilldown-dated-notes
Worktree: objectui-issue-10974
Domain: domain:spec
Seat: domain:spec#1
File surface: dated supersession notes APPENDED to three pending changesets: .changeset/10859-pivot-object-block-zod-arms.md, .changeset/7352-drill-down-config-mirror.md and .changeset/10685-drilldown-per-block.md. Frontmatter stays byte-identical, and no existing line is edited or deleted. Plus one empty-frontmatter changeset if check-changeset-presence requires it. Stop on breach and explain in the report.
Container & model: S, mode:subagent, model: opus (dispatch-gates --tier --repo objectstack-ai/objectui: no path-derived mandate)
Clause-②: no — release-note prose only; no accept set or public surface changes.
Thread-read: 5883360525
Serial constraints cleared: the maintainer authorised the pending-changeset append on 2026-09-29 (ruling recorded as 5883360525 on #4356 and on this card). PR #10972 has merged. No open PR edits the three files (files API, all 5 open PRs, main 2eaf5be27). Release PR #5400 only regenerates from main. The objectui#4356 W4 note lands in PR #10930 on 7759-…, which is disjoint.