@troylar/flightdeck 1.12.0 → 1.13.0

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 1.13.0 · Oct 18, 2026
+
+Runs get a workspace of their own, corrections replace Suggest a fix, and notes take files.
+
+### New
+
+- **Next up, and one place to answer a step** (Runs). Next up, pinned atop the checklist, points at where the run stands (the next step, a blocked step, a gate to review), never at what you're looking at. The selected step shows how to do it, values to copy, evidence to record, Done, Blocked, N/A and notes. Done reads what you typed in its evidence boxes. Check the step Next up points at and the next one is selected, so Space keeps going. *Where:* A run: the checklist and the selected step.
+- **Suggest a fix became Corrections** (Runs). Correct this step starts on the wording, with a Before/After redline as you type; Change something else covers a missing step, the order, who does it, a screenshot or removing it. It never answers the step. Runs and receipts list their Corrections; on the process page the same one from several runs shows once, and anyone marks it applied or declines it with a reason. *Where:* A run: Correct this step on the selected step (or press C). A process page: Corrections.
+- **Done differently** (Runs). Beside Done, the recorder can mark a step Done differently: say what happened, then choose Just this run or Fix the checklist too, which adds a correction. It follows every rule of Done, so required evidence still has to be there. *Where:* A run: the selected step.
+- **Attach files to notes and corrections** (Runs). Drop files on the note box, paste them, or choose Attach: images (PNG, JPEG, WebP, GIF), PDF, text and logs (.txt, .log, .md, .csv, .json, .yaml) and .zip, up to 10 MB each and several per note. Images show as pictures; text opens as plain text; other files save a copy. A file that isn't allowed is refused next to the box with the reason. *Where:* A run: the selected step's notes, or Correct this step.
+
+### Improved
+
+- **A run fills the window** (Runs). A run is a page of its own: a slim header with 7/14 answered, a strip saying who's recording with Pause, Hand off, Pick up or Take over beside it, then three panes that each scroll on their own: Phases, the checklist and the selected step. The strip also says what this window saved and when it checked the folder; a failed save or a conflict shows there with Try again or Compare copies. *Where:* Runs: open any run.
+- **What you type stays with its step** (Runs). Evidence typed into a step, an open Fill in and an unsent note stay with that step while you move around the run, and come back when you return; the row says Draft. Drafts belong to their team folder. Checking a step (row, Done, Space or Done differently) uses what was typed on that step only. While its Fill in is open or unsaved, Done waits and says "Save or cancel Fill in first." *Where:* A run.
+- **Keyboard, phones and screen share** (Runs). J and K open a folded phase they move into, X works like Space, and a held key checks one step. On a phone a step opens as a full-screen sheet with Close, Previous and Next. Screen share shows who's recording, a pause, and why a step is blocked; Back to the run returns to the same step and scroll. *Where:* A run. Press ? for the keys.
+- **Plain words for your AI assistant** (Skills). Flightdeck now says "your AI assistant" everywhere: copy the brief for your AI assistant, and it builds or updates the skill. *Where:* Skills, and a process page: Skills.
+
+### Fixed
+
+- **Attachments with runs of dots in their names** (Runs). A file named like deploy..output.log is saved as deploy.output.log and stays listed with its note after a reload. *Where:* A run: attachments on notes and corrections.
+
 ## 1.12.0 · Oct 18, 2026
 
 Build a checklist from parts, with Undo, Redo and History in every editor and a clearer step-type editor.
@@ -72,7 +94,7 @@ Clear sections, and templates and step types you manage in the app.
 
 ### Fixed
 
-- **The right words after copying a brief** (Skills). Copying a skill brief says to paste it to your LLM, and gate approvals in the checklist preview show as formatted text.
+- **The right words after copying a brief** (Skills). Copying a skill brief says to paste it to your AI assistant, and gate approvals in the checklist preview show as formatted text.
 
 ## 1.9.1 · Oct 18, 2026
 
@@ -90,8 +112,8 @@ Process-to-skill traceability, values that flow through a run, and a hierarchy f
 
 - **Install with npm** (Install). npm install -g @troylar/flightdeck, then flightdeck open to try it, flightdeck install <team folder> to put the app there, and flightdeck skills <team folder> to add the skills for your AI assistant. No dependencies, nothing runs on install, no network. *Where:* A terminal.
 - **See which skills implement each process** (Skills). Each process page lists the skills built from it: where each lives (any repo or folder), its own version, the process version it follows, and the steps it covers or the whole process. The map marks covered steps. *Where:* Skills, on a process page; Home → Skills.
