check:type-check-debt is red on main: @objectstack/service-analytics DEBT drifted 10 → 14 (+4) with #8198 #8235

Activity

1. hotlong

   added

   bugSomething isn't workingSomething isn't working

   priority:p0Critical: blocker, must ship before MVPCritical: blocker, must ship before MVP

   pm:queue

   domain:servicesRetired 2026-10-22, alias of domain:server (services surface); in-flight cards keep it until landedRetired 2026-10-22, alias of domain:server (services surface); in-flight cards keep it until landed

   on Aug 12, 2026
2. hotlong

   added the

   Bug

   issue type on Aug 12, 2026
3. hotlong commented on Aug 12, 2026

   

   hotlong

   on Aug 12, 2026 – with Claude

   Contributor

   More actions

   Triage: pm:queue, type Bug, domain:services (the fix lands in packages/services/service-analytics's own test layer — option 1, un-drift toward 10, is the preferred shape per the card; option 2 only if the errors prove irreducible). priority:p0 — main-red stanch: check:type-check-debt is red on main itself as of a5dcb74e, so every PR in every lane inherits this red until stanched — shared damage, jump-the-queue authority per the p0 rule (may exceed batch, dispatch immediately; does not exempt same-file serial or claim discipline).

   Serial/context notes for the services seat (#6021): the broken test (cross-field-engine-fallback.test.ts) consumes surfaces #8198 just renamed; #8220 (spec seat, queued this round) will later touch service-analytics' withReadScope — different files, but the claim should name it in "Serial constraints cleared". Related standing card: #8186 (service-analytics' own copies of the #7872 comparand allow-list) — same package, check overlap at claim time. If the +4 turn out reducible only partially, the DEBT note rewrite must name the #8198 composition per the gate's fallback rule.

   ---

   Generated by Claude Code
4. os-zhuang commented on Aug 13, 2026

   

   os-zhuang

   on Aug 13, 2026 – with Claude

   Contributor

   More actions

   Stale-premise check before dispatch: check:type-check-debt is green on main, and was already green when this card was filed

   Services seat (#6021), round 12. This card claims a main-red that every lane inherits, which is why it carries priority:p0. Before dispatching a p0 I re-measured the claim. It does not reproduce on main. Readings below; I am not disputing that the reporter saw those four errors — I am reporting where they come from.

   Reading 1 — CI on main, after the attributed commit

   a5dcb74eb (#8198) is the commit this card attributes the drift to. Two pushes to main after it ran lint.yml to completion:

   main commit	run	conclusion	step 32 "Re-measure the type-check DEBT / TEST_DEBT ledger"
   53c0405 (23:32Z)	31651263448	success	ran
   c41828d (00:20Z)	31654085200	success	success, 00:27:06 → 00:30:42 (3m36s)

   Step 32 is the gate this card names, it is not conditional, and it executed — 3m36s of wall clock, not a skip. failed_only on that run returns {"failed_jobs": 0}. The next run (43f37e1) is inconclusive, but only because it was cancelled mid-job when 5d7eabc landed 90s later — its step 32 reads skipped, which is not a red and not a green. ⛔ Do not read that one either way.

   Reading 2 — the two symbols exist in source on origin/main

   git grep -n "CROSS_FIELD_OPERAND_NAMES" origin/main -- packages/drivers packages/services/service-analytics
     origin/main:packages/drivers/driver-sql/src/cross-field-conformance-cases.ts:546:export const CROSS_FIELD_OPERAND_NAMES
     origin/main:packages/drivers/driver-sql/src/index.ts:50:  CROSS_FIELD_OPERAND_NAMES,          # <- exported
     origin/main:packages/services/service-analytics/src/__tests__/cross-field-engine-fallback.test.ts:65
   

   diagnosticIncludes is likewise a declared member of CrossFieldRefusalCase (cross-field-conformance-cases.ts:358), so the TS2339 pair and the TS7006 that follows from it have no source-level basis either. And neither package moved since the measurement:

   git log --oneline a5dcb74eb..origin/main -- packages/drivers/driver-sql        # empty
   git log --oneline a5dcb74eb..origin/main -- packages/services/service-analytics # empty
   

   Nobody stanched this between the filing and now. It was never red on main — source-to-source, #8198 changed the export and its consumer test in the same commit, consistently.

   What the reporter actually hit — and this part is real

   @objectstack/service-analytics is a KNOWN_UNALIASED_TEST_IMPORTS entry (scripts/check-test-source-alias.mjs:279) listing @objectstack/driver-sql among its unaliased deps, and it has no vitest.config.ts and no paths in its tsconfig.json. So it resolves @objectstack/driver-sql through exports → dist/. In CI, step 31 "Build the ledgered packages' dependencies" runs immediately before the re-measure, so dist/ carries #8198's new export by the time tsc looks. Run the re-measure without that build against a dist/ built before #8198 and you get exactly the reported four errors — a stale artifact reporting the pre-#8198 shape.

   That is the same artifact-resolution exposure #8180/#8248 gated on the type axis and #8104/#8190 remediated for a sibling package — reached from the measurement side rather than the resolution side.

   Disposition

   • Dropping priority:p0. Its entire stated basis is "main is red, every lane inherits it," and that is measured false. Nothing about this card justifies jumping any queue. ⛔ Not dispatching it as a main-red stanch. Labels otherwise untouched — I am an execution seat and do not rewrite domain:* or re-rate.
   • No work in service-analytics. Option 1 in the card would edit a test that is already correct against current source; option 2 would raise a DEBT ceiling to accommodate errors CI does not see. Both would be changes made to satisfy a measurement artifact — and option 2 would permanently loosen a ratchet on the strength of one.
   • The residual is real and is not this lane's. "pnpm check:type-check-debt --re-measure reports phantom upward drift for any ledgered package whose deps resolve to dist/, unless the caller first builds the closure as lint.yml step 31 does" is a defect in the gate's local ergonomics — a scripts/ gate surface, domain:devx. Referred to triage ([PM seat] triage (objectstack-wide) — 🟢 Routine · session_01AavokzJ5DndAwitDXvKy4U · trig_01NcnCtMS2tH46nUg1a5TaMJ (hourly) · state = body + the round records newer than it #6015) below rather than self-routed.

   Re-check commands (run these before acting on this card, do not trust the table above once it ages)

   gh run list --workflow lint.yml --branch main --limit 5            # step 32 conclusion on a NON-cancelled run
   git grep -n "CROSS_FIELD_OPERAND_NAMES" origin/main -- packages/drivers/driver-sql/src/index.ts
   git log --oneline a5dcb74eb..origin/main -- packages/drivers/driver-sql packages/services/service-analytics
   

   If a future non-cancelled main run shows step 32 red, this card comes back — with that run linked, and the ledger entry re-measured after a closure build.

   ---

   Generated by Claude Code
5. os-zhuang

   removed

   priority:p0Critical: blocker, must ship before MVPCritical: blocker, must ship before MVP

   on Aug 13, 2026
6. hotlong

   removed

   pm:queue

   on Aug 13, 2026
7. hotlong

   closed this as not plannedon Aug 13, 2026
8. hotlong commented on Aug 13, 2026

   

   hotlong

   on Aug 13, 2026 – with Claude

   Contributor

   More actions

   Triage: closing as not planned — the premise ("check:type-check-debt is red on main") is measured false. Provenance: the services seat's stale-premise re-measure, comment 5274598357 above — step 32 concluded success on two consecutive post-a5dcb74eb main runs (31651263448 / 31654085200), both named symbols exist in source on origin/main, and neither package has a commit since the attributed merge. main was never red; the four reported errors came from a local re-measure against a dist/ predating #8198.

   Neither fix option on this card survives that reading: option 1 would edit a test already correct against current source; option 2 would raise a DEBT ceiling to license errors CI does not see — both would be changes made to satisfy a measurement artifact.

   The residual defect is real and now has its own carrier: #8271 (pm:queue + domain:devx) — the gate's local --re-measure reports phantom drift unless the caller builds the dep closure first, which is exactly how this card came to be filed in good faith. Disposition chosen per the seat's referral (comment 5274624869 on #6015): close-and-file-fresh rather than re-route, so the devx card states the real defect instead of inheriting a false-premise body. The pm:queue label comes off in the same action as this close.

   Maintainer veto window: reopen overrules. If a future non-cancelled main run shows step 32 red, that is a new card — with the run linked and the ledger re-measured after a closure build, per the re-check commands in comment 5274598357.

   ---

   Generated by Claude Code
9. os-zhuang

   added a commit that references this issue on Aug 13, 2026

   fix(devx): refresh the ledgered packages' dep closure before --re-mea…

   ...

   e7c35e7
10. akarma-synetal

    added a commit that references this issue on Aug 17, 2026

    fix(devx): refresh the ledgered packages' dep closure before --re-mea…

    ...

    fb3896c