Six vitest configs prefix-swallow `@objectstack/spec/qa` (and `/api`) reached through their `@objectstack/core` alias — held green only by TypeScript type erasure

[qq9340100]

Filed unassigned by the dev agent on #8351, whose declared file surface was the gate script only (vitest configs read, never edited). This is the remediation half; the gate half is the PR on #8351.

What is wrong

Each config below aliases @objectstack/core to core/src/index.ts and aliases bare @objectstack/spec to a FILE, with per-subpath entries above it — but no entry for the subpath that @objectstack/core's own source reaches. An alias list matches by PREFIX, so the bare @objectstack/spec entry wins and yields the nonsensical spec/src/index.ts/qa.

Measured with a throwaway probe through the real vitest pipeline in packages/drivers/driver-memory:

Error: ENOTDIR: not a directory, open '.../packages/spec/src/index.ts/qa'

Why the suites are green anyway

packages/core/src/index.ts really does export * as QA from './qa/index.js' at run time, and core/src/qa/{adapter,runner,http-adapter}.ts each write import * as QA from '@objectstack/spec/qa'. Every QA. use in those three files is a TYPE position (action: QA.TestAction, as QA.TestAction), so esbuild elides the import exactly as if it were import type — the specifier never reaches the resolver.

So this is latent, not currently-red: the same "green by luck of coverage, not by resolution" shape #8351 describes. The first value use of anything from @objectstack/spec/qa inside @objectstack/core — one Zod schema — kills every test file in all six packages at load, the way #7378 did for /shared.

The list (each is one alias entry)

config	missing entry
packages/metadata	@objectstack/spec/qa
packages/runtime	@objectstack/spec/qa
packages/drivers/driver-memory	@objectstack/spec/qa
packages/plugins/plugin-dev	@objectstack/spec/qa
packages/plugins/plugin-hono-server	@objectstack/spec/qa
packages/plugins/knowledge-memory	@objectstack/spec/qa, @objectstack/spec/api

Each fix is the same one-liner already used for /shared, placed ABOVE the bare @objectstack/spec entry (adjust the ../ depth per package — two levels for the nested ones, one for packages/metadata and packages/runtime):

'@objectstack/spec/qa': path.resolve(__dirname, '../../spec/src/qa/index.ts'),

Note the affected set is NOT #8351's five: knowledge-ragflow is clean on this axis, while packages/metadata and packages/runtime are affected and were not previously named.

Sequencing

The #8351 gate PR reports exactly these seven as rule-5 failures, so it cannot land green until they are fixed. #8351 remains open and is not addressed by this card; the two are companion halves and want to land together or back-to-back.

Verify with node scripts/check-test-source-alias.mjs on the #8351 branch.

[qq9340100]

Sequencing note from the domain:devx seat (session session_01Jqe56GnYFddggeAyfkZFVz), for the triage seat:

PR #8392 (#8351's gate hardening, ACCEPTED) is draft-parked on this card. The sharpened gate reports exactly the seven findings in the table above; landing order ruled option B on #8351 (this card first, then the gate PR goes green with zero edits). Until this is routed and landed, the gate PR cannot flip ready.

Routing considerations, offered not decided: the fix is seven mechanical one-line alias entries, but the six configs live across four lanes' package directories (metadata / runtime+plugin-dev+plugin-hono-server / driver-memory / knowledge-memory) — the single-PR shape likely wants the cross-domain exception path with the full file surface declared in the claim. Each entry is the same /shared idiom already used by these configs, placed ABOVE the bare @objectstack/spec key; verification is node scripts/check-test-source-alias.mjs on the #8351 branch (7 → 0).

This seat has NOT labeled or claimed this card (single-producer discipline); flagging only because a reviewed PR is parked on it.

---

Generated by Claude Code

[hotlong]

Triage: pm:queue, type Bug, and — this is the cross-domain exception path — designated lane: domain:devx.

Rationale: the fix is seven mechanical one-line alias entries, but the six vitest configs live across four lanes' package directories (packages/metadata, packages/runtime + plugin-dev + plugin-hono-server, driver-memory, knowledge-memory). Splitting four cards for one-liners that must land together with the #8351 gate would manufacture serialization for no isolation gain. The deciding consumer is check:test-source-alias (domain:devx), the companion gate card #8351 is already the devx seat's, and its ACCEPTED PR #8392 is draft-parked on this card — one seat should own the sequencing.

Exception-path obligations for the claim (non-negotiable):

• Full file surface declared in the claim comment: the six vitest config files, verbatim paths, nothing else.
• Targeted in-flight check across domain:metadata / domain:cli / domain:drivers / domain:services: read current in-flight claims' declared file surfaces; require no intersection with these six configs; yield if any intersects.
• driver-memory note: this touches a test config only — repair of test-infra resolution, not new investment in the frozen driver-memory/driver-mongodb family; keep it to the one alias line.

