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

package/CHANGELOG.md

@@ -7,6 +7,51 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.0-alpha.15] - 2026-07-01
+
+### Changed
+
+- **`stackbone init` now links every workspace to the control plane, and `add`
+  no longer touches the network.** The workspace is the linked unit: `init`
+  registers the workspace's identity (an agent named after the workspace) and
+  writes the single `.stackbone/project.json` for EVERY `--with` kind — `empty`
+  and `workflow` included — that `dev`, `publish` and the management commands
+  read. Because of this, `init` now needs a signed-in session for every kind (the
+  fully-offline `init` path is gone — run `stackbone login` first). In exchange,
+  `stackbone add agent` and `add workflow-agent` are now 100% offline: the pieces
+  you add are members of the already-linked workspace, not separate control-plane
+  registrations, so they no longer register an agent or write `project.json`.
+  This fixes the confusing flow where `init` left a workspace unlinked and
+  `stackbone dev` then failed with "No project linked — run `stackbone init`".
+
+## [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

package/README.md

@@ -9,28 +9,31 @@ The CLI for [Stackbone](https://stackbone.ai) — the marketplace and runtime fo
 No install required — invoke the CLI through `npx`:
 
 ```bash
-npx @stackbone/cli@alpha init my-agent
-cd my-agent
+npx @stackbone/cli@alpha login
+npx @stackbone/cli@alpha init my-workspace
+cd my-workspace && npm install
 npx @stackbone/cli@alpha dev
 ```
 
-That's it. `init` scaffolds a new agent project (templates + Claude skill); `dev` runs a local control-plane emulator with Stackbone Studio at `http://localhost:4242` so you can iterate without publishing.
+That's it. `init` scaffolds a new workspace shell (agents + workflows + coding-agent skills) and links it to your organization, so you sign in first; `dev` boots the whole workspace locally — Postgres, Redis, MinIO and Stackbone Studio at `http://localhost:4242` — so you can iterate without publishing.
 
 ## Commands
 
-| Command                      | What it does                                                           |
-| ---------------------------- | ---------------------------------------------------------------------- |
-| `stackbone init [name]`      | Scaffold a new Stackbone project from a template.                      |
-| `stackbone dev`              | Run the local control-plane emulator + Stackbone Studio.               |
-| `stackbone publish`          | Build, push, and publish the current agent to Stackbone runtime.       |
-| `stackbone login` / `logout` | Authenticate the CLI via the device-code flow (RFC 8628).              |
-| `stackbone whoami`           | Show the active user and organization.                                 |
-| `stackbone current`          | Print the organization currently linked to this session.               |
-| `stackbone link`             | Link the current directory to an existing organization + agent.        |
-| `stackbone list`             | List organizations the current user owns.                              |
-| `stackbone metadata`         | Agent-friendly snapshot of the workspace state.                        |
-| `stackbone db <subcmd>`      | Manage the local emulator database (migrations, queries).              |
-| `stackbone docs <topic>`     | Print Stackbone documentation inline. Run with no args to list topics. |
+| Command                       | What it does                                                           |
+| ----------------------------- | ---------------------------------------------------------------------- |
+| `stackbone init [name]`       | Scaffold a new workspace shell and link it to your org (needs login).  |
+| `stackbone add <kind> <name>` | Add an agent / workflow / workflow-agent to the workspace (offline).   |
+| `stackbone dev`               | Boot the whole workspace locally + Stackbone Studio.                   |
+| `stackbone workflows <verb>`  | List, inspect the schema of, or start the install's workflows.         |
+| `stackbone publish`           | Compile every agent + workflow and pack the workspace bundle.          |
+| `stackbone login` / `logout`  | Authenticate the CLI via the device-code flow (RFC 8628).              |
+| `stackbone whoami`            | Show the active user and organization.                                 |
+| `stackbone current`           | Print the organization currently linked to this session.               |
+| `stackbone link`              | Link the current directory to an existing organization + agent.        |
+| `stackbone list`              | List organizations the current user owns.                              |
+| `stackbone metadata`          | Agent-friendly snapshot of the workspace state.                        |
+| `stackbone db <subcmd>`       | Manage the local emulator database (migrations, queries).              |
+| `stackbone docs <topic>`      | Print Stackbone documentation inline. Run with no args to list topics. |
 
 Run any command with `--help` for the full flag reference, or `npx @stackbone/cli@alpha docs cli` for the inline documentation.