@troylar/flightdeck 2.12.2 → 2.14.0

package/CHANGELOG.md

@@ -2,6 +2,30 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.14.0 · Nov 3, 2026
+
+Your AI assistant saves step types through a checked command.
+
+### New
+
+- **flightdeck type list, type read and type save** (AI assistants). An assistant reads a step type with flightdeck type read and saves it with flightdeck type save --expect, which compares the exact bytes it read, refuses copies, checks the definition as Flightdeck does, reads the save back and records who asked in History. Like two Flightdeck windows in different browsers, two saves at the same instant can replace one another without either being told. *Where:* docs/apps.md › Writing step types
+
+### Improved
+
+- **The new-step-type skill uses the commands** (AI assistants). The skill uses type list, type read and type save, says what to do after each outcome, and gives the route in Flightdeck when the command can't save. AGENTS.md is unchanged. Update with flightdeck install or Settings; Team notes stay as they are. *Where:* Settings › AI assistant files
+
+## 2.13.0 · Nov 2, 2026
+
+Your AI assistant checks a draft exactly as Review & publish does.
+
+### New
+
+- **flightdeck draft check** (AI assistants). flightdeck draft check gives an assistant the verdict Review & publish gives a draft: what stops publishing, the tips, and what Publish would refuse, screenshots and version: pins included. It only reads. A part of the folder it couldn't read is named, and never becomes a finding. *Where:* docs/apps.md › draft check
+
+### Fixed
+
+- **An assistant's draft checks are complete** (AI assistants). draft read, save and propose load what Review & publish loads and give the same words. AGENTS.md and the review, new-checklist and edit-checklist skills say so and use draft check. Update with flightdeck install or Settings; Team notes stay as they are. *Where:* Settings › AI assistant files
+
 ## 2.12.2 · Nov 2, 2026
 
 AGENTS.md says what an assistant's draft checks really cover.

package/README.md

@@ -25,7 +25,7 @@
 ## Quick start
 
 1. `npx @troylar/flightdeck open` opens the app in your browser (needs Node 18 or later).
-2. No Node? Save [flightdeck.html](https://unpkg.com/@troylar/flightdeck@2.12.2/dist/flightdeck.html) from the npm package as a file (right-click, **Save link as…**) and open that file in Edge or Chrome.
+2. No Node? Save [flightdeck.html](https://unpkg.com/@troylar/flightdeck@2.14.0/dist/flightdeck.html) from the npm package as a file (right-click, **Save link as…**) and open that file in Edge or Chrome.
 3. Choose **Look around the examples** to try it, or **Start your team** to set up your team's folder.
 
 <p align="center"><a href="https://github.com/troylar/flightdeck/blob/main/docs/images/run-light.png" title="Open in GitHub's image viewer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/run-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/run-light.png" alt="A release in progress on the run screen: 7/15 answered in the header with Details, Screen share, Receipt and More; a strip saying you're recording, with Pause and Hand off and the run's details; Phases with each gate's state; the checklist with Next up pinned at its top; and the selected step, whose text shows the run's tag (Start the production deploy job v2026.10.16), with the values to copy, Record the result, Done, Done differently and Blocked" width="1000"></picture></a></p>