@troylar/flightdeck 2.1.1 → 2.2.1

package/CHANGELOG.md

@@ -2,6 +2,32 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.2.1 · Oct 24, 2026
+
+Write a checklist fast, practice it, stage it.
+
+### New
+
+- **Enter in Add a step adds it and keeps the box open for the next one** (Editing). Type a step, press Enter, type the next. The box stays open after the step it added, with the type kept; Enter on an empty box closes it, and Escape closes it too. Add step still adds the step and opens it. *Where:* The builder, Add a step
+
+### Improved
+
+- **A blank new process opens ready to type its steps, with Practice beside it** (Editing). The first phase starts empty. In the builder its Add a step box is open, and on a wide screen Practice opens beside it so you can try steps as you add them. Run detail and role names with spaces become dashes (server name is server-name), and a name that still can't be used is refused beside its box. *Where:* Processes, New process
+- **Stage it for a test run, from the end of Practice** (Editing). When you get through the whole checklist, write what changed (First version, for a new process) and stage it right there; its page opens with Start a test run ready. If you've carried on practicing meanwhile, practice stays as it is. *Where:* The draft editor, Practice
+
+### Fixed
+
+- **Adding a run detail or role with Enter no longer says it's already there** (Editing). It's added once, and Added stays on screen. *Where:* The builder, Checklist details
+
+## 2.2.0 · Oct 24, 2026
+
+Practice a draft while you edit it.
+
+### New
+
+- **Practice: run the draft on screen while you edit it, recording nothing** (Editing). Practice in the draft editor runs what's on screen: check steps, pass gates, try sample details, and keep editing. A step you change says Try it again; a gate whose steps changed asks for a pass again; the rest keeps your place. It has its own Undo, and offers Stage it for a test run at the end. It stays in this browser tab, is never written to the team folder, and never counts as a run. *Where:* The draft editor, Practice
+- **Practice evidence, Fill in, values steps set, and Run from here** (Editing). Checking a step that asks for evidence opens its boxes under the step, checked as a run checks them, or Check without it. Fill in works as in a run. A value a step sets flows to the steps after it, and they ask again if that step does. Run from here starts partway: the steps before it are assumed, and it asks for the sample details it needs. *Where:* The draft editor, Practice
+
 ## 2.1.1 · Oct 23, 2026
 
 A planned run starts exactly once.

package/README.md

@@ -570,7 +570,7 @@ A process is one page, with its checklist in the middle.
 | **See its shape** | **Flight plan**: phases as waypoints, gates as checkpoints, tracks as parallel lanes, linked processes as connecting flights. From that version's runs and skills it adds typical times, autopilot (steps skills cover) and turbulence (steps that go off-script most). Each phase's steps open under it, or all at once with **Show all steps** and **Hide all steps**. Choose a phase to jump to it. |
 | **Edit it** | **Edit** opens the draft on a page of its own, with the **Builder** or the **Markdown** beside a live check (what blocks publishing, and what's just a tip) and a preview. |
 | **Look back** | The Versions panel shows the newest, with every version under **All versions**. An older version shows a way back to the current one and **Restore as draft**. |
-| **Try it first** | Under **All versions**, **Stage the draft for testing**, then **Start a test run** on the staged line. Real runs stay on the current default until someone chooses **Make v3 the default**. See [Staging and test runs](#staging-and-test-runs). |
+| **Try it first** | **Practice** in the editor runs the draft as you edit it, recording nothing. Then, under **All versions**, **Stage the draft for testing**, then **Start a test run** on the staged line. Real runs stay on the current default until someone chooses **Make v3 the default**. See [Staging and test runs](#staging-and-test-runs). |
 | **See how runs go** | **How runs go**: typical time per phase, the steps that go off-script most, and who has held each role. |
 | **Plan ahead** | **Plan a run**, next to **Start a run**: a name, the details you know, who does what and an optional time. |
 
@@ -597,7 +597,11 @@ A process is one page, with its checklist in the middle.
 
 </details>
 
-**New process** on the Processes page asks for a title; the file name is made from it and shown before you create it. The group, tags, run details, roles, owner and file name are under **More options**. Start blank, from Code check-in or Weekly review (publish v1 as it is, or open it in the editor), or copy a prompt for your AI assistant.
+**New process** on the Processes page asks for a title; the file name is made from it and shown before you create it. The group, tags, run details, roles, owner and file name are under **More options**. A blank one opens with its **Add a step** box ready (type a step, press Enter, type the next) and Practice beside it; run detail and role names with spaces become dashes. Start blank, from Code check-in or Weekly review (publish v1 as it is, or open it in the editor), or copy a prompt for your AI assistant.
+
+### Practice while you edit
+
+**Practice** in the draft editor runs what's on screen without recording anything: check steps, pass gates, give run details sample values, and keep editing as you go. A step you change shows **Try it again**; a gate whose steps or details changed asks to be passed again. Evidence opens under the step as it would in a run (or **Check without it**), **Fill in** works as in a run, a step's `sets:` value flows to the steps after it, and **Run from here** starts partway, assuming the steps before it and asking for the sample details it needs. It's kept in this browser tab only, never written to the team folder, and never counted as a run. Links and commands you follow still act on real systems. When you get through the whole checklist, write what changed and **Stage it for a test run** right there. See docs/design.md, section 34.
 
 ### Staging and test runs