@troylar/flightdeck 1.17.0 → 1.19.0

package/CHANGELOG.md

@@ -2,6 +2,37 @@
 
 <!-- Generated by build.py from src/releases.json. Edit that file, not this one. -->
 
+## 1.19.0 · Oct 19, 2026
+
+Edit a checklist with your AI assistant at the same time.
+
+### New
+
+- **See your AI assistant's changes as you edit** (Checklist editor). When your AI assistant changes a draft you have open with nothing unsaved, its change appears in the editor within a few seconds, marked "Changed by your AI assistant", and is saved. One Undo takes it back. Otherwise it waits for you on the process page. From another computer, add OneDrive's time. With the draft open on two computers, use Decline there rather than Undo. *Where:* Edit on a process page
+- **Proposed changes wait for you** (Processes). When a draft is open in an editor, or changed since your AI assistant read it, its changes arrive as a proposal. Review it, then Apply or Decline it on the process page. Apply works only when the proposal starts from the draft as it is now; anything else waits for you to look at it. *Where:* A process page
+- **See who's editing a draft** (Checklist editor). A draft open in someone's editor shows who and on which computer, as far as this computer can see right now. You can still edit it, and each save is checked against the draft you opened.
+- **flightdeck draft read, save and propose** (Command line). AI assistants read and save drafts with the flightdeck command. When someone has the draft open, it sends a proposal instead of writing over their work.
+- **Drafts up to 1 MB** (Checklist editor). Drafts are saved up to 1 MB. A bigger one isn't saved: Flightdeck says how much to cut and keeps your text. From 0.9 MB the editor shows the size.
+
+### Improved
+
+- **Add screenshots to a step in the builder** (Checklist editor). Select a step and add screenshots in its form: choose files, drop them there, or paste one. Each needs a caption, which is also what screen readers say. Edit captions, move screenshots up or down, or remove one from the draft; the image file stays in the folder. Undo takes back any of it, and nothing is saved until you save the draft. *Where:* Edit on a process page, then select a step
+- **Undo a newer draft that arrived** (Checklist editor). A newer draft arrives as one change you can undo, and the changes before it can still be undone.
+- **Saves check the exact text** (Checklist editor). Saving a draft checks that the file is still exactly the text you started from, right before writing, not only a short fingerprint of it.
+
+## 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.

package/README.md

@@ -395,6 +395,12 @@ The same rules are in the `flightdeck-skill-brief` skill for your AI assistant,
 | `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 |
 
@@ -407,6 +413,8 @@ The same rules are in the `flightdeck-skill-brief` skill for your AI assistant,
 
 `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).
 
 <br>