@troylar/flightdeck 2.5.0 → 2.6.1

package/CHANGELOG.md

@@ -2,6 +2,32 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 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.
+
+### Improved
+
+- **Every box asks a question, with an example and why it matters** (Editor). Each box in the step form asks what to put there ("Which job?", "What do you run?"), shows an example in gray and says what it's used for and what happens when it's left empty. Phases, gates, lanes, checklist details, screenshots and Questions ask too. *Where:* Editing a checklist, the step form and the other forms
+- **Only the boxes a step usually needs are shown; the rest are one click away** (Editor). A step shows the boxes its type usually needs and any that hold a value. The others wait behind "+ add" buttons, and the fields every step accepts (a link, how long it takes, a deadline, proof, a time) are under More about this step. A value the step doesn't use, such as another action's field, is kept and says why. *Where:* The step form
+- **Short choices are buttons, and the step says what checking it will ask for** (Editor). A choice of five or fewer (an action, Ask for proof, how a phase is worked) is a row of buttons you can also move through with the arrow keys. What must be recorded offers only names the step can record, and When it's checked, they record lists exactly what the run will ask for. *Where:* The step form and the phase form
+- **One Pull request step, with GitHub or Bitbucket as its first question** (Editor). The parts box and the type picker have one Pull request. Its first question is Where is the pull request?, GitHub or Bitbucket; switching keeps every value and points out what the other one doesn't use. A new one uses the host the checklist already uses most. *Where:* The parts box, the type picker and the step form
+- **Fill in and the record form ask the same questions** (Runs). Filling in a step or recording what you did asks the box's question, shows an example and says why under the box. The step's What to do now names every kind of proof: a link, a note, a number, a yes or no, or a date. *Where:* The run screen and practice
+
 ## 2.5.0 · Oct 25, 2026
 
 Big folders.