@troylar/flightdeck 1.16.1 → 1.18.0

package/CHANGELOG.md

@@ -2,6 +2,43 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 1.18.0 · Oct 19, 2026
+
+Other apps can read checklists, runs, what's waiting and follow-ups as JSON.
+
+### New
+
+- **Read checklists and runs as JSON** (Command line). Scripts and other apps can read the team folder as a teammate would: flightdeck processes, process, runs, run, next and followups, with --json. They show checklists, runs, what's waiting and on whom, and follow-ups. They only read and never change the folder. Anything they couldn't read is named file by file, with exit code 4. People-directory email fields are omitted. *Where:* flightdeck run <team folder> <process>/<run id> --json, and docs/apps.md
+- **Copy a run's key** (Runs). Copy run key copies the key other apps use to read a run, like backup-check/k3m9p2q8. *Where:* A run's More menu
+
+### Improved
+
+- **See each phase's steps in the flight plan** (Flight plan). Each phase lists its steps: the type, the text, must-dos, who does it, the skill that covers it, lanes side by side, and the gate last. Choose a step to open it in the checklist. Show all steps or Hide all steps opens or closes every phase. Phases start open when the checklist has 40 steps or fewer. Your choice is kept for each process in this browser. *Where:* A process page, Flight plan
+
+## 1.17.0 · Oct 19, 2026
+
+Search everything with Ctrl+K, and big team folders open and refresh faster, show 50 runs at a time, and warn when refreshing is slow.
+
+### New
+
+- **Search everything with Ctrl+K** (Search). Press Ctrl+K (Cmd+K on a Mac), or / when single-key shortcuts are on. Find runs, steps, notes, corrections, follow-ups, step types, skills and pages, grouped by kind, with your words highlighted. Accents don't matter. Choose a result to go straight there; anything you were typing is kept. Results update as the folder changes, and a run that couldn't be read is found from its last copy and marked. *Where:* Search in the top bar, on every page
+- **Export a run's evidence** (Runs). Make an evidence pack of one run, or of a process's runs between two days: a zip with the original files, a page to read, and SHA-256 hashes to check them by. It says what it left out and why, and anything that changed while it was made. Save it, and keep its SHA-256 somewhere separate. The people directory is left out; the records may still name people. *Where:* A run's Receipt or its More menu, and Runs › Export evidence…
+- **flightdeck export** (Command line). flightdeck export makes the same evidence pack from the command line, for one run (--run) or for the runs started between two days (--process, --from, --through, in --tz). It never changes the team folder, prints the pack's SHA-256, and exits 0 for a complete pack, 4 for a partial one and 1 when it made none. *Where:* flightdeck export <team folder> --run <process>/<run id>
+- **Filter runs** (Runs). Narrow the Runs page by process, version, outcome and the dates runs started. Each filter shows as a chip you can remove. *Where:* Runs › Filter runs
+- **Says when refreshing is slow on this computer** (Folder health). When the last 3 refreshes each took more than 15 seconds, Folder health says how long refreshing takes here, with what to do about a big folder. *Where:* Settings › Folder health
+
+### Improved
+
+- **How runs go counts runs, one version at a time, and says what it left out** (Insights). Each number belongs to one version, counts runs, and says how many runs it's out of and which it couldn't count, and why. Unreadable or future times and reopened gates are left out of times. Choose a number to see its runs. Known limit: a time that can't be read is dropped when any copy saves the run, as before, so it's left out only until then. *Where:* A process › How runs go, and the flight plan
+- **Runs load 50 at a time** (Runs). Running and Finished each show 50 runs and say how many there are. Show 50 more adds the next ones and moves you to the first one added. *Where:* Runs
+- **Big team folders open faster, and show runs as they're read** (Team folder). Reading a file now gives its size too, so opening a big folder asks OneDrive about half as many things. Runs appear as they're read, and Home and Runs say "Still reading runs (640 of 2,000)" until it's done. A run not read yet is never shown as gone. Pictures are read when they scroll into view, a few at a time, after the run you're recording. *Where:* Opening a team folder, Home, Runs, and any page with pictures
+- **Refreshing a big team folder asks for much less** (Team folder). Running runs and runs that ended in the last week are checked on every refresh. Older runs are checked a share at a time, each one at least every 10 minutes, so a refresh asks OneDrive about 80% fewer things. A late note on an old run can take up to 10 minutes to show. Refresh in the top bar still reads everything at once. *Where:* Every team folder, while Flightdeck is open
+- **An edit that keeps a file's size and time still shows up** (Team folder). Every finished run is read in full at least once an hour, and every running run you don't have open at least every 5 minutes, whatever its size and time say. Decisions on corrections and follow-ups are read again at least once an hour too. *Where:* Every team folder, while Flightdeck is open
+
+### Fixed
+
+- **Changing the clock or waking from sleep no longer delays refreshing** (Team folder). Setting the clock back doesn't delay refreshing, and after the computer sleeps, Flightdeck refreshes as soon as you come back and reads whatever went past its time first. While the tab is hidden nothing is read. *Where:* Every team folder, while Flightdeck is open
+
 ## 1.16.1 · Oct 19, 2026
 
 Make the editors' side panels wider or narrower.

package/README.md

