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

package/CHANGELOG.md

@@ -7,6 +7,75 @@ 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
+
+- **`stackbone dev`'s eve workspace boot now runs on the shared `@stackbone/workspace-runtime`
+  engine** (a pure refactor — no behaviour change). The supervisor that spawns the
+  N eve agents, the per-agent session Worlds, the main workspace World, and their
+  ordered teardown moved out of `apps/cli/src/dev/` into the new
+  `libs/runtime/workspace-runtime` lib, behind a single `bootWorkspaceRuntime`
+  entry point. The CLI is now just the dev SHELL around it (docker, tunnel,
+  watchers, local config, and the `eve build` / workflow compile it injects); the
+  same engine will boot cloud BYOC + self-host so the three environments run the
+  identical workspace. The engine assumes pre-compiled `.output/` and never
+  compiles — `stackbone dev` keeps its build-then-start behaviour by injecting
+  `runEveBuild`. `stackbone dev` over a v3 workspace boots identically (same
+  ports, health, workflows, chat).
+
+### Added
+
+- **`stackbone publish` now blocks an incomplete eve trace.** A new per-agent build
+  guardrail (alongside the native-deps + SDK-inline gates) detects when `eve build`
+  shipped a PARTIAL externalized `eve` into an agent's `.output/` — the symptom of an
+  upstream bug where eve's bundler (nitro + `@vercel/nft`) drops a file reachable only
+  through eve's `#`-subpath imports (e.g. `connections/errors.js`), which crash-loops
+  the agent at boot with `ERR_MODULE_NOT_FOUND`. Publish aborts with the fix: add
+  `"eve*"` to the agent's `defineAgent({ build: { externalDependencies } })`, which
+  forces nitro's full-trace of eve (and sidesteps eve's own self-filter). Agents that
+  fully inline eve are unaffected, so they never carry the full-trace's extra weight.
+- **`stackbone publish` now packages a v3 workspace.** When the current directory
+  has a `stackbone.config.ts` (`defineWorkspace`), publish compiles every eve
+  agent (`eve build` → its Nitro `.output/`) and the workflows on THIS host, then
+  packs `stackbone.config.ts` + each `.output/` + `.well-known/` + a derived
+  workspace manifest into a single tar with a verifiable SHA-256, written to
+  `dist/stackbone/`. Compiling at publish (not at boot) makes cold starts fast and
+  deterministic and turns a build error into a publish failure instead of a
+  production crash-loop. Each agent is scanned for native (`.node`) dependencies
+  and for an inlined `@stackbone/sdk` — either aborts with an actionable message
+  naming the offending package/agent before any tar is produced. (The
+  control-plane upload + build-pointer registration is the provisioning saga's
+  job; publish produces and records the artifact locally for now.)
+
 ## [0.1.0-alpha.12] - 2026-06-17
 
 ### Added