Routed CLI (src/cli/**) is only emitted into the npm package build, not into host artifacts — artifact scripts/skills cannot invoke it

[ScriptedAlchemy]

What happened

In framework mode src/cli/**/*.tsx compiles to the generated CLI bin (dist/bin/<name>.js, dist/bin/<name>-flight.mjs) as part of the package build. Host artifacts (artifact/plugin, artifact/portable) receive scripts/*.mjs, mcp/, hooks/, skills/, mcp-apps/ — but not the routed CLI.

For cargo-hauler that means:

• The plugin ships scripts/hauler.mjs (a src/scripts/hauler.ts script route) which owns exec / install-shim / daemon and is meant to forward status | log | last | await | result | request to the routed CLI. Inside an installed plugin there is nothing to forward to, so node <plugin-root>/scripts/hauler.mjs status prints usage and exits 2.
• The bundled SKILL.md files tell agents to run hauler status / hauler await <ticket>. From a plugin-only install (Claude marketplace, Codex marketplace, Cursor ~/.cursor/plugins/local) those commands do not exist unless the user separately installs the npm package.
• The MCP tools cover the same surface, so MCP-capable sessions are fine — but hooks and skills are the surfaces that reach non-MCP shells.

Reproduce: agent-bundle build on ScriptedAlchemy/cargo-hauler at fa2f923, then node artifact/plugin/scripts/hauler.mjs status.

Ask

One of:

1. Emit the generated routed CLI into each host artifact as well (e.g. artifact/<target>/bin/<name>.mjs alongside scripts/), so a script route can spawn(process.execPath, [sibling]) or the skills can reference ${CLAUDE_PLUGIN_ROOT}/bin/<name>.mjs.
2. Or expose an in-process entry (agent-bundle/cli-runtime or similar) that a script route can import to dispatch argv through the compiled route graph without a second binary.

Related: a raw/streaming output mode for CLI routes that proxy a child process (own stdio entirely, return only an exit code) would let exec itself be a .ts CLI route instead of living in a separate script — today CLI routes must return a JSON-projectable result.

Pin: agent-bundle@105c65d8f.

[ScriptedAlchemy]

Landed in #419 (squash 7afb3286). Decision: emission, not an in-process entry — the routed CLI is the same class of surface as scripts/*.mjs, so every host artifact whose adapter publishes the new cli capability now receives the compiled command graph.

What changed

• agent-bundle build emits <target>/bin/<plugin-name>.mjs (plus bin/<plugin-name>-flight.mjs when any command renders) into every selected target that publishes the cli capability — all built-in targets (claude, codex, cursor, portable, plugin). It is a self-contained ESM module run as node <plugin-root>/bin/<plugin-name>.mjs <command> [args], identical in help, argv grammar, output modes, and exit codes to dist/bin/<plugin-name>.js; projected routes.mcpCommands tools ride along. The npm package bin is unchanged.
• Reaching it: script routes use the sibling convention new URL('../bin/<plugin-name>.mjs', import.meta.url) → spawn(process.execPath, [...]) (so scripts/hauler.mjs can forward status | log | last | await | result | request); skills/hooks use the plugin-root token (${CLAUDE_PLUGIN_ROOT}/bin/<plugin-name>.mjs). The composite plugin bundle's AGENTS.md documents the executable.
• Model/validation: cli capability row on every built-in adapter (component judgment componentCapabilities ?? capabilities), TargetArtifactLayout.cliBin pinned to bin/*.mjs at registration, artifact ownership validation and the manifest (bundle provenance naming every command route) know the directory, inspect accounts for a cli component per target, inspect --bundler dumps the per-target bin composition, BuildResult.compiledCliBins.
• Diagnostics: AB4765 (warning) when a selected target has no supported cli capability — the bin is omitted and inspect shows the unsupported-capability skip; AB4766 (build error) when a host-emitted file (e.g. a Claude claude.bin directory) collides with the bin path, compared case-insensitively.
• Durable state: the artifact bin anchors workspace-durable state on the artifact root (the parent of bin/), the same fallback as the MCP worker beside it; the npm bin keeps $PWD/.agent-bundle/state.
• Docs: docs/entry-conventions.md (“The routed CLI inside host artifacts”), docs/framework-mode.md, docs/diagnostics.md, packages/agent-bundle/README.md; changeset agent-bundle patch.

Tests

• tests/artifact-cli-bin.test.ts (integration): one fixture (plain + rendered CLI routes, a plain script route spawning the sibling bin) built for all five built-in targets plus a custom legacy-host adapter without the capability — bin + worker present per capable target, node bin/<name>.mjs status ticket-7 --json prints the routed JSON, help/version/rendered Markdown/--json/exit-2 usage, self-contained bundle, script route forwards argv through the sibling bin, legacy-host gets no bin/ and exactly one AB4765, manifest provenance, validateArtifact clean, inspect selected/skipped cli component, inspect --bundler entries; a Claude-only build proving ${CLAUDE_PLUGIN_ROOT}/bin/<name>.mjs in a skill lowers to a file the artifact ships and runs; AB4766 for an exact and a case-variant collision.
• tests/adapter-capability-states.test.ts: every built-in target publishes cli + cliBin; registration rejects a supported cli row without the layout (or with no layout at all), a layout not at bin/*.mjs; component overrides decide emission.
• Gates: typecheck, lint, unit (2728 passed; one pre-existing native-claude-contract 5 s timeout reproduced on pristine origin/main), route-unit 37, projection 66, build + integration 950/0, check:release:ci (packed suite 28/28, which caught and now covers the MCP-App ordering).

The related ask (a raw/streaming output mode for CLI routes that proxy a child process) is not part of this change.