@stackbone/cli 0.1.0-alpha.13 → 0.1.0-alpha.14

package/CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.0-alpha.14] - 2026-06-25
+
+### Removed
+
+- **`stackbone trigger` and `stackbone queues` are gone.** Both belonged to the
+  deprecated classic `/invoke` runtime. `stackbone trigger` posted to the dev
+  emulator's `/api/invoke`, which the eve runtime retired (replaced by the
+  `/api/agents/:name/chat` proxy), so the command hit a route that no longer
+  exists. `stackbone queues` drove the classic agent-jobs BullMQ dispatcher,
+  which `stackbone dev` no longer boots (it answers `503 queues_unavailable`);
+  in the new runtime async work is modelled as durable workflow runs. To
+  exercise a trigger-driven workflow locally, start it by name with
+  `stackbone workflows start <name>`. The `STACKBONE_EMULATOR_URL` env var
+  (only `stackbone trigger` read it) is removed too. The `client.queues` SDK
+  capability and Studio's Queues inspector are unaffected.
+
+### Fixed
+
+- **`stackbone init` no longer scaffolds a workspace that fails `pnpm install`.**
+  The generated `package.json` pinned `@stackbone/workflow-world` — our durable
+  Workflow SDK World fork, a platform internal that is never published to npm —
+  so the post-init `pnpm install` 404'd ("could not resolve
+  @stackbone/workflow-world"). The CLI now ships its own esbuild-bundled copy of
+  the World and provisions it into the workspace's `node_modules` at `stackbone
+dev` boot (the same mechanism already used for `@stackbone/agent-server`), and
+  the scaffold no longer declares the package. The public `@workflow/world` is
+  kept as the single shared base.
+
 ## [0.1.0-alpha.13] - 2026-06-25
 
 ### Changed