@stackbone/cli 0.1.0-alpha.3 → 0.1.0-alpha.5

package/CHANGELOG.md

@@ -7,6 +7,95 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.0-alpha.5] - 2026-05-18
+
+### Added
+
+- `stackbone docs <section>` content is now generated from the wiki
+  (`apps/wiki/public/content/docs/<section>/*.md`). A new
+  `cli:sync-docs` Nx target reads every markdown page, strips the
+  frontmatter, prepends the title as an H1 and emits
+  `apps/cli/src/docs/topics.generated.ts`; `cli:build` depends on it so
+  the bundled CLI can never drift from the wiki again. `docs <section>`
+  prints an auto-generated table of contents; `docs <section>/<slug>`
+  prints the page body. The inline `starters` / `connections`
+  placeholders are gone — once the corresponding wiki pages land they
+  surface automatically.
+- Branded interactive surface. Clack's prompt glyphs (`◆`, `│`, `┌`,
+  `└`, spinner) are repainted to brand orange via a pnpm patch on
+  `@clack/prompts`, the boot banner picks up the same truecolor
+  accent, and every interactive command (`init`, `link`, `dev`,
+  `login`) now opens with a `◆◆◆  stackbone  v<version> · <command>`
+  header. The `login` flow uses `note()` for the device code + URL,
+  `log.step()` for the browser hint and a `spinner()` for the polling
+  wait — replacing the raw `process.stdout` writes that read flat
+  against the rest of the clack session.
+
+### Changed
+
+- **Breaking — `--api-url` flag removed.** Control-plane URL resolution
+  collapses to `STACKBONE_API_URL` → project config → global config.
+  The env var keeps working internally so the team can still point at
+  staging/prod, but it is no longer advertised in the wiki, the
+  embedded skill template or the README — external developers should
+  not need to think about it. HTTP, device-flow and dev-tunnel error
+  suggestions are updated to match.
+- Native Windows shells (PowerShell, CMD, Git Bash) are now blocked at
+  startup. `process.platform === 'win32'` triggers a branded `◆◆◆`
+  banner pointing at issue #70 for the long-term Windows-support work,
+  routed through the canonical `StackboneCliError` envelope so
+  `--json` consumers see the same `{schema_version, error, exit_code}`
+  shape they get from every other failure. WSL is unaffected because
+  Node there reports `linux`.
+- The truecolor ANSI palette is centralised in `core/ansi.ts` and
+  reused from the boot-banner, brand-header and platform-guard
+  formatters instead of three hand-copied `{ reset, bold, dim, accent }`
+  objects drifting in parallel.
+- Internal cleanup: `parseResponse(schema, raw, context)` extracted to
+  `infra/http.ts` so every control-plane service shares one error
+  envelope for unexpected response shapes; `resolveDrizzleKitBin`
+  consolidated in `dev/drizzle-bin.ts`; UUID validation centralised in
+  `dev/uuid.ts`. `stackbone dev` only fetches the active organization
+  when the project is missing `localDevInstallationId` /
+  `organizationSlug`, and SIGINT teardown runs the tunnel-PATCH and
+  `session.stop()` via `Promise.allSettled` so a hung control-plane
+  call cannot block docker teardown. Independent filesystem writes in
+  `project.service` and `dev/compose.ts` now run in parallel.
+
+### Fixed
+
+- `stackbone init` on a clean directory no longer errors with "Refusing
+  to overwrite agent.yaml". Every starter ships a placeholder manifest
+  that `writeStarterFiles` would write first, then
+  `writeAgentManifest` would refuse to overwrite. The new
+  `writeStarterProject` helper drops the placeholder, writes the rest
+  of the starter, and regenerates the manifest with the user-chosen
+  name; a flow-level test pins the contract so the two helpers cannot
+  re-diverge.
+
+## [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