From 66cb0a4786839eae07fa9537466c13a6c552423f Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 16:39:10 +0000 Subject: [PATCH 1/3] ci: take a same-tree size-gate reading (#277 repeatability control) Empty on purpose. The card asks for the gate to be run twice on ONE unchanged commit; this commit exists so a pull-request run and a re-run of that same run produce two readings over one identical SHA, with no tree diff to argue about. The measured figures land in the next commit. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01ChPQM8jamxLUfUAxwFpJ8S From 1bf8b7059d5d21d3e2c3160fc4023e5e4139b2b7 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 20:55:50 +0000 Subject: [PATCH 2/3] ci: say what the size gate's reading is repeatable to, not only accurate to MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The size-gate comment sets the reading up as a precise instrument — it quotes a 1.96 KiB / 0.0033% agreement with the figure Cloudflare accepted and concludes "the reading tracks the enforced figure". That is the right claim for the gate's job, accuracy against the limit, and it is silent on repeatability, which is what a diff-attribution question needs. Measured, not assumed. One commit run twice with no tree difference at all (66cb0a4, an empty commit whose tree hash is byte-identical to main's at 50aacb9), run 34252385192 attempts 1 and 2, two different ubuntu-latest runners: 58549.04 KiB and 58553.46 KiB, 4.42 KiB apart. Four cold rebuilds of that tree in one container spanned 0.62 KiB. Comment only. The budget, the limit and how the measurement is taken are unchanged. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01ChPQM8jamxLUfUAxwFpJ8S --- .github/workflows/ci.yml | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 08faeb5..ae2eeda 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -200,6 +200,39 @@ jobs: # Total Upload: 58553.98 KiB # 1.96 KiB low — 0.0033%. The reading tracks the enforced figure. # + # ## Accurate against the limit; NOT repeatable to better than a few KiB + # + # #277. Accuracy is this gate's job and the figure above is the right + # claim for it. It says nothing about REPEATABILITY, and a reader who + # meets 0.0033% at the point of use will reasonably assume a small + # per-PR delta means something. Measured, it does not. + # + # The control is ONE commit run twice, with no tree difference at all — + # not a workflow file, not a specifier line, nothing. `66cb0a4` is an + # empty commit whose tree hash is byte-identical to `main`'s at + # `50aacb9`; run 34252385192, attempts 1 and 2, landed on two different + # `ubuntu-latest` runners: + # attempt 1: Total Upload: 58549.04 KiB + # attempt 2: Total Upload: 58553.46 KiB + # 4.42 KiB apart. That is larger than the 1.96 KiB agreement above, so + # the agreement cannot be read as sub-KiB precision either — it is one + # comparison, taken inside this much noise. + # + # Holding the machine fixed shrinks the spread without closing it: four + # cold rebuilds of that same tree in one container gave 58548.93, + # 58548.93, 58548.94 and 58549.55 KiB — 0.62 KiB apart. + # + # So this number answers "is the bundle near the ceiling", not "did my + # PR grow the bundle". A single-digit-KiB move between two commits is + # inside the spread measured above and has not been shown to be a change + # in the bundle at all; a real growth of a few KiB is equally invisible. + # Attributing a small delta needs a same-tree control — the same commit + # run twice — not the previous commit's reading. + # + # n is small (2 CI runs, 4 local builds) and 4.42 KiB is the largest + # same-tree gap MEASURED, not a proven bound. Causes are NOT measured + # here and none is claimed. + # # ## The budget # # ONE constant, below, with the limit written beside it; every From 28056de228963a722f587140849b397f6d7954f2 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 8 Sep 2026 21:03:37 +0000 Subject: [PATCH 3/3] ci: fold the third size-gate reading in, and freeze the population MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The push of the previous commit produced a reading of its own (1bf8b70, run 34277657373, job 102234545211): 58549.06 KiB. That tree is not byte-identical to 66cb0a4's — it carries the comment — but the bundle inputs are, since a workflow file cannot enter the Worker, so it is recorded as the weaker of the two kinds of control and labelled that way. It changes the claim, not just the count. Two of the three readings agree to 0.02 KiB while the third sits ~4.4 KiB above both, so the shape is a tight cluster with one outlier rather than a reading that wanders across a 4.42 KiB band. The gzip column moves too (8800.26 / 8800.65 / 8797.64), which shows the artifact's bytes genuinely differ and nothing more — it does not track the raw figure. n corrected to 3 CI runs and 4 local builds. Every run produces another reading, so the block now says in its own words that it is a snapshot at named commits and is not maintained. Freezing the population is what stops "fold in the latest" from running forever. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01ChPQM8jamxLUfUAxwFpJ8S --- .github/workflows/ci.yml | 50 +++++++++++++++++++++++++++++++--------- 1 file changed, 39 insertions(+), 11 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index ae2eeda..e1c4016 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -207,19 +207,39 @@ jobs: # meets 0.0033% at the point of use will reasonably assume a small # per-PR delta means something. Measured, it does not. # - # The control is ONE commit run twice, with no tree difference at all — - # not a workflow file, not a specifier line, nothing. `66cb0a4` is an - # empty commit whose tree hash is byte-identical to `main`'s at + # The strongest control is ONE commit run twice, with no tree difference + # at all — not a workflow file, not a specifier line, nothing. `66cb0a4` + # is an empty commit whose tree hash is byte-identical to `main`'s at # `50aacb9`; run 34252385192, attempts 1 and 2, landed on two different - # `ubuntu-latest` runners: - # attempt 1: Total Upload: 58549.04 KiB - # attempt 2: Total Upload: 58553.46 KiB - # 4.42 KiB apart. That is larger than the 1.96 KiB agreement above, so - # the agreement cannot be read as sub-KiB precision either — it is one - # comparison, taken inside this much noise. + # `ubuntu-latest` runners. The third reading is from `1bf8b70`, a + # DIFFERENT tree — it carries this comment — but the same bundle inputs, + # since a workflow file cannot enter the Worker. Bundle-identical, not + # tree-identical: the weaker of the two controls, and labelled as one. + # + # 66cb0a4 attempt 1, job 102149701548 58549.04 KiB + # 66cb0a4 attempt 2, job 102152795435 58553.46 KiB + # 1bf8b70 run 34277657373, job 102234545211 58549.06 KiB + # + # Largest gap: 4.42 KiB, between two runs of the SAME commit. That is + # larger than the 1.96 KiB agreement above, so the agreement cannot be + # read as sub-KiB precision either — it is one comparison, taken inside + # this much noise. + # + # The SHAPE is a tight cluster and one outlier, NOT a wander across a + # 4.42 KiB band: two of the three agree to 0.02 KiB and the third sits + # ~4.4 KiB above both. Three points cannot carry a distribution and none + # is modelled here. What is claimed is only that repeated readings over + # identical bundle inputs are not equal, and how far apart the measured + # ones landed. + # + # wrangler's gzip column moves too — 8800.26, 8800.65, 8797.64 KiB — so + # the artifact's bytes genuinely differ; this is not the same number + # being displayed differently. It does not track the raw figure (the + # third reading has the smallest compressed size and a middling raw + # one), so it confirms that much and nothing more. # # Holding the machine fixed shrinks the spread without closing it: four - # cold rebuilds of that same tree in one container gave 58548.93, + # cold rebuilds of `66cb0a4`'s tree in one container gave 58548.93, # 58548.93, 58548.94 and 58549.55 KiB — 0.62 KiB apart. # # So this number answers "is the bundle near the ceiling", not "did my @@ -229,10 +249,18 @@ jobs: # Attributing a small delta needs a same-tree control — the same commit # run twice — not the previous commit's reading. # - # n is small (2 CI runs, 4 local builds) and 4.42 KiB is the largest + # n is small (3 CI runs, 4 local builds) and 4.42 KiB is the largest # same-tree gap MEASURED, not a proven bound. Causes are NOT measured # here and none is claimed. # + # ⚠️ A SNAPSHOT at the commits named above, deliberately NOT maintained. + # Every run of this workflow produces another reading, so "fold in the + # latest" has no end; the population was frozen at these three instead + # of chased. Nobody is obliged to update this block, and a later reading + # that differs is the point being made, not a defect in it. If the + # question ever needs more than "a few KiB", take a fresh same-commit + # series rather than appending to this one. + # # ## The budget # # ONE constant, below, with the limit written beside it; every