@troylar/flightdeck 2.0.0 → 2.1.0

package/CHANGELOG.md

@@ -2,6 +2,41 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 2.1.0 · Oct 22, 2026
+
+Steps and phases that only some runs need.
+
+### New
+
+- **Only when: steps and phases that only some runs need** (Checklists). Put "only when ^risk is high" under a step, or right under a phase heading, and it applies only to runs whose details match. Everything else shows as Not needed with the reason, folded away, and a phase that isn't needed is skipped with its gate. A checklist without "only when" works as before. *Where:* Checklist format, Only when; the run screen and the receipt
+- **Only when in the builder, and everywhere a checklist shows** (Builder). In the builder, a step's or phase's Only when edits its conditions, one a line. The process page and flight plan show each as one muted line, search finds them, Insights leaves out runs that didn't need a step, the evidence page says Not needed and why, and Ready for a skill? names conditional steps no clean run has needed yet. *Where:* Checklist format, Only when; the builder, the process page, Insights and Export evidence
+- **Stage a version before it becomes the default** (Checklists). On a process page, open All versions and choose Stage the draft for testing. Runs keep using the current default until someone chooses Make vN the default, which publishes exactly what was staged as the next version. A stage can be retired and reopened. Anyone can do these, and each is logged with their name. *Where:* The process page, All versions
+- **Test runs on a staged version** (Runs). Choose Start a test run on a staged version's line. A test run is labeled Test run everywhere it shows, and it isn't counted with real runs: How runs go says how many it left out, and Home skips them. Its follow-ups and corrections are real. Until they update to 2.1, older copies show it by name only, count it in Home's running number and list its stage as a version in How runs go. *Where:* The process page, All versions; Runs
+- **Test runs and a sign-off on a staged version count once it's the default** (Skills). Once a staged version has test runs, its line says how many are clean, and with enough its owner can sign it off there. When it's made the default with exactly what was staged, Ready for a skill counts those clean test runs and that sign-off for it, and says they were from while it was staged. Nothing from a test run counts for any other version. *Where:* The process page, All versions; Ready for a skill?
+
+### Improved
+
+- **A checklist with only when needs Flightdeck 2.1** (Updating). A version that uses only when needs Flightdeck 2.1 on every computer that runs it. The publish panel says so before you publish, and 2.0 names the version and says it needs 2.1. *Where:* Updating Flightdeck, Using conditions
+
+### Fixed
+
+- **A sign-off still syncing is named, never taken as missing** (Skills). A sign-off file that can't be read yet is named in Folder health. Until it reads, Ready for a skill? and a staged version's line say they can't tell, and Sign off isn't offered; if it stays that way, restore or delete it. One from a newer Flightdeck says to update. Other JSON in validations/ is named as ignored.
+- **A plan whose decision can't be read isn't started again** (Plans). When a decision on a planned run can't be read yet, Folder health names it and the plan can't be started, declined or switched until it reads. One made with a newer Flightdeck says to update; one this copy can't read says to fix or delete the file.
+- **A plan is started, declined or switched only after its files are read again** (Plans). Right before Start, Decline or Switch writes anything, Flightdeck reads the plan's files in proposals/ again: every copy of the plan and every decision on it. If one can't be read, the copies differ, the plan changed since you opened it, or it was already started or declined, nothing is written and the message says why. A Decline clicked while a Start is still saving waits for it. *Where:* A plan's start form
+- **A save never writes over a run that changed elsewhere** (Runs). Saving a run, people.json or a step type compares the whole file with what was read, so a change made elsewhere is always kept: as a conflict copy for a run, or shown to you for the others.
+- **A test run that's gone stops counting as soon as a stage sign-off finds it** (Skills). When Sign off staged vN finds one of its test runs gone, the stage's line stops counting it at once, even if a refresh started while the sign-off waited.
+- **A copied test run is labeled in an evidence pack** (Evidence). A test run's file found in another run's folder is labeled Test run in an evidence pack, with its staged version.
+
+## 2.0.1 · Oct 22, 2026
+
+Each run counts once, and a sign-off or correction counts only from the exact person who made it.
+
+### Fixed
+
+- **A copy of a run in another run folder no longer counts twice** (Runs). A run.json counts only in its own folder (runs/<process>/<run ID>/). A copy anywhere else is listed with the files that can't be read, with where it belongs, and is never counted or opened. Nothing is removed: move or delete the copy yourself. *Where:* Folder health and Refresh list the copy. Evidence packs include such a folder as it is and say so
+- **Sign-offs count only from the owner's exact ID** (Skills). The ID on a sign-off, and the process and version it names, are compared exactly. The same goes for who wrote a correction, so only its author can withdraw or revise it. A run that names someone by an ID over 80 characters opens read-only. *Where:* A process page, Ready for a skill?
+- **Only runs read now count toward a sign-off** (Skills). Such a run stays on screen, with any change you haven't saved, but isn't counted toward a sign-off until its file reads again. *Where:* A process page, Ready for a skill?, and Home
+
 ## 2.0.0 · Oct 21, 2026
 
 Typed values, exact versions and reports from tools, in a lighter Flightdeck. Move every computer to 1.21 or later first.