@stackbone/cli 0.2.7 → 0.2.8

package/CHANGELOG.md

@@ -7,6 +7,53 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.8] - 2026-07-22
+
+### Fixed
+
+- **A failing run no longer takes down `stackbone dev`.** The start-and-wait
+  path read `Run.returnValue` twice, and that property is a getter that starts
+  a fresh poll on every read — so the first read produced a promise nobody was
+  awaiting. While runs succeeded nobody noticed; a FAILED run rejected that
+  orphan, Node escalated it to an uncaught exception, and the whole dev process
+  died. One failing Auto-map was enough to lose the emulator mid-session. The
+  getter is now read once: a failed run returns a 502 and the same process keeps
+  serving.
+- **Auto-map now proposes expressions that actually resolve.** The suggestion
+  prompt handed the model one `{ sourceSample, targetSchema }` envelope, so it
+  wrote paths relative to that envelope (`sourceSample.subject`) — they parse
+  cleanly, the editor accepts them, and then they match nothing against a real
+  event. It also invented `upperCase` for JSONata's `$uppercase`, which only
+  fails at evaluation time. The two documents are now passed as separately
+  labelled blocks, the event itself is stated as the root context, and only
+  `$`-prefixed builtins are allowed. A plain copy is asked for as a bare field
+  reference too, unless the target field's type, format, enum or description
+  genuinely asks for a shape.
+- **An agent no longer loses every surface because the runtime advertises one
+  unknown capability.** The contract's capability list was validated as a strict
+  enum, so a single unrecognised entry failed the whole document and took `ai`,
+  `storage`, `rag`, `queues`, `secrets`, `config` and `approval` down with it —
+  even though capability membership is additive by design. It is validated as
+  plain strings now, so an unknown capability is simply one no gate matches.
+
+### Changed
+
+- **`stackbone link` proves `--secret` against the container before it registers
+  anything.** It signs a challenge to the box's public
+  `GET /api/proxy-challenge`, which verifies it against the `HMAC_SECRET` the
+  container was actually booted with, and registers the deployment only on a
+  2xx. A mistyped or stale secret now fails right there with an actionable
+  error and nothing is persisted, instead of surfacing later as a fully broken
+  Studio proxy. Deployments registered before this need a re-link.
+- **Connector credentials live in the agent's own box.** The Connect broker —
+  connector registrations with their write-only `client_secret`, the grants, the
+  OAuth code exchange and the token cache — runs inside the box and is encrypted
+  under the box key; the control plane only forwards to it and holds none of it
+  at rest. `stackbone dev` keeps its existing dev fallbacks, and now also arms
+  the proactive token-refresh worker whenever Redis is up — including in a
+  workspace that only has deep agents and no workflows, so a local session
+  refreshes expiring grants the same way the production image does.
+
 ## [0.2.7] - 2026-07-21
 
 ### Removed