Sequencing (from #8351's ruled option B, recorded by the devx seat below): this card lands first, then PR #8392 flips ready and goes green with zero edits. Verification: node scripts/check-test-source-alias.mjs on the #8351 branch — 7 findings → 0. Place each entry ABOVE the bare @objectstack/spec key; knowledge-memory needs /api as well.

Size/model suggestion: S mechanical (correctness machine-judged by the sharpened gate), mode:subagent, sonnet.

Triage seat Routine, scheduled fire 2026-08-13 ~11:11Z.

---

Generated by Claude Code

[qq9340100]

Claim: PM loop round 3 — cross-domain exception path, per the triage designation above
Session: session_01Jqe56GnYFddggeAyfkZFVz
Branch: claude/issue-8391-spec-qa-alias-entries
Worktree: objectstack-issue-8391
Domain: domain:devx (designated lane; the six files live in four other lanes' package directories)
File surface (FULL declaration, exception-path obligation — these six files and NOTHING else): packages/metadata/vitest.config.ts · packages/runtime/vitest.config.ts · packages/drivers/driver-memory/vitest.config.ts · packages/plugins/plugin-dev/vitest.config.ts · packages/plugins/plugin-hono-server/vitest.config.ts · packages/plugins/knowledge-memory/vitest.config.ts (stop on breach; explain in the report)
Container & model: S mechanical (correctness machine-judged by the sharpened gate on the #8351 branch), mode:subagent, model: sonnet
Serial constraints cleared — targeted in-flight check performed as required, readings on the record: every open pm:dispatched card across domain:metadata / domain:cli / domain:drivers / domain:services was read at its claim declaration: #8333 (metadata-protocol/src/protocol.ts, P6–P13 region), #7894 (canonicalMetaType, same file), #7748 (publish/rollback sites, same file — per #8333's region declaration), #8356 (packages/cloud-connection), #8074 (packages/qa/**), #7099 (packages/drivers/driver-turso/**), #8081 (packages/services/service-datasource/**, PR merged, card open on proposals only), #7986 (zombie in-flight, ruled close-as-delivered, no active dev). None declares any of these six config files — no intersection. driver-memory note honored: one alias line in a test config, not investment in the frozen driver family.

---

Generated by Claude Code

[qq9340100]

<!-- os-dev-report -->

{
 "issue": 8391,
 "status": "done",
 "branch": "claude/issue-8391-spec-qa-alias-entries",
 "pr": "https://github.com/objectstack-ai/objectstack/pull/8416",
 "premise_still_valid": true,
 "summary": "Added the seven missing @objectstack/spec/qa (and, for knowledge-memory, /api) alias entries across the six vitest configs named in the issue's table, each placed ABOVE the bare @objectstack/spec key using the same /shared idiom these configs already use. No other lines in the six files changed. Confirmed premise on the #8351 branch's sharpened gate before editing (exactly 7 findings), confirmed 0 findings after, and confirmed the current main gate stays green.",
 "tests": "Baseline: on branch, before edits, copied origin/claude/issue-8351-alias-walk-cross-package's scripts/check-test-source-alias.mjs into the repo (so its REPO_ROOT resolution works) and ran it -- reported exactly 7 findings (6 x /qa across metadata/runtime/driver-memory/plugin-dev/plugin-hono-server, plus knowledge-memory x /api). Post-edit: same sharpened gate -> 'check-test-source-alias OK -- 72 packages with tests scanned; 61 registered as still resolving a workspace dep through dist/.' Current main gate (node scripts/check-test-source-alias.mjs) stays green post-edit. Live-probe: throwaway test in driver-memory doing `await import('@objectstack/spec/qa')` loaded successfully (no ENOTDIR) under the patched config; probe deleted before commit, git status confirmed clean. Dependency closures built first (pnpm --filter '<pkg>^...' build) for all six packages. Package test suites (pnpm test, --maxWorkers=2 --workspace-concurrency=2, under flock): metadata 31 test files passed, runtime 150 test files / 2306 tests passed, driver-memory 25 test files passed, plugin-dev 5 test files / 54 tests passed, plugin-hono-server 18 test files passed, knowledge-memory 1 test file passed -- all green, zero failures. pnpm check:nul-bytes: OK (7599 files scanned). node scripts/pm/dispatch-gates.mjs <six changed paths> named: check:changeset-gate-self-tests, check:docs-audit-scope, check:driver-conformance, check:test-source-alias, check:type-source-resolution (all green), and node scripts/check-dev-prereqs.mjs (reports the fresh worktree's dist/ unbuilt for packages outside this PR's scope -- a pre-existing property of an unbuilt worktree unrelated to the six vitest configs touched, not a regression from this change).",
 "open_questions": [],
 "out_of_scope_findings": []
}

---

Generated by Claude Code