@kadj-amoah/showrunner 1.1.2 → 1.1.4

package/CHANGELOG.md

@@ -2,6 +2,38 @@
 
 All notable changes to Showrunner are documented here. Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); the project tracks loose semver — minor bumps for new capability, patch for fixes.
 
+## [1.1.4] — 2026-05-24
+
+**Phase A of the interactive-setup overhaul.** `showrunner init` now walks you through configuration via a real terminal wizard instead of scaffolding placeholder files and expecting you to fill them in afterwards.
+
+### Added
+
+- **`showrunner init` is interactive by default** (when stdout is a TTY). The wizard:
+  1. Detects your environment — `claude` CLI on PATH, `ffmpeg`/`ffprobe`, chromium install, provider env vars already set — and surfaces what it found before any prompts fire.
+  2. Asks the right questions in order: project name → resolution preset → LLM provider (defaults to `agent_bridge` if `claude` is detected) → API key paste-in (masked) → TTS provider → API key paste-in → target URL.
+  3. **Probes the target URL** with a 4s HEAD request. If your dev server is up, it prints `reachable (HTTP 200, …ms)`; if not, it tells you to run `showrunner set-target` later (subcommand coming in v1.1.5) instead of failing.
+  4. Writes a real `.env` (not just `.env.example`) populated with the keys you pasted. `.env.example` still ships for reference / version-controlled documentation.
+- **`--yes` flag for non-interactive use.** `showrunner init --yes` skips the wizard and uses defaults / passed `--name`/`--url`/`--llm-provider`/`--tts-provider`/`--resolution` flags. CI-friendly. When `stdout` isn't a TTY (e.g. piped output) Showrunner forces this mode regardless.
+- **`@clack/prompts` dependency** for the wizard UI — small, ESM-first, no postinstall, no postinstall network hops.
+
+### Changed
+
+- **`init` footer now adapts to what the wizard already did.** When the wizard wrote your keys into `.env`, the footer skips the "edit .env" step entirely and confirms ".env is already populated". When only some keys were provided (you skipped a prompt), the footer lists just the missing ones with their dashboard URLs.
+
+### Coming next
+
+- **v1.1.5 (Phase B):** standalone `showrunner set-target` subcommand for re-pointing at a new URL after you start your dev server, plus port-scanning common dev-server ports during init to suggest the right URL automatically.
+- **v1.2.0 (Phase C):** if you've picked `agent_bridge` and have `claude` on PATH, the wizard can offer to read your project, infer your dev-server command + URL, and optionally spawn the server for you.
+
+## [1.1.3] — 2026-05-24
+
+UX polish on the post-install discovery path, prompted by author feedback during the CachyOS install smoke-test of v1.1.2 ("the entire welcome wagon needs to be worked on"). No functional change — pure copy + structure.
+
+### Changed
+
+- **Bare-command welcome rewritten to one-thing-at-a-time.** Each state (chromium missing, no project here, project here) now shows a single next command and a one-line description, instead of a 15-line wall that duplicated `init`'s footer and crammed multiple ideas per line. The outside-project branch now just points at `showrunner init` and defers all sequencing to `init`'s own output.
+- **`init` next-steps footer tightened.** The previous `cp .env.example .env       # then paste in: KEY_A, KEY_B` line conflated three things (file op, key list, no-keys alternative). Now split: step 2 is the `cp`, step 3 lists each required env var on its own line alongside the dashboard URL it's issued from, with the `agent_bridge` alternative as a single parenthetical at the end. Each step is exactly one observable action.
+
 ## [1.1.2] — 2026-05-24
 
 Hot-fix for a regression discovered while smoke-testing the v1.1.1 install on CachyOS.