Measured while re-tallying @objectstack/rest's TEST_DEBT composition (#10821). Not repaired
there: that card is a data repair on one entry, and lowering another package's ceiling is a
different change with a different reviewer question.
What the measurement says
pnpm check:type-check-debt on main at 951b025e4, closure built, 32 ledger entries
re-measured in 282.1s, reports three entries sitting below their recorded ceiling:
| entry | recorded | tsc reports | surplus |
|---|
@objectstack/plugin-auth | 109 | 97 | −12 |
@objectstack/plugin-approvals | 348 | 347 | −1 |
@objectstack/runtime | 227 | 226 | −1 |
The gate prints all three itself, on every run, and states the consequence: nothing else reads
these hidden test layers, so that many regressions can land in them while this gate reports
success.
Why this is worth a card rather than the gate's own advisory line
The advisory names #6376 as the tracking card for the class — and #6376 is closed. So the
two small surpluses are currently tracked by nothing: they are printed on every run, they are
labelled "Not an error" in the same breath, and there is no open card that says who closes them.
@objectstack/plugin-auth's is the exception and already has #10615.
Two things a reader should not conclude from the numbers above:
Suggested scope
One PR that runs --lower for plugin-approvals and runtime and re-tallies whichever of the
two notes the lowering leaves describing a larger pile. Deliberately excludes plugin-auth,
which is #10615's.
Generated by Claude Code
Generated by Claude Code
Measured while re-tallying
@objectstack/rest's TEST_DEBT composition (#10821). Not repairedthere: that card is a data repair on one entry, and lowering another package's ceiling is a
different change with a different reviewer question.
What the measurement says
pnpm check:type-check-debtonmainat951b025e4, closure built, 32 ledger entriesre-measured in 282.1s, reports three entries sitting below their recorded ceiling:
@objectstack/plugin-auth@objectstack/plugin-approvals@objectstack/runtimeThe gate prints all three itself, on every run, and states the consequence: nothing else reads
these hidden test layers, so that many regressions can land in them while this gate reports
success.
Why this is worth a card rather than the gate's own advisory line
The advisory names
#6376as the tracking card for the class — and #6376 is closed. So thetwo small surpluses are currently tracked by nothing: they are printed on every run, they are
labelled "Not an error" in the same breath, and there is no open card that says who closes them.
@objectstack/plugin-auth's is the exception and already has #10615.Two things a reader should not conclude from the numbers above:
not lowered afterwards. The remedy is
pnpm check:type-check-debt --lower, which writes themeasured number, plus a note re-tally for any entry whose composition the lowering makes stale
(that second half is what [finding] plugin-rest's TEST_DEBT per-code tally lists 147 while declaring it was counted at 153 — 6 unaccounted, with no remainder clause #10821 was about, and it is the part
--lowercannot do for you).@objectstack/plugin-auth's TEST_DEBT records 109 where tsc now reports 98 — an 11-error surplus opened by PR #10614 #10615 was filed at "records 109where tsc now reports 98" — an 11-error surplus. Today the same entry measures 97, so the
surplus has widened to 12 since that card was written. Recording it here so the number on that
card is not read as current; the card itself is untouched.
Suggested scope
One PR that runs
--lowerforplugin-approvalsandruntimeand re-tallies whichever of thetwo notes the lowering leaves describing a larger pile. Deliberately excludes
plugin-auth,which is #10615's.
Generated by Claude Code
Generated by Claude Code