fix(scripts): list the 17th error in @objectstack/formula's TEST_DEBT note

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Fixes#13631

The @objectstack/formulaTEST_DEBT entry recorded errors: 17 above a per-code tally
that summed to 16. Which of the two numbers was wrong was established by measurement, not
by picking the easier edit.

Which number was right: the recorded 17

The gate's own --re-measure was run, not replicated. Its refusal path (a ledgered
package whose dependency closure has no built type entry point) was cleared by building
the closure first, exactly as lint.yml does:

pnpm exec turbo run build --filter='./packages/*' --filter='./packages/*/*'
pnpm check:type-check-debt

check-type-check-coverage --re-measure: OK — 29 ledger entr(ies) re-measured in 376.3s,
1542 raw tsc error(s) total, none above its recorded number.
surplus: none — every entry sits exactly at its measurement, so any new error is red.

surplus: none is the load-bearing line: every entry, this one included, measures
exactly its recorded number. So @objectstack/formula measures 17, the field was
right, and the tally was one line short.

The per-code breakdown was taken separately, through the gate's own measureTestDebt and
remeasureProject (a verbatim copy of the gate with a reporting block appended, so no
helper was re-implemented), at base cc837dbfec with the closure built:

TS2591 x6, TS2345 x3, TS2352 x3, TS1470 x2, TS2339 x2, TS2739 x1
SUM=17 measureTestDebt=17 RECORDED=17

The unlisted 17th is

packages/formula/src/cel-to-filter.test.ts(173,52): error TS2739: Type
'{ org_user_ids: never[]; }' is missing the following properties from type
'{ id: string; organization_id: string; org_user_ids: string[];
team_member_ids: string[]; department: string; }': id, organization_id,
team_member_ids, department

which reproduces the reporter's reading to the character position.

Why no gate had caught it

COMPOSITION (#10722) is the mechanical half that exists for exactly this shape — an
itemisation contradicting its own field. It reads tier itemisations
(code-tier / config-tier / noise) and, by an explicitly reasoned decision in its
own docblock, never sums per-code tallies, which are "partial by construction". This
entry's note is a pure per-code tally, so tierItemisation() returns null and the
entry is unguarded — measured in both directions, with a positive control proving the
probe was live:

[probe] OLD note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] NEW note -> null (no tier itemisation -> ENTRY UNGUARDED)
[probe] compositionProblems over the WHOLE live TEST_DEBT ledger -> []
[probe] POSITIVE CONTROL — a tier itemisation the same code DOES read
[probe] "code-tier 30, config-tier 25, noise 34." -> sum=89
[probe] contradicting tier note over errors:80 -> 1 problem(s)

That is a documented, deliberate false negative rather than a defect in the gate, and it
is not touched here. It is written into the corrected note so the next reader does not
mistake the entry's silence for a check.

The change

One TEST_DEBT entry's note. errors: 17 is untouched, no baseline moves, and the
entry is reflowed into the multi-line form its longer-noted siblings already use.

Gates

Derived from the real change set with node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack (not from a hand-written list), re-derived after merging
origin/main so the answer comes from a tree at origin/main. All run at
a8a9374b6, exit codes captured before any pipe:

result	gate
0	pnpm check:type-check-coverage
0	pnpm check:type-check-debt (full --re-measure, 29 entries)
0	pnpm check:pm-dispatch-gates
0	node scripts/pm/bare-root-worklist.mjs --self-test
0	pnpm check:agent-test-spelling
0	pnpm check:bash32-floor
0	pnpm check:cli-command-ids
0	pnpm check:cross-package-test-inputs
0	pnpm check:entry-guard
0	pnpm check:parse-guard
0	pnpm check:pnpm-filter-targets
0	pnpm check:watch-hint-literal
0	node scripts/check-ci-filter-parity.mjs
0	node scripts/check-cross-package-test-inputs.mjs
0	node scripts/check-shard-attestation.mjs
0	pnpm lint (repo-wide, 108s — not narrowed)
0	pnpm check:nul-bytes
NOT MEASURED	node scripts/check-test-completeness.mjs

The last one exits 3 on its own documented PREREQUISITE NOT MET branch — it grades a
saved turbo run test log and the derived family names it with no argument. Its own text
rules that branch NOT MEASURED rather than red.

The two convention-triggered obligations for editing a gate script
(bare-root-worklist --self-test, check:pm-dispatch-gates) were run, not just the
path-derived families.

Changeset

None, and skip-changeset is applied. This PR releases nothing: the only file is a
repo gate script under the private root package @objectstack/spec-monorepo, and
scripts/ appears in no package's published files.

Generated by Claude Code

---

Generated by Claude Code