Skip to content
This repository was archived by the owner on Nov 4, 2026. It is now read-only.

Commit 452f1f7

Browse files
baozhoutaoclaude
andauthored
docs(scripts): record the maintainer ruling the i18n-locales ceiling raise could not (objectui#8816) (#8956)
* docs(scripts): record the maintainer ruling the `i18n-locales` ceiling raise could not (objectui#8816) `fffa30d3f` raised `PER_CHUNK_GZIP_CEILINGS['i18n-locales']` to 465,000 over a 456,196 baseline and rested that raise, in the header, on the maintainer's INSTRUCTION of 2026-09-10 that red pull requests are RESOLVED rather than parked. That was a priority instruction, and at the time it was the only thing that existed: whether it also authorised route A rather than only the urgency was named as an open fork on objectui#8816 while the fork was still open. The ruling exists now — director seat summon #21, decision batch #110 item 3, recorded on objectui#8816 at comment 5615808548 on 2026-09-10, on the maintainer's reply to the recommendation of route A at comment 5615318265 — and the header rests on it instead, quoting both the reply and the ruling's own refusal to be read as a precedent: the next change that meets this line returns to the decision box. The sequence is recorded plainly, because it is the half a later reader cannot recover from the constant. The pair landed at 06:05:37Z as a RIDER inside PR objectui#8901 (`fix(data-objectstack): a refused view read is not an object with no saved views`), about two hours and forty minutes AHEAD of the ruling, and not in the dedicated pull request the ruling's execution clause asks for. No constant moves, in either direction. Reverting a maintainer-ruled value in order to re-land it in the ruled shape would land `main` red on `Bundle Analysis` for form; the number is right and it is ruled, and what was wrong is the record. Everything the block already got right is kept: the four-build derivation, the 8,804-byte = 0.10x headroom arithmetic, and that the size comes from this key's own convention rather than from the overage. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FhBNJcLRZLe8M87VcUgpKr * docs(scripts): the `i18n-locales` baseline's forward reading is spent, both sites (objectui#8816) The `PER_CHUNK_BASELINE` entry for `i18n-locales` was recorded as a FORWARD reading: 456,196 named "the state `main` reaches once objectui#8901 and objectui#8888 have BOTH landed", and the inline comment above the constant pointed at that note for "why this one names a state `main` has not reached yet ... while only one claimant has landed". `main` has reached it. `fffa30d3f` landed at 2026-09-10T06:05:37Z and `8ea3beee4` at 2026-09-10T06:05:40Z, three seconds apart, and both are ancestors of the tip. The two sentences were therefore false as written, in the present tense, six lines from the constant they describe — the same defect as the provenance repaired in the commit before this one, falsified by the same event, and repaired the same way. Both sites move together, deliberately. Repairing one and leaving the other is the split record this card exists to stop. Neither rewrite restates a headroom. The old sentence's arithmetic is kept as history, in the past tense, with the gate's own printed figure named as the one in force — a comment cannot keep a number that moves on most builds, which is the rule the prose pin in `scripts/__tests__/check-eager-closure-budget.test.ts` enforces one column over. No constant moves. All eight budgeted values still read byte-identically to `origin/main`, and the diff touches no line that names one. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FhBNJcLRZLe8M87VcUgpKr --------- Co-authored-by: Claude <noreply@anthropic.com>
1 parent dbc7e5b commit 452f1f7

2 files changed

Lines changed: 93 additions & 18 deletions

File tree

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
---
3+
4+
Record the maintainer ruling behind the `i18n-locales` per-chunk ceiling in
5+
`scripts/check-eager-closure-budget.mjs` (objectui#8816). Prose only; no package
6+
is released by this change and no constant moves.
7+
8+
The raise that landed as `fffa30d3f` rested its header provenance on the
9+
maintainer's _instruction_ of 2026-09-10 that red pull requests are resolved
10+
rather than parked — a priority instruction, and all that existed when the
11+
sentence was written. The route ruling exists now: director seat summon #21,
12+
decision batch #110 item 3, recorded on objectui#8816 at comment 5615808548 on
13+
2026-09-10, on the maintainer's reply to the recommendation of route A at
14+
comment 5615318265. The header now rests on that, quotes the ruling's own
15+
refusal to be read as a precedent — the next change that meets this line returns
16+
to the decision box — and records the sequence plainly: the pair landed as a
17+
rider inside PR objectui#8901 about two hours and forty minutes ahead of the
18+
ruling, and not in the dedicated pull request the ruling asks for.
19+
20+
The number is right and it is ruled, so nothing moves it back: a revert to
21+
re-land it in the ruled shape would land `main` red on this line for form. What
22+
was wrong is the record, and a record is repaired by writing it.
23+
24+
Two further sentences in the same header are repaired in the same commit, for
25+
the same reason and by the same event. The `PER_CHUNK_BASELINE` entry for
26+
`i18n-locales` described itself as a FORWARD reading naming "a state `main` has
27+
not reached yet ... while only one claimant has landed". `main` reached it:
28+
`fffa30d3f` at 2026-09-10T06:05:37Z and `8ea3beee4` at 2026-09-10T06:05:40Z are
29+
three seconds apart and both ancestors of the tip, so the sentence was false as
30+
written. Both sites — the prose entry and the inline comment above the constant
31+
— now say what the reading now is, and neither restates a headroom the gate is
32+
the only thing that can keep current.

‎scripts/check-eager-closure-budget.mjs‎

Lines changed: 61 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -653,10 +653,40 @@ export const REGRESSION_THIS_GATE_MUST_CATCH_BYTES = 89 * 1024;
653653
* paragraph under "Raising one" forbids. It is not "the gate fired, so the
654654
* number moved". objectui#8816 is a decision card opened 2026-09-09 that asks
655655
* exactly this question and carries three routes, and it stood unclaimed while
656-
* two finished pull requests queued behind it. The authorisation to take one of
657-
* those routes rather than wait is the maintainer's instruction of 2026-09-10
658-
* that red pull requests are RESOLVED rather than parked; WHICH route is the
659-
* measurement below, and it was taken on measurement, not on the instruction.
656+
* two finished pull requests queued behind it. WHICH route is the measurement
657+
* below, and it was taken on measurement. THAT one of the three could be taken
658+
* at all is a MAINTAINER RULING — director seat summon #21, decision batch #110
659+
* item 3, recorded on objectui#8816 at comment 5615808548 on 2026-09-10, on the
660+
* maintainer's reply to the recommendation of route A at comment 5615318265.
661+
* That reply, verbatim:
662+
*
663+
* 其他同意
664+
*
665+
* ⛔ The same ruling refuses to be read as a precedent, and the clause is
666+
* quoted rather than paraphrased because it governs the NEXT reader of this
667+
* constant rather than this one:
668+
*
669+
* 这是一次维护者裁决下的 ratchet 移动,⛔ 不是先例:下一次撞墙仍回决策箱。
670+
*
671+
* ⇒ the next change that meets this line goes back to the decision box, and
672+
* ⛔ this raise is not authorisation for the one after it.
673+
*
674+
* ⚠️ THE CONSTANT AND ITS RULING ARRIVED IN THAT ORDER — the wrong one — and
675+
* the sequence is recorded here rather than smoothed over, because a reader who
676+
* finds the ruling above and the number below will otherwise reconstruct a
677+
* history that did not happen. The pair landed in `fffa30d3f` at 06:05:37Z on
678+
* 2026-09-10 as a RIDER inside objectui#8901 (`fix(data-objectstack): a refused
679+
* view read is not an object with no saved views`), about two hours and forty
680+
* minutes BEFORE the ruling was recorded, and ⛔ not in the dedicated pull
681+
* request the ruling's execution clause asks for. What stood in for the ruling
682+
* at that moment was the maintainer's instruction of 2026-09-10 that red pull
683+
* requests are RESOLVED rather than parked — a PRIORITY instruction, read on
684+
* the day as authorising the route as well as the urgency. Whether it did was
685+
* named as an open fork while the fork was still open, and the maintainer then
686+
* settled it as A. ⇒ the number is the ruled number, so ⛔ moving a ruled
687+
* constant back in order to re-land it in the ruled shape is refused: that
688+
* lands `main` red on this line for form. What was wrong is the record, and a
689+
* record is repaired by writing it — objectui#8816, these paragraphs.
660690
*
661691
* ⛔ WHAT THE BYTES BUY — one console build per row, each from the repo ROOT,
662692
* `i18n-locales` read out of the `apps/console/dist/eager-closure.json` the
@@ -782,8 +812,14 @@ export const PER_CHUNK_GZIP_CEILINGS = Object.freeze({
782812
// Headroom 18,971 bytes = 0.21x REGRESSION_THIS_GATE_MUST_CATCH_BYTES, the
783813
// proportion the retiring pair carried (18,539 = 0.20x).
784814
'vendor-objectstack': 1_254_000,
785-
// Raised by objectui#8816, on the maintainer's instruction of 2026-09-10 that
786-
// red pull requests are resolved rather than parked, and sized by the four
815+
// Raised by objectui#8816 on a MAINTAINER RULING — director seat summon #21,
816+
// decision batch #110 item 3, comment 5615808548 of 2026-09-10, on the
817+
// maintainer's own reply to the recommendation of route A at 5615318265 —
818+
// and ⛔ not a precedent, in that ruling's own words: the next change that
819+
// meets this line returns to the decision box. ⚠️ It landed BEFORE that
820+
// ruling, as a rider inside objectui#8901 (`fffa30d3f`) rather than in the
821+
// dedicated pull request the ruling asks for; "Why `i18n-locales` moved UP"
822+
// above records that sequence and quotes the ruling. Sized by the four
787823
// console builds in "Why `i18n-locales` moved UP" above — ⛔ not by the
788824
// overage, which is the one size that card's own evidence rules out. Headroom
789825
// 8,804 bytes = 0.10x REGRESSION_THIS_GATE_MUST_CATCH_BYTES over the baseline
@@ -829,15 +865,21 @@ export const PER_CHUNK_GZIP_CEILINGS = Object.freeze({
829865
* instrument and container as the three trees it is compared against, which
830866
* is what makes those deltas subtractable.
831867
*
832-
* ⚠️ It is a FORWARD reading and the only entry here that is. It names the
833-
* state `main` reaches once objectui#8901 and objectui#8888 have BOTH
834-
* landed, so while only one of them has, the live payload sits below this
835-
* constant (455,271 and 455,519, both measured) and
836-
* `pnpm check:eager-closure` prints MORE headroom than arithmetic on these
837-
* two constants gives. Read on purpose: a shared budget with two admitted
838-
* claimants has no single-commit baseline that is not stale the moment the
839-
* second one lands, and erring toward the larger payload is the direction
840-
* that cannot hide growth.
868+
* ⚠️ It WAS a FORWARD reading — the only entry here that ever has been —
869+
* and it is not one any more. It names the state `main` reaches once
870+
* objectui#8901 and objectui#8888 have BOTH landed, and both have:
871+
* `fffa30d3f` at 2026-09-10T06:05:37Z and `8ea3beee4` at
872+
* 2026-09-10T06:05:40Z, three seconds apart and both ancestors of `main`.
873+
* ⇒ the gap this entry used to describe is CLOSED, and the sentence that
874+
* described it is history: while only one claimant had landed the live
875+
* payload sat below this constant (455,271 and 455,519, both measured) and
876+
* `pnpm check:eager-closure` printed MORE headroom than arithmetic on these
877+
* two constants gives. ⛔ Do not read a current headroom out of that — the
878+
* figure in force is the one the gate prints on YOUR build. Recorded
879+
* forward on purpose, and the reason outlives the gap: a shared budget with
880+
* two admitted claimants has no single-commit baseline that is not stale
881+
* the moment the second one lands, and erring toward the larger payload is
882+
* the direction that cannot hide growth.
841883
*
842884
* ⚠️ Unlike the entries above it, this is a reading of a tree carrying
843885
* diffs of its own — the two claimants — which is the point rather than a
@@ -916,9 +958,10 @@ export const PER_CHUNK_BASELINE = Object.freeze({
916958
// `34a1578ef`, the same build as BASELINE above (objectui#7122).
917959
'vendor-objectstack': 1_235_029,
918960
// `ba20b0bc0` (objectui#8816) — `main` `bbe285ee7` with BOTH admitted pull
919-
// requests merged in. A FORWARD reading; see the provenance note above for
920-
// why this one names a state `main` has not reached yet and what that does to
921-
// the printed headroom while only one claimant has landed.
961+
// requests merged in. It WAS a FORWARD reading; `main` has since reached that
962+
// state (`fffa30d3f` and `8ea3beee4`, both 2026-09-10, three seconds apart),
963+
// so the gap the provenance note above describes is closed. ⛔ The figure in
964+
// force is still the one the gate prints on your own build.
922965
'i18n-locales': 456_196,
923966
// `3f775eeb8`, its OWN console build — ⛔ not the one above it and not
924967
// BASELINE's. Moved with the ceiling in the same commit, per the maintainer

0 commit comments

Comments
 (0)