@stackbone/cli 0.1.0-alpha.2 → 0.1.0-alpha.4

package/CHANGELOG.md

@@ -7,6 +7,74 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.0-alpha.4] - 2026-05-18
+
+### Changed
+
+- **Breaking — `--template` renamed to `--starter`.** The `stackbone init`
+  command now reads `--starter <slug>` and scaffolds from `starters/<slug>/`,
+  a directory subtreed from one of the public
+  `github.com/stackbone/starter-<slug>` repos (10 slugs: `hello-world`, `ai`,
+  `rag`, `db`, `storage`, `queues`, `hitl`, `secrets`, `prompts`, `config`).
+  The legacy `--template` flag is recognised solely to emit the migration
+  message `--template was renamed to --starter; rerun with --starter <slug>`
+  and exit non-zero. The interactive picker now groups starters by
+  `stackbone.category` (`Core` first, then `Capabilities`) and lists ten
+  entries (the three bundled `hello-world` / `workflow` / `autonomous`
+  templates are gone — `workflow` and `autonomous` were mocks).
+  `.stackbone/project.json` writes `starter: <slug>`; the field is read-compat
+  with the legacy `template:` key (one release) and rewritten on next
+  `init`/`link`. The bundled `apps/cli/src/templates/` directory is deleted
+  in favour of the subtreed `starters/` layout. Public exports of
+  `services/scaffolding.ts` were renamed: `TEMPLATES` → `STARTERS`,
+  `TemplateChoice` → `StarterChoice`, `parseTemplateId` → `parseStarterId`,
+  `renderTemplate` → `renderStarter`.
+
+## [0.1.0-alpha.3] - 2026-05-15
+
+### Added
+
+- `stackbone dev` sessions are now first-class `installation` rows
+  (`kind='local'`). The CLI registers the row via
+  `POST /api/v1/installations/local-dev` during `init`/`link`, `PATCH`es
+  `local_tunnel_url` on dev start, and nulls it on Ctrl-C. The dev
+  boot banner emits a path-aware deeplink
+  (`app.stackbone.ai/app/<orgSlug>/installations/<id>?stackbone-dev=<tunnel>`)
+  consumed in one shot by the `stackboneDevBootstrapGuard` so Studio
+  opens straight on the local installation. Local-dev rows skip the
+  provisioning saga and the tier-quota gate by construction and are
+  garbage-collected after 7 days of inactivity.
+
+### Changed
+
+- Unified agent runtime env contract under `STACKBONE_*`. The dev
+  emulator now injects `STACKBONE_AGENT_ID` (the agent slug) plus
+  `STACKBONE_S3_ACCESS_KEY` / `STACKBONE_S3_SECRET_KEY` /
+  `STACKBONE_S3_ENDPOINT` / `STACKBONE_S3_BUCKET` /
+  `STACKBONE_S3_REGION` / `STACKBONE_POSTGRES_URL` into the agent
+  process, replacing the previous mix of `AWS_*` / `S3_*` /
+  `DATABASE_URL` names. Agents that still read the legacy names must
+  migrate.
+- Emulator `/api/schema` now returns `{ input: null, output: null }`
+  (200) when the manifest declares neither schema or the agent is
+  unreachable — was 502 before. Mirrors the cloud `/studio/schema`
+  shape so the Studio Playground UI can boot before the agent is
+  healthy.
+- `dev/fixtures-store.ts` persists JSONL records using the canonical
+  `Fixture` wire schema (camelCase `createdAt`, typed as `Fixture`) so
+  list/create return the wire type directly.
+
+### Fixed
+
+- `protectedCommand` no longer triggers the device-code flow on the
+  user's behalf. When no valid session exists it fails fast with
+  `code: 'auth'` and the standard "Run stackbone login" hint, and it
+  no longer retries on a mid-flight 401. Reason: the HTTP adapter
+  caches `tokenStore.activeSession()` once per process, so the
+  pre-login `POST /api/auth/device/code` poisoned the cache with
+  `null` and every subsequent request from the same process went out
+  without an Authorization header.
+
 ## [0.1.0-alpha.2] - 2026-05-12
 
 ### Added