agent-bundle/meta throws at import outside the compiler, making any source module that uses it un-importable from unit tests (agentBundleRstest does not alias it)

[ScriptedAlchemy]

What happened

Following the framework-mode guidance ("plugin source imports agent-bundle/meta instead of maintaining a hand-written src/lib/version.ts"), cargo-hauler moved its daemon version constant to:

import { version } from 'agent-bundle/meta';

in src/daemon/main.ts. Outside a compiled surface, node_modules/agent-bundle/dist/meta.js initializes every binding through throwUnavailableEntrypoint(), so importing the module throws at evaluation:

agent-bundle/meta is available only inside a surface Agent Bundle compiles; a plugin module reached it outside the compiler.

Consequences:

• Every plain rstest unit test that imports the daemon (directly or transitively: tests/harness.ts, lifecycle, ensure-daemon, broker, query, …) fails at import.
• The framework's own agentBundleRstest() route-unit preset does not alias it either. renderRoute('tool:hauler/hauler_status') and invokeCli(['daemon','status']) both fail with the same error as soon as the route reaches the daemon module (error load file dist/.rstest-temp/src_daemon_main_ts-effect_Schedule.mjs failed).

Workaround in use

A package.json-backed stand-in plus an alias in both rstest configs:

// tests/fixtures/agent-bundle-meta.ts
import type { AgentBundleMeta } from 'agent-bundle/meta';
import pkg from '../../package.json' with { type: 'json' };
export const version: AgentBundleMeta['version'] = pkg.version;
// ...

// rstest.config.ts and rstest.route-unit.config.ts
resolve: { alias: { 'agent-bundle/meta': fileURLToPath(new URL('./tests/fixtures/agent-bundle-meta.ts', import.meta.url)) } }

Ask

Either of:

1. A non-throwing development fallback for agent-bundle/meta that reads the nearest package.json when no compiled surface replaced the module (the value is knowable; only the compile-time inlining is not), or
2. agentBundleRstest() (and agent-bundle/test) aliasing agent-bundle/meta to such a fallback automatically, with the docs blurb updated to say how unit tests are expected to load a module that imports it.

Pin: agent-bundle@105c65d8f (pkg.pr.new), @rstest/core@0.11.11.

[ScriptedAlchemy]

Fixed by #416 (merged as 926b035).

What changed

• agentBundleRstest() and agentBundleBrowserRstest() (agent-bundle/rstest) now write .agent-bundle/test/meta.mjs and alias agent-bundle/meta$ to it via resolve.alias. The module is generated by the same generatedMetaModuleSource(projectMeta(...)) the build injects, fed from the compiler pass's plugin identity, so a source module doing import { version } from 'agent-bundle/meta' loads under plain unit tests, the route-unit level, renderRoute, and invokeCli with the identity package.json + agent-bundle.config.ts declare — no build, no hand-written stand-in, no per-config alias. Point every pool that reaches such source at the preset, e.g. defineConfig(await agentBundleRstest({ include: ['tests/**/*.test.ts'] })) for the ordinary unit run beside the route-unit config.
• When preparation produced no plugin model there is no identity to stamp; the aliased module then throws AB4760 naming the compiler diagnostics instead of serving unknown@0.0.0.
• The published agent-bundle/meta (dist/meta.js) reached outside the compiler now throws the structured AB4760 diagnostic (code, recovery, and a diagnostic field; the recovery is also inline in the message) instead of a bare Error. Documented in docs/diagnostics.md, docs/entry-conventions.md, docs/framework-mode.md, and the package README.

Tests

• New fixture project packages/agent-bundle/fixtures/meta-consumer (package.json-backed identity, source importing agent-bundle/meta, tool + CLI routes).
• tests/rstest-meta-alias.test.ts: the written module is byte-identical to what the build stamps and yields the package.json name/version; the sentinel case; src/meta.ts rejects with AB4760 + recovery.
• tests/rstest-meta-consumer.test.ts: spawns the fixture's unit and route-unit pools under the preset (pass), and the same unit tests without the preset (fail with [AB4760], no ReferenceError) — the exact repro from this issue.
• tests/mcp.test.ts: the bare-node dist proof asserts the AB4760 code and recovery.