@stackbone/cli 0.4.1 → 0.5.1

package/CHANGELOG.md

@@ -7,6 +7,68 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.1] - 2026-09-17
+
+### Fixed
+
+- **The `AGENTS.md` that `init` writes said four skills while seven landed next
+  to it.** `init` and `link` install the set by cloning
+  `stackbone/stackbone-skills`, which went from four skills to seven on
+  2026-09-17. The scaffold template still described the old four and listed them
+  in a four-row table, so a creator opened a workspace whose own documentation
+  contradicted its `.claude/skills/` directory, with `stackbone-evals`,
+  `stackbone-guardrails` and `stackbone-integrations` named nowhere
+  (PLA-1587).
+
+- **`stackbone dev` and `stackbone package` pull MinIO from `quay.io`.** Docker
+  Hub closed the `minio/minio` namespace, so the compose file both commands
+  write named an image that no longer resolves and the local stack failed to
+  come up.
+
+- **`stackbone link` refuses an `http://` box address itself.** The rejection
+  lived only in the browser wizard, so linking from the terminal registered a
+  deployment whose agent URL was not encrypted in transit (PLA-1583).
+
+## [0.5.0] - 2026-09-14
+
+### Added
+
+- **`stackbone dev` records a write's echo and answers `isOwnEcho`.** A
+  connector call that names an `echoPath` has the value extracted from the
+  provider's response and recorded on its `connection` run step, and the
+  emulator plants the reader `isOwnEcho` queries on first dispatch, looking one
+  hour back across every workflow in the project. Three cases leave an
+  unresolved marker instead of a value, and reading one makes `isOwnEcho` throw
+  `echo_guard_unavailable` rather than answer a false "not ours": the path
+  resolved to nothing (missing, `null` and `''` are one case, because an empty
+  echo would match every later delivery whose value renders empty), the call
+  failed in a way that may still have landed (`execute_failed`, `timeout`, an
+  envelope-less `credential_error`), or the write ran with no workflow owner,
+  such as inside an agent turn's tool, which blinds every caller on that
+  connector. The runtime warns which write left the marker when it writes the
+  row. A call with no invocation context at all still writes to the provider
+  and records nothing, so it warns. Both halves need the `@stackbone/sdk`
+  released alongside this version: a project on an older SDK never sends
+  `echoPath`, and its `isOwnEcho` throws "No echo guard reader is bound".
+
+### Fixed
+
+- **`stackbone package --target self-host`: the agent no longer races the
+  control plane for the shared connect tables.** The two containers share one
+  Postgres and both declared `connection_grant`: db-core's migration with a
+  bare `CREATE TABLE`, the box's lazy boot DDL with
+  `CREATE TABLE IF NOT EXISTS`. Whichever arrived second lost, and a boot where
+  the box won killed the control plane's migration and surfaced as a
+  health-check timeout. The generated compose now sets
+  `STACKBONE_PLATFORM_SCHEMA_OWNER: control-plane` on the agent service and the
+  box stands down. Not overridable from `.env`: it is a fact about that compose
+  file, not a preference. `stackbone dev` and BYOC set nothing and keep creating
+  their own tables.
+
+- **A failed broker-context build is no longer cached for the life of the
+  process.** One Postgres hiccup on the first Connect request used to disable
+  Connect until the container restarted; the next request now rebuilds it.
+
 ## [0.4.1] - 2026-09-11
 
 ### Added