Repository navigation
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 #10974
Description
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:
.changeset/10859-pivot-object-block-zod-arms.md: 「drillDownis the sharedDrillDownConfigSchema」..changeset/7352-drill-down-config-mirror.md, in its 2026-09-28 dated note: 「itsdrillDownis this entry'sDrillDownConfigSchema, so the opening paragraph's two referencing declarations are three for the release」..changeset/10685-drilldown-per-block.md, in its dated note: 「a validator does read the members of apivotnode'sdrillDown, and acceptsmodethere」.
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 record5866443287), if the maintainer routes it here rather than into PR feat(core)!: retire the bare-stringglobalFilters[].optionslift (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. 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-…mdand a paragraph in8913-…mdinvalidated by objectui#9021; both ship into the types CHANGELOG at the next publish #9042, docs(changeset): six PENDING changesets cite atracked as #Ncard 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 atdata-display.ts:1383and 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 inchangeset-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:devxcards 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
Activity
objectstack-fleet commentedon Sep 28, 2026
Serial condition met: PR #10972 merged as
cc4e47638, so the three sentences this card names are now false onmainfor the next release. The dated notes must land before release PR #5400 is merged. From thedomain:spec @ objectuiseat, sessionsession_012UwY3ahMixEFkfTUxMVkYm. The write question (a session's append to a pending changeset) is still with the maintainer.objectstack-fleet commentedon Sep 28, 2026
Path: release text — what a CHANGELOG states | 缺项 (three pending changesets on
pivotdrillDown) | P2Triage: first grade —
bug·documentation·priority:p2·domain:spec·area:devpath·pm:queue(findingremoved)Triage: lands in three pending
.changeset/*.mdfiles ⇒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/typesCHANGELOG. 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.
Clause-②: no.5866443287). Triage has raised it with the maintainer in the seat's chat, together with this card's release deadline.objectstack-fleet commentedon Sep 29, 2026
Ruling recorded: appending to a pending changeset is authorised. From the
domain:spec @ objectuiseat, sessionsession_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:
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:
.changeset/*.md, in the objectui#10877 / PR objectui#10891 form.globalFilters[].optionslift (objectui#4356) #10930 itself;objectstack-fleet commentedon Sep 29, 2026
Claim: PM loop round 9
Session:
session_012UwY3ahMixEFkfTUxMVkYmAccount:
huangyiirene(the seat's linked user asGET /useranswers it; the card's assignee)Branch:
claude/issue-10974-pivot-drilldown-dated-notesWorktree:
objectui-issue-10974Domain:
domain:specSeat:
domain:spec#1File surface: dated supersession notes APPENDED to three pending changesets:
.changeset/10859-pivot-object-block-zod-arms.md,.changeset/7352-drill-down-config-mirror.mdand.changeset/10685-drilldown-per-block.md. Frontmatter stays byte-identical, and no existing line is edited or deleted. Plus one empty-frontmatter changeset ifcheck-changeset-presencerequires 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
5883360525on #4356 and on this card). PR #10972 has merged. No open PR edits the three files (files API, all 5 open PRs,main2eaf5be27). Release PR #5400 only regenerates frommain. The objectui#4356 W4 note lands in PR #10930 on7759-…, which is disjoint.objectstack-fleet commentedon Sep 29, 2026
os-dev-report
{
"issue": 10974,
"status": "done",
"branch": "claude/issue-10974-pivot-drilldown-dated-notes",
"pr": "#11045",
"session": "session_012UwY3ahMixEFkfTUxMVkYm (subagent, parent seat session)",
"premise_still_valid": true,
"summary": "Appended one dated 2026-09-29 supersession note at the end of each of .changeset/10859-pivot-object-block-zod-arms.md, .changeset/7352-drill-down-config-mirror.md and .changeset/10685-drilldown-per-block.md (commit 4f412d5, one commit on base 2eaf5be), in the objectui#10877 / PR #10891 form, each naming objectui#10932 and PR objectui#10972 and citing the false sentence by quotation. All three before-sentences were re-quoted verbatim from main 2eaf5be first; the notes state what main holds now: PivotTableSchema.drillDown?: never on the TS face, the zod pivot arm drillDown = retirementTombstone (z.never().optional(), invalid_type at drillDown whatever it holds, message names object-pivot), DrillDownConfigSchema referenced only by ChartSchema and ObjectDataTableSchema (.extend), object-pivot the node that drills (ObjectPivotTable passes onDrillDown) and still without a zod arm. Completeness sweep over the 2325 pending changesets found no fourth same-class sentence, so no extra note; 7759-dashboard-header-global-filters-spec.md untouched. check-changeset-presence says no changeset is owed, so none was added. Draft PR #11045 opened via the relay, assignee huangyiirene set and read back; CI at report time (one read of the head check-runs, 40 total): 24 success, 3 skipped, 13 in_progress, 0 failure, so CI is in_progress. Discrepancy, reported not acted on: the dispatch and the claim Thread-read cite the ruling as comment 5883360525 on this card, but 5883360525 lives on objectui#4356; the same ruling on #10974 is comment 5883365010 (the PR body cites both correctly). Worktree and its node_modules removed after push; the remote branch head equals 4f412d5.",
"tests": "Per-file (vs base 2eaf5be): frontmatter md5 base = head for 10859 (ecedb10c5189b2c8841ea736b67c3cc6), 7352 (ecedb10c5189b2c8841ea736b67c3cc6), 10685 (ac1bfd0472c0d0b981d923c32d435f18); the whole base file is a byte prefix of head in all three (md5 of head first-N-lines = base whole-file md5); git diff --numstat 2eaf5be: 10685 13/0, 10859 2/0, 7352 16/0 (0 deletions); angle brackets in each note: 0; control-byte self-scan grep -naP exit 1 (no hits); model identifiers in the diff: 0. Gates at head 4f412d5, exit codes captured before any pipe: check-changeset-presence 0 (no changeset is owed), check-changeset-no-major 0, check-changeset-fixed 0, check-changeset-claims 0 (Corpus: 3 changeset(s) this change adds or modifies), check-changeset-overwrite 0 report-only (lists the 3 files as M with identical declarations at base and now), pnpm check:pending-changeset-literals 0, pnpm check:control-bytes 0 (9330 tracked text files), pnpm check:new-line-citations 0 (VERDICT: 0 new citation(s)), check-governed-queue-guard --test on the 3 paths 0 (NOT GOVERNED). Script tests under os-verify-lock: pnpm exec vitest run --maxWorkers=2 over scripts/tests/check-changeset-{claims,fixed,no-major,overwrite,presence}.test.ts + check-pending-changeset-literals.test.ts gives Test Files 6 passed (6), Tests 220 passed (220), VERDICT command-exit 0. Current-truth probe on main 2eaf5be under the lock: packages/types/src/tests/pivot-drilldown-retired-10932.test.ts gives 8 passed (8), VERDICT command-exit 0. Extra, not dispatch-named (neither reads .changeset/): check-shell-escape-residue 0, check-doc-links 0. PR body read back after create: 9512 bytes sent = 9512 stored, byte-identical, session-URL footer intact. No ablation: prose-only diff, nothing to mutate.",
"mcp_calls": "0",
"api_writes": "3 relay strokes, each one POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]: (1) pr_create = POST /repos/objectstack-ai/objectui/pulls (draft, PR #11045, run 36520652590); (2) label-write --assign = POST /repos//issues/11045/assignees (run 36520722061, read back MATCHES); (3) os-dev-report comment = POST /repos//issues/10974/comments. Plus 2 git pushes (not REST): the empty-branch probe and the commit push. Zero label writes: objectui path labels belong to labeler.yml and the dispatch named none.",
"open_questions": [],
"out_of_scope_findings": []
}
Generated by Claude Code
objectstack-fleet commentedon Sep 29, 2026
PR #11045 waits for its contract review. From the
domain:spec @ objectuiseat, sessionsession_012UwY3ahMixEFkfTUxMVkYm, 2026-09-29.The review tier's quota is nearly spent. The maintainer chose 「Hold until fable returns (Recommended)」 for the release-note PRs, then said, verbatim, 「11045 也切换到等契约复审」. So:
needs:contract-review, stays in draft and is not queued.objectstack-fleet commentedon Sep 29, 2026
Contract review done on the maintainer's ask 「契约复审」 · director seat (objectstack#12708,
session_01AsCNgFBs8HCjwhyHQsFbx3) 2026-09-29T06:41ZPR objectui#11045 carries this seat's record
5885040828at head4f412d5a85: PASS (inside the ruling's form — frontmatter identical on all three entries, 31 insertions and 0 deletions, each old file a byte prefix of the new; thepivottombstone on both faces and the two remainingDrillDownConfigSchemareferences re-read onmain; no changeset owed).needs:contract-reviewremoved. CI is green on the head and a driver-free merge-tree againstmainis clean, so the landing is this seat's, and it must come before release PR objectui#5400 merges.objectstack-fleet commentedon Sep 29, 2026
ACCEPT: PR #11045 at
4f412d5a8. From thedomain:spec @ objectuiseat, sessionsession_012UwY3ahMixEFkfTUxMVkYm.The review checklist was run against GitHub.
main, first lineFixes #10974,Clause-②: noas the claim has it, assigneehuangyiirene. 3 files, +31/−0,.changeset/prose only.5885040828(director seat,session_01AsCNgFBs8HCjwhyHQsFbx3) is PASS on this head.5883365010): the frontmatter is identical at base and head, and each old file is a byte prefix of the new one.main(pivot.drillDownis a tombstone on both faces;DrillDownConfigSchemahas two referencing arms), and each note says so.Landing: marked ready and auto-merge enabled through the relay in this round, ahead of release PR #5400.
objectstack-fleet commentedon Sep 29, 2026
Landed. PR #11045 merged through the merge queue as
338482fe7. From thedomain:spec @ objectuiseat, sessionsession_012UwY3ahMixEFkfTUxMVkYm.Verified by content on
main: each of the three pending entries carries its dated 2026-09-29 note..changeset/10859-pivot-object-block-zod-arms.md(+2).changeset/7352-drill-down-config-mirror.md(+16).changeset/10685-drilldown-per-block.md(+13)The squash is +31/−0,
.changeset/prose only, and landed before release PR #5400. The commit's co-author trailer is the model-freeCo-authored-by: Claudeline only. A grep of the message for a model identifier finds 0.This card closed
completedthroughFixes, andpm:dispatchedis removed.docs(changeset): date-note three pending entries on the pivot node's …