@troylar/flightdeck 2.6.0 → 2.7.0

package/CHANGELOG.md

@@ -2,6 +2,35 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.7.0 · Oct 26, 2026
+
+Boxes that know your details.
+
+### New
+
+- **Type ^ to put a run detail in a step, a gate or a field** (Editor). Typing ^ in a step's text, a gate's approval or a text field lists the checklist's run details, with where each comes from; Enter or a click puts it in. Insert a detail does the same, and Add ^name as a run detail adds one you haven't listed yet. The detail stays where you typed it in the step's text. *Where:* Editing a draft, the step and gate forms
+- **A misspelled detail is marked, with a one-click fix** (Editor). Each ^detail in a box is marked: fine, not a run detail, or maybe not set yet at that step. A misspelled one offers Use ^environment, and one the run may reach before it's set names the step that sets it, with Show that step. *Where:* Editing a draft, under each box
+- **See a box filled in, the way a run will show it** (Editor). In a run: under a box shows it with the values from this checklist's latest run, exactly as the run screen will. *Where:* Editing a draft, under each box that holds a ^detail
+- **Rename a run detail everywhere at once** (Editor). Rename in Checklist details changes the detail in its list, step text, gate approvals, fields, only when and sets, as one Undo step. It says how often each detail is used, and refuses when another checklist receives the detail by that name. *Where:* Editing a draft, Checklist details
+
+### Fixed
+
+- **A caret that isn't a run detail stays as written** (Runs). A field like grep ^ERROR shows ^ERROR in a run, and Checks name it as a tip, with the detail it likely meant. *Where:* The run screen and Checks
+
+## 2.6.1 · Oct 25, 2026
+
+Documentation that matches the app.
+
+### Improved
+
+- **A shorter README with a quick start, and update notes through 2.6** (Docs). The README starts with what Flightdeck is and how to open it in a minute, and says each thing once. The update notes cover 2.3 to 2.6.1, the checklist format lists every field and rule, and the screenshots show the current app. *Where:* README.md and docs/ on GitHub
+
+### Fixed
+
+- **The instructions for AI assistants match what Flightdeck does today** (AI assistants). AGENTS.md and the skills cover practice, staging, test runs, conditions, typed details and proof, version pins and registering skills with the command. Their examples publish as written, and assistants leave staged versions and test runs alone. *Where:* AGENTS.md and the skills in a team folder; update with npx @troylar/flightdeck@2.6.1 install <folder>
+- **When something goes wrong: a working link, and the folder size limits** (Help). The guide's link to the update notes works again, and it lists the sizes Folder health watches: runs, attachments, path length, files in a run folder and what's read. *Where:* Settings, When something goes wrong
+- **The editor's top bar fits on a laptop screen** (Editor). Below 1,600 pixels wide the editing tools take their own row, which gives the checklist's name room and keeps Review & publish on one line. *Where:* Editing a draft
+
 ## 2.6.0 · Oct 25, 2026
 
 Boxes that explain themselves.