assertLazyLinterStaysLazy ignores resolveSpecDistInjection's output — the counter-probe fails every console build made with OBJECTSTACK_SPEC_DIST set #5388

Activity

1. os-project-manager

   added

   bugSomething isn't workingSomething isn't working

   pm:queue

   pm:dispatched

   and removed

   pm:queue

   on Aug 20, 2026
2. os-project-manager

   self-assigned this

   on Aug 20, 2026
3. os-project-manager

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

   fix(console): feed the lazy-linter counter-probe the injection-aware …

   ...

   b7b2b3b
4. os-project-manager commented on Aug 20, 2026

   

   os-project-manager

   on Aug 20, 2026 – with Claude

   CollaboratorAuthor

   More actions

   {
     "issue": 5388,
     "status": "done",
     "branch": "claude/issue-5388-lazy-linter-injection",
     "pr": "https://github.com/objectstack-ai/objectui/pull/5390",
     "premise_still_valid": true,
     "summary": "Every line number in the issue was re-verified on origin/main (0fd11444a) before editing and all were accurate. resolveSpecDistInjection now publishes specModuleTest beside vendorChunkTest, widened by one shared widen() rule; assertLazyLinterStaysLazy takes the spec test as a parameter and the config hands it the injection-aware value, exactly as the vendor-objectstack group does at line 442. specModuleTest is deliberately NOT vendorChunkTest, because the latter is the whole vendor scope minus lint and an eager @objectstack/client would satisfy it without proving the walk can see the spec chunk. LINT decision: NOT made injection-aware (no producer publishes a lint location today, so it could only be speculative and untestable), but it gains its own counter-probe, because a blind LINT fails SILENT where a blind SPEC fails LOUD. One measurement in the issue and the dispatch is wrong and is corrected in the PR body: @object-ui/console is NOT a private app. It has no private:true, carries publishConfig.access public, is one of the 40 packages in the .changeset fixed group and ships its built dist/. Nothing publishes here for a narrower reason: vite.config.ts and repo tooling are not in its files list and the emitted bundle is unchanged. Empty-frontmatter changeset added; this repo has no skip-changeset label and none was minted.",
     "tests": "All at HEAD b7b2b3b8c (= the final commit; the gate union below was run on that tree). BASELINE FIRST, on unfixed origin/main: OBJECTSTACK_SPEC_DIST set => EXIT=1, 'counter-probe failed: no eagerly loaded chunk contains an @objectstack/spec module ... (entry chunks: assets/index-BInyohVQ.js; eager chunks: 58/507)'; unset => EXIT=0. WITH FIX: set => EXIT=0, 8592 modules transformed; unset => EXIT=0, 8592 modules transformed. The probe FOUND the injected spec rather than skipping: the injected build's own dist/stats.html carries 13 distinct module ids under the override directory and 0 ids from the installed @objectstack+spec@17.0.0. REVERSE VERIFICATION, direction predicted before running (plain RED, and on the LINT message not the counter-probe): negative lookaheads removed from VENDOR_OBJECTSTACK_TEST so the vendor group claims the linter => EXIT=1 both with and without the override, 'RolldownError: [assert-lazy-linter-stays-lazy] `@objectstack/lint` is in the EAGER closure (assets/vendor-objectstack-BXk7O0mY.js), so every console page load pays for it - ~89 KiB gzipped'. Ablation applied on top of the committed fix and reverted with git checkout HEAD --; tree verified clean afterwards. UNIT: vitest run --project unit over vite-objectstack-spec-dist + vitest-config-alias-targets-3944 + side-effects-declaration-consistency + check-type-check-coverage => 'Test Files 4 passed (4) / Tests 381 passed (381)'. GATES at b7b2b3b8c: type-check:scripts [0]; tsc -b apps/console/tsconfig.node.json --force [0] (the project that actually contains vite.config.ts and scripts/vite-*.ts); eslint on all 3 changed files [0] (5 pre-existing-style no-explicit-any warnings, 0 errors); check-changeset-presence [0]; check-changeset-no-major [0]; check-control-bytes [0]. NOT RUN and why: apps/console's full 'tsc --noEmit' half needs a built workspace dep closure that does not exist in a fresh worktree (no packages/*/dist anywhere) - it fails identically on unmodified origin/main with TS2307/TS2882 on @object-ui/* and covers src/, which this diff does not touch. The full gate farm runs once in CI.",
     "open_questions": [],
     "out_of_scope_findings": [
       "filed as #5391 (label: finding, unassigned): resolveSpecDistInjection validates the override's exports targets but not that the overriding package's own dependencies resolve from its location - a dep-less spec dist produces no error from the helper and fails ~80s later as a rolldown 'failed to resolve zod', naming zod rather than OBJECTSTACK_SPEC_DIST. Noted alongside it: while 5388 was unfixed that resolve error was completely invisible, because the counter-probe threw in generateBundle before rolldown escalated the accumulated resolve errors."
     ]
   }

   ---

   Generated by Claude Code
5. os-project-manager

   closed this as completedin #5390on Aug 20, 2026
6. akarma-synetal

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

   fix(console): feed the lazy-linter counter-probe the injection-aware …

   ...

   9a3daf8