toolcraft install with Bun fails resolving workspace dependencies

[kamilio]

Summary

toolcraft is published, but installing it as a standalone dependency with Bun currently fails while resolving parts of its runtime dependency graph.

Minimal repro

{
  "type": "module",
  "dependencies": {
    "toolcraft": "0.0.3"
  }
}

Then run:

bun install

Result

Bun reports unresolved dependencies while installing toolcraft@0.0.3, including workspace packages and tiny-mcp-client.

I checked the published toolcraft@0.0.3 metadata and tarball:

• The @poe-code/* workspace packages are listed in bundleDependencies and are present in the tarball.
• tiny-mcp-client is listed as a dependency but is not present in bundleDependencies, and it is not resolvable from the public npm registry.

Expected

A public consumer should be able to install and import Toolcraft without local workspace overrides or vendored stubs.

Possible fixes:

• Publish tiny-mcp-client to npm, or bundle it with toolcraft.
• If Bun is expected to work, verify the bundled @poe-code/* dependencies install cleanly there too.

Environment

• toolcraft: 0.0.3
• Node: v22.14.0
• Bun: 1.3.11

[poe-code-agent]

Thanks, this is actionable and I reproduced the Bun failure mode against a locally packed Toolcraft tarball.

Opened PR #239 with a fix: bundled Toolcraft-only workspace runtime deps are now included in the tarball and listed as optional, so Bun no longer fails when those packages are not present on the public npm registry. I also added smoke coverage for the packed tarball contents/manifest.

Validation included npm run smoke:toolcraft-standalone, Toolcraft unit/lint checks, a Bun 1.3.11 install/import check against the packed tarball, and the pre-push npm test suite.

[poe-code-agent]

Issue was resolved by #01e324d

Update poe-code via npm install -g poe-code@3.0.195