@stackbone/cli 0.3.5 → 0.4.0

package/CHANGELOG.md

@@ -7,6 +7,155 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-09-10
+
+### Added
+
+- **A workflow declares what it sends outward, and `stackbone dev` types it.**
+  `export const declaredOutputs = [{ name: 'report', kind: 'file' }, { name:
+'fileIssue', kind: 'action' }]` is a sibling export next to
+  `inputSchema`/`outputSchema`, read out of the workflow module or its
+  `.contract.ts`. The emulator writes `.stackbone/outputs.d.ts` from it, which
+  closes the name sets the SDK's `stackbone.outputs.write` and
+  `stackbone.action` accept — naming an action where a file output belongs
+  becomes a compile error instead of a run-time `unbound`. The list is read by
+  PARSING, never by evaluating: an operator binds a name to a destination before
+  any run exists, so a name that only appears once the workflow is running is a
+  name nobody can point a destination at, and the parse refuses it where it is
+  written, with a line. `kind` is required in source and defaulted on both wires
+  (PLA-1092, PLA-1251).
+
+- **`.stackbone/connect.d.ts` types the connections the box has registered, not
+  just the connectors declared as files.** For seven of the eight built-ins the
+  difference is cosmetic, because their operations are a published API. For
+  Supabase it is the whole problem: a connection's operations ARE the customer's
+  schema, one per table, so they exist in no file and used to be retyped by hand
+  off the picker with nothing checking either half. The codegen now also reads
+  the box's own management surface. The box introspects and the CLI consumes,
+  which is forced rather than chosen — the credential is custodied in the broker
+  and Supabase refuses its metadata endpoint to an unauthenticated read. An id
+  declared in `connect/*.json` wins on collision, so the existing path stays
+  byte-identical.
+
+- **`stackbone init` offers the organization's existing workspaces.** It used to
+  resolve the workspace by (org, slug) and create on a 404, so a creator who had
+  made a workspace in the browser and then ran `init` in a folder of that name
+  silently got a second, empty one. When nothing else names the workspace it now
+  lists the organization's agents and offers to pick one. The non-interactive
+  contract does not move: `--name`, a positional directory, `--json`, `--yes`
+  and a missing terminal all skip the listing and the prompt (PLA-1204).
+
+### Changed
+
+- **BREAKING: `stackbone link` registers a box against one INSTALLATION, named
+  by `--installation <id>`, and never creates one.** The deployment registry
+  used to hold one row per agent template, while a box answers for exactly one
+  installation id and refuses every other with a 401 — so with two installations
+  of the same template at most one could be reached. The row now belongs to the
+  installation (`POST /api/v1/deployments` requires `installationId`), and
+  `link` has to be told which one: `--installation <id>` is one of the linked
+  agent's `cloud` rows in `stackbone agents list`. It is validated before the
+  box is touched — an id of another agent, an id this organization does not
+  hold, or a local-dev id (served by its `stackbone dev` tunnel, never by a
+  registered deployment) is refused with no teach and no registration. Without
+  the flag, `link` refuses before any network call and names the discovery
+  command, except on a `--force` re-run in a directory whose
+  `.stackbone/project.json` remembers the id the last link wrote (new field
+  `deploymentInstallationId`, named that because it sits next to
+  `localDevInstallationId` and the two are different rows; older files still
+  load, including one written under the interim `installationId` spelling —
+  that key is simply dropped, so the next `link --force` in that directory asks
+  for `--installation` once and rewrites the file. Nothing has to migrate it).
+  `link` no longer creates a cloud
+  installation when the agent has none — install the agent first. When the
+  target installation already answers somewhere, `link` prints the address it
+  is about to replace before proceeding. The JSON envelope keeps
+  `installation {id, organization_id, kind}` and drops `deployment_reachable`,
+  which could only ever say `reachable: true` now that a local-dev target is
+  refused up front (PLA-853).
+
+### Removed
+
+- **BREAKING: `stackbone runs retry` is gone.** `POST /api/runs/:id/retry`
+  copied the failed run's input, inserted a fresh `running` row and published
+  `run.created` so Studio repainted — and stopped there. Nothing ever advanced
+  that row, because nothing dispatched the payload to the agent. Three surfaces
+  sold it as real anyway, this verb among them, gated behind `--yes` as if it
+  were destructive. The route now answers 404 and a test pins it there, so the
+  placebo cannot come back without a dispatch behind it. Nothing is lost: the
+  action never did anything (PLA-949).
+
+### Fixed
+
+- **`stackbone eval` counts `not_evaluable` as an ending, and a swallowed
+  refusal no longer grades as a quality regression.** The CLI holds a twin of
+  Studio's ending list and only Studio's had been widened, so the same run got
+  one verdict in CI and another in the browser. The connector registry is now
+  asked before the row's status is read, on all three terminal paths and on the
+  timeout, rather than on `failed` alone — a workflow that catches its refused
+  connector call and returns anyway ends `done`, and the criteria would
+  otherwise grade an answer produced without the call ever happening.
+
+- **`stackbone package` ends `mc`'s flag parsing before the minted MinIO
+  password.** A generated password beginning with a dash was read as a flag.
+
+- **The CLI sends the bearer of the control plane it is actually calling.** The
+  session was picked by `credentials.activeUrl`, a single global pointer, while
+  the URL was resolved per invocation from `STACKBONE_API_URL`, the project's
+  `.stackbone/project.json` and the global config. On a machine signed in to
+  both production and a local stack the two disagreed constantly, so `whoami`,
+  `metadata` and `dev` sent one environment's token to another and got a 401
+  whose only suggestion — `stackbone login` — could not fix it, because the
+  operator was already logged in. Any CLI command run from a second workspace
+  rewrote the pointer and broke a session in progress. Sessions are now read
+  from `sessions[apiUrl]`, the active organization is keyed the same way,
+  `logout` revokes at the URL it prints in `control_plane_url` instead of
+  wherever the pointer aimed, and a missing session names the URL:
+  `No session for http://localhost:3790` (PLA-797).
+
+## [0.4.0-alpha.0] - 2026-08-31
+
+### Added
+
+- **`stackbone package --target byoc | self-host` picks which folder the command
+  writes.** It used to write one artifact, the two-service self-host stack.
+  `byoc` is the default and the historic folder — the agent alone, registered
+  from app.stackbone.ai — while `self-host` keeps the control plane and Studio
+  beside it. The exclusion is the point, not a convenience: a box that finds
+  `STUDIO_STANDALONE_TOKEN` on its boot env authenticates the operator by static
+  bearer and turns the browser identity gate off, so a BYOC folder carrying that
+  variable would be a box anyone holding one string could drive, with every
+  container still healthy. The BYOC inputs have no field to write it into
+  (PLA-1056).
+
+- **The `self-host` target generates both application services.** The shipped
+  Compose started the control plane, Postgres, Redis and MinIO and no agent at
+  all, so nothing served the box-owned routes Studio needs. It now brings up the
+  control plane with the Studio SPA and the workspace image beside it, on
+  separate configurable host ports, sharing one database, one `HMAC_SECRET` and
+  one operator token, with health checks and real startup ordering. The control
+  plane addresses the box as `http://agent:8080`, its Compose service name
+  (PLA-1069).
+
+### Changed
+
+- **The offline archives are named apart.** `agent-image.tar` carries one image
+  and never pulls a control plane; `stackbone-images.tar` carries both. A script
+  that hardcoded the single old name has to pick the one its target writes.
+
+### Fixed
+
+- **A rejected payload prints the fields it names, not just the sentence.**
+  `stackbone secrets set` printed `Request body failed schema validation.` and
+  nothing else, because the per-field detail rides under `details.issues` and
+  the reader took only `message`. It now prints the server's sentence followed
+  by one `  - name: Required` line per offending field, three at most and then a
+  `  (+<n> more)` line. A refusal carrying no issues prints its sentence
+  byte-for-byte, and a malformed or non-JSON body still prints `HTTP <status>`.
+  A local `ZodError` renders through the same bound, so the CLI's own rejections
+  and the box's read alike. SSE and multipart inherit it through the same
+  function (PLA-1044).
+
 ## [0.3.5] - 2026-08-27
 
 ### Added