-- **Know when a process change affects a skill** (Skills). When a new version changes the steps a skill covers, the skill shows as needing an update, with the exact before and after; if its steps didn't change, it only needs its version noted. Copy the update brief for your LLM. *Where:* Copy update brief, on a skill.
-- **Prove a version, then turn it into a skill** (Skills). Each version shows its run evidence: completed runs, clean ones, and what people did differently. With 3 clean runs the owner signs it off, and Flightdeck writes the brief an LLM needs to build the skill. The flightdeck-skill-brief skill does the same from the folder, with your AI assistant. *Where:* Ready for a skill?, on a process page.
+- **Know when a process change affects a skill** (Skills). When a new version changes the steps a skill covers, the skill shows as needing an update, with the exact before and after; if its steps didn't change, it only needs its version noted. Copy the update brief for your AI assistant. *Where:* Copy update brief, on a skill.
+- **Prove a version, then turn it into a skill** (Skills). Each version shows its run evidence: completed runs, clean ones, and what people did differently. With 3 clean runs the owner signs it off, and Flightdeck writes the brief an AI assistant needs to build the skill. The flightdeck-skill-brief skill does the same from the folder, with your AI assistant. *Where:* Ready for a skill?, on a process page.
 - **Organize processes and skills in a hierarchy, with tags** (Library). Maps and skills say group: (like Engineering / Releases) and tags:. Home shows processes and skills as foldable trees, filtered by tag. *Where:* Home → Processes and Skills.
 - **Let a step set a run detail** (Checklists). A step can say sets: tag. Checking it asks for the tag and saves it as a run detail, so every later ^tag (commands, messages, Jira fields) uses it. The start form leaves it out and says which step fills it in. Correcting it later sends the steps that used the old value back for a re-check. *Where:* sets: in a map; the example release's merge step sets the release tag.
 

package/README.md

@@ -20,7 +20,7 @@ Every team has processes that live in someone's head: the release, the check-in,
 
 It's **one HTML file**. No server, no sign-in, no network, no AI inside. It works offline in Edge or Chrome and keeps everything in a folder your team already shares.
 
-<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: run details including a release tag set by an earlier step, roles, phases on the left with their gates, the current phase, and step notes on the right" width="1000"></picture></a></p>
+<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 full-page run screen: a slim header with 7/14 answered, 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 with what to do, its timing, Record the result, Done, Done differently and Blocked" width="1000"></picture></a></p>
 
 <br>
 
@@ -88,9 +88,9 @@ Then open `flightdeck.html` from the team folder, go to **Settings → Open team
 <tr>
 <td valign="top">
 
-**A process** is one page: its checklist with skill badges, whether it's ready for a skill, its skills, versions and recent runs.
+**A process** is one page: its checklist with skill badges, the Corrections people recorded during runs, whether it's ready for a skill, its skills, versions and recent runs.
 
-<a href="https://github.com/troylar/flightdeck/blob/main/docs/images/process-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/process-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/process-light.png" alt="The Production release process: the v2 checklist, Ready for a skill, two skills marked needs update, versions and recent runs"></picture></a>
+<a href="https://github.com/troylar/flightdeck/blob/main/docs/images/process-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/process-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/process-light.png" alt="The Production release process: the v2 checklist with skill badges, How runs go, Start a run and Plan a run, and its Corrections panel with two open corrections"></picture></a>
 
 </td>
 <td valign="top">
@@ -152,21 +152,23 @@ The **Builder** edits a draft as an outline: drag a step or press Alt+Up / Alt+D
 <tr>
 <td valign="top">
 
-**Suggest a fix** from any step or phase during a run: what's wrong, and what it should say.
+**Correct this step** during a run: it starts on the wording, with a live Before/After redline, and **Change something else** covers a missing step, the order, who does it, a screenshot, removing the step, or any other problem. The checklist's own text stays on screen.
 
-<a href="https://github.com/troylar/flightdeck/blob/main/docs/images/fix-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/fix-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/fix-light.png" alt="Suggest a fix to a step during a run: the instructions are wrong, with the text it should say"></picture></a>
+<a href="https://github.com/troylar/flightdeck/blob/main/docs/images/correction-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/correction-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/correction-light.png" alt="Correct this step during a run: the checklist's text, the suggested wording, a Before/After redline, why, and Attach for files"></picture></a>
 
 </td>
 <td valign="top">
 
-**Suggested fixes** on the process page: accept or decline each one, see which are fixed in a newer version, and copy a fix 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". Mark one as applied, decline it with a reason, or reopen it, and copy a correction brief for your AI assistant.
 
-<a href="https://github.com/troylar/flightdeck/blob/main/docs/images/fixes-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/fixes-dark.png"><img src="https://raw.githubusercontent.com/troylar/flightdeck/main/docs/images/fixes-light.png" alt="Suggested fixes on the process page: one declined with a reason, one fixed in v2, one open with Accept into the draft and Decline, one in the draft"></picture></a>
+<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>
 
 </td>
 </tr>
 </table>
 
