@leftoff/cli 0.9.17-beta.9 → 0.9.17

package/CHANGELOG.md

@@ -2,7 +2,25 @@
 
 What changed in Leftoff (called Checkpoints until 0.4.5), newest first. The board's **What's new** page and `leftoff changelog` both read this file.
 
-## Unreleased
+## [0.9.17] - 2026-11-02
+
+- **Point the walkthrough's question at exact lines.** Click a line number in a walkthrough's code to pick it; shift-click or drag for a range, and Cmd/Ctrl-click to add lines from another file or step (on a phone, tap one number, then another). The picks show as chips over the ask box, and the question goes into the chat with each ref and its exact lines.
+
+- **A step's files fold.** Each file in a step has its own header (status, path, +/− counts) that folds, with Collapse all and Expand all. What you fold is remembered per walkthrough, and lockfiles and generated files start folded.
+
+- **Side-by-side diffs.** Unified or Split in the walkthrough's toolbar, remembered on this device. Split is offered on screens 1000px and wider, and picked lines carry across.
+
+- **A file list you can fold or widen.** `[` or its button folds the walkthrough's file list to a slim rail with counts; drag its edge to make it wider or narrower. Both are remembered.
+
+- **Walkthroughs open at once when the change has moved on.** A walkthrough was already kept for its exact diff, but in a live session every edit made a new one and opening it ran the whole read again. Now the last one opens straight away with "3 files changed since this walkthrough · Update", and the steps whose files changed say so. Update writes the new one, and your Mark reviewed carries over for steps whose files didn't change.
+
+- **Next spot.** A toolbar button (or `n`, Shift+N for back) jumps across steps to the next place worth a real look: flagged lines, Core changes, and risky ones (removed logic, auth, config, migrations, error handling), each with a short reason tag. Supporting steps come last.
+
+- **See how far you got.** The session panel's Walk me through it button shows "◐ 3 of 7 reviewed" or "✓ Reviewed", plus how many files changed since.
+
+- **Walkthroughs cover every repo a session changed.** When a session’s edits also landed in another repo, Walk me through it reads that repo too: each step says which repo it’s in (“api · src/x.ts”), the reading order and the page group steps under a small header per repo with its counts, and the downloaded .html and Copy as Markdown get a heading per repo. A repo it only read stays out, and one that can’t be read here gets one quiet line instead of vanishing.
+
+- **Walkthroughs render Markdown, and say all of it.** `code`, bold, lists, links and code blocks in a step now render on screen and in the downloaded .html (Copy as Markdown stays raw), as do the `code` bits in Catch me up and Claude’s recap line. A step’s explanation is no longer cut off mid-sentence, and the slides get a second Next: “Mark reviewed & next” (Shift+→ or Enter) beside the plain › Next.
 
 - **A calmer session panel.** Only a slim head stays pinned (the title row and the status chips); the newest checkpoint shows Stopped and Next with the rest behind More, PRs are one row each (several unchecked refs fold into “+4 not checked”), and everything else is a one-line header with a count, closed until you open it and remembered on this device. Files touched read relative to the repo, five then “+N more”; a duplicate checkpoint written from Claude Code’s own task notice is gone; answers from your phone say “via relay”, not “over Tailscale”. A file path in a message is a link only when its file can be opened from here; otherwise it’s plain text that says why.