v0.2.0 — 2026-04-29

Added

• Three slash commands wrapping the flow lifecycle:
  • /initflow — one-time project bootstrap; discovers screens, grep-detects auth, scaffolds .maestro/{config.json, README.md, app-launch.yaml, login.yaml?} with project values substituted
  • /authorflow [flow-name] — phased loop (Discover → Interview → Walk-the-screens → Compose → Run once → Commit + index README); captures one screenshot + maestro hierarchy per step; one-run stability bar
  • /stabiliseflow <flow> [N] — runs an existing flow N times consecutively (default 3) to detect flakiness; diagnoses non-deterministic failures rather than blindly rerunning
• references/authoring-flows.md — process guide for the phased authoring loop (separate from writing-flows.md which remains the syntax reference)
• references/maestro-readme-template.md — fixed onboarding-doc template for <project>/.maestro/README.md
• <project>/.maestro/authoring-evidence/<flow>/ — gitignored directory for Phase C screenshots, persisted as future debugging evidence

Changed

• SKILL.md "Authoring flows" section rewritten to point at the three slash commands and the new authoring reference; the four-step ad-hoc pattern is removed in favour of the phased loop
• Token-efficient debug tiering documented in SKILL.md step 8 and references/troubleshooting.md: Tier 0 logs → Tier 1 maestro hierarchy → Tier 2 screenshot → Tier 3 video, in that order
• maestro studio repositioned as user-only (interactive browser inspector); Claude defaults to maestro hierarchy for selector inspection