+**A run** fills the window, like the editor. The header says how far it is (`7/14 answered`); a strip under it says who's recording, with **Pause** and **Hand off** (or **Pick up**, **Record here**, **Take over**) right beside it, and what this window saved and when it last checked the folder. Below, three panes scroll on their own: **Phases** with each gate's state, the **checklist** with **Next up** pinned at its top, and the **selected step**: how to do it, the values to copy, the evidence to record, **Done**, **Done differently** (say what happened, and fix the checklist too if it should change), **Blocked** and **N/A**, then the step's corrections and notes. Check the step Next up points at and the next one is selected, ready for **Space**. The row's check, **Done**, **Space** and **Done differently** all answer that one step with the evidence typed on it. Typed evidence, Fill in values and unsent notes stay with their step (and their team folder) when you move around, and the row says **Draft**; while a step's Fill in is open or unsaved, Done says "Save or cancel Fill in first." Notes and corrections take files: drop them on the note box, paste, or **Attach** (images, PDF, text and logs, CSV, JSON, YAML and .zip, up to 10 MB each). On a phone the checklist scrolls and a step opens as a full-screen sheet.
+
 <br>
 
 ## What it does
@@ -187,7 +189,7 @@ Every phase ends at a **gate**. Nothing after it opens until someone passes it,
 <td width="50%" valign="top">
 
 ### One recorder, everyone watching
-One person records; everyone else follows on their own screen and adds notes and screenshots to any step. Hand recording over, or pick it up from another window. Every save first checks the file hasn't changed; if it has, yours is kept next to it as a copy you can compare and keep. Where two computers can't take turns, a save that gets replaced is still kept as a receipt and shown as a copy, so nothing is silently lost.
+One person records; everyone else follows on their own screen and adds notes, screenshots and files (logs, PDFs, .zip) to any step. Hand recording over, or pick it up from another window. Every save first checks the file hasn't changed; if it has, yours is kept next to it as a copy you can compare and keep. Where two computers can't take turns, a save that gets replaced is still kept as a receipt and shown as a copy, so nothing is silently lost.
 
 </td>
 </tr>
@@ -229,7 +231,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 "did it differently", every block, every re-check is kept. Anyone in a run can **suggest a fix** to the checklist from a step, a phase or a screenshot; the team accepts or declines it on the process page, and one click copies a fix 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 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.
 
 </td>
 </tr>
@@ -392,10 +394,11 @@ The same rules are in the `flightdeck-skill-brief` skill for your AI assistant,
 people.json            who's on the team
 maps/drafts/           checklists being written (Markdown)
 publications/          published versions, frozen (Flightdeck writes these)
-runs/                  one folder per run: run.json, everyone's notes, screenshots
+runs/                  one folder per run: run.json, everyone's notes and corrections, attached files
 skills/                skill registrations: each skill's source, what it implements
 validations/           owners' sign-offs that a version is ready for a skill
-suggestions/           decisions on suggested fixes (accepted, declined, reopened), one file per person's window
+corrections/           decisions on corrections (applied, declined, reopened, withdrawn), 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
 proposals/             planned runs (from the app or your AI assistant), waiting for a person to start them
@@ -419,7 +422,7 @@ Every file has exactly one writer, which keeps ordinary use of a shared folder f
 | `/flightdeck-new-checklist` | Turns a runbook, notes or a conversation into a checklist |
 | `/flightdeck-edit-checklist` | Changes a checklist and keeps its step IDs |
 | `/flightdeck-review-checklist` | Checks a checklist for format errors and quality, without changing it |
-| `/flightdeck-learn-from-runs` | Turns what actually happened in runs into suggested checklist changes |
+| `/flightdeck-learn-from-runs` | Reads runs and their corrections and proposes checklist changes |
 | `/flightdeck-plan-run` | Plans the next run, rotating roles fairly |
 | `/flightdeck-status` | Summarizes the folder: what needs a person, what's running, what's stale |
 | `/flightdeck-new-step-type` | Creates or changes a team step type from a description |
@@ -488,6 +491,13 @@ Both. The app's editor and your AI assistant write the same draft files. The app
 
 </details>
 
+<details>
+<summary><b>The checklist was wrong during a run. What do I do?</b></summary>
+
+Select the step and choose **Correct this step** (or press C): change its wording with a live Before/After, or choose **Change something else** for a missing step, the order, who does it, a screenshot or removing it. Attach files to show why. It never answers the step. If you already did the step another way, use **Done differently** beside Done and choose **Fix the checklist too**. Corrections wait on the process page, grouped by step, where anyone marks one as applied to the draft or declines it with a reason. Then edit the draft and publish as usual.
+
+</details>
+
 <details>
 <summary><b>What if someone on the team has a newer Flightdeck?</b></summary>