Observed while running the derived gate set for #10746 (full packages closure built, then pnpm check:type-check-debt --re-measure, 2026-08-23, tree at origin/main merge-base 2f93d0f53):
ℹ @objectstack/trigger-record-change: TEST_DEBT records 9, and tsc now reports 0 -- graduation candidate. Onboard it (add "typecheck": "tsc --noEmit", or drop the test exclusion, and delete the ledger entry in the same PR). --lower deliberately leaves this one alone: 0 is not a lower ceiling, it is a graduation, and an entry recording 0 fails the structural half of this gate.
The gate's own message names the remedy: onboard the package (add a typecheck script or drop the test exclusion) and delete the TEST_DEBT ledger entry in the same PR. Until someone does, the entry holds a 9-error ceiling over a package that is now clean — room for regressions to land in that layer without any gate saying anything (the same surplus class as the ledger's standing surplus: note, see #6376).
Observation only — no defect today; the run itself was green (check-type-check-coverage --re-measure: OK — 33 ledger entr(ies) re-measured … none above its recorded number). Filed unassigned per the out-of-scope-findings rule; searched open issues for trigger-record-change graduation first and found none (nearest siblings are per-package surplus findings like #10615, different package).
Observed while running the derived gate set for #10746 (full packages closure built, then
pnpm check:type-check-debt --re-measure, 2026-08-23, tree atorigin/mainmerge-base2f93d0f53):The gate's own message names the remedy: onboard the package (add a
typecheckscript or drop the test exclusion) and delete the TEST_DEBT ledger entry in the same PR. Until someone does, the entry holds a 9-error ceiling over a package that is now clean — room for regressions to land in that layer without any gate saying anything (the same surplus class as the ledger's standingsurplus:note, see #6376).Observation only — no defect today; the run itself was green (
check-type-check-coverage --re-measure: OK — 33 ledger entr(ies) re-measured … none above its recorded number). Filed unassigned per the out-of-scope-findings rule; searched open issues fortrigger-record-changegraduation first and found none (nearest siblings are per-package surplus findings like #10615, different package).