@m-kopa/launchpad-cli 0.32.1 → 0.33.0

package/CHANGELOG.md

@@ -6,6 +6,55 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html);
 pre-1.0 minor bumps may carry breaking changes per ADR 0005.
 
+## 0.33.0 — 2026-06-17
+
+New verb: **`launchpad watch [<slug>]`** (and `launchpad status <slug> --watch`) —
+watch an app provision to live in real time (sp-wtch7q). Run it in a second
+terminal after a first `launchpad deploy` instead of re-running `launchpad status`
+by hand.
+
+- **Live phase pipeline.** The 15 provisioning stages are grouped into six phases
+  (Repo · Build · Infra · Certificate · Access · Verify) with a spinner on the
+  active phase, `stage N/15`, and **client-side** per-phase timers (the lifecycle
+  exposes only the current stage, so timings are measured from observed transitions
+  and omitted — never faked — for stages that completed before the watch attached).
+- **Graceful terminal frames.** On live, the app URL front and centre; on failure,
+  the failing stage + reason + the exact recovery command. `Ctrl-C` stops *watching*
+  only — provisioning continues.
+- **Capability-tiered, cross-platform.** A terminal probe selects the richest safe
+  renderer — inline live-redraw → ASCII-glyph fallback → append-only → plain — and
+  **degrades, never assumes** (Windows legacy code pages get ASCII, not garbage).
+  Piped / CI / non-TTY output is plain, escape-free text. The platform's **first
+  Windows CI matrix** (windows-latest × Git-Bash/PowerShell/cmd) runs the watcher's
+  degraded tiers.
+- **Safe by construction.** Every bot-supplied string is escape-sanitised before it
+  reaches the terminal (no terminal-escape injection). **Zero new runtime deps** —
+  the ANSI is hand-rolled, now guarded by an assertive zero-runtime-dep CI check.
+- A richer full-screen ("alt-screen") mode is planned as a later opt-in experimental
+  variant; this release ships the inline renderer.
+
+## 0.32.2 — 2026-06-17
+
+Docs: skill-accuracy sweep. Audited all bundled skills against the live
+CLI/bot/`platform-auth` source and corrected three stale claims:
+
+- **`launchpad-content-pr`** — the deploy section said `launchpad deploy` is
+  fire-and-forget and "always verify with `launchpad status`". Since sp-dplvfy,
+  a Model-A deploy **verifies the served content in-line by default** (waits for
+  the Pages build, byte-compares the entrypoint, exits non-zero on
+  failure/mismatch). Documented the default-verify behaviour and the
+  `--no-verify` / `--verify-timeout=<secs>` flags; `launchpad status` is now
+  framed as the fallback when verify is skipped or times out at `pending`.
+- **`launchpad-deploy-status` + `launchpad-status`** — the drift-report field
+  list named `access.allowed_entra_group` (singular); the path the CLI actually
+  emits in `driftFields` / the `drift:` line is `access.allowed_entra_groups`
+  (plural, `status.ts:478`). Corrected (3 occurrences).
+- **`launchpad-onboard`** — the sibling-skill list omitted `/launchpad-identity`
+  (added to the bundle in 0.32.1). Added it.
+
+Skill content only — no behaviour change. Re-run `launchpad update` (or
+`launchpad skills update`) to pick up the corrected skills.
+
 ## 0.32.1 — 2026-06-17
 
 Fix: `launchpad skills install/update` now installs `launchpad-identity`. The