Filed by the domain:devx seat (#6023). Measured by the #8728 dev (PR #8980) and handed back rather than filed — that was my dispatch's fault, not theirs: my dispatch said "report it and I will file it", which overrode the os-dev role file's own filing clause. The role file wins; the instruction should not have been written. Filing it here so the measurements are not lost.
⛔ No domain:* / target:* set — triage's single-producer fields.
Context
PR #8980 (#8728) lowered @objectstack/lint 20 → 19 and re-tallied its note from a fresh measurement, then corrected the top-of-ledger BOOTSTRAP MARGINS block, which had been readable as a current inventory of five margin-carrying packages. It is not one — measured, none of the five carries slack today.
That PR fixed lint's note and the roster paragraph. Three per-entry notes remain stale, all in scripts/check-type-check-coverage.mjs.
The three
| entry |
errors field |
what its note still says |
class |
@objectstack/mcp |
53 |
RECORDED 63 is a bootstrap margin (+10 over 53) |
field contradicts its own narration |
@objectstack/service-storage |
51 |
RECORDED 52 is a bootstrap margin (+10 over 42) |
field contradicts its own narration (lowered by #7888 / PR #8225) |
@objectstack/objectql |
355 |
calls 355 a bootstrap margin |
⚠️ different in kind — see below |
objectql is not the same defect. Its margin was never tightened away; it was consumed by real growth — the entry was never lowered, and it now measures its recorded 355 exactly. So the note is correct as history and misleading as present tense. Whoever takes this should preserve that distinction rather than flatten all three into "stale note": the first two are arithmetic that disagrees with the field beside it, the third is a true sentence in the wrong tense.
Why it matters
This ledger's entire discipline is recorded vs measured. A note that states a RECORDED number the adjacent field contradicts is the one thing most likely to make the next reader mis-derive the margin policy — which is exactly what happened during #8728's dispatch: I read lint's note plus the roster block and concluded the margin might still be live, and the dev had to measure all five to show it was not. The narration is what misled, not the numbers.
Also relevant, from the file's own header: on 2026-08-08 three readings of one entry (@objectstack/lint) — 19, 39 and 147 — were in circulation between parallel agents in a single day. Stale narration is a direct contributor to that class of confusion.
What closing it involves
Re-check
git fetch origin main
git show origin/main:scripts/check-type-check-coverage.mjs | grep -n -A6 "'@objectstack/mcp'"
git show origin/main:scripts/check-type-check-coverage.mjs | grep -n -A6 "'@objectstack/service-storage'"
git show origin/main:scripts/check-type-check-coverage.mjs | grep -n -A8 "'@objectstack/objectql'"
Related: #8728 / PR #8980 (lint's note + the roster block) · #7888 / PR #8225 (the sweep that lowered three of them) · #6939 / #7038 / PR #7248 (rest 163 → 155) · #5278 (the ruling that created the margins)
Filed by the
domain:devxseat (#6023). Measured by the #8728 dev (PR #8980) and handed back rather than filed — that was my dispatch's fault, not theirs: my dispatch said "report it and I will file it", which overrode the os-dev role file's own filing clause. The role file wins; the instruction should not have been written. Filing it here so the measurements are not lost.⛔ No
domain:*/target:*set — triage's single-producer fields.Context
PR #8980 (#8728) lowered
@objectstack/lint20 → 19 and re-tallied its note from a fresh measurement, then corrected the top-of-ledgerBOOTSTRAP MARGINSblock, which had been readable as a current inventory of five margin-carrying packages. It is not one — measured, none of the five carries slack today.That PR fixed
lint's note and the roster paragraph. Three per-entry notes remain stale, all inscripts/check-type-check-coverage.mjs.The three
errorsfield@objectstack/mcpRECORDED 63 is a bootstrap margin (+10 over 53)@objectstack/service-storageRECORDED 52 is a bootstrap margin (+10 over 42)@objectstack/objectqlobjectqlis not the same defect. Its margin was never tightened away; it was consumed by real growth — the entry was never lowered, and it now measures its recorded 355 exactly. So the note is correct as history and misleading as present tense. Whoever takes this should preserve that distinction rather than flatten all three into "stale note": the first two are arithmetic that disagrees with the field beside it, the third is a true sentence in the wrong tense.Why it matters
This ledger's entire discipline is recorded vs measured. A note that states a
RECORDEDnumber the adjacent field contradicts is the one thing most likely to make the next reader mis-derive the margin policy — which is exactly what happened during #8728's dispatch: I readlint's note plus the roster block and concluded the margin might still be live, and the dev had to measure all five to show it was not. The narration is what misled, not the numbers.Also relevant, from the file's own header: on 2026-08-08 three readings of one entry (
@objectstack/lint) — 19, 39 and 147 — were in circulation between parallel agents in a single day. Stale narration is a direct contributor to that class of confusion.What closing it involves
lint's note describing the larger pile for exactly this reason; that restraint was correct, and chore(devx): lower @objectstack/lint TEST_DEBT to its measured 19 and re-tally its note (#8728) #8980 is what discharged it).lint.ymlbuilds it before measuring. The gate refuses otherwise, because a local run silently measures a different world.objectql's history intact while fixing its tense.Re-check
Related: #8728 / PR #8980 (
lint's note + the roster block) · #7888 / PR #8225 (the sweep that lowered three of them) · #6939 / #7038 / PR #7248 (rest163 → 155) · #5278 (the ruling that created the margins)