@@ -393,6 +393,14 @@ The same rules are in the `flightdeck-skill-brief` skill for your AI assistant,
 | `flightdeck skills <folder>` | Adds or updates only the skills, in `<folder>/.flightdeck/skills` |
 | `flightdeck skills --to <dir>` | The same, into any other folder you name (absolute or relative), such as your assistant's own skills folder or another repo. `<dir>` is created if it's missing |
 | `flightdeck backup <folder>` | Copies the whole team folder to `~/Flightdeck backups/<folder> backup <date> <time>/`, or under `--to <dir>`. Skips links and temporary files, and refuses a destination inside the folder |
+| `flightdeck export <folder> --run <process>/<id>` | Makes an evidence pack of one run in `~/Flightdeck evidence/` (or `--out <dir>`, never inside the team folder): a zip of the original files, a readable `evidence.html`, `manifest.json`, `SHA256SUMS` and a `README.txt`. Prints the pack's SHA-256 to keep somewhere separate. Reads only; never changes the team folder |
+| `flightdeck export <folder> --process <id> --from YYYY-MM-DD --through YYYY-MM-DD` | The same for every run of a process started on those days, both included, in `--tz Area/City` (this computer's time zone unless you say) |
+| `flightdeck processes <folder> --json` | For other apps: every process and its versions, as JSON |
+| `flightdeck process <folder> <process> --json` | One version of a checklist (the latest usable one, or `--version N`, or `--folder v3-…`): phases, steps, gates and the evidence each step can record |
+| `flightdeck runs <folder> --json` | Runs and planned runs, with `--process <id>` and `--status running\|planned\|ended\|all` |
+| `flightdeck run <folder> <process>/<run id> --json` | One run in full: each step's state, who and when, what was recorded, gates and follow-ups. In the app, a run's **More** menu has **Copy run key** |
+| `flightdeck next <folder> <process>/<run id> --json` | What's waiting in a run and on whom; `--person <id>` adds that person's own next step |
+| `flightdeck followups <folder> --json` | Every follow-up and what became of it (`--status open` for the open ones) |
 | `flightdeck path` | Prints where the app file is |
 | `flightdeck version` | Prints the version |
 
@@ -401,6 +409,11 @@ The same rules are in the `flightdeck-skill-brief` skill for your AI assistant,
 | `--check` | With `install` or `skills`: lists what would change and changes nothing. Exit code 0: nothing to do; 2: updates to install; 3: files your team changed need merging; 1: a problem |
 | `--app-only` | With `install`: copies only `flightdeck.html` |
 | `--force` | Replaces a newer app, an unrecognized file, or files your team changed. Like every install, it first saves a checked copy of each file it replaces in `.flightdeck/updates/<version>/replaced/` |
+| `--no-attachments` | With `export`: lists attachments with their sizes instead of packing them |
+
+`export` exits with 0 for a complete pack, 4 for a partial one (made, and it lists at the top what changed or was missing while it read), and 1 when it made no pack. It writes `<name>.zip.partial` as it goes and renames it only when it's done; Ctrl+C or a failure removes it. It uses only the code in its own installed `flightdeck.html`, never a team folder's copy, and never reads through a link. The people directory and its email fields are left out; original records and attachments may contain personal information. A pack isn't signed: checking its hashes shows whether its files still match, and comparing its SHA-256 with the one you kept shows whether the pack is the one you made. See [Evidence packs](docs/evidence.md).
+
+The JSON commands let other apps read a team folder the way a teammate would: a script beside the monthly backup check, a reminder bot for an access review, an onboarding tracker, a deploy script. They only read, never through a link, and never change a file in the team folder. Every result says which contract it follows (`flightdeck-read/1`) and names, file by file, anything it couldn't read. Exit code 0: complete; 4: partial (the data is still printed, with each problem listed); 1: no data; 5: no such process, version or run. People-directory email fields are omitted. See [Using Flightdeck from other apps](docs/apps.md).
 
 Install and skills sort every `AGENTS.md` and skill file the same way. A file that's still a Flightdeck default (this version's or an earlier one) is updated. A file your team changed is left alone. If this version changed that file's default too, the new default goes to `.flightdeck/updates/<version>/`, with a `README.md` holding a prompt for your AI assistant to merge it. In `AGENTS.md` only the part between the `flightdeck:begin` and `flightdeck:end` markers is Flightdeck's; Team notes, below it, are never touched. `.flightdeck/installed.json` records which defaults the folder is based on; it can make install more careful, never less. Every file install replaces is first copied to `.flightdeck/updates/<version>/replaced/`. A file that changes while install runs is left alone and install exits with 1. Nothing is written through a link or outside the folder (see [Updating Flightdeck](docs/updating.md) for the limits).
 
@@ -482,6 +495,13 @@ Flightdeck was called Preflight before 1.9.0. Team folders, runs and published v
 
 ## FAQ
 
+<details>
+<summary><b>How do I find an old run, note or ticket?</b></summary>
+
+Press Ctrl+K (Cmd+K on a Mac), or choose Search in the top bar. It searches runs, steps, notes, corrections, follow-ups, step types, skills and pages in the team folder, ignores accents, and takes you straight to what you choose. The search stays in memory on your computer; nothing is written to the team folder.
+
+</details>
+
 <details>
 <summary><b>Does Flightdeck run anything for me?</b></summary>