@troylar/flightdeck 1.15.0 → 1.16.1

package/CHANGELOG.md

@@ -2,6 +2,53 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 1.16.1 · Oct 19, 2026
+
+Make the editors' side panels wider or narrower.
+
+### Improved
+
+- **Resize the Run preview** (Step types). Drag the line between the form and the preview to make the preview wider or narrower. Or focus the line and use the Left and Right arrow keys (Shift moves further), Home and End. Enter or a double-click puts it back. The form always keeps room. Your width is kept in this browser only. *Where:* Step types › a step type, the line left of Run preview
+- **Resize the parts and the inspector** (Draft editor). The Parts list and the inspector each have a line you can drag or move with the arrow keys, the same way as the step-type preview, and each keeps its own width. The Markdown view uses the inspector's width too. When the parts are folded to icons, only the inspector resizes. *Where:* A process page › Edit, the lines beside Parts and the inspector
+
+### Fixed
+
+- **The step-type form has its room again** (Step types). The form takes most of the page and the preview is a narrower column beside it, as intended. *Where:* Step types › a step type
+- **Dialogs fit the window** (Keyboard). Dialogs stay inside the window and scroll when their content is longer. *Where:* Keyboard shortcuts, and History
+- **Opens in a browser that blocks site storage** (Examples). The examples open, and a short dialog explains once that they and your changes to them last only while the tab is open. After that, a Tab only badge at the top of the window stays in view on every screen, dialog and phone step panel. The run's save status and the editors' labels say Saved in this tab only. A team folder still keeps everything. *Where:* Opening Flightdeck
+
+## 1.16.0 · Oct 19, 2026
+
+Apply a correction to the draft, then see which version has it.
+
+### New
+
+- **Review and apply** (Corrections). Review and apply shows what the run's version said, the draft now and the result side by side, then makes the change in the draft and saves it. Only that step changes. If the step changed since the run, you edit or confirm the result first. If the draft already has it, Link this correction records that. A screenshot or a described problem opens the editor at that step instead. *Where:* A process page › Corrections › Review and apply
+- **Choose between two proposals, or combine them** (Corrections). When people suggested different wording for one step, use one of them, or combine them into your own wording. Combining marks each of them as applied. *Where:* Review and apply, on a step with two proposed changes
+- **Undo an applied correction** (Corrections). Applying is one change in the draft editor's history, named for the step, so Undo takes it back. The draft then has unsaved changes until you save it. *Where:* The Undo button in the message, or the draft editor's Undo and History
+- **Changed since applied** (Corrections). A correction applied in Flightdeck remembers what the step said. If the step changes again in the draft, the correction says Changed since applied. *Where:* A process page › Corrections › All
+- **Published in vN** (Corrections). Publishing records which applied corrections the new version includes. A correction then says Published in v5, but only when v5 both lists it and really says it; a later version with other edits never counts. The publish panel says how many corrections the version includes and names any that changed since they were applied. *Where:* A process page › Draft › Publish, and Corrections › All
+- **Changed in vN, and why** (Corrections). In runs of the version that first has a correction, its step says Changed in v5. Why is this here? shows what it said before and after, the reason, the runs that suggested it and who applied it. *Where:* A run › the step's row and the selected step
+- **Hear back about your corrections** (Home). When a correction you suggested is published, Home says so once per version, with View change. When someone declines one, Home says who and why. Dismiss hides it in this browser. *Where:* Home › Your corrections
+- **Say what became of a follow-up** (Follow-ups). Mark a follow-up Done (with a link or note), Moved to a ticket, Moved to another run or plan, or Won't do (with a reason), and Reopen it if that changes. Anyone on the team can. Two people deciding at once shows as Needs review. *Where:* A run › Follow-ups, Home › Your follow-ups, and Runs › Follow-ups
+- **Every follow-up in one list** (Runs). See open follow-ups across all runs, oldest first, with who owns each, how long it's been open and its run. Switch to Yours or All. *Where:* Runs › Follow-ups
+- **Follow-ups open for more than 30 days** (Folder health). Folder health lists follow-ups that have been open for more than 30 days as worth a look, with Review follow-ups. *Where:* Settings › Folder health
+- **Saved history** (Draft editor). History has a This session | Saved history switch. Saved history lists every save of the draft kept in the team folder, from every computer, newest first: who saved it, how (saved, restored from a version, applied a correction), what changed, and where each version was published. A change made outside Flightdeck, by hand or by an AI assistant, is marked where it happened. *Where:* The draft editor › History › Saved history
+- **Reverse a saved change** (Draft editor). Reverse this change takes one saved change back out of the draft, if the lines it added are still there exactly. The draft then has unsaved changes, and Undo takes the reversal back. If the text changed since, Compare shows the change so you can edit it yourself. *Where:* The draft editor › History › Saved history
+- **Saved history of a step type** (Step types). A step type's History has Saved history too, with each save's changes field by field. A field's History shows only its own. *Where:* Step types › a type › History
+
+### Improved
+
+- **Steps with open corrections are marked while you edit** (Draft editor). The builder's rows say how many open corrections a step has. The Markdown view lists them above the text, with Go to line for each. *Where:* A process page › Edit
+- **Say which version has an older correction** (Corrections). For a correction applied before 1.16, Flightdeck says it can't confirm which version has it. It's in v5 records that, and Flightdeck still checks that v5 makes the change. *Where:* A process page › Corrections › All
+- **The correction brief quotes what the step said and what was proposed** (Corrections). The brief for your AI assistant quotes From and Proposed as data, lists attached files' paths, and leaves out corrections already published. *Where:* A process page › Corrections › Copy correction brief
+- **Your open follow-ups stay until they're dealt with** (Home). Home lists the open follow-ups you own, however old. Once one is done, moved or won't be done, it drops off. *Where:* Home › Your follow-ups
+- **Follow-ups show where they stand** (Receipt). The receipt and the finish page show each follow-up's status, and the text you copy for Jira says what became of it. *Where:* A run › Receipt
+
+### Fixed
+
+- **The example release watches new pods for 20 minutes everywhere** (Examples). The example step's expected result and timing say 20 minutes, and the correction its runs suggest puts the same 20 minutes in its wording. *Where:* The examples › Production release
+
 ## 1.15.0 · Oct 18, 2026
 
 Team confidence: Folder health, a connection check between computers, and safer updates and backups.

package/README.md

@@ -173,7 +173,7 @@ The **Builder** edits a draft as an outline: drag a step or press Alt+Up / Alt+D
 </td>
 <td valign="top">
 
-**Corrections** on the process page, grouped by step: the same correction from several runs shows once, "Suggested in 3 runs". Mark one as applied, decline it with a reason, or reopen it, and copy a correction brief for your AI assistant.
+**Corrections** on the process page, grouped by step: the same correction from several runs shows once, "Suggested in 3 runs". **Review and apply** compares what the run's version said, the draft now and the result side by side, then applies it to the draft in one click as one change you can undo; if the draft already has it, **Link this correction**. Mark one as applied, decline it with a reason, or reopen it, and copy a correction brief for your AI assistant. The draft editor marks the steps with open corrections. Publishing records which applied corrections the version includes, so a correction says **Published in v5** once v5 both lists it and says it; runs of v5 show **Changed in v5** on that step, with **Why is this here?**, and Home tells whoever suggested it.
 
 <a href="https://github.com/troylar/flightdeck/blob/main/docs/images/corrections-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/corrections-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/corrections-light.png" alt="Corrections on the process page: a wording change suggested in two runs, with the runs listed, and a missing step, each with Mark as applied and Decline, then Copy correction brief"></picture></a>
 
@@ -245,7 +245,7 @@ A step can **set** a run detail: the merge step records the release tag, and eve
 <td valign="top">
 
 ### Runs that teach the checklist
-Every block, every re-check and every step **done differently** (with what happened) is kept. Anyone in a run can **correct a step**: what the checklist said, what it should say, and files to show why. Corrections are part of the run's record and its receipt, and wait on the process page, where anyone marks them applied or declines them with a reason; one click copies a correction brief for your AI assistant. A process's **How runs go** shows typical time per phase, the steps that go off-script most, and who has never held which role yet, so the next rotation is obvious.
+Every block, every re-check and every step **done differently** (with what happened) is kept. Anyone in a run can **correct a step**: what the checklist said, what it should say, and files to show why. Corrections are part of the run's record and its receipt, and wait on the process page, where anyone applies them to the draft (after a side-by-side comparison), marks them applied or declines them with a reason; one click copies a correction brief for your AI assistant. Once published, a correction says which version has it, and that version's runs say why the step changed. A process's **How runs go** shows typical time per phase, the steps that go off-script most, and who has never held which role yet, so the next rotation is obvious.
 
 </td>
 </tr>
@@ -421,6 +421,7 @@ runs/                  one folder per run: run.json, everyone's notes and correc
 skills/                skill registrations: each skill's source, what it implements
 validations/           owners' sign-offs that a version is ready for a skill
 corrections/           decisions on corrections (applied, declined, reopened, withdrawn), each a file written once
+followups/             what became of each follow-up (done, moved, won't do, reopened), each a file written once
 suggestions/           decisions on suggested fixes from before 1.13 (still read)
 step-types/            your team's own step types (create them in the app)
 jira/workflows.json    your real Jira workflows, with required fields