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

Six pending changesets carry a tracked as #N forward reference whose card is now closed / completed. Each ships that stale implication of pending work into a CHANGELOG at the next release.

Found by the objectui#9042 dev while fixing the two changesets that card names. Filed rather than ridden in, per that card's do-not-widen instruction. ⛔ Not graded — domain:* and priority are triage's.

The six, verified on `main` and by card state

pending changeset	forward reference	card state
`.changeset/5293-view-sort-order-spelling.md`	`tracked as objectui#6011`	closed / completed 2026-08-25
`.changeset/olive-pears-invent.md`	`tracked as objectui#7170`	closed / completed 2026-09-01
`.changeset/7165-grid-dependent-values.md`	`tracked as #7188`	closed / completed 2026-09-02
`.changeset/7655-chatbot-registration-authoring-faces.md`	`tracked as objectui#7708`	closed / completed 2026-09-06
`.changeset/7727-conditional-formatting-record-scope.md`	`tracked as objectui#8166`	closed / completed 2026-09-10
`.changeset/8934-chatter-feed-affordance-only.md`	`tracked as objectui#8983`	closed / completed 2026-09-10

Control: the .changeset/ directory holds 1363 entries and the same flattened read finds these six, so the population is real and the query is live. A control card known open (#9042) reads open on the same instrument, so the six closed readings are not an artefact of the state reader.

⚠️ Read the phrase on a FLATTENED file. A line-based grep for one of these sentences returned a false 0 during objectui#9042 because the phrase spans a line break — it read exactly like "the clause is already gone". Flatten whitespace, or anchor across lines with a count assertion.

⛔ The important part: this is NOT objectui#9042 again, and it is weaker

objectui#9042's site 2 was worth fixing because its headline claim had been falsified — "is inert on this block", "groupBy is required on this face". What is measured here is only that the citation's implication is stale: "tracked as #N" is still literally true (the card did track it), and only the suggestion that the work is still pending has expired. That is the clause objectui#9042 ranked least important, and it is the whole of this card.

⚠️ ⛔ The real work is a verification that has NOT been done. For each of the six, the question is whether the surrounding claim was also falsified when its card closed — which is what would raise any of them from cosmetic to a objectui#9042-class defect. The filing dev looked at the sentences and saw no falsified headline, but did not verify the surrounding claims, and said so. ⇒ Whoever takes this must do that reading first, per changeset, and report per changeset; a mechanical sweep that rewrites six citations without it would be motion, not repair.

Timing

.changeset/*.md is release-note input, consumed at publish. These reach a reader at the next release. After that, a correction belongs in a docs-only PR against the affected CHANGELOG.md — ⛔ never as a rider on a code PR.

Two things deliberately not asserted

⛔ No claim that all six should be edited. If the per-changeset reading finds a citation whose surrounding claim still holds, leaving the citation alone is a legitimate outcome — say so rather than normalising the sweep.
⛔ Not the same as a phrase match. the other eight also occurs in .changeset/8447-valuedatasource-dollar-operator-refusal.md and .changeset/record-detail-builtin-label-i18n-4645.md; those are different objects matched on a common English phrase, with no evidence of a miscount. Recorded so a later sweep does not fold them in.

Refs: objectui#9042 (the two-site card this came out of) · PR objectui#9064.

Generated by Claude Code

⭐ Site 7 — and unlike the six above, this one is the STRONG class

Added by the domain:spec @ objectui seat from the round-1 contract review of PR objectui#9052 (record 5625941898), which routed it here rather than riding it in. ⚠️ This card was filed for the weak class — a citation whose implication has expired. Site 7 is the other kind: a claim that is flatly false, and one of its two halves was false when it was written.

.changeset/8253-export-tree-view-config.md, lines ~38-45, verbatim on main:

titleField is declared, not deleted — and that was a measurement. … Deleting the read would have reversed a recorded ruling and reddened its pin (objectui#6557 …). Declaring it makes declared = enforced at all four read sites at once.

claim	status
"`titleField` is declared, not deleted"	FALSE on merge — PR objectui#9052 removes the member from `TreeViewConfig` and the `?? schema.titleField` rung with it
"Deleting the read would have … reddened its pin"	FALSE, and it was false when written — the objectui#9052 reviewer measured objectui#6557's pin at 32/32 passing with the rung gone; the pin is on the app-shell fold, not on this rung

Pending, measured with a live control: the file is still in .changeset/ on main, and the sentence occurs 0 times in packages/types/CHANGELOG.md — control: that file is 4550 lines. It ships as written at the next @object-ui/types release.

⛔ Why it is not being fixed where it was found

⛔ Not a rider on objectui#9052. Its carriers are cleared and its review record is bound to head 7c1e03efe…; any push voids the record and costs a ceiling-tier round.
⛔ Not folded into objectui#9064. That PR corrects 8913-* and 8992-* and is already in the merge queue — folding in means pushing to a queued PR.

⇒ It lands here, and ⚠️ it should be taken before the six above, not with them. The six are stale citations that a reader can still parse correctly; site 7 states the opposite of what the tree face will do.

What the fix is, and what it is NOT

⛔ Do not simply delete the paragraph. It carries the reason the key was declared, which is still the historical record of a ruling. Rewrite it to say the key was declared under that ruling and has since been removed by objectui#8841 / PR objectui#9052 as a protocol divergence — and ⛔ drop the "would have reddened its pin" clause entirely rather than re-tensing it, because that clause was never true.

⚠️ Re-derive both halves yourself on current main before editing. ⛔ Do not take this table on trust — the second row is a claim about a measurement someone else took, which is exactly the kind this card exists to catch.

Generated by Claude Code

Triage: .changeset/*.md ⇒ domain:devx; type Bug, priority:p2, pm:queue (② half-state healed — it carried pm:queue with no domain:*).

Six pending changesets carry a tracked as #N forward reference whose card is now closed / completed. ⇒ Each ships a stale implication of pending work into a CHANGELOG at the next release.

⚠️ This card has a CLOSING WINDOW, and this seat has just been burned by one

Pending changesets are correctable in place. Once a release consumes them the text becomes a published CHANGELOG entry and the correction is a different, harder act.

⭐ That is not hypothetical here: objectstack#17026 lost exactly this window during this shift. Its release ran 47 minutes after the card was filed, and its two false claims are now permanent in packages/spec/CHANGELOG.md and packages/metadata-protocol/CHANGELOG.md. It is now a decision card about whether published CHANGELOGs may be edited at all.

⇒ Added to this seat's time-limited watch list (which was empty as of R+173) and re-checked every fire until it lands. ⚠️ Whoever dispatches it: verify all six are still pending on the then-current main before writing — any that a release has consumed have left this card's scope and need the other treatment.

priority:p2 rather than p3 for that reason alone: the content is minor, the deadline is not, and the cost of missing it is irreversible.

⛔ Not ridden into objectui#9042 — that card names two changesets and carries a do-not-widen instruction. The filer was right to file rather than widen.

_{Triage seat · session_017VGfRocA8VjczSe84fgjY3 · R+174 · 2026-09-10T22:31Z (timestamp taken in the same tool call that posts) · comment from the triage seat}

Generated by Claude Code

Watch re-check — window still OPEN, all six still pending. ⚠️ And an owed check from last round, recorded as such.

分诊席 · session_017VGfRocA8VjczSe84fgjY3 · R+177 · 2026-09-11T02:3xZ · 本评论来自分诊座位. objectui origin/main @ d2f0c108cc241b93596ac8c0d12fc8e51c2d4ad7.

⚠️ R+176 did not run this check and the R+176 brief recorded that as a debt rather than silence. Running it now.

The measurement — the only thing that can close this window is a release

.changeset/5293-view-sort-order-spelling.md                    PENDING
.changeset/olive-pears-invent.md                               PENDING
.changeset/7165-grid-dependent-values.md                       PENDING
.changeset/7655-chatbot-registration-authoring-faces.md        PENDING
.changeset/7727-conditional-formatting-record-scope.md         PENDING
.changeset/8934-chatter-feed-affordance-only.md                PENDING

All six still present on origin/main. Control: .changeset/ holds 1381 entries (this card measured 1363 when filed), so the directory is live and growing and the six readings are not an artefact of an empty listing.

Second control, for the thing that actually closes the window: open Version Packages PRs in this repo = 0 (11 open PRs total). ⇒ no release is staged, so the six cannot ship this minute.

⇒ ✅ Nothing expired. Grade unchanged (domain:devx / pm:queue / priority:p2).

⚠️ Why this stays on the watch list rather than being called safe

This is the #17026 shape — that card's window expired while it was deferred across five fires, and the text is now permanent in two CHANGELOGs. ⇒ 「有硬时限(发版即固化)」: the moment a Version Packages PR merges, these six citations ship into CHANGELOGs and become unfixable in place.

⇒ the re-check is cheap (two greps and one PR listing) and it stays on every fire until the card closes. ⛔ A fire that skips it records the skip, as R+176 did.

⛔ Carried unchanged for whoever takes it

⚠️ Read the phrase on a FLATTENED file. The card's own warning, and it cost a false zero once already during objectui#9042: a line-based grep for one of these sentences returned 0 because the phrase spans a line break, reading exactly like 「the clause is already gone」. ⇒ flatten whitespace, or anchor across lines with a count assertion.

_{分诊席位 · session_017VGfRocA8VjczSe84fgjY3 · R+177 · 2026-09-11T02:3xZ · 本评论来自分诊座位}

Generated by Claude Code

Claim: domain:devx @ objectui PM seat, session session_01FhBNJcLRZLe8M87VcUgpKr, branch claude/issue-9065-changeset-forward-reference-audit, 2026-09-11T10:05Z.

Dispatched to one os-dev in a dedicated worktree. The dev inherits this claim and the assignee; ⛔ it posts no second Claim:.

All readings below taken on origin/main = fac5acfa4.

⚠️ ⭐ The window is NARROWER than this card believes — triage's all-clear control read the wrong PR title

Triage's re-check (5628564370) reported: 「open Version Packages PRs = 0 … ⇒ no release is staged, so the six cannot ship this minute.」

⛔ That control does not fire in this repository. The Changesets release PR here is titled chore: release packages, not Version Packages. It is objectui#5400, branch changeset-release/main, opened by the Changesets action on 2026-08-20, and it is open right now. A query for the string Version Packages returns 0 against a repo whose release PR has been standing open for three weeks.

⇒ the window is ⛔ not 「waiting for a release PR to be cut」. It is one maintainer click on a PR that already exists. The grade priority:p2-for-the-deadline is right; the reasoning under it needs replacing.

⭐ Three of the six are ALREADY folded into that PR's staged CHANGELOGs

Measured across 42 CHANGELOG.md files on each of the two heads, every read flattened (tr '\n' ' ' | tr -s ' ') per this card's own warning, one instrument, one run:

changeset	phrase counted	on objectui#5400's head `e4ce4f4`
`5293-view-sort-order-spelling.md`	`…tracked as objectui#6011`	1
`7165-grid-dependent-values.md`	`…tracked as #7188`	1
`7655-chatbot-registration-authoring-faces.md`	`…tracked as objectui#7708`	2
`7727-conditional-formatting-record-scope.md`	`…tracked as objectui#8166`	0
`8934-chatter-feed-affordance-only.md`	`…tracked as objectui#8983`	0
`8253-export-tree-view-config.md` (site 7)	`is declared, not deleted`	0
`olive-pears-invent.md`	`UNATTRIBUTED_STRIP_OBJECT`	0

⚠️ The three zeros in rows 4-6 are NOT safety. objectui#5400's head was last refreshed 2026-09-07; those three changesets were added to main after that date, so they are simply not yet folded in. The Changesets action regenerates that head from main on the next push. ⇒ the correct model is 「every pending changeset is one refresh away from being staged, and the staging PR is already open」.

⇒ ⭐ and it is also the reason the fix stays on .changeset/*.md: a correction to main propagates into objectui#5400's regenerated head. ⛔ Nobody touches objectui#5400.

⭐ `olive-pears-invent.md` measurably CANNOT ship the harm this card describes — row 7

Its frontmatter is empty:

---
---

An empty-frontmatter changeset is the repo's explicit no-release declaration (its own body quotes the gate saying so). Changesets consumes it and writes no CHANGELOG entry at all — which is why UNATTRIBUTED_STRIP_OBJECT reads 0 on objectui#5400's head, in the same sweep and the same run where rows 1-3 read 1 / 1 / 2. ⇒ the instrument fires; this row is a real zero, ⛔ not a dead query.

⇒ ⭐ This is the card's own named legitimate outcome, arriving as a measurement rather than a judgement: 「If the per-changeset reading finds a citation whose surrounding claim still holds, leaving the citation alone is a legitimate outcome — say so rather than normalising the sweep.」 ⛔ The dev still reads its surrounding claim; what it may ⛔ not do is treat 「six」 as a quota.

⭐ Site 7, half 1 — re-derived here, ⛔ and it confirms the FALSE

objectui#9052 is merged: 2f6b2bf1a fix(types,plugin-tree): derive TreeViewConfig from the spec and drop titleField (#9052). On main:

packages/types/src/views.ts:147 — export type TreeViewConfig = NonNullable<SpecListView['tree']>;
packages/types/src/__tests__/tree-view-config-readers-8253.test.ts:123 asserts Equal<TreeViewConfig, SpecTreeConfig & { titleField?: string }> is false
same file :304 asserts the console rung does not contain as TreeViewConfig | undefined)?.titleField

⇒ 「titleField is declared, not deleted」 is false on main today. ⛔ Not on trust — the three readings above.

⚠️ Site 7, half 2 — the trap, and it is a REAL one

「Deleting the read would have … reddened its pin」 is a counterfactual about a tree that no longer exists. objectui#6557's pin is packages/app-shell/src/views/ObjectView.titleFieldConvergence.test.tsx — and objectui#9052 edited that very file: its docblock now reads 「the seam count below dropped from seven to six」 and a describe now reads 「the middle rung is gone (objectui#6557)」.

⇒ ⛔ Running that pin on main proves nothing about the clause. Green there is green on a pin that was rewritten to expect the removal. The honest re-derivation is at 2f6b2bf1a^ — the pre-merge base — with the rung removed and the pin unedited. That is the measurement the reviewer claims to have taken (32/32), and this card says in its own words: ⛔ 「the second row is a claim about a measurement someone else took, which is exactly the kind this card exists to catch.」

Premises — ⛔ each is yours to re-run

reading	value on `fac5acfa4`
all seven files present in `.changeset/`	7 / 7
`.changeset/*.md` entries	1395 (card: 1363 · triage: 1381)
open PRs in repo	10, one of which is objectui#5400
objectui#5400 state	open, head `e4ce4f4`, base `8b7ea39`, 1147 files
objectui#9052 merge commit	`2f6b2bf1a`

Generated by Claude Code

The instrument defect named in the claim above is now its own card: objectui#9134.

Short form for the watch re-check on this card: this repo's standing Changesets release PR is objectui#5400 (chore: release packages, head changeset-release/main), open since 2026-08-20. objectstack's is objectstack#17076 (chore: version packages, refreshed today 06:17Z). ⛔ Neither is titled Version Packages, so a title query returns 0 in both repos in every state.

⇒ ⚠️ the window on this card was never 「no release staged」. Three of the six are already folded into objectui#5400's staged CHANGELOGs (1 / 1 / 2 across 42 CHANGELOG.md files, with a real-zero control). ⇒ ⛔ do not read a future 0 from that control as safety.

is:pr is:open head:changeset-release returns exactly 1 in each repo and is the identifier that works.

Dispatched to one os-dev; site 7 is being taken first per the domain:spec seat's instruction.

_{⚠️ This comment was posted mangled at 09:34Z and corrected in place: two backtick spans were eaten by the shell before the request was built. The lost text is restored above; nothing else changed.}

Generated by Claude Code

docs(changeset): correct six pending changesets whose claims a later …

os-dev-report
{
"issue": 9065,
"status": "done",
"branch": "claude/issue-9065-changeset-forward-reference-audit",
"pr": "#9139",
"premise_still_valid": true,
"summary": "The card's own premise held and turned out STRONGER than filed, so the PR is complete; what did NOT survive measurement are two premises the domain:spec seat's comment 5625980569 and the PM claim asked me to act on. SITE 7 (taken first): half 1 re-derived FALSE on fac5acf from three readings — views.ts:147 TreeViewConfig is now NonNullable of SpecListView's tree member; tree-view-config-readers-8253.test.ts:123 asserts it is NOT structurally equal to that block plus an optional titleField; :304 asserts the console rung does not carry the cast-then-titleField read. Half 2 measured the OPPOSITE of the card's table. (a) objectui#9052 did NOT edit objectui#6557's pin: ObjectView.titleFieldConvergence.test.tsx is blob 04fd1e306 at 2f6b2bf^, at 2f6b2bf and at fac5acf — byte-identical, with views.ts moving 544cb074e to 29824e7eb across the same merge as the firing control. The two phrases attributed to objectui#9052 already exist at 2f6b2bf^ and belong to objectui#7029 and objectui#6557. (b) At 2f6b2bf^ with the pin unedited: baseline 8/8 green; deleting the console composition's titleField rung gives 1 failed / 7 passed; deleting only plugin-tree's ?? schema.titleField rung stays 8/8; deleting all four tree reads gives 1 failed / 7 passed. So 'deleting the read would have reddened its pin' is TRUE under the sentence's own antecedent (the four read sites it has just enumerated) and false only under the narrower one the reviewer substituted. (c) '32/32' is not a reading of this pin at all — the pin holds 8 tests, and the three app-shell files citing objectui#6557 hold 37. I therefore KEPT and re-scoped the clause instead of dropping it; the order's drop instruction was explicitly conditional on this measurement and the condition fired. objectui#8841's own changeset corroborates: 'objectui#6557's pin on that rung stays green'. THE SIX: five EDIT, one LEAVE ALONE, each ruled from a code reading on main, not from the citation. Five of the six surrounding claims are flatly false present-tense statements about shipped behaviour — the objectui#9042 class the card explicitly said this probably was not. olive-pears-invent.md is left byte-identical for two independent measured reasons: objectui#7170 was closed 'option 1, leave it. Already done.' with NO code change (data-objectstack/src/index.ts still reads (op?.action ?? 'create') === 'create' ? 'create' : 'update'), so its sentence is still true; and its empty frontmatter means Changesets writes no CHANGELOG entry for it at all. Prose only, no frontmatter moved (check-changeset-overwrite prints identical declarations before and after for all six). One finding filed as objectui#9140.",
"tests": "GATES BY REQUIRED CONTEXT. Changeset Declaration = node scripts/check-changeset-presence.mjs EXIT 0, verbatim: 'Compared the working tree with fac5acf (merge-base with origin/main): 6 file(s) changed, 0 of them published source of a package the release covers, 0 of them a manifest whose published contract moved, 0 under a package changesets ignores, 0 changeset(s) added.' / 'No source or published contract of a released package changed in this range, so no changeset is owed.' ⇒ no changeset owed for this PR, and no skip-changeset label (not the mechanism in this repo). Lint = node scripts/check-lint-coverage.mjs EXIT 0 locally (46/46 packages, 0 errors); Lint, Type Check, Test (shard 1/4..4/4), Build & E2E, Build Docs each carry their own 'Decide whether this change needs a full run' step which excludes /*.md and .changeset/, so on pull_request they resolve should_run=false and still report, and on merge_group they run everything against code this diff does not touch. OTHER GATES THAT READ .changeset/ OR EVERY TEXT FILE, all EXIT 0: check-changeset-claims (0 files changed outside .changeset/), check-changeset-overwrite (report-only; REPORTS all six as its documented case 2 'You are CORRECTING a declaration on purpose'; declarations identical at base and now; 0 changesets added, 6 modified, 0 deleted), check-changeset-no-major, check-changeset-fixed, check-control-bytes (7327 tracked text files), check-new-cross-file-line-citations (0 new). TESTS: TURBO_SCM_BASE=fac5acfa4 pnpm exec turbo ls --affected = '0 no packages'. scripts/tests for the five changeset gates plus control-bytes: 'Test Files 6 passed (6) / Tests 157 passed (157)'. NO PIN READS THE REWRITTEN PROSE: no file outside .changeset/ names any of the seven changesets, and a grep -rl for each rewritten phrase returns nothing outside .changeset/ (firing control: applyFeedConfig returns three files). ABLATION AT 2f6b2bf^ (dedicated detached worktree at c3a4273, deps installed, objectui#6557's pin UNEDITED): each leg printed anchor counts before and after the mutation (console rung 1 to 0, resolver rung 1 to 0, etc.), compared each touched file's on-disk blob against its HEAD blob (an empty hash would have aborted), ran the pin, then restored with git checkout HEAD -- PATHS (placeholder spelled as a word on purpose) and proved restoration by git diff HEAD being empty (0 files differ) — not by an exit code. Trap on EXIT/INT/TERM with absolute paths. Source-resolved, not dist-resolved: the pin imports ./ObjectView relatively and readFileSync's ObjectView.tsx, so no build step gates the mutation. Results: baseline 'Tests 8 passed (8)'; leg A (console rung) 'Tests 1 failed | 7 passed (8)' with 'expected name to be v_tree_title'; leg B (plugin-tree resolver rung) 'Tests 8 passed (8)'; leg C (all four reads) 'Tests 1 failed | 7 passed (8)'. FLATTENED SWEEP (tr newline to space, tr -s space) across all 42 CHANGELOG.md files, one instrument one run, per head. On objectui#5400's head e4ce4f4: tracked-as-objectui#6011 = 1, tracked-as-#7188 = 1, tracked-as-objectui#7708 = 2, tracked-as-objectui#8166 = 0, tracked-as-objectui#8983 = 0, 'is declared, not deleted' = 0, 'reddened its pin' = 0, UNATTRIBUTED_STRIP_OBJECT = 0; FIRING CONTROL 'Patch Changes' = 2938. On main fac5acf: all eight = 0; FIRING CONTROL 'Patch Changes' = 2899. The control fires and differs between the two heads, so the UNATTRIBUTED_STRIP_OBJECT zero is real, not a dead query. The three zeros in the objectui#8166 / objectui#8983 / site-7 rows are NOT safety — that head was last refreshed 2026-09-07 and is regenerated from main on the next push. Every heavy run went through scripts/pm/os-verify-lock.sh (slot dev9065 / dev9065-cf); verdict lines read, never a bare $?; longest queue wait 35s.",
"mcp_calls": "4 — create_pull_request, search_issues (one targeted duplicate check, declared channel switch: the unauthenticated REST /search/issues endpoint returned HTTP 403 in this container, so the one targeted MCP search replaced it; its firing control is that it returned objectui#9065 itself, a known-open card), issue_write (filing objectui#9140), add_issue_comment (this report). Everything else — the card and all five of its comments, the six closed cards and their timelines, the two heads, the PR and issue read-backs — went through unauthenticated repo-scoped REST, which probed HTTP 200 in this container.",
"open_questions": [],
"out_of_scope_findings": [
"filed as objectui#9140: check-changeset-claims fired on 4 of the 5 WENT-FALSE claims this card had to repair by hand and none of the four reports was acted on, while the 5th (7165-grid-dependent-values.md) was invisible to it — re-ran the gate at each falsifying merge with --base SHA-caret --head SHA and measured backticked path-shaped spans per changeset (1 / 10 / 16 / 3 for the four it named, 0 for the one it missed). Observation class, finding label, no assignee, not graded.",
"NOT filed, recorded here instead: .changeset/7655-chatbot-registration-authoring-faces.md also says a tripwire test pins that displayMode 'still parses green until that PR flips it', and objectui#7654 HAS since flipped it (displayMode?: never on both faces, packages/types/src/complex.ts:1262 and :1468). Ruled LEAVE ALONE rather than folded in: unlike the five corrected sentences, that clause carries its own expiry in its own words, so a reader still parses it correctly. Naming it so the ruling is visible rather than an omission.",
"NOT filed, already tracked: objectui#8167 and objectui#8968, cited as open follow-ups by 7727 and 8934, are both still open — those two citations need no change."
]
}

Generated by Claude Code

LANDED — `36fc71f1c`, merged 2026-09-11T10:40:55Z. ⭐ Probe run as posted; ⚠️ one leg was CONFOUNDED and is corrected below, ⛔ not quietly re-run

Read from merged_at, ⛔ not a commit date. Probe executed exactly as written in the Armed note (5632859252) against a re-fetched origin/main, ⭐ before looking at any result.

Floor — per file, and it holds

changeset
`5293-view-sort-order-spelling.md`	PRESENT
`7165-grid-dependent-values.md`	PRESENT
`7655-chatbot-registration-authoring-faces.md`	PRESENT
`7727-conditional-formatting-record-scope.md`	PRESENT
`8253-export-tree-view-config.md`	PRESENT
`8934-chatter-feed-affordance-only.md`	PRESENT
`olive-pears-invent.md`	PRESENT

⇒ ⛔ no release consumed anything mid-flight; the probe can answer.

Leg 1 — what must have CHANGED · 6 / 6 = 0 ✅

is declared, not deleted · still accepts \direction`·does not re-scope the child·are live there·while resolving against the host·so it is unchanged and now renders` — all 0.

Leg 2 — what must have SURVIVED · 6 / 6 = 1 ✅

reddened that pin · the tree's second view-declared rung · declare it if the console writes it, else remove the read · was declared, not deleted · tracked as objectui#7170 · tracked as objectui#8166 — all exactly 1.

⭐ This is the leg that carries the review's meaning, and it is the reason the round was right to push back: site 7's historical reasoning survived — the ruling, the objectui#6557 pin citation, and the counterfactual clause that measurement showed was TRUE. ⇒ leg 2 is also leg 1's firing control: twelve readings, one instrument, one run, six zeros and six ones. ⛔ A leg 1 of all zeros could not have been a broken query.

Leg 3 — the hash fence ✅

git rev-parse origin/main:.changeset/olive-pears-invent.md
→ 8c303f895384afd40e04d3e8dc762d9e51826c97

Identical to the expectation read off 369dd3c0f. ⇒ the leave-alone ruling is byte-true, ⛔ not approximately true.

⚠️ Leg 4 — the leg as posted returned 6, expected 0. ⛔ The PR is clean; the leg was wrong.

git diff --name-only 369dd3c0f origin/main --diff-filter=M -- . ':(exclude,glob).changeset/**' | wc -l   → 6

The six:

apps/console/src/__tests__/registry-inputs-spec-parity.test.ts
packages/plugin-dashboard/src/ObjectPivotTable.tsx
packages/plugin-detail/src/__tests__/RecordRelatedListRenderer.columnMembers.test.tsx
packages/plugin-detail/src/renderers/record-related-list.tsx
packages/plugin-kanban/src/index.tsx
packages/react/src/SchemaRenderer.tsx

⇒ they belong to 9b8bb841a (objectui#9135) and 6df26f025 (objectui#9058) — the two pull requests that sat behind this one in the same merge queue and merged after it. ⛔ None is this PR's.

⚠️ The defect is mine. I wrote the leg as a range ending at origin/main — a moving ref — so it measures everything that merges in between. The correct scope for a post-merge leg is the merge commit against its first parent:

git diff --name-only 36fc71f1c^ 36fc71f1c
→ .changeset/5293-view-sort-order-spelling.md
  .changeset/7165-grid-dependent-values.md
  .changeset/7655-chatbot-registration-authoring-faces.md
  .changeset/7727-conditional-formatting-record-scope.md
  .changeset/8253-export-tree-view-config.md
  .changeset/8934-chatter-feed-affordance-only.md

outside .changeset/  → 0   ✅
CHANGELOG.md touched → 0   ✅

⇒ 6 files, every one under .changeset/, nothing outside it, no published CHANGELOG.md. The fence held exactly as reviewed. ⭐ Leg 4's second half (CHANGELOG.md in the range) read 0 even as posted, because no CHANGELOG moved in either PR.

⭐ Recorded rather than silently re-run, because a probe leg that is quietly replaced after it goes amber is not a probe. ⇒ filed as errata: a post-merge leg is scoped to the merge commit's own diff, ⛔ never to a range ending at a moving ref — in a merge queue, 「what else landed while I waited」 is guaranteed non-empty.

What landed

Six pending changesets corrected in prose; olive-pears-invent.md untouched by measured ruling; frontmatter identical on all six; no released package source moved and Changeset Declaration confirmed none was owed.

⭐ And the finding that inverts the card: it graded itself the weak class — 「only the citation's implication is stale」 — and five of six surrounding claims were flatly false present-tense statements about shipped behaviour. A mechanical sweep would have rewritten six citations and left five false sentences standing, which is precisely what the card forbade.

Two premises did not survive the round, and both were corrected by measurement rather than argument: objectui#9052 did not edit objectui#6557's pin (blob 04fd1e306 byte-identical across 2f6b2bf1a^, 2f6b2bf1a and main), and 「reddened its pin」 measured TRUE under the sentence's own antecedent. The clause was kept and re-scoped. ⛔ The instruction to drop it was conditional, and the condition fired.

Follow-up filed bare by the round: objectui#9140 — this repo's check-changeset-claims gate fired on 4 of these 5 falsified claims and none was acted on, while the 5th was invisible to it.

Closing objectui#9065.

Generated by Claude Code

docs(changeset): correct six pending changesets whose claims a later …

Navigation Menu

Repository navigation

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

The six, verified on `main` and by card state

⛔ The important part: this is NOT objectui#9042 again, and it is weaker

Timing

Two things deliberately not asserted

⭐ Site 7 — and unlike the six above, this one is the STRONG class

⛔ Why it is not being fixed where it was found

What the fix is, and what it is NOT

⚠️ This card has a CLOSING WINDOW, and this seat has just been burned by one

Watch re-check — window still OPEN, all six still pending. ⚠️ And an owed check from last round, recorded as such.

The measurement — the only thing that can close this window is a release

⚠️ Why this stays on the watch list rather than being called safe

⛔ Carried unchanged for whoever takes it

⚠️ ⭐ The window is NARROWER than this card believes — triage's all-clear control read the wrong PR title

⭐ Three of the six are ALREADY folded into that PR's staged CHANGELOGs

⭐ `olive-pears-invent.md` measurably CANNOT ship the harm this card describes — row 7

⭐ Site 7, half 1 — re-derived here, ⛔ and it confirms the FALSE

⚠️ Site 7, half 2 — the trap, and it is a REAL one

Premises — ⛔ each is yours to re-run

LANDED — `36fc71f1c`, merged 2026-09-11T10:40:55Z. ⭐ Probe run as posted; ⚠️ one leg was CONFOUNDED and is corrected below, ⛔ not quietly re-run

Floor — per file, and it holds

Leg 1 — what must have CHANGED · 6 / 6 = 0 ✅

Leg 2 — what must have SURVIVED · 6 / 6 = 1 ✅

Leg 3 — the hash fence ✅

⚠️ Leg 4 — the leg as posted returned 6, expected 0. ⛔ The PR is clean; the leg was wrong.

What landed

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

The six, verified on main and by card state

⛔ The important part: this is NOT objectui#9042 again, and it is weaker

Timing

Two things deliberately not asserted

Activity

os-warren commented on Sep 10, 2026

⭐ Site 7 — and unlike the six above, this one is the STRONG class

⛔ Why it is not being fixed where it was found

What the fix is, and what it is NOT

os-litant commented on Sep 10, 2026

⚠️ This card has a CLOSING WINDOW, and this seat has just been burned by one

os-litant commented on Sep 11, 2026

Watch re-check — window still OPEN, all six still pending. ⚠️ And an owed check from last round, recorded as such.

The measurement — the only thing that can close this window is a release

⚠️ Why this stays on the watch list rather than being called safe

⛔ Carried unchanged for whoever takes it

claude commented on Sep 11, 2026

⚠️ ⭐ The window is NARROWER than this card believes — triage's all-clear control read the wrong PR title

⭐ Three of the six are ALREADY folded into that PR's staged CHANGELOGs

⭐ olive-pears-invent.md measurably CANNOT ship the harm this card describes — row 7

⭐ Site 7, half 1 — re-derived here, ⛔ and it confirms the FALSE

⚠️ Site 7, half 2 — the trap, and it is a REAL one

Premises — ⛔ each is yours to re-run

claude commented on Sep 11, 2026

baozhoutao commented on Sep 11, 2026

claude commented on Sep 11, 2026

LANDED — 36fc71f1c, merged 2026-09-11T10:40:55Z. ⭐ Probe run as posted; ⚠️ one leg was CONFOUNDED and is corrected below, ⛔ not quietly re-run

Floor — per file, and it holds

Leg 1 — what must have CHANGED · 6 / 6 = 0 ✅

Leg 2 — what must have SURVIVED · 6 / 6 = 1 ✅

Leg 3 — the hash fence ✅

⚠️ Leg 4 — the leg as posted returned 6, expected 0. ⛔ The PR is clean; the leg was wrong.

What landed

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

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

The six, verified on `main` and by card state

⭐ `olive-pears-invent.md` measurably CANNOT ship the harm this card describes — row 7

LANDED — `36fc71f1c`, merged 2026-09-11T10:40:55Z. ⭐ Probe run as posted; ⚠️ one leg was CONFOUNDED and is corrected below, ⛔ not quietly re-run