@troylar/sightline 0.0.0-stage → 1.120.2

package/CHANGELOG.md

@@ -0,0 +1,1882 @@
+# Sightline release notes
+
+<!-- Generated by build.sh from src/releases.json. Edit that file, not this one. -->
+
+## 1.120.2 · Oct 25, 2026
+
+Install Sightline with npm.
+
+### Improved
+
+- **One command to install** (Install). npx @troylar/sightline install <folder> puts the app, the planning skills and an invented example plan in a new folder. The README and the availability page explain each install route. *Where:* README, and docs/availability.md
+- **Neutral wording for any assistant** (Assistant). The instructions the app gives your AI assistant use a generic source name and batch id in their example. Any assistant's name is still accepted and shown as written. *Where:* Roadmap, Assistant amendments
+
+### Fixed
+
+- **Helpers match the app they came with** (Install). sightline helpers points to helpers stamped with the app's version, the same files the app and its download carry. *Where:* npx @troylar/sightline helpers
+
+## 1.120.1 · Oct 25, 2026
+
+Stories under a feature are sorted under their epic.
+
+### Improved
+
+- **Says when it can't trace stories to their epic** (Jira sync). If the sync didn't find Jira's Parent Link field, it says so after each run, and Sort Jira work explains why stories under a feature show with No epic and how to check. *Where:* The sync's output, and Work, then Sort Jira work
+
+### Fixed
+
+- **A story under a feature groups under its epic** (Sort Jira work). It's grouped under the first epic above it, with the epic's name, in the list and in In a sprint, not on the board. *Where:* Work, then Sort Jira work
+
+## 1.120.0 · Oct 25, 2026
+
+See where we are: the sprint we're in and today, on every timeline.
+
+### New
+
+- **The sprint we're in is shaded, and its header says now** (Timeline). A soft band runs behind the bars for the sprint we're in, and its header reads, for example, "Sprint 42 · now". Between sprints there's no band, the next sprint's header says when it starts, and the line above the chart says we're between sprints. *Where:* Timeline, in Weeks and Days
+
+### Improved
+
+- **Today has a line and a Today tab in both zooms** (Timeline). A red line marks today, with a Today tab in the time header. In Weeks it sits at today inside the week. When today is before or after the plan's dates, the tab waits at that edge with the date. *Where:* Timeline
+- **Jump to today works in Weeks too** (Shortcuts). Pressing . keeps your zoom: in Weeks it scrolls to the sprint we're in, or the next one between sprints. *Where:* Timeline, the . key
+- **Now shows in the load grid and the roadmap** (Capacity and Roadmap). The load grid marks the sprint's weeks and this week, and the roadmap marks the quarter we're in. *Where:* Capacity, then People, and Roadmap
+
+### Fixed
+
+- **Sprint names keep their space** (Timeline). Sprint names show as written. *Where:* Timeline header
+
+## 1.119.2 · Oct 25, 2026
+
+An update that keeps being overwritten no longer saves over and over.
+
+### Fixed
+
+- **Putting back an overwritten update can't loop** (Saving). An overwritten update is put back once. If the file changes back again, Sightline stops, downloads your version as a backup, and says what to check, naming whoever saved the file last when the file says. A file that still holds exactly what you saved is never saved again. *Where:* Any quick update to a shared plan
+
+## 1.119.1 · Oct 25, 2026
+
+Assistant changes apply whole, or say why not.
+
+### Fixed
+
+- **A change no longer lands only partly** (Assistant). The change waits instead, and review says why: it would start on the later date because it waits on the named item. Change what it waits on, or move that first. A change the schedule allows still applies whole, with one undo. *Where:* Assistant panel
+
+## 1.119.0 · Oct 25, 2026
+
+Settings pages that say where you are, and a File menu for files.
+
+### New
+
+- **Plan details has its own page** (Settings). Settings, then Plan details shows them, with Edit plan details to change them. *Where:* Settings, then Plan details
+
+### Improved
+
+- **Every Settings page is titled with its name** (Settings). Each page starts with its name exactly as the menu says it, and the menu's group names (Plan, Team, Connections) are read out by screen readers. *Where:* Settings
+- **File holds only file actions** (File). File has the shared file, importing a copy and exporting one. Set baseline is on Delivery, then Snapshots, and Start Sightline with is in the menu at the right of the header. Jira setup is Settings, then Jira connection. *Where:* File menu
+
+## 1.118.0 · Oct 25, 2026
+
+Text size, and a tidier header.
+
+### New
+
+- **Make the text larger or smaller** (Header). Choose A+ or A− to change the page's text from 90% to 150% in 10% steps, without browser zoom, and Reset to go back to 100%. Text never gets smaller than 9 pixels. The size stays in this browser and isn't saved in the plan. *Where:* The menu at the right of the header, under Text size
+
+### Improved
+
+- **You, theme, what's new and help in one menu** (Header). One button at the right of the header shows your initials, or Choose yourself, and opens a menu with who you are, text size, theme, What's new and help. A dot on it means there's something new to read. *Where:* Right of the header
+- **View says how you're looking at the plan** (Timeline). View holds the rows (by workstream, person or epic) and the sources, and the button says what's chosen, like View: By person · Jira only. R still switches rows. *Where:* Timeline, above the chart
+
+## 1.117.0 · Oct 25, 2026
+
+What each workstream is for, and skills on the team.
+
+### New
+
+- **See what a workstream is for** (Timeline). Point at a workstream's name, or move to it with the keyboard, to see its description with headings, lists and links, who works in it and what it holds. An item's panel links to its workstream's description, and the workstream's panel lets you edit it. *Where:* Workstream names in Weeks and Days, and the item panel
+- **Skills on people and on work** (Team). Keep a list of the skills your team cares about, give people theirs, and say which skills an initiative or task needs. Renaming a skill keeps it everywhere, and a skill still in use can't be removed until it's taken off. *Where:* Settings, then Team, and each person's, initiative's and task's panel
+- **Milestones get a story** (Milestones). Write what a milestone marks and when it's reached, in Markdown, from a template you can change. Gates get a description the same way. Both show when you point at them. *Where:* The milestone or gate panel, and Settings for the template
+- **Notes for your assistant** (Assistant). Leave a short note for your assistant on people, work, milestones, gates, deliverables, decisions and risks. It sits under For the assistant, closed, and is only ever advice: it can't approve or authorize a change. Anyone who can open the plan, and your assistant's provider, can read it. *Where:* Each item's panel
+
+### Improved
+
+- **Your assistant can keep descriptions and skills up to date** (Assistant). Your assistant can suggest workstream descriptions, the planning guide, skills and needs, milestone stories, gate descriptions and meeting notes, and change a workstream's color, dates and order. Deleting a workstream always waits for you, and only works on an empty one. Review shows the text as it is now and as it would be. *Where:* Assistant panel
+- **Your assistant sees what's missing** (Assistant). What your assistant reads now includes skills, needs, milestone stories, gate descriptions and Jira descriptions, and lists exactly which workstreams, people, work and milestones are still missing a description, skills or needs. The planning guide preview shows the same list. *Where:* Settings, then Planning guide
+- **Older copies open these plans read-only** (Files). A plan with skills, assistant notes, milestone stories or gate descriptions opens read-only in older copies of Sightline, so they can't drop them. Update every copy your team uses to keep editing. *Where:* Opening a plan
+
+### Fixed
+
+- **Moves from the assistant** (Assistant). Moves written from what the assistant reads apply, including for initiatives that start and milestones that fall partway through a week. *Where:* Assistant panel
+
+## 1.116.0 · Oct 25, 2026
+
+A menu down the left side.
+
+### New
+
+- **Fold the menu to a rail** (Navigation). Collapse the menu to a narrow rail of icons with the button at its top or the \ key, and hover or focus an icon to open its group. Sightline remembers your choice in this browser, and narrow windows start with the rail. *Where:* Top of the left menu
+
+### Improved
+
+- **Every page has one home** (Navigation). A menu on the left lists Work, Delivery, Product updates and Settings with every page under its group. Sort Jira work and Jira change proposals live only in Work, and counts and warnings sit on the page they belong to. *Where:* Left side of the page
+
+### Fixed
+
+- **Settings key and Jira hints** (Navigation). Pressing 4 opens Settings, and messages point to Work, then Sort Jira work, or to Settings, then Jira connection. *Where:* Keyboard shortcuts and Jira messages
+
+## 1.115.0 · Oct 25, 2026
+
+Workstream names stay in view.
+
+### New
+
+- **Workstream names stay in view as you scroll** (Timeline). Each workstream's name stays just under the dates while its rows are on screen. In Days the next workstream's header slides over it as you reach it; in Weeks the name moves down with its row. It also stays below any rows you've pinned with Show, then While scrolling. Printing is unchanged. *Where:* Timeline, Weeks and Days
+
+## 1.114.0 · Oct 25, 2026
+
+A calmer planning assistant panel.
+
+### Improved
+
+- **The conversation comes first** (Assistant). One line at the top says whether your assistant is connected, with a dot that pulses while a reply is on its way. Your messages and the assistant's read as a conversation, an empty one offers two ways to start, and the message box shows what you're asking about. *Where:* Planning assistant panel
+- **Setup and files, out of the way** (Assistant). Connection steps, what's kept where, planning skills and the assistant's files are quiet rows under Setup and files at the end of the panel. An open row is set apart, and the commands sit in their own box. *Where:* Planning assistant panel, Setup and files
+- **You can tell what to click** (Assistant). Every action in the panel is a button: Refresh, Export, Disconnect, Skip and Edit included. Pause and when changes apply sit together in one box, and the older-tools warning names the version once, shows the files as chips and offers Replace or Keep. *Where:* Planning assistant panel
+
+## 1.113.1 · Oct 25, 2026
+
+Edit your assistant's milestone moves.
+
+### Fixed
+
+- **Edit shows a change's fields** (Assistant). Edit shows the change's own fields, such as a milestone move's date and whether it's the stretch date, and checks your edit the same way as the assistant's version. A change with nothing you can edit says so: skip it and ask your assistant. *Where:* Assistant panel, Changes
+- **Milestone moves read plainly** (Assistant). It reads "stretch date cleared", and a move reads as a move to a date. *Where:* Assistant panel, Changes
+
+## 1.113.0 · Oct 25, 2026
+
+Your assistant proposes where Jira work goes.
+
+### New
+
+- **The assistant proposes where unsorted Jira work belongs** (Assistant). Your assistant reads what's waiting in Sort Jira work against each workstream's planning guide and the initiatives already there, and proposes a place for each issue: a workstream, an initiative, or not ours. An epic's stories that belong together move together. Every placement waits for you to review it, at every assistant level, and nothing is written to Jira. *Where:* Assistant panel, Changes
+- **Review Jira placements in one table** (Assistant). Placements show as one table with the issue, where it goes, the assistant's reason, and high or low confidence. Edit offers only the places the issue can go. Skip leaves it in Sort Jira work. Apply ready applies up to 25 as one update, with one Undo. *Where:* Assistant panel, Changes
+- **A Sort Jira work skill** (Assistant). The bundled planning skills include Sort Jira work: it groups issues by epic, proposes placements with reasons, sends them for review, and reports what was placed, skipped, changed since, and what it couldn't place, with the question it would need answered. *Where:* Assistant panel, Planning skills
+
+### Improved
+
+- **Bring back issues marked not ours** (Sort Jira work). Sort Jira work says how many issues are marked not ours, and Show them again brings them back. *Where:* Work, Sort Jira work
+
+### Fixed
+
+- **The helper accepts --json where the guide puts it** (Assistant). It accepts --json before or after the command. *Where:* sightline-app.py
+
+## 1.112.0 · Oct 25, 2026
+
+Every button answers when you hover and click.
+
+### New
+
+- **Bars glide to their new dates** (Timeline). When an edit, undo or redo moves a few bars, they glide from where they were and glow once, so you can see what changed. A new view or a drag doesn't animate, and nothing moves if your system asks for reduced motion. *Where:* Timeline
+
+### Improved
+
+- **Controls answer your hover and click** (Interface). Every button, chip, tab, menu item and row lightens when you point at it and presses in when you click. Filled buttons keep their color on hover, and the keyboard focus ring stays visible everywhere. *Where:* Everywhere
+- **Switches slide to what you pick** (Interface). The selected option is a raised pill that slides to the one you pick. The main navigation underlines the view you're on. *Where:* Timeline, List and Plan toolbars
+- **A new typeface, built into the page** (Interface). Sightline uses Instrument Sans, with narrower headings and bar labels so more of a name fits. The font is part of the file, so it looks the same offline and the page makes no network requests. *Where:* Everywhere
+- **A short count on the Settings tab** (Interface). It shows just the number. Point at it to read what it counts; screen readers still hear the full words. The warning sign has its own space. *Where:* Main navigation, Settings
+
+### Fixed
+
+- **Long links in Breakdown read left to right** (Side panel). It lines up on the left like the text around it. *Where:* Side panel, Breakdown
+- **Similar sprint names no longer look the same** (Settings). The name column has room for typical sprint names. Where a name still has to be cut, the timeline header and the commitment table cut it in the middle and keep the end, such as S15, in view. Point at a name to see all of it. *Where:* Settings, Timeboxes and ceremonies; Timeline header
+
+## 1.111.0 · Oct 25, 2026
+
+The assistant keeps your timeboxes in line with the work.
+
+### New
+
+- **The assistant can set timebox goals and names** (Assistant). The assistant can set the name and goal of the plan's own timeboxes, add one at the end, or add timeboxes through a date, the same way Add timeboxes through does: at most 60 at a time, and asking again once they reach the date changes nothing. Several goals in one change apply as one update with one undo. *Where:* Assistant panel, Changes
+
+### Improved
+
+- **The context lists your timeboxes and what finishes in each** (Assistant). The context file lists the plan's timeboxes in order: Jira sprints, the rows between them and the plan's own, with the plan's dates, Jira's own dates, the goal, and the tasks, initiatives and milestones finishing in each. The guide says to write a goal as one plain line about what that timebox finishes. *Where:* Assistant panel, Files and assistant handoff
+- **Jira sprints stay where Jira puts them** (Settings). A Jira sprint can't be lengthened, moved or deleted here, and neither can a row whose change would move one, such as the weeks between two Jira sprints. Those rows' goals are still yours. Each locked control says why, and the assistant is refused the same way: This sprint comes from Jira; change it in Jira. *Where:* Plan, Timeboxes & ceremonies
+
+## 1.110.0 · Oct 25, 2026
+
+Assistant batches apply in order, and the right tools are one click away.
+
+### New
+
+- **Put assistant tools in this folder** (Assistant). One click puts the assistant tools that match this page in the assistant folder, each with a .sha256 checksum. Files it doesn't recognize are never replaced, and it asks before replacing an older copy. The context file says whether the folder's tools match. *Where:* Assistant panel, Files and assistant handoff
+
+### Improved
+
+- **Changes that build on each other are ready together** (Assistant). The panel checks a batch in order. A change an earlier one enables shows Ready after change N, with that change's summary. Skip a change and the ones it enables say they need it, with Reopen. *Where:* Assistant panel, Changes
+- **Apply ready applies in order and says what happened** (Assistant). Apply ready applies the ready changes from the top as one update with one undo, and stops at the first one that can't apply. It then says which changes applied, which were already in the plan, which was skipped, what waits and why, and whether the plan was saved. *Where:* Assistant panel, Apply ready
+- **Held changes hold what they enable** (Assistant). When a change waits for review, is paused, has expired or was written against an older plan, the changes it enables wait with it and say why. Size and delete checks look at the plan as the earlier changes leave it. *Where:* Assistant panel, When your assistant writes changes
+- **The checking tool says what it checked** (Assistant). check-amendments checks a batch in order, and lists what it checked and what only Sightline checks when it applies the batch. *Where:* sightline-jira-sync.py check-amendments
+- **Start-up help for synced folders** (Saving). If Sightline doesn't start, the first step it suggests is to wait for OneDrive or another synced folder to finish syncing, then reload. *Where:* The Sightline didn't start screen
+
+### Fixed
+
+- **Results right after an apply while editing** (Assistant). The results file describes the plan as it is in this browser, says when it isn't saved yet, and carries the same summary the page shows. *Where:* sightline-assistant-results.json
+- **Moving a milestone with its date as prev** (Assistant). prev is a date, as the context gives it, and a stretch date can now be cleared (stretch true, day null). *Where:* Assistant changes, milestone.move
+
+## 1.109.0 · Oct 25, 2026
+
+Stories: the why behind each item.
+
+### New
+
+- **Write a story for any initiative or task** (Timeline). Each initiative and task can have a story: why it exists, what it delivers and when it's done. Edit shows a live preview beside the text, and a new story starts from a template. *Where:* Click an item, then Write a story or Edit
+- **See the story at a glance** (Timeline). Hovering an item shows the first lines of its story, or No story yet. Click it to read the whole story in its details. *Where:* Timeline and List
+- **Walk an initiative's breakdown** (Timeline). An initiative's details list its tasks with their owner, status and whether each has a story. Click one to open it, and Up and Down move to the next item while the details are open. *Where:* An initiative's details, Breakdown
+- **Jira descriptions as stories** (Jira). An item linked to Jira shows the issue's description, marked From Jira. What the plan had before is kept as a draft, and is shown when Jira's description is empty. Run the updated sync to bring descriptions in. *Where:* An item's details, Story
+- **Story templates** (Settings). Set the starting text for new initiative and task stories, for the whole plan. *Where:* Settings, Planning guide, Story templates
+
+### Improved
+
+- **Assistants can read and propose stories** (Assistant). The assistant context includes stories and templates, and an assistant can propose stories for many items at once. Review shows each story in full and Edit opens it in a text box. A batch applies as one update with one undo. Older copies of Sightline open a plan with stories read-only. *Where:* Assistant panel
+
+## 1.108.0 · Oct 25, 2026
+
+Hide what you don't need, and pin the top rows.
+
+### New
+
+- **Show: hide gates, meetings, done work and more** (Timeline). Show has an eye for each kind of item: gates, releases, deliverables, meetings, process blocks, milestones and done work. One click hides or shows a kind on Timeline, List and People. Focus hides meetings, process blocks and done work at once. *Where:* Timeline toolbar, Show (or press H)
+- **Pin the top rows while you scroll** (Timeline). Pin the top rows keeps them under the dates while you scroll, so you can see what's coming next to any workstream. *Where:* Show, Pin the top rows
+- **Keys to clear the chart** (Timeline). G hides or shows gates, M hides or shows meetings, H opens Show, and Shift+H shows everything you hid. In any meeting, gate, process block, release or milestone, Hide all hides that kind. *Where:* Timeline, List and People, and an item's details
+
+### Improved
+
+- **Kinds can be hidden, not only shown** (Filters). Each kind cycles through Show only, Hide and off, and Hide wins. Releases, deliverables and done work can be hidden too. The line under the toolbar says what's hidden, with Show everything. *Where:* Filters, Kinds
+- **Saved views remember what's hidden** (Views). What you hide stays in this browser for each plan, and a saved view keeps its own choice. A plan whose team views hide kinds opens read-only in older copies of Sightline, so they can't drop the setting. *Where:* Views
+
+## 1.107.0 · Oct 25, 2026
+
+Read the whole plan as a list.
+
+### New
+
+- **A List page next to Timeline** (List). List shows the same work Timeline draws, as rows: Start, End, Item, Owner, Waits on and Status. Read it by initiative, by person, or as one list by start date. Work Timeline doesn't draw is at the end under Not on the timeline, with the reason. *Where:* Delivery, List (or press L)
+- **See what each item waits on** (List). Waits on names the task, initiative, gate or process step an item waits for, and links Jira dependencies to Jira, warning when one ends after the item starts. Click a name to open it. *Where:* List, Waits on
+- **Copy or print the list** (List). Copy as table copies the rows as shown as a markdown table, ready to paste into a document. Print prints every row, with the header repeated on each page. *Where:* List, Copy as table and Print
+
+### Improved
+
+- **Views and selection carry across** (Views). A saved view applied on List stays on List. The selected item stays selected when you switch between Timeline and List, and a link to List opens the same layout and item. *Where:* List and Timeline
+
+## 1.106.0 · Oct 25, 2026
+
+The whole forecast in one place.
+
+### New
+
+- **A Forecast section in Capacity** (Capacity). Capacity opens with the forecast for the whole plan: one line with how many items, their effort and the likely and high finish, then every initiative with its effort, start, likely and high finish, and why it starts when it does. Click an initiative to open it on the timeline. *Where:* Capacity, Forecast
+- **See when the forecast isn't complete** (Capacity). When any initiative has no forecast date (no effort, nobody to do it, or waiting on something with no date), the summary says the forecast is incomplete, counts why, and doesn't claim a finish date for everything. *Where:* Capacity, Forecast
+- **The chain behind the last finish, and load by workstream** (Capacity). Under the table: the critical chain that sets the last finish date, the workstream the waiting was for, and each workstream's demand against its people's time, with a weekly chart of Jira-dated work, forecast work and ready work waiting. *Where:* Capacity, Forecast
+
+### Improved
+
+- **Clearer reasons** (Forecast). Reasons read as plain sentences: "It starts then because it waited for Index rebuild (finishes Mar 20)." *Where:* Initiative card and Capacity, Forecast
+
+### Fixed
+
+- **Overlapping waits are counted once** (Forecast). When naming the workstream most of the waiting was for, a working day that several steps of the chain spent waiting counts once. *Where:* Initiative card, "Why it finishes then"
+
+## 1.105.1 · Oct 25, 2026
+
+People rows draw their work again, and the assistant scripts travel with the page.
+
+### Improved
+
+- **The assistant scripts are published with the page** (Assistant). Publishing the page also copies sightline-app.py and sightline-jira-sync.py beside it, each with a checksum file. Each copy says which Sightline version it matches (--version), and refuses, with the reason, to send or check against a page of another version, so an assistant on another computer can't check a batch against old actions. *Where:* Beside the published page
+- **Clearer instructions for assistants** (Assistant). The instructions an assistant reads now say, near the top, to take each action's arguments exactly as listed and never guess field names, and to check a batch with sightline-app.py check before handing it over. *Where:* Connect assistant, the context file
+
+### Fixed
+
+- **Rows by person show their work** (Timeline). With rows by person, in Weeks and in Days, each person's row draws their initiatives and tasks again. *Where:* Timeline, rows by person (R)
+
+## 1.105.0 · Oct 25, 2026
+
+Why an initiative finishes when it does, and who the work waits for.
+
+### New
+
+- **Follow the chain that sets a finish date** (Forecast). An initiative's card has a "Why it finishes then" list. It walks back through what held the initiative up: the work it waited for, and the work that had or shared its people, each with dates, until it reaches the first day, a gate, a Jira sprint or a workstream's start. *Where:* Initiative card, under the forecast dates (open "Why it finishes then")
+- **See which workstream the work is waiting for** (Forecast). Under the chain, the card names the workstream, and its people, that most of the waiting was for, with the number of working days. When nobody on the chain waited for people, it names the busiest workstream instead: how much work it had against how much time its people had, and over which dates. *Where:* Initiative card, at the end of "Why it finishes then"
+
+### Improved
+
+- **Waits are dated by working days** (Forecast). When an initiative waited for its people, the dates given for the wait start and end on working days, not on a weekend or holiday. *Where:* Initiative card, forecast line
+
+## 1.104.0 · Oct 24, 2026
+
+A forecast date on every initiative, with the reason for it.
+
+### New
+
+- **See when an initiative is likely to finish** (Forecast). An initiative with an effort shows its forecast on its card: the likely start and finish, and the finish if everything takes its high estimate. Sightline works it out day by day from who's in each workstream, their time, holidays and time off, what each item waits for, and the other work competing for the same people. It never moves anything on the timeline. *Where:* The initiative card, under Effort left
+- **Know why a date is what it is** (Forecast). The forecast says what set an item's start: the item it waited for, a gate, a Jira issue's sprint, or the work its people were on, with dates. It also gives the pace in person-weeks a week and who's on it. *Where:* The initiative card
+- **No date, with the reason, when the forecast can't give one** (Forecast). An item gets no date, never a guess, when it waits for something with no effort, sits on a dependency loop, is in a workstream with nobody in it, or waits for a Jira issue with no sprint. The card says which one, and anything waiting on it says so too. *Where:* The initiative card
+- **Holders show their latest finish** (Forecast). An initiative with others inside shows the forecast finish of the last of them, or how many have no date yet. *Where:* The card of an initiative with others inside
+
+## 1.103.0 · Oct 24, 2026
+
+Capacity day by day, the second step toward a forecast.
+
+### New
+
+- **Say when people join and leave** (Forecast). A person's card has Joins on and Leaves on. Their capacity counts only the days in between, so someone starting mid-sprint or rolling off is planned for the days they're actually here. *Where:* The person card
+- **Split someone's time across workstreams** (Forecast). For someone in two or more workstreams, the person card has Time split: a weight for each workstream. With no split, their time divides evenly. When a workstream ends, its share moves to their other workstreams. *Where:* The person card, Time split
+- **Keep time back for support and unplanned work** (Forecast). Set a reserve for the team in Team, and a different one for any workstream on its card. The workstream card shows this week's capacity for planned work, in person-weeks, after the reserve. *Where:* Team, Reserve; the workstream card
+- **Your assistant can set capacity inputs** (Assistant). Assistant changes can set when someone joins or leaves, how their time splits across workstreams, and the team's or a workstream's reserve. *Where:* Assistant changes
+
+### Improved
+
+- **Sprint capacity counts joining and leaving dates** (Capacity). A person's capacity for a sprint leaves out the days before they join and from the day they leave. *Where:* Capacity in the sprint view
+- **Older copies open a plan with these settings read-only** (Plan file). A plan with join or leave dates, time splits or reserves opens read-only in copies older than 1.103.0, so they can't save over them. *Where:* Opening a plan in an older copy
+
+## 1.102.0 · Oct 24, 2026
+
+Effort estimates, the first step toward a forecast.
+
+### New
+
+- **Give an initiative its effort left, in person-weeks** (Forecast). Each initiative's card has Effort left (person-weeks): a likely figure, and a low and high if you know them. The card says what the forecast will do with it: Forecast, Fixed (Jira's sprint sets its dates), Not counted (no effort yet, which is never treated as zero), or Out of scope if you tick Leave out of the forecast. An initiative with others inside shows their sum. *Where:* The initiative card, under Workstream
+- **Link work to what it ships** (Forecast). Delivers on an initiative's card links it to deliverables, and each deliverable's card lists what delivers it, or says Not forecast when nothing does. Linking the existing work, instead of adding a second initiative for it, keeps the same work from being counted twice. *Where:* Initiative card, Delivers; deliverable card, Delivered by
+- **Your assistant can set effort and links** (Assistant). Assistant changes can set an initiative's effort, leave it out of the forecast, and link it to what it delivers. It's told never to guess an effort. *Where:* Assistant changes
+
+### Improved
+
+- **Older copies open a plan with effort read-only** (Plan file). A plan with effort, scope or delivers opens read-only in copies older than 1.102.0, so they can't save over them. *Where:* Opening a plan in an older copy
+
+## 1.101.0 · Oct 24, 2026
+
+Pause your assistant, and big changes wait for you.
+
+### New
+
+- **Pause and Resume** (Assistant). One click stops anything your assistant writes from applying on its own, whatever level you picked, until you click Resume. You can still review and apply changes by hand, and your assistant is told it's paused. *Where:* Assistant panel, Pause
+
+### Improved
+
+- **Changes that move a lot wait for your review** (Assistant). When your assistant's changes apply routine changes on their own, a change that would move more than 5 other items, or a batch touching more than 50 items, waits for you instead, and says why. At Apply everything, they apply as before. *Where:* Assistant panel, When your assistant writes changes
+
+## 1.100.0 · Oct 24, 2026
+
+See what your assistant changed, and undo a whole batch.
+
+### New
+
+- **Items show when your assistant added or edited them** (Assistant). Anything your assistant adds or changes is stamped with who it acted for and which assistant and batch did it, for example "edited by Avery via Planning bot". The stamp is kept when the plan is saved, reopened, merged or saved as YAML. *Where:* The item card, under its title; Activity
+- **Undo this batch** (Assistant). The Assistant panel lists the last five batches your assistant applied to the shared file, each with Undo this batch. Undo puts back only what that batch changed, even if other updates came after it, and leaves anything a teammate has changed since. It's available in this browser until you reload. *Where:* Assistant panel, Applied by your assistant
+
+### Improved
+
+- **Older copies open a plan with assistant stamps read-only** (Plan file). A plan with these stamps opens read-only in copies of Sightline older than 1.100.0, so they can't save over them. Update everyone's copy to keep editing together. *Where:* Opening a plan in an older copy
+
+## 1.99.1 · Oct 24, 2026
+
+The header holds still while Sightline checks the file.
+
+### Fixed
+
+- **The page no longer bounces every 15 seconds** (Editing). The automatic check of the shared file (Check automatically) runs without touching the header or the editing bar, unless a save or check takes a while. The status line at the top says only what matters: who's editing, the last save and the lock. *Where:* The status line at the top, and the editing bar
+
+## 1.99.0 · Oct 24, 2026
+
+Your assistant can add holidays, and check its work before sending.
+
+### New
+
+- **Assistant changes can add and remove holidays** (Assistant). An assistant can add a day off for everyone, add a range such as a winter shutdown (stored as its working days, like the Holidays table does), or remove a holiday. The review shows what each one moves. *Where:* Assistant changes; Settings, Calendar, Holidays
+
+### Improved
+
+- **The assistant helper checks a batch before it sends it** (Assistant). sightline-app.py check reads the batch against the context your assistant read, with no page open, and names each problem: an unknown action, a missing or extra argument, a bad date, a new item with no id, or a batch written against an older plan. send and run make the same check and send nothing if it fails. *Where:* tools/sightline-app.py
+
+## 1.98.0 · Oct 24, 2026
+
+Assistant changes can apply on their own.
+
+### New
+
+- **Choose whether your assistant's changes wait for you** (Assistant). Pick a level for each plan: wait for your review, apply routine changes on their own, or apply everything. Deletes wait for you unless you choose everything, and deleting an initiative with Jira-linked work always waits. Each batch that applies is one quick update you can Undo. *Where:* Assistant panel, When your assistant writes changes
+- **A change that can't apply says why instead of waiting quietly** (Assistant). A batch written against an older version of the plan, one more than an hour old, or one that arrives while you have unsaved edits isn't applied on its own, and your assistant is told why. While the page is open, even in a background tab, it tells your assistant every 30 seconds that it's there, so the assistant knows when nobody's listening. *Where:* Assistant panel; the results and status files in your private folder
+
+### Improved
+
+- **Meeting notes skill records decisions, risks and links** (Assistant). The meeting-to-plan skill now records agreed decisions, risks, starts-after links and milestones as changes, instead of listing them for you to enter by hand. *Where:* Assistant panel, Planning skills
+
+## 1.97.1 · Oct 24, 2026
+
+The timeline stays where you scrolled.
+
+### Fixed
+
+- **The timeline no longer jumps back to the top** (Timeline). When the chart redraws, for example after a Jira sync, an assistant update, a teammate's save, or when you click Start editing or Done editing, the timeline stays on the rows you were looking at. *Where:* Timeline, in both Weeks and Days
+
+## 1.97.0 · Oct 24, 2026
+
+Your assistant can do the whole replan.
+
+### New
+
+- **Assistant changes cover links, people, milestones, gates, risks and decisions** (Assistant). An assistant's changes can now add and remove starts-after links, delete initiatives, add and rename workstreams, set people's roles, allocation and workstream, add milestones with what they're done after, add gates, and add or update risks and decisions. You review them together and apply them with one click. *Where:* Roadmap, Assistant changes
+
+### Improved
+
+- **Assistant changes say what they move and refuse what the chart would refuse** (Assistant). Before you apply, each change lists every item it moves, with both dates and how much later. A link that would make a loop, a link inside one initiative, dates Jira sets, and work landing in blacked-out time are refused with the reason, the same as when you edit by hand. *Where:* Roadmap, Assistant changes
+
+## 1.96.1 · Oct 24, 2026
+
+Dragging on the chart follows the same rules as editing.
+
+### Fixed
+
+- **Dragged items are stamped and kept out of blacked-out time** (Timeline). When you drag an initiative, task or milestone on the chart, the change records who made it and when, like any other edit, and a drag that would land outside its workstream's dates is refused with the reason. *Where:* Timeline, dragging initiatives, tasks and milestones
+
+## 1.96.0 · Oct 24, 2026
+
+Give your external assistant the planning picture.
+
+### Improved
+
+- **Plan with capacity, dependencies, risks and decisions** (Assistant context). Your assistant context includes people, allocation and availability, workstream membership, dependencies, gates, milestones, risks and decisions. It calculates capacity and known Jira demand across the loaded active and future sprints. Parked work stays visible, and exact coverage counts explain any data omitted to fit the export. Notes and time-off descriptions stay excluded. *Where:* The private assistant folder and manual assistant context export
+
+## 1.95.0 · Oct 24, 2026
+
+Take your planning skills straight from the app.
+
+### New
+
+- **Deploy planning skills directly from the HTML app** (Planning skills). The HTML includes the planning skills from its build. Download them as a ZIP or install them into a chosen folder from the Planning assistant or Planning guide, without source code, npm or Python. Existing different files are kept, and the bundle shows its Sightline version. *Where:* Planning assistant → Planning skills; Settings → Planning guide → Get planning skills
+
+## 1.94.1 · Oct 24, 2026
+
+Get clearer, more reliable assistant guidance.
+
+### Fixed
+
+- **Match proposal results and explain the source of a plan summary** (Planning skills). The six external assistant skills check plan and proposal identities before reporting outcomes. Status summaries distinguish saved shared snapshots from browser state and manual exports. Pending proposals allow read-only reviews and guide drafts to continue, and guide text is grouped by the fields in Settings. *Where:* The six planning skills installed with the sightline command
+
+## 1.94.0 · Oct 24, 2026
+
+Take your plan from first idea to team conversation.
+
+### New
+
+- **Install the app and six reusable planning skills** (Getting started). The public npm package installs the self-contained HTML app and six assistant skills. A visual walkthrough covers first use, four-quarter planning, Jira context, and reviewing AI proposals. Existing different files are kept; install into a new folder to update. *Where:* README and the sightline command
+
+### Improved
+
+- **Start with clear, invented planning examples** (Examples). The idea composer uses a general onboarding example. The public guide includes an invented team plan, Jira snapshot and two prepared proposals so you can try the review loop without an AI account. *Where:* Roadmap and the getting-started guide
+
+## 1.93.1 · Oct 23, 2026
+
+Keep context when following up with your assistant.
+
+### Fixed
+
+- **Retain the selected outcome or quarters in conversation history** (Assistant). Follow-up requests retain the stable outcome IDs or quarters that belonged to earlier questions, including when you switch outcomes. Historical selections are labeled as earlier context. Requests keep complete recent turns within the existing message limit and preserve the full question length.
+- **Reconnect the changes file or folder you already selected** (Connections). Reconnect in the Planning assistant requests access to the existing individual changes file or private assistant folder. Paused file connections are labeled as files.
+
+## 1.93.0 · Oct 23, 2026
+
+Describe a plan change in one message.
+
+### Improved
+
+- **Start with your notes and see what the assistant is working on** (Assistant). Plan with AI opens an empty composer with the selected quarters in Working on. Ask assistant about this selects an outcome by its stable ID. Paste notes or describe a change and Send once; the selection travels with the request. The composer comes first, with setup and file details below. *Where:* Product updates → Roadmap → Plan with AI, or open an outcome → Ask assistant about this.
+
+### Fixed
+
+- **Keep roadmap ideas when opening your assistant** (Drafts). Unsubmitted roadmap ideas stay with their plan during navigation and redraws in this tab's session. A successful submission clears only the text that was submitted. Untouched assistant starters follow a new selection; a question you have written keeps its original context until you choose Switch context.
+
+## 1.92.0 · Oct 23, 2026
+
+Plan four quarters with your assistant.
+
+### New
+
+- **Focus on four quarters and ask about an outcome** (Roadmap). Choose a starting calendar quarter for a four-quarter roadmap, or switch to Long range. Work outside the window stays counted and recoverable. Plan with AI prepares a question using the displayed quarters; each outcome has Ask assistant about this. Questions keep existing drafts and wait for Send. *Where:* Product updates → Roadmap. Horizon choices stay in this browser; plan contents are unchanged.
+
+### Improved
+
+- **Check for a reply before your first planning conversation** (Assistant). Test reply sends a short question with the saved plan context through your configured companion and preserves your unfinished message. A matching response confirms a reply for that snapshot; test responses cannot introduce proposed changes. Starter questions help organize roadmap notes or review gaps. *Where:* Connect assistant → Test reply, with the local companion configured and running.
+
+### Fixed
+
+- **See the welcome screen and know what Today can assess** (Getting started). A fresh browser renders the welcome screen immediately. Today offers a planning step when no work is loaded, explains when Jira data is needed, and qualifies quiet summaries when connected data is stale or incomplete.
+
+## 1.91.0 · Oct 10, 2026
+
+Talk through changes to your plan.
+
+### New
+
+- **Turn a planning conversation into reviewed changes** (Assistant). Ask questions, capture ideas, and refine proposed changes in the assistant panel. An optional local companion connects to your company's Chat Completions endpoint using a separate private configuration file. Replies use the saved plan and Planning guide; proposed changes wait for review and Apply, with normal undo and shared Save controls. *Where:* Connect assistant → conversation, with the local companion running against the same private assistant folder.
+
+## 1.90.0 · Oct 10, 2026
+
+Project guidance for your assistant.
+
+### New
+
+- **Explain how your project is organized** (Assistant). Settings → Planning guide lets the team describe project scope, workstream purposes, work breakdown, vocabulary, planning rules, and examples. Save it with the plan to include it in assistant context, or preview and copy the instructions. Guide drafts wait for an explicit Save guide; older app copies open plans with saved guidance read-only. *Where:* Settings → Planning guide, or Planning guide in the assistant panel.
+
+## 1.89.0 · Oct 10, 2026
+
+A clearer way to open Sightline.
+
+### Improved
+
+- **Find the ready-to-use app** (Getting started). The repository start page links to the built app and explains how to open your separate plan file. If you open the development template, a notice points to the app in a new tab while keeping your current work available.
+- **See which version is open** (Updates). The current app version appears beside What's new without opening a dialog. The development template identifies itself and directs you to the built app instead of opening an empty release history.
+
+## 1.88.1 · Oct 9, 2026
+
+Safer reconnects and more reliable Find.
+
+### Fixed
+
+- **Keep edits with their original plan** (Recovery). When you have browser edits, reconnecting stops if the file now contains a different plan. Your edits stay intact so you can download them before opening another plan.
+- **Reveal milestones hidden by a people filter** (Find). Finding a milestone clears a people filter when it would keep the milestone hidden. Restore previous view brings back your original filter.
+
+## 1.88.0 · Oct 9, 2026
+
+Safer updates and easier daily work.
+
+### Improved
+
+- **Reach routine work directly** (Navigation). Sort Jira work is available under Work. Choose yourself in the toolbar to use Mine and author your updates. Find reveals matching milestones, gates and notes even when filters or layers hide them, with an option to restore your previous view.
+- **See feedback and keep your place** (Usability). Status messages remain visible on narrower screens. Filters retain keyboard focus after updating, and Today names the person who decides each due decision, including when no decider is set.
+- **Refresh the screen you are using** (Performance). Other workspaces leave the hidden Timeline and setup tables alone. Text edits update the plan immediately and combine derived screen updates while you type; returning to a workspace renders current data.
+
+### Fixed
+
+- **Keep unsaved work during lock and reconnect problems** (Recovery). A teammate's active edit lock leaves your plan, undo history and recovery draft intact. Reconnecting compares the saved file with your original version and preserves your current edits before merging or asking you to resolve a conflict.
+- **Keep the message you are writing** (Notes). Refreshing Jira or redrawing details keeps unsent notes, quick updates and blocker explanations for each item in this session, including your cursor position. Submitting clears only the message that was sent.
+- **Refuse oversized updates without changing the plan** (Amendments). Deliverable limits are checked on a private candidate before an update reaches the live plan. Repeated initiative and task additions with the same details stay completed, including changes that add an item and then set its fields.
+- **Count unfinished board work consistently** (Jira metrics). Sprint history follows the board's final column when determining completed work, matching the page. An issue in a non-final review column stays unfinished even if Jira categorizes its status as done. Earlier recorded days are retained.
+
+## 1.87.0 · Oct 8, 2026
+
+Clearer shared-file refresh and recovery.
+
+### New
+
+- **Review another copy before recovering work** (Recovery). Compare a recovery copy with the current shared file and download backups. Choose deliberately whether to bring that copy into the editor, then review it before saving. *Where:* File, Review another copy.
+
+### Improved
+
+- **Check for teammates' updates automatically** (Shared files). Shared plans check the local file every 15 seconds by default. An explicit choice to turn checks off is remembered. Automatic checks wait while you type, drag or use a dialog.
+- **Know what saved means** (Shared files). Shared-file status distinguishes a local save from OneDrive synchronization and shows when the local file was last checked. Check OneDrive itself to confirm cloud synchronization.
+
+## 1.86.0 · Oct 8, 2026
+
+Clearer workspaces and a connected assistant.
+
+### New
+
+- **Work, Delivery and Product updates** (Navigation). Find Today and Sprint under Work; Timeline, Capacity, Status update, Decisions and Risks under Delivery; Roadmap and release notes under Product updates. Settings holds the team, calendar and Jira connection. Each group remembers where you were. *Where:* The main navigation.
+- **Connect your assistant once** (Assistant). Choose a private folder. Sightline keeps context and results current; your assistant writes proposed changes for you to review. Shared context comes from the confirmed saved file. Reconnect when browser permission expires. *Where:* Connect assistant in the toolbar; Edge or Chrome.
+
+### Improved
+
+- **Controls match the view you are using** (Scope). View and filter controls appear on Timeline and Capacity, where they apply. Roadmap and Status update clearly describe the whole plan. Your Timeline filters stay ready for when you return.
+- **Common actions first** (Details). Initiative and task details keep routine updates visible and put organizing or moving the item behind a disclosure. Deliverable timing explains its source and separates target windows from commitments.
+- **Refresh only what changed for the assistant** (Performance). Changing views leaves unchanged assistant context alone. Export lookups are indexed, and navigation uses cached controls so it stays cheap as more screens are opened.
+
+### Fixed
+
+- **Saved views remember which sources you chose** (Views). Personal and team views now save and restore All sources, Jira only or Jira + mine. Changing sources marks the view modified, and All work restores all sources. *Where:* Timeline and Capacity saved views.
+
+## 1.85.0 · Sep 30, 2026
+
+Rows by epic follow every parent link.
+
+### New
+
+- **Rows by epic go past the epic** (Timeline). Rows by epic now nest by any parent link, not only epics: an epic under its feature, the feature under its initiative, as deep as Jira goes. Each row says what it is (Feature, Initiative), and a task linked to a sub-task sits on its story's epic. *Where:* Timeline, By epic.
+- **The sync brings the parents above your epics** (Jira). The Jira helper now also fetches the parents above what it syncs (Parent Link or parent), up to six levels, and writes them apart from your issues, so they never show up as work to sort. Copy the new sightline-jira-sync.py next to the plan. *Where:* The Jira helper.
+
+## 1.84.0 · Sep 30, 2026
+
+Rows by epic in the Days view.
+
+### New
+
+- **By epic in Days too** (Timeline). The Days view now has rows by epic as well: the same nesting, summary bars, and Expand all and Collapse all, with each story and task on its day. Still read-only, since the tree comes from Jira. *Where:* Timeline, Days, By epic (R).
+
+## 1.83.0 · Sep 30, 2026
+
+Timeline rows by epic.
+
+### New
+
+- **Rows by epic, nested** (Timeline). By epic puts one row per Jira epic, nested the way Jira's parent links nest, each with a bar spanning everything under it. Top epics open one level down; expand or collapse any row, or all of them. Work not under an epic sits on No epic, and a parent the sync didn't bring is named. It comes from Jira, so nothing drags there. *Where:* Timeline, Weeks, By epic (R).
+
+## 1.82.2 · Sep 30, 2026
+
+Jira stories by person, and keys that fit.
+
+### Fixed
+
+- **By person shows Jira stories** (Timeline). Each Jira story now sits on its assignee's row, in Weeks and Days, and counts toward what they have active. Unassigned stories go on Unassigned. An initiative carried by its stories no longer also sits on Unassigned. A plan run from Jira used to show almost nothing by person. *Where:* Timeline, By person.
+- **Jira keys no longer run into names** (Timeline). When a task or story is too short for its name, its Jira key moves into the label to its right instead of being cut off inside the bar. *Where:* Timeline, Days view.
+
+## 1.82.1 · Sep 29, 2026
+
+Senior review 16: safer bulk sorting.
+
+### Fixed
+
+- **Bulk sort never counts stories nobody picked** (Jira). Sorting stories only groups them into their epic's initiative when the Jira files list all of that epic's stories, and only the ones on that list. Otherwise each story goes on by itself, so an initiative never counts stories you didn't pick. A parent that isn't an epic is no longer treated as one. *Where:* Plan setup, Sort Jira work.
+- **Bulk sort respects what just changed** (Jira). Sorting a story from a parked epic brings the epic back with only that story. Every sort is decided again on the latest file, so a teammate's placement, epic link, parking or Not ours from a moment ago wins. Accept suggested is one save, so one Undo takes it all back, and number keys no longer also switch pages. *Where:* Plan setup, Sort Jira work.
+
+## 1.82.0 · Sep 29, 2026
+
+Plan setup, and fewer tabs for readers.
+
+### Improved
+
+- **Manage is now Plan setup, in four groups** (Plan). Manage is now Plan setup, and its 15 sections are grouped: Lists (Milestones, Gates, Decisions, Risks, Tags), Team (Team, Calendar, Meetings, Timeboxes & ceremonies), Jira (Sort Jira work, Proposals, Jira connection) and Reports (Status update, Snapshots, Activity). Jira work is now Sort Jira work, and Jira is Jira connection. Links to the old places still open. *Where:* Plan setup (was Manage).
+- **Fewer tabs while you're reading** (Plan). Someone only reading a shared plan sees Today, Timeline, Sprint and Roadmap, with People and Plan setup under More. Start editing and all six are back. The page you're on always keeps its tab. *Where:* The tabs.
+
+## 1.81.0 · Sep 29, 2026
+
+Today at a glance.
+
+### New
+
+- **A summary at the top of Today** (Today). Today now opens with a summary: what needs attention (to escalate, blocked, stale, late, should have started, decisions due; each jumps to its list), what's coming up (the next milestone and Jira release, and this quarter's deliverables with how many are at risk), and buttons to the Roadmap, Sprint and Timeline. The work queue follows below. *Where:* Today.
+
+## 1.80.0 · Sep 29, 2026
+
+A gentler first look.
+
+### Improved
+
+- **Clear next steps on an empty plan** (Timeline). Reconnecting a shared file is one clear button in the middle of the page. An empty shared plan you're reading says so and offers Start editing to set it up. An empty plan you're editing gets a short checklist (name it, name workstreams, add the first initiative, optionally bring in Jira and share it) that ticks itself off and goes away once there's work. *Where:* Timeline, on an empty or reconnecting plan.
+- **Quieter setup notes for readers** (Plan). Someone only reading a shared plan sees setup offers (like switching to Jira's sprints) as one quiet line, "1 setup note for whoever runs this plan · Show". Blockers, like reconnecting the file or recovering unsaved edits, still show in full, and editors see everything. *Where:* The notices under the header.
+
+## 1.79.0 · Sep 29, 2026
+
+Start with your page.
+
+### New
+
+- **Start with** (Plan). Choose the page Sightline opens on: Today, My work (Today, just yours), Timeline, Sprint, Team capacity or Roadmap, or where you left off. It's yours, in this browser; links and reloads still open where they point. *Where:* File, then Start with.
+
+## 1.78.0 · Sep 29, 2026
+
+What a story serves.
+
+### New
+
+- **Serves on story cards** (Sprint). A Sprint card now says which deliverable its story is for ("Serves Faster checkout"), when the deliverable links the story itself or its feature or epic, so developers see the customer-facing thing behind the work. *Where:* Sprint tab cards.
+
+## 1.77.0 · Sep 28, 2026
+
+Sort Jira work in bulk.
+
+### New
+
+- **Sort Jira work into the plan, in bulk** (Jira). Jira work now offers Sort them in bulk: everything in a sprint or your searches that isn't on the plan, grouped by epic, sprint, assignee or label. Pick whole groups or Shift-click a range, then drop on a workstream, click it, press its number, or use Move to. Accept suggested sorts each group to where its people already have work. *Where:* Manage, then Jira work.
+
+### Improved
+
+- **Stories from one epic become one initiative** (Jira). Stories you sort from the same epic become one initiative for that epic, with its other stories switched off, instead of one initiative per story: 70 stories under 10 epics are 10 initiatives. Dropping on an initiative adds them to it. Every drop is one save, with Undo. *Where:* Manage, then Jira work, Sort.
+
+## 1.76.0 · Sep 28, 2026
+
+Smoother everyday use.
+
+### Improved
+
+- **Before we commit: the sprint being planned, and a check before recording** (Sprint). Before we commit opens on the next sprint in the week before it starts, otherwise on the one running now. Recording a commitment while things are still flagged asks first and names them, so you can add an assumption. *Where:* Sprint tab.
+- **What changed at a glance** (Today). Today says how many things changed right under its heading, with a link to the list; past the first 12 plan changes, See all opens Activity. The time Jira is compared from is in the panel's header. *Where:* Today.
+- **Smaller touches** (Plan). Snapshot groups can show every item. The status update says when its draft was made. The Deliverables row keeps a Roadmap link when only broader ones exist, and reads out ship days. The amendment editor names items instead of ids. Amendments open faster: what a date change moves is only worked out while their panel is open. *Where:* Manage, Timeline, Roadmap.
+
+### Fixed
+
+- **The status line reads properly** (Saving). The status line ran the file's state into the buttons' labels ("revision 73Start editingSave as you go"). It now shows just the state: "Read-only · Team.json · saved 3:02 PM · revision 73". *Where:* The status line at the bottom.
+
+## 1.75.1 · Sep 28, 2026
+
+Senior review 15.
+
+### Fixed
+
+- **Safer handling of odd plan files** (Plan). A plan whose id is a reserved word gets a safe one, so it can't disturb the page's settings. If teammates' snapshots merge past the limit of 12, none are dropped (adding a new one still waits until there's room). *Where:* Opening and merging plans.
+- **Amendment edits you can trust** (Roadmap). Saving the editor no longer breaks an amendment that changes owners (owner lists aren't edited as text). If this browser can't store your edits, it says so and keeps the editor open instead of saying they were saved. Only recent batches' edits are kept. *Where:* Roadmap, Assistant amendments.
+- **check-amendments refuses NaN** (Sync). The offline checker now refuses NaN and Infinity in an amendments file, as the page does, instead of calling it ready. *Where:* The sync script.
+- **Smaller fixes** (Plan). A plan title can't add headings to the Markdown copy of a status update. A deliverable whose release ships before its Jira work's sprints now starts at its ship day on the Timeline, so the ship mark sits on its bar. *Where:* Status update; Timeline.
+
+## 1.75.0 · Sep 28, 2026
+
+Amendments for initiatives and tasks.
+
+### New
+
+- **Your assistant can amend initiatives and tasks** (Roadmap). Amendments can now add initiatives and tasks, and change their name, status, owners, workstream and dates. The review shows how many linked items a date change would move before you apply it. Jira-linked items keep Jira's status and dates (propose those in Jira instead), and dates that come from tasks can't be set directly. *Where:* Roadmap, Assistant amendments; the sync's check-amendments checks them too.
+
+## 1.74.0 · Sep 28, 2026
+
+Check amendments offline.
+
+### New
+
+- **check-amendments in the sync script** (Sync). The sync script can now check an amendments file against the plan without opening Sightline: python sightline-jira-sync.py check-amendments plan.json amendments.json. It uses the same rules as the page and lists each change as ready, changed since, invalid or already in the plan, with the reason; --json prints it for your assistant. The page still checks again when you apply. *Where:* The sync script; the guide in Export for your assistant says to use it.
+
+## 1.73.0 · Sep 28, 2026
+
+Edit an amendment before applying it.
+
+### Improved
+
+- **Edit your assistant's amendments** (Roadmap). Each waiting amendment now has Edit: fix a name, a target, the Jira keys or a proposal's value before you apply it. Your edits stay in this browser and are checked as strictly as the assistant's own; Apply writes the edited version. If your assistant rewrites that change, your edit stops applying and the change says so. Use the assistant's version puts it back. *Where:* Roadmap, Assistant amendments.
+
+## 1.72.1 · Sep 28, 2026
+
+Deliverables in the Days view.
+
+### Improved
+
+- **The Deliverables row in the Days view** (Timeline). The Deliverables row now shows in the Days view too, from the first working day of its linked Jira work's sprints, with its ship day marked. Click one to open it. *Where:* Timeline, Days view.
+
+## 1.72.0 · Sep 28, 2026
+
+Before we commit.
+
+### New
+
+- **A check before the sprint starts** (Sprint). The Sprint tab opens with Before we commit for the sprint about to start: its goal, points against the team's capacity, and what to look at: not estimated, not assigned, people with work who are out, assignees not on the team, sprint work not on the plan, gates during the sprint, and work outside its workstream's dates. *Where:* Sprint tab. Switch between this sprint and the next.
+- **Record sprint commitment** (Sprint). Record what the team took on (issues, points, capacity, and any assumption) in the shared file. Afterwards the check shows what changed since: points added, removed and re-estimated. *Where:* Sprint tab, Before we commit.
+
+## 1.71.0 · Sep 28, 2026
+
+Risks and decisions that move.
+
+### New
+
+- **Next action, waiting on, escalate by, who decides** (Plan). Decisions now have who decides, a next action, what they're waiting on and an escalate-by date; risks get the same, plus open or closed. The status update includes them. *Where:* Manage, then Decisions or Risks.
+- **An Escalate list** (Today). Today now opens with risks and decisions past their escalate-by date, and decisions past when they were needed: who decides, the next action, what it's waiting on, and how far over. Mine shows the ones you own or decide. The Today badge counts them. *Where:* Today.
+
+## 1.70.0 · Sep 28, 2026
+
+Status update.
+
+### New
+
+- **Prepare a status update** (Plan). A draft status update from the plan: On track, Changed, At risk, Decisions needed and Next milestone, with a suggested overall status. Edit any part, copy it as text or Markdown, and save a frozen copy to the shared file. The next update's Changed compares with the last saved one (or the newest snapshot). *Where:* Manage, then Status update.
+
+## 1.69.0 · Sep 28, 2026
+
+Snapshots.
+
+### New
+
+- **Snapshots to compare against** (Plan). Save a named snapshot of the plan ("Q4 commit") and compare today with it: what's later or earlier and by how many working days, what was added, removed or dropped, what finished, and which deliverables were retimed. Snapshots are in the shared file (up to 12), so everyone sees the same ones. *Where:* Manage, then Snapshots.
+
+### Improved
+
+- **Slip marks from any snapshot** (Timeline). Show slip on the Timeline makes a snapshot the baseline, so the Timeline's slip marks and summary compare with it by name ("Since Q4 commit: 3 slipped"). Set baseline still works as before. *Where:* Manage, then Snapshots; Timeline.
+
+## 1.68.0 · Sep 28, 2026
+
+What changed.
+
+### New
+
+- **What changed since your last visit** (Today). Today now opens with what changed: teammates' plan changes (yours are summed up) and Jira's (done, started, changed sprint, new, release dates moved). Choose your last visit, yesterday or this week. Jira is compared with a daily summary of earlier syncs that this browser keeps; nothing goes into the plan file. *Where:* Today, top of the right column. Click a line to open it.
+
+## 1.67.0 · Sep 28, 2026
+
+Deliverables on the Timeline.
+
+### New
+
+- **A Deliverables row** (Timeline). Planned and done deliverables with a quarter, a date or a Jira release now show in a row under Releases. Each spans its linked Jira work's sprints and shows its progress; a release or date marks its ship day, and one with no sprint dates yet is a faint band across its quarter. Broader ones (a half, a year, Later) stay on the Roadmap and are counted in the row's header. *Where:* Timeline, weeks view. Click one to open it.
+
+## 1.66.1 · Sep 28, 2026
+
+Jira's facts stay Jira's.
+
+### Fixed
+
+- **Saving no longer copies Jira's status and sprint dates into the plan** (Jira). A save used to write Jira's status and sprint dates into the plan file as if someone had edited them. They now stay on screen only: saves, drafts, backups, downloads and merges keep the plan's own values. Jira's facts are applied again on every draw, so when Jira stops covering an item, the plan's own values come back. *Where:* Saving, Unsaved changes, Download JSON.
+
+## 1.66.0 · Sep 28, 2026
+
+Quick updates draw once.
+
+### Improved
+
+- **One redraw per quick update** (Saving). A quick update used to redraw the page twice: once while it was applied and again once it was saved. It now redraws once, when the save is confirmed, including after a retry because a teammate saved at the same moment. *Where:* Quick updates: status, notes, updates.
+
+### Fixed
+
+- **A refused quick update no longer stays on screen** (Saving). When a quick update couldn't be saved (for example, it would push the plan over 2 MB), the page kept showing the change even though the file didn't have it. It now shows the file's version, with the reason in the status line. *Where:* Quick updates.
+
+## 1.65.0 · Sep 28, 2026
+
+Undo that costs almost nothing.
+
+### Improved
+
+- **Undo kept as change records** (Saving). Undo used to keep a full copy of the plan for every step; older steps are now kept as the few hundred bytes that undo them, so a long editing session uses a fraction of the memory. Each step is checked when it's stored; the rare one that can't be described that way keeps its copy, so undo and redo are always exact. *Where:* Undo and Redo.
+- **Bigger changes stay undoable from Activity** (Plan). Activity's Undo this now works for changes up to 96 KB (it was 16 KB), which covers a large Apply of assistant amendments. Anything bigger is listed as too big to undo from there, instead of the undo quietly disappearing. *Where:* Manage, Activity.
+
+## 1.64.0 · Sep 28, 2026
+
+How big is the plan?.
+
+### New
+
+- **Plan size** (Plan). Manage, Activity now shows how big the plan file is against the 2 MB a save can write, and what takes the most room (the change log, initiatives, deliverables, notes). Past 1 MB it warns that saves slow down on a synced drive; near 2 MB, that saves will stop. *Where:* Manage, Activity.
+
+## 1.63.0 · Sep 28, 2026
+
+Data checked.
+
+### New
+
+- **Know the numbers are complete** (Views). Today, Sprint, the Roadmap and release notes now show a Data checked line: when Jira last synced, issues found against each search's total, linked keys not found, pull requests read against the sprint's issues, and whether the two Jira files are from one sync. Green is complete; amber says what's partial; red means a late or held-back sync. Check opens Jira setup. *Where:* Today, Sprint, Roadmap, a release's notes.
+
+### Improved
+
+- **Copied notes say when data was partial** (Views). When the Jira data isn't complete, copied release notes end with the Data checked line, so whoever pastes them knows. When it is complete, the notes stay clean for customers. *Where:* A release's notes: Copy as text or Markdown.
+
+## 1.62.1 · Sep 28, 2026
+
+Senior review 13: amendments you can rely on.
+
+### Fixed
+
+- **Amendments keep working** (Views). An amendments file that hadn't changed stopped working after its next 30-second check; it now stays loaded. Clearing a date no longer fails, and a change applies on a copy first, so it never lands halfway. Reads don't overlap, a file that's too big is refused before it's read, and switching plans drops the other plan's file. *Where:* Roadmap, Assistant amendments.
+- **Hostile input is refused** (Saving). Amendment files can't use names that would change how the page works (like __proto__), odd values are refused rather than coerced, and link limits are enforced. Invalid wins over changed since. An add for an existing item must match everything it sets. Receipts follow what a change says, so an undone or rewritten change shows as Ready again. *Where:* Assistant amendments.
+- **One set of rules** (Views). Amendments now follow the same rules as editing a card: a target makes an idea Planned, no timing makes it an idea again, a release sets the quarter, and new wording needs approving again. Jira proposals from amendments record Jira's current value and use sprint and assignee ids, so they don't look stale at once. *Where:* Assistant amendments; Roadmap.
+- **Release notes and pull requests** (Views). Approvals are protected from older copies (they open the plan read-only), approval needs customer wording, and Markdown notes keep names as text. Merged pull requests are those updated this sprint, and a sprint with none says so. The export leaves notes out, lists linked Jira work first and says what it left out, and is there before a file is connected. *Where:* A release's card; Sprint; Assistant amendments.
+
+## 1.62.0 · Sep 28, 2026
+
+Amendments from your AI assistant.
+
+### New
+
+- **Your assistant's changes, reviewed first** (Views). Connect a personal amendments file that your AI assistant writes. The Roadmap shows how many are waiting, new ones as dashed Proposed cards, and a proposed mark on cards they'd change. Nothing touches the shared plan until you apply it. *Where:* Roadmap: Assistant amendments.
+- **Ready, Changed since, Needs attention** (Views). Each change is checked strictly and gets a result with a reason: Ready, Changed since (the plan moved after your assistant wrote it), Needs attention (something in it isn't allowed), or Completed. Apply one, or apply the ready ones as one quick update; each is checked again on the latest file as it saves, and Jira links merge by membership. Skip and Reopen are remembered. *Where:* The Assistant amendments panel.
+- **What your assistant reads** (Views). Export for your assistant saves a view of this plan's deliverables, workstreams, people, releases and targets, with the rules for writing amendments, an example, and a note to treat all names and notes as data. Version 1 covers deliverables (add, change fields, link or unlink Jira work) and Jira change proposals. *Where:* The Assistant amendments panel.
+
+## 1.61.0 · Sep 28, 2026
+
+Customer release notes.
+
+### New
+
+- **Release notes from your deliverables** (Views). A Jira release's card now shows its release notes: its deliverables grouped by New, Improved and Fixed, each in its customer wording. Final lists only Done deliverables whose wording is approved; Draft shows everything planned, marked where it isn't done or approved. Copy as text or Markdown, or print just the notes. *Where:* A Jira release's card.
+- **Approve the wording** (Views). A Done deliverable with a release has Approve for release notes, which records who approved it and when. Changing its name, customer wording or kind clears the approval, so the notes always use approved words. Its badge says Approve for notes until then, then In release notes. *Where:* A deliverable's card; Roadmap.
+
+## 1.60.0 · Sep 28, 2026
+
+Pull requests: what's done and what's left.
+
+### New
+
+- **Active, Merged and Drafts** (Views). Sprint's pull requests widget switches between Active (waiting for review: what's left), Merged this sprint (what's done), and Drafts. The sync now reads pull requests for the sprint's done issues too (reusing them for hours, since they rarely change), so merged ones show. *Where:* Sprint, Pull requests; sightline-jira-sync.py.
+
+### Improved
+
+- **A clearer idea form** (Views). The Roadmap's quick add now labels its fields, New idea and From. From is optional, suggests your meetings, and remembers the last one you used in this plan; it no longer guesses today's meeting. *Where:* Roadmap.
+
+## 1.59.2 · Sep 28, 2026
+
+Draft pull requests stay out of the way.
+
+### Fixed
+
+- **Only active pull requests** (Views). Sprint's Open pull requests now lists active ones only; drafts (marked by Bitbucket, or titled Draft: or WIP) are hidden, with Show drafts to see them, marked Draft. Card PR counts and the PR waiting 3+ days filter leave drafts out too. *Where:* Sprint, Open pull requests; sightline-jira-sync.py.
+
+## 1.59.1 · Sep 28, 2026
+
+Senior review 12: deliverables you can trust.
+
+### Fixed
+
+- **Linked Jira work is synced** (Jira sync). The sync now fetches Jira work linked to a deliverable even when it isn't on the board or in a search, so its progress and its epics' stories show. *Where:* sightline-jira-sync.py.
+- **Honest progress** (Views). A deliverable's progress uses the team's status mapping for epics too, says "about" (≈) when some stories are counted through their epic, and says how many linked issues weren't in the last sync, instead of showing 0/0. *Where:* Roadmap; a deliverable's card.
+- **Split, delete and owners are safe to share** (Saving). Split builds its parts from the latest file and carries the release and date too; the original stays findable, lists its parts, and can move its Jira links to one. Delete stops if someone changed it since you opened it. Owners on a deliverable are a quick update, like its other fields. *Where:* A deliverable's card.
+- **Limits refuse instead of dropping** (Saving). More deliverables or Jira links than a plan keeps are refused with a message, instead of vanishing on reload, and a plan with two deliverables sharing an id isn't opened. Chart drags' undo steps now stay within the undo memory budget. *Where:* Roadmap; Timeline.
+- **Smaller fixes** (Views). Capacity says whose load is unknown (no Jira user) instead of counting them as within. An idea's From is remembered per plan. Many ideas get one When picker each. The Jira key box suggests as you type. A deliverable deleted elsewhere closes its panel. Timeboxes wording is consistent. *Where:* Sprint, Capacity; Roadmap; Manage, Timeboxes.
+
+## 1.59.0 · Sep 28, 2026
+
+Roadmap and deliverables.
+
+### New
+
+- **A Roadmap of deliverables** (Views). A new Roadmap tab (key 6) shows what we plan to ship, by workstream and time. The columns get coarser further out (this quarter, next quarter, halves, a year, Later), and a broad target is a wide card that narrows as you sharpen it. Drag a card to another time or workstream, or onto a Jira release to tie it to that release. *Where:* Roadmap.
+- **Ideas in one line** (Views). + Add idea takes just a name, stamped with the meeting it came from (today's meeting by default), and lands in Ideas to sort. One click picks when it might ship. It's a quick update, so anyone can add ideas during the meeting without Start editing. *Where:* Roadmap.
+- **Deliverables** (Views). A deliverable is something we'll ship, in words a customer would understand: a name, release-note wording, a kind (New, Improved, Fixed), a target that sharpens from a year to a quarter to a Jira release or date, a workstream, owners, tags and notes. Stages are Idea, Planned (automatic once it has a target), Done and Dropped (with a reason). *Where:* Roadmap; a deliverable's card.
+- **Deliverables link to Jira work** (Jira). Link one or more Jira issues, features or epics to a deliverable, and progress rolls up ("3 of 5 linked Jira issues done"), counting each issue once. In Manage, Jira work, pick epics or stories and choose Group into a deliverable. Links never change Jira. *Where:* A deliverable's card; Manage, Jira work.
+- **Badges and nudges** (Views). Cards show In Jira, Needs detail (with the reason, such as pick a quarter as it comes into view, add an owner, link the Jira work), At risk (past its target, or little done close to it) and Ready for release notes (Done, with its Jira release). Split turns a broad deliverable into smaller ones. *Where:* Roadmap.
+
+## 1.58.0 · Sep 28, 2026
+
+Clearer names: Sprint, Manage, Jira work.
+
+### Improved
+
+- **Sprint and Manage** (Views). The Cards tab is now Sprint: the current Jira sprint's work. The Plan tab is now Manage: Jira work, the team, the lists and setup. Keys 1 to 5 still go to the same places. *Where:* The tabs.
+- **Jira work and Timeboxes** (Plan). In Manage, Epics is now Jira work (it holds stories too), and Sprints is now Timeboxes: Jira's sprints, then the plan's own timeboxes after them, each marked Jira sprint or Plan timebox. *Where:* Manage.
+- **All sources, Jira only, Jira + mine** (Views). The layer buttons now say what they show: All sources (Jira and everything added here), Jira only, and Jira + mine (Jira plus what you added). Mine elsewhere means work assigned to you or owned by you. *Where:* The toolbar.
+- **One meaning of release** (Plan). Release means a Jira release. The Scrum pack's release block is now Release day (a plan that already has Release keeps it), and What's new is What's new in Sightline, so it isn't mistaken for your own release notes. *Where:* Manage, Timeboxes; What's new.
+
+## 1.57.3 · Sep 28, 2026
+
+A compact capacity widget.
+
+### Improved
+
+- **Capacity takes less room** (Views). With more than 8 people, Capacity lists only who's over or close to capacity, with a line per sprint (for example, 1 over, 2 close, 12 within) and Show all to see everyone; your choice is remembered. Once the team capacity is set it's one line with Change, and rows are tighter. *Where:* Cards, Capacity.
+
+## 1.57.2 · Sep 28, 2026
+
+The page is now sightline.html.
+
+### Improved
+
+- **The page file is named sightline.html** (Saving). The shared page is now sightline.html, with sightline.html.sha256 beside it, and the copy instructions say so. Your saved settings, who you are and your linked plan carry over; nothing needs setting up again. *Where:* The page file; the damaged-copy message.
+
+## 1.57.1 · Sep 27, 2026
+
+Senior review 11: Saved means saved.
+
+### Fixed
+
+- **Save as you go says Saved only when it saved** (Saving). A change a rule refuses (like a workstream blackout) stays unsaved on screen instead of being reported saved. If a teammate deleted what you changed, your version downloads as a backup. When a teammate starts editing, your change waits and says so. After a failed save it waits longer before each retry. *Where:* Save as you go.
+- **Nothing doubles or overwrites in a race** (Saving). Two people adding team capacity on different dates both keep theirs. Putting stories or epics on the board, and setting team capacity, are worked out again on the latest file when someone saves at the same moment, so a story is never placed twice. *Where:* Cards, Capacity; Plan, Epics.
+- **Bulk stories keep your picks** (Jira). Picked stories stay picked while you filter, and the bar says how many are hidden by the filter. Pick all says how many it picks, including any beyond the 300 listed. If a bulk save doesn't land, the stories stay picked. The Epics filter redraws after a short pause, which keeps big lists fast. *Where:* Plan, Epics.
+- **Cards and capacity read right** (Views). Someone at 0% (or away all sprint) with assigned work shows against zero, as over. The team capacity figure can be removed, and Set never sticks on Saving. Jira work assigned to someone not linked here gets a row with their name and a Link action. Pull requests say when coverage was partial even with none found, and when the list is cut to 100. *Where:* The Cards tab.
+- **Faster with big teams** (People). Jira user pickers show their best few choices and fill in the rest when opened, instead of building tens of thousands of options. Today's count no longer searches every task for each task on every keystroke. *Where:* Plan, Team; People; Today.
+- **The pull request time limit holds** (Jira sync). After its two-minute limit, the sync keeps earlier pull request data, even if old, instead of asking Jira again, and it checks every page in the plan's folder for a newer Sightline. *Where:* sightline-jira-sync.py.
+
+## 1.57.0 · Sep 27, 2026
+
+Put many stories on the board at once.
+
+### New
+
+- **Put many stories on the board at once** (Jira). In Plan, Epics, stories in a sprint with no epic now have checkboxes and Pick all. Put the picked stories on one workstream, or each on its suggested workstream (where its assignee already has work), in one save. Stories with no suggestion stay picked so you can place them next. *Where:* Plan, Epics, In a sprint, not on the board.
+
+## 1.56.1 · Sep 27, 2026
+
+Pull requests show their repository.
+
+### Fixed
+
+- **A Repository column for pull requests** (Views). The pull request list on Cards has a Repository column (project/repo). The sync takes it from Jira's development panel, the target repository, or the pull request's Bitbucket address, so it shows even when Jira leaves the name out; files synced before this get it from the address too. *Where:* Cards, Open pull requests; sightline-jira-sync.py.
+
+## 1.56.0 · Sep 27, 2026
+
+Senior review 10: safer saving, truer capacity.
+
+### Fixed
+
+- **Save as you go never loses an edit** (Saving). If a Save as you go write fails, your edit stays on screen and unsaved, and it tries again. Turning it off saves any pending change first. A field left focused still saves after a pause. If a teammate changed the same thing since you started, yours is saved and theirs downloads as a backup. *Where:* Save as you go.
+- **Merges are careful** (People). Merging changes only fields that hold people, never text that happens to match. If someone saves at the same moment, the merge is worked out again on the latest file, so new work isn't left with a missing owner. Merging away yourself keeps you as the person kept. Two Jira users with the same name are never offered as duplicates, and Merge all lists any Jira link it drops. *Where:* Plan, Team; a person's card.
+- **Capacity counts what it should** (Views). Team capacity now saves and merges like other changes. A company holiday takes a day off everyone's share, and a figure dated mid-sprint applies to that sprint. With a team figure, people without a Jira user are shown too. Each heat-map cell says in words whether it's within capacity or over, for screen readers. Deactivating counts open work Jira assigns them. *Where:* Cards, Capacity.
+- **Cards and burndown, more honest** (Views). The burndown notes work added since the sprint started and doesn't count it as slipping, and an overdue sprint's last day uses resolved dates. A person filter keeps their Jira issues that aren't on the plan. Pull requests say when they were read for only some issues. Focus stays on the control you used, and with no Jira sprint yet one line says what to set up. *Where:* The Cards tab.
+- **Read-only quick controls work** (People). Allocation, team capacity and Jira linking in Plan, Team stay usable when you're not editing, as quick updates. Team and Jira users are drawn only when shown, which keeps large teams fast. *Where:* Plan, Team; People.
+- **Faster, clearer sync extras** (Jira sync). Reading pull requests stops after two minutes and records how many issues it covered. The newer-page check looks only at .html files. If the newer page has another name, the banner says to open that file instead of offering a refresh that wouldn't get it. *Where:* sightline-jira-sync.py; the banner.
+
+## 1.55.0 · Sep 27, 2026
+
+Team capacity, with allocation.
+
+### New
+
+- **Team capacity, set from a date** (Views). Set one figure for the team, points per person per sprint, and change it from a date when it changes. Each person's share is that figure times their allocation, less time off and holidays in the sprint. Each sprint column shows the figure in force. Plans without one still use each person's own points per sprint. *Where:* Cards, Capacity; Plan, Team.
+- **Allocation** (People). Give someone who's partly on the team an allocation (for example 50%); their share of capacity follows it. Left blank, it follows their days per week. Set it in Plan, Team or right in the Capacity widget, without Start editing. *Where:* Plan, Team; Cards, Capacity.
+
+## 1.54.1 · Sep 27, 2026
+
+Open a person from Plan, Team.
+
+### Fixed
+
+- **Names in Plan, Team open the person's card** (People). In Plan, Team a name now opens that person's card (Jira user, Merge into, Deactivate). While editing, an Open link sits beside the name box. *Where:* Plan, Team.
+
+## 1.54.0 · Sep 27, 2026
+
+Knows when there's a newer Sightline.
+
+### New
+
+- **A newer Sightline? Refresh safely** (Saving). The page now says when a newer Sightline is available: a teammate saved the plan with a newer version, or the Jira sync found a newer page in the plan's folder. Refresh saves your unsaved edits first and ends editing; if the save fails or you cancel, the page stays open with your edits. *Where:* The banner at the top.
+- **The sync spots a newer page** (Jira sync). Each sync notes the newest Sightline page among the .html files in the plan's folder (only its version stamp and file name), so an open page can offer to refresh. *Where:* sightline-jira-sync.py.
+
+## 1.53.0 · Sep 27, 2026
+
+Cards is Jira's sprint; outside owners.
+
+### New
+
+- **Outside owners** (People). Add a team, vendor or group (like Platform team) as an outside owner. It can own anything and be waited on, but has no capacity, time off or sprint load. Any owner field can pick one or add one on the spot, Waiting on lists them, and they get a row by person while they own open work. *Where:* Plan, Team, Outside owners; any Owner field; Mark blocked.
+
+### Improved
+
+- **Cards shows Jira's work only** (Views). Cards now shows the active Jira sprint's issues, including ones not placed on the plan (marked Not on the plan; they open in Jira). Plan-only tasks and initiatives are left off, with a note that they're on Today and the Timeline. *Where:* The Cards tab.
+
+## 1.52.0 · Sep 27, 2026
+
+Merge duplicate people; faster linking.
+
+### New
+
+- **Merge duplicate people** (People). If you typed a first name and later added the same person from Jira with their full name, merge them: their work, notes, blockers, meetings, groups, views, history, time off, capacity and Jira link move to the one kept, and the duplicate is removed. Plan, Team lists likely duplicates with Merge all; any person's card has Merge into. *Where:* Plan, Team; a person's card.
+- **Link all suggested at once** (People). People, Jira users has Link all suggested, which links every suggested match in one save instead of one save each. Link, Unlink and Add to team buttons now show that they're working as soon as you click. *Where:* People, Jira users.
+
+### Fixed
+
+- **Stopping a watch frees it at once** (Jira sync). Ctrl+C on watch now gives back its lock, so starting a new watch works straight away instead of saying one is already running. When one really is running, the message says which process, when it last checked in, and that it may be the minimized window that starts at sign-in. *Where:* sightline-jira-sync.py watch.
+
+## 1.51.0 · Sep 27, 2026
+
+Deactivate people.
+
+### New
+
+- **Deactivate someone who left the team** (People). Deactivate a person from Plan, Team or their card. They keep their history (past owners, notes, their Jira link) but leave owner pickers, Cards rows, load, capacity and meetings' Everyone. While they still own open work, they keep a row by person, flagged so it gets reassigned. Reactivate any time from Team, Inactive. *Where:* Plan, Team; a person's card.
+
+## 1.50.0 · Sep 27, 2026
+
+Cards reads at a glance; add sprints through a date.
+
+### New
+
+- **A sprint header you can read at a glance** (Views). Cards now opens with the sprint's name (without the dates in it), its dates, tiles for to do, in progress, done and blocked, and a bar for how far in it is. The burndown leads with points left and how far ahead of or behind the ideal line you are, and marks Today. *Where:* The Cards tab.
+- **Capacity as a heat map** (Views). Capacity is now a heat map: each cell is shaded by load against what the person can take (under 70%, on target, over, 30%+ over), or by relative load where that isn't set. Numbers no longer repeat "pts", and setting points per sprint is a quick update. *Where:* Cards, Capacity.
+- **Add sprints through a date** (Plan). Pick a date under the sprint list and Sightline adds sprints of the default length, named on from the last one, until one reaches it. It says how many it will add before you click. *Where:* Plan, Sprints.
+- **Link Jira users without Start editing** (People). Linking a person to their Jira user, or adding a Jira user to the team, is now a quick update that works read-only. The Team tab has a Jira user column to link from there too, and capacity's unlinked row links straight to People. *Where:* Plan, Team; People, Jira users; a person's card.
+- **The demo shows releases, pull requests and burndown** (Demo). tools/make-demo.py now writes Jira releases, pull requests from the development panel, burndown notes, created, updated and comment dates, and points per sprint, so every Cards widget and the release cards show without a Jira. *Where:* tools/make-demo.py.
+
+### Fixed
+
+- **Clearer sprint days, tidier lists** (Views). "5 of 10 days in" now reads "working day 5 of 10", or "5 of 10 working days done" on a weekend or holiday, and the top bar follows Jira's active sprint as Cards does. A release's issue list is one left-aligned line each, and the Jira users table fits its content. *Where:* The top bar, Cards, a release's card, People.
+
+## 1.49.1 · Sep 27, 2026
+
+Cards widgets line up.
+
+### Fixed
+
+- **Burndown, capacity and pull requests as widgets** (Views). On Cards, the burndown, capacity and pull requests are now widgets of one shape in one grid: aligned, with the same header, and the chart fills its widget instead of floating in a wide box. *Where:* The Cards tab.
+- **One sprint, and the right points left** (Views). Cards now follows Jira's active sprint, as the burndown does, instead of the plan's own sprint dates. Points left counts stories that are done now as done, even without a resolved date. *Where:* The Cards tab.
+
+## 1.49.0 · Sep 27, 2026
+
+Pull requests from Bitbucket.
+
+### New
+
+- **Pull requests on Cards** (Jira). Cards now has an Open pull requests panel for the sprint's open work: each PR's repository, author, when it was last updated and how many reviewers approved, oldest first, with the ones waiting 3+ days called out. Cards can show a PRs field, and a quick filter finds work with a PR waiting. *Where:* The Cards tab.
+
+### Improved
+
+- **A Jira item's pull requests** (Jira). A Jira item's card now lists its pull requests, with links to Bitbucket. *Where:* A Jira item's card.
+- **The sync reads pull requests** (Jira sync). For the active sprint's open work, the sync reads pull requests from Jira's development panel, with your Jira token: no Bitbucket token or setup. It rereads at most every 30 minutes, and stops asking if your Jira has no development panel. Copy the updated sightline-jira-sync.py. *Where:* sightline-jira-sync.py.
+
+## 1.48.0 · Sep 27, 2026
+
+Save as you go.
+
+### New
+
+- **Save as you go** (Saving). Turn on Save as you go (in the bar above the timeline) to edit without Start editing: each change saves on its own a moment after you stop, and teammates' changes merge in, the way quick updates do. Two people can edit at once. Undo works on what's saved. It waits while someone else has Start editing. It's per person, in this browser; turn it off to go back to Start editing. *Where:* The bar above the timeline.
+
+## 1.47.0 · Sep 27, 2026
+
+Review: smoother, safer, clearer.
+
+### Improved
+
+- **Smaller touches** (Views). Saved card views keep the layout and leave your quick filters yours. Fit covers gates and releases. Releases are in Find and their issues open. Move its work checks first and says what doesn't fit. Pasted tags save as one change. Activity shows the newest 50 at a time. The parked note returns when different work is parked. New Year's observed on Dec 31 is included. *Where:* Throughout.
+
+### Fixed
+
+- **Nothing lost in a merge or an older copy** (Saving). Saved card views now merge with a teammate's save instead of being dropped, and come back with Put them back. A saved view's zoom and an edited update are named for older copies, so those open the plan read-only instead of dropping them. *Where:* Saving with teammates.
+- **Blackouts hold, and typing is light** (Timeline). A change that the automatic scheduling would push into a workstream's blackout is refused. Typing a title no longer reschedules the plan or redraws the timeline: the chart's label updates as you type. *Where:* The timeline.
+- **Scrolling doesn't redraw** (Timeline). Workstreams leaving or entering the dates on screen are shown and hidden in place as you scroll, without redrawing the timeline. *Where:* The timeline, zoomed in or in Days.
+- **Sprints and numbers you can trust** (Jira). A long gap before Jira's first sprint no longer pulls Jira's sprints earlier. Abandoned work is left out of the burndown and capacity, and said; the sync reads statuses the way the plan does. Capacity names work assigned to people not linked here. Cards uses Jira's active sprint when the plan's sprints don't cover today. *Where:* Use Jira's sprints, and Cards.
+
+## 1.46.0 · Sep 27, 2026
+
+Card views, quick filters and aging.
+
+### New
+
+- **Card views** (Views). Lay out Cards by person, workstream or epic, and pick what each card shows: points, epic, how old it is, when it was last updated, and when it last got a comment, from Jira. Save a layout as a view for the team. *Where:* The Cards tab.
+- **Quick filters** (Views). Narrow the cards with quick filters, like Jira's: mine, unassigned, blocked, not estimated, updated in 2 days, no update in 7+ days, or one person's. They're yours, separate from the saved layout, and the board says how many they hide. *Where:* The Cards tab.
+
+### Improved
+
+- **The sync reads last comments** (Jira sync). For the issues on Cards (this and coming sprints) the sync reads when each last got a comment, in small batches. Copy the updated sightline-jira-sync.py; no new options. *Where:* sightline-jira-sync.py.
+
+## 1.45.0 · Sep 27, 2026
+
+Sprint burndown and capacity in points.
+
+### New
+
+- **Sprint burndown** (Views). Cards now shows a burndown for the active Jira sprint: points left each working day against the ideal line, with today marked. It uses each story's resolved date, and the sync's daily notes where it has them, which also show scope added mid-sprint. It says how many stories aren't estimated. *Where:* The Cards tab.
+- **Capacity, in points** (Views). A capacity grid shows each person's points in Jira for this and the next sprints against their points per sprint, less their time off and holidays; over is red. Set each person's points per sprint right in the grid. *Where:* The Cards tab.
+
+### Improved
+
+- **The sync keeps a daily burndown note** (Jira sync). Each sync notes the active sprint's points in scope and points left for the day, and reads each issue's created and resolved dates. Copy the updated sightline-jira-sync.py; no new options. *Where:* sightline-jira-sync.py.
+
+## 1.44.0 · Sep 27, 2026
+
+Workstream blackouts.
+
+### New
+
+- **Blackouts outside a workstream's dates** (Timeline). Before a workstream starts and after it ends is now a striped blackout. Making or moving the plan's own initiatives, tasks or milestones into it is refused with the reason, and the + to add doesn't appear there. Work already there when you set the dates stays, shown in the blackout. *Where:* Workstreams with start or end dates.
+
+### Improved
+
+- **Jira work and a workstream's dates** (Jira). An epic put in a workstream that hasn't started lands at its start, and you're told when its stories' sprints fall outside the workstream's dates. Proposing a sprint outside them says so too; Jira's sprints win. *Where:* Plan, then Epics, and proposals.
+- **Workstreams follow what's on screen** (Timeline). Zoomed in or in Days, a dated workstream shows while any of its dates are on screen, and the note counts the ones that aren't, as you scroll. *Where:* The timeline.
+
+### Fixed
+
+- **Scrolling stays put** (Timeline). The timeline no longer jumps back to the start when it redraws while you're scrolled sideways, and the details pane now scrolls to its end without scrolling the page first. *Where:* The timeline and the details pane.
+
+## 1.43.1 · Sep 27, 2026
+
+The details pane scrolls to the end.
+
+### Fixed
+
+- **The details pane scrolls to the end** (Timeline). On a wide screen the details pane on the right was taller than the window under the toolbar, so its last fields couldn't be reached. It now fits below the toolbar and scrolls to the bottom. *Where:* The details pane.
+- **A clearer note about parked initiatives** (Timeline). The note above the timeline now says what parked means (switched off for now; nothing is lost), with Review parked, which opens Plan, then Epics at the Parked list, and Don't show this again, until another one is parked. *Where:* The note above the timeline.
+
+## 1.43.0 · Sep 27, 2026
+
+Titles as you type, and where you are.
+
+### Improved
+
+- **The sync says what releases it read** (Jira sync). The sync's console now lists how many releases it read and from which projects, and any it couldn't read. Copy the updated sightline-jira-sync.py. *Where:* sightline-jira-sync.py.
+
+### Fixed
+
+- **New items show their title as you type** (Timeline). When you add an initiative, task, milestone or gate from the timeline, its title on the chart now follows what you type in its card, instead of saying New initiative until you click away. Made while filtering to a tag, it gets that tag, so it stays where you made it. *Where:* Adding from the timeline.
+- **The pager says what's on screen** (Timeline). Next to ‹ and ›, the timeline now shows the dates on screen as you scroll, and Today is its own button (greyed out while today is in view), in Weeks and Days. *Where:* The corner of the timeline.
+
+## 1.42.0 · Sep 27, 2026
+
+Links to everything, and Back.
+
+### New
+
+- **Back and Forward work** (Views). The browser's Back and Forward now step through where you've been: tabs, Plan tabs and the items you opened. Zooming and filtering update the place without adding steps. *Where:* The browser's Back and Forward.
+- **A link to anything** (Views). The page's address now says exactly where you are: the tab, the open item, the zoom, the filters and the layer. Open that link and you land in the same place; an item opens only in the plan it belongs to. Each item's card has Copy link. *Where:* The address bar, and Copy link on item cards.
+
+## 1.41.0 · Sep 27, 2026
+
+Jira releases on the timeline.
+
+### New
+
+- **Jira releases on the timeline** (Jira). The sync now brings in your projects' releases (Jira's versions) with their dates, and which release each issue is in. The timeline shows the releases dated in the plan, from Jira and read-only; ones past their date and not released are marked. Click one for its dates and how its issues are going. *Where:* The Releases row on the timeline.
+
+### Improved
+
+- **Each Jira item names its release** (Jira). A Jira item's card now says which release it's in, with that release's date. *Where:* A Jira item's card.
+- **The sync reads releases** (Jira sync). The sync reads each project's releases (read-only) and each issue's fix version. A project it can't read is skipped, not fatal. Copy the updated sightline-jira-sync.py. *Where:* sightline-jira-sync.py.
+
+## 1.40.0 · Sep 27, 2026
+
+Standup is now Cards.
+
+### Improved
+
+- **Standup is now Cards** (Views). The Standup tab is renamed Cards, since the board of cards is for more than standups. It works the same: this sprint's work by person, key 5. *Where:* The Cards tab.
+
+## 1.39.0 · Sep 27, 2026
+
+Days off in ranges, and US holidays.
+
+### New
+
+- **Days off as a range** (Plan). Add company days off as a range with a name (Winter shutdown, Dec 24 to Jan 2): each working day in it becomes a holiday, and the table shows the range as one row you can rename or remove together. *Where:* Plan, then Calendar.
+- **US federal holidays in one click** (Plan). + US federal holidays adds the eleven federal holidays that fall in the plan's dates, on the weekday they're observed. Remove any your company doesn't observe. *Where:* Plan, then Calendar.
+
+## 1.38.0 · Sep 27, 2026
+
+See which work changes sprint.
+
+### Improved
+
+- **Which work changes sprint** (Jira). Before you switch the plan to Jira's sprints, it lists the plan's own initiatives and tasks that will land in a sprint with other dates (Jira's S16 starts a week later than the plan's did, say). Their dates never change. A sprint that's only renamed isn't counted. The sprints banner says how many. *Where:* Plan, then Jira, and the sprints banner.
+
+## 1.37.0 · Sep 27, 2026
+
+Jira setup moves to Plan.
+
+### Improved
+
+- **Plan, then Jira** (Jira). The settings gear next to File is gone. Jira setup (the Jira folder, how the sync runs, your searches, the board's sprints and how Jira's statuses show here) is now a tab under Plan, next to Epics. File, then Jira status, and every Jira settings link go there. The plan's own dates stay under File, then Plan settings. *Where:* Plan, then Jira.
+
+## 1.36.0 · Sep 27, 2026
+
+Make tags as you type.
+
+### Improved
+
+- **Make tags as you type** (Plan). The tag box now suggests matching tags as you type, with Create tag at the end when the name is new. Enter or a comma adds it, a pasted list like "a, b, c" adds each, and the arrow keys move through the suggestions. The box stays ready for the next tag. *Where:* Tags on any item's card.
+
+## 1.35.0 · Sep 27, 2026
+
+Edit and delete updates.
+
+### New
+
+- **Edit and delete updates** (Plan). Each update on an initiative or task now has Edit and Delete. Your own change straight away; someone else's asks first. An edited update says who edited it and when, and deleting takes a second click. Both save as quick updates and can be undone. *Where:* The Updates list on an item's card.
+
+## 1.34.0 · Sep 27, 2026
+
+Remove a workstream without losing work.
+
+### Improved
+
+- **End a workstream, or move its work** (Plan). A workstream's card now says what it holds, and offers End it today or End when its work ends (nothing is deleted; it fades after that date), or Move its work to another workstream, keeping every item's dates, notes and links, then removing it. Undo puts it back. *Where:* A workstream's card.
+
+### Fixed
+
+- **No more deleting work with a workstream** (Plan). Deleting a workstream used to delete its initiatives, tasks and notes, and clear its milestones' dates. Now only an empty workstream can be deleted; one with work in it is ended or moved instead. *Where:* A workstream's card.
+
+## 1.33.0 · Sep 27, 2026
+
+Zoom by sprints, and Fit.
+
+### New
+
+- **Zoom by sprints, in Weeks and Days** (Timeline). Use − and + (or the − and + keys) to show one sprint more or fewer, the same way in Weeks and Days, and the same number when you switch. Zoomed in, Weeks scrolls sideways with the workstream names pinned, and has Today and paging. *Where:* The corner of the timeline.
+- **Fit follows your filters** (Timeline). Zoom all the way out to Fit: the timeline frames exactly the work your filters show, from where it starts to where it ends. Filter to one feature and Fit snaps to it; change the filter and it snaps back out. *Where:* The timeline's zoom.
+
+### Improved
+
+- **Saved views keep their zoom** (Views). A saved view remembers how many sprints it shows. Views saved before keep their Days zoom, as the nearest number of sprints. *Where:* Views.
+
+## 1.32.0 · Sep 27, 2026
+
+Workstreams with start and end dates.
+
+### New
+
+- **Workstreams can start and end** (Timeline). Give a workstream a start or end date in its card (a workstream that starts in 2027, say). Outside those dates its row fades, with the date at the edge, so it's clear what's happening as you scroll. Leave both empty and nothing changes. *Where:* A workstream's card, and the timeline in Weeks and Days.
+- **Out of view, and counted** (Timeline). A workstream the dates on screen don't reach isn't drawn, and the note above the timeline says which one and when it starts, with Show anyway. Work dated outside its workstream's dates says so in its card. *Where:* The timeline and item cards.
+
+### Improved
+
+- **Pickers know when a workstream starts** (Jira). Workstream pickers list the ones that haven't started last, with their start date. *Where:* Plan, then Epics.
+- **Older copies stay safe** (Saving). A plan with workstream dates opens read-only in an older Sightline, so it can't drop them. *Where:* Opening the plan in an older copy.
+
+## 1.31.1 · Sep 27, 2026
+
+Use Jira's sprints saves.
+
+### Fixed
+
+- **Use Jira's sprints is saved right away** (Jira). Switching to Jira's sprints from the banner started editing and changed the plan, but left it unsaved, so a refresh undid it and the banner asked again. It now saves as part of the switch, and says how many sprints came from Jira and how many more follow Jira's schedule. *Where:* The sprints banner, and Settings.
+
+## 1.31.0 · Sep 27, 2026
+
+Sprints follow Jira's schedule past its last sprint.
+
+### Improved
+
+- **After Jira's last sprint, Jira's schedule** (Jira). When the plan runs past Jira's last dated sprint, Use Jira's sprints carries on with Jira's own schedule: sprints as long as Jira's usually are, numbered on from Jira's last (S15, then S16, S17), to the plan's end. The plan's goals for those weeks stay, and a named sprint like Hardening keeps its name. *Where:* Use Jira's sprints.
+
+### Fixed
+
+- **Sprint numbers, not dates** (Jira). A Jira sprint named with its dates, like Sprint 15 03/02-03/13, no longer makes the next sprints 3/14 and 3/15; they're S16 and S17. *Where:* Use Jira's sprints.
+- **The sprint header stays on top** (Timeline). Meetings, gates and process blocks no longer draw over the sprint names and dates as you scroll down the timeline. *Where:* The timeline header.
+
+## 1.30.1 · Sep 27, 2026
+
+Gates and milestones open on click.
+
+### Fixed
+
+- **Clicking a gate or milestone opens it** (Timeline). In edit mode, a click that moved the pointer a few pixels was taken as a tiny drag, so nothing opened. A drag that ends on the same day is now a click, and a drag starts a little later. Dragging to another day still moves it. *Where:* Gates, milestones and notes on the timeline.
+
+## 1.30.0 · Sep 27, 2026
+
+Safer undo, one editor per tab, nothing lost from the sprint list.
+
+### Improved
+
+- **In a sprint, not on the board** (Jira). The group is renamed, parked initiatives come back where they were (no pick box), the Plan badge counts exactly what it lists with units, and after Put on the board a note offers Show on the timeline. Rows stack on a phone. *Where:* Plan, then Epics, and the Plan badge.
+- **Standup counts its own hidden work** (Views). Standup says how many of this sprint's items your view or filters hide, with Show everyone's or Clear filters. Every count names its unit, and opening a card moves focus to its details. *Where:* The Standup tab.
+
+### Fixed
+
+- **Undo never removes a teammate's work** (Saving). Undoing an add leaves the item if a teammate changed it since; putting something back skips it if that id is in use again. Undo never rewrites who last edited something. It says how many it left alone. *Where:* Undo after quick updates.
+- **A duplicated tab doesn't share the edit lock** (Saving). Tabs check with each other before opening the plan. A copy of a tab that's editing becomes view-only, even if it opened the file first, and says so. *Where:* Duplicating a tab while editing.
+- **The sprint list loses nothing** (Jira). Sprint stories whose parent isn't in the Jira files are listed with a note, and stories under an epic under another epic group under the top one. The sync now sends each epic's sprint stories even before it's on the board. Copy the updated sightline-jira-sync.py. *Where:* Plan, then Epics.
+- **Nested epics and features count once** (Jira sync). An epic under another epic keeps its own count and adds to the top one; it's never counted as a story. A feature that holds stories frees its place in the story list and no longer stretches its epic's sprint dates. *Where:* sightline-jira-sync.py.
+- **Sprints banner and proposals** (Jira). Not now on the sprints banner is remembered per plan until the next sync; the switch applies only to the plan it was shown for, and only says it worked when it did. Proposals are checked against the Jira server they were made on in every file. *Where:* The sprints banner and proposals.
+
+## 1.29.1 · Sep 27, 2026
+
+Jira's sprint names, and tidy rows.
+
+### Improved
+
+- **Use Jira's sprints, from a banner** (Jira). When the synced board's sprints differ from the plan's own (S0, S1…), a banner says so with Use Jira's sprints one click away, starting editing first if needed. See the change first opens the side-by-side table; Not now hides it until the page reloads. *Where:* The banner under the toolbar.
+
+### Fixed
+
+- **Stories with no epic line up** (Jira). In Plan, then Epics, stories in a sprint with no epic no longer print their key over their title. *Where:* Plan, then Epics.
+
+## 1.29.0 · Sep 27, 2026
+
+Sprint work first, and features roll up.
+
+### New
+
+- **In a sprint, needs a workstream** (Jira). Plan, then Epics now starts with the epics whose stories Jira has in the active or an upcoming sprint, soonest first, and says what's in which sprint. Pick a workstream and put one on the board, or pick several and place them together. Parked epics with sprint work are flagged here, and sprint stories with no epic are listed too. *Where:* Plan, then Epics.
+- **A suggested workstream** (Jira). Each one comes with a suggested workstream: where its stories' Jira assignees already have work on the board, when one is clearly ahead. You still choose. *Where:* Plan, then Epics.
+
+### Improved
+
+- **Features roll up to their epic** (Jira sync). Stories under a feature under an epic now count toward the epic and show under it. The feature itself isn't counted as a story. Copy the updated sightline-jira-sync.py. *Where:* sightline-jira-sync.py and every epic count.
+- **The Plan badge puts sprint work first** (Plan). The badge on the Plan tab says how many need a workstream because they're in a sprint, before the count of epics to sort. *Where:* The Plan tab.
+
+### Fixed
+
+- **Refreshing keeps you editing** (Saving). Refreshing the page while you're editing no longer says someone else is editing. The tab keeps its place as the editor. A duplicated tab gets its own, so two tabs never both think they're editing. *Where:* Start editing, then refresh.
+
+## 1.28.0 · Sep 27, 2026
+
+Plan format checks and a better Standup.
+
+### New
+
+- **Plan format checks everywhere** (Saving). The page and the sync script now agree on the plan's format. The sync won't read a plan saved in a newer format, and the page won't read Jira files from a newer sync. When a new Sightline changes the format, the first save downloads the old file as a backup and says older copies will open it read-only. *Where:* Saving, and sightline-jira-sync.py.
+
+### Improved
+
+- **Standup opens cards beside the board** (Views). Clicking a card on Standup opens it on the right and keeps you on the board, with the open card outlined. Counts say what they count, columns keep their labels on a phone, and the note about hidden items shows here as on the timeline. *Where:* The Standup tab.
+- **Draws faster** (Timeline). The timeline and every tab redraw faster: a color check that ran once per label now runs once per draw, and epic counts no longer rescan each epic's stories. *Where:* Everywhere.
+
+### Fixed
+
+- **Undo respects a teammate's newer change** (Saving). Undoing a quick update no longer overwrites a field a teammate changed since; it says how many it left alone. A quick update that had to retry reports how it finally went, so Undo and Redo stay right. *Where:* Undo after quick updates.
+- **Every hidden item is counted** (Views). The hidden-items note now counts meetings and process blocks, notes hidden by the Notes setting, and items hidden by the Added by filter, each with a way to show them. *Where:* The note above the timeline and Standup.
+- **Roomier Activity, Tags and Proposals** (Plan). More space between the heading, controls and list, and a proposal made on another Jira server says so instead of being checked against this one. *Where:* Plan, then Activity, Tags or Proposals.
+
+## 1.27.1 · Sep 27, 2026
+
+Safer saves and hides.
+
+### Fixed
+
+- **Never saves over a newer Sightline's plan** (Saving). If someone saved the plan with a newer Sightline since you last looked, a quick update, Start editing or a save no longer writes over it. The plan opens read-only and says why, and your unsaved edits stay here. *Where:* Quick updates, Start editing and Save.
+- **Merges keep more of everyone's work** (Saving). Two people tagging the same Jira item for the first time both keep their tag. If a teammate's edit keeps an item you deleted, your version is downloaded as a backup first. *Where:* Saving while someone else is making quick updates.
+- **Put them back restores everything** (Saving). After someone saves with an older Sightline, Put them back now restores tags, Jira items' tags, notes and dependencies on Jira items, and proposals, not just who added what and the activity log. *Where:* The older-copy warning.
+- **Hides that stick** (Views). Hiding a person hides their notes on item cards too, with Show to see them. Hiding a tag hides an initiative even when its tasks don't carry that tag. *Where:* Item cards and the timeline.
+- **Sync limits and a stronger guard** (Jira sync). The sync fetches at most 2,000 of a plan's Jira items and says so when it stops short. A sync that returns none of the plan's Jira items keeps the earlier sync, whatever the plan's size. Copy the updated sightline-jira-sync.py. *Where:* sightline-jira-sync.py and Plan, then Epics.
+
+## 1.27.0 · Sep 27, 2026
+
+A standup board.
+
+### New
+
+- **Standup** (Views). A new Standup tab (or press 5) shows this sprint's work by person in To do, In progress and Done: Jira stories and Jira-linked items with their Jira assignee, and the plan's own tasks and initiatives with their people. Late, blocked, Jira-dependency, proposal and note flags show on each card. Click a card to open it. *Where:* The Standup tab.
+
+### Improved
+
+- **The same view, every tab** (Views). Standup follows your layers, hidden people and tag filters, just like the timeline, but always shows the current sprint whatever date range the timeline is set to. *Where:* The Standup tab.
+
+## 1.26.0 · Sep 27, 2026
+
+Propose changes to Jira.
+
+### New
+
+- **Propose a change to a Jira item** (Jira). From a Jira item's card, anyone can propose a change: move it to another sprint, assign it, set points, change its status, or add or remove a label, with a reason. Sightline doesn't change Jira. It records the proposal, who made it, and what Jira said at the time, and the item shows a pending mark. *Where:* A Jira item's card.
+- **Plan, then Proposals** (Plan). Every open proposal in one list for whoever maintains Jira, with Approve and Reject, and Copy as text to paste into Jira or a message. After the next sync, a proposal Jira now has is marked In Jira now; one where Jira changed another way says so. *Where:* Plan, then Proposals.
+
+### Improved
+
+- **The sync fetches proposed items** (Jira sync). Issues that have proposals are fetched even when they aren't on the board. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+
+## 1.25.0 · Sep 27, 2026
+
+A bad sync can't make the team's work look lost.
+
+### New
+
+- **A guard against a bad sync** (Jira sync). When a sync finds far fewer of the plan's Jira items than the last one, the sync keeps the earlier files and says so. If the drop is real, run the sync with --accept-drop. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+- **The page says when it's showing an earlier sync** (Jira). Epics and Settings say the last sync came back short, that the earlier sync is shown, and that nothing was removed. The health dot turns red. *Where:* Plan, then Epics; Settings.
+
+### Improved
+
+- **Missing items still read as themselves** (Jira). Sightline remembers, in your browser only, the last title it saw for each Jira item. An item the last sync didn't return shows as "Faceted search (not in the last sync)" instead of just its key, and its card shows the title it was last seen with. *Where:* Everywhere a Jira item appears.
+
+## 1.24.0 · Sep 27, 2026
+
+Notes and dependencies on Jira items.
+
+### New
+
+- **Notes on Jira items follow the issue** (Jira). Add a note to a Jira story, or any Jira item, from its card. The note is kept by its Jira key, so it follows the issue to another epic or initiative. Notes added before stay where they were. *Where:* The card of a Jira item or story.
+- **Nothing is lost when a sync misses an issue** (Jira). If a sync stops returning an issue, notes on it are kept and listed under Notes on Jira items not in the last sync. They go back on the item by themselves when the issue returns. *Where:* Plan, then Epics.
+- **Wait for a Jira item** (Jira). In an initiative's or task's card, Waits for Jira items takes Jira keys. If it would start before Jira says that item finishes (its sprint's end, or its due date), the card and the bar warn you. Nothing moves on its own: Jira's dates are Jira's. *Where:* Cards; the timeline.
+
+### Improved
+
+- **The sync fetches what the plan refers to** (Jira sync). Jira items the plan only refers to (notes on them, dependencies on them, tags kept by key) are fetched too. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+
+## 1.23.0 · Sep 27, 2026
+
+Cards that show what's Jira's and what's the plan's.
+
+### Improved
+
+- **Cards in two parts** (Jira). A Jira item's card starts with From Jira: title, status, assignee, sprint and dates (or an epic's stories and sprints), points, type, labels, when it was synced, and Open in Jira, none of it editable. Then Added here has the plan's own: who put it in the plan, tags, workstream, chart name, lead, notes, dependencies. A plan item's card is all the plan's. *Where:* Every card.
+- **Says when an issue isn't in the last sync** (Jira). If the last sync didn't return an item's issue, its card says so, and that everything added here is kept for when it comes back. *Where:* A Jira item's card.
+
+### Fixed
+
+- **Removing a tag from a Jira item** (Plan). Removing a tag takes it off wherever it was kept. *Where:* A Jira item's card.
+
+## 1.22.0 · Sep 27, 2026
+
+Tags on everything, and Jira's labels.
+
+### New
+
+- **Tags on everything** (Plan). Add the plan's own tags to initiatives, tasks, milestones, gates, notes, meetings and Jira items, from any card. Type a new name to create one. Anyone can add or remove tags without Start editing. On a Jira item the tag is kept with its Jira key, so it follows the issue. Tagged items show colored dots on the chart. *Where:* Any card; the timeline.
+- **Jira's labels, read-only** (Jira). The sync brings in each issue's Jira labels. Cards show them as Jira's, separate from the plan's tags, even when the names match. Copy the updated sightline-jira-sync.py and run install again. *Where:* Jira items' cards.
+- **Filter by tag or Jira label** (Filters). In Filters, click a tag or label once to show only what has it, again to hide it, and again to turn it off. Filters apply to stories too, and a view can save them. *Where:* Filters.
+- **Plan, then Tags** (Plan). See every tag and how often it's used. Rename, recolor or delete them (in an editing session); deleting a tag takes it off everything. *Where:* Plan, then Tags.
+
+## 1.21.0 · Sep 27, 2026
+
+Hide what someone added, and undo one change.
+
+### New
+
+- **Hide what someone added, just for you** (Timeline). In Filters, under Hide from my view, tick a person (or items with no recorded author) to hide what they added. It's your view only, remembered per plan in your browser, and it never hides what comes from Jira. A line under the view bar says how many are hidden, and whose, with Show them. *Where:* Filters.
+- **Added by** (Filters). A filter for what one or more people added (or what has no recorded author). Like other filters, a view can save it. *Where:* Filters.
+- **Work that waits on something hidden says so** (Timeline). An initiative that waits on something your view hides shows "⇠ 1 hidden". Going to that item (from Find, for example) shows everyone's work again. *Where:* Timeline.
+- **Undo one change** (Plan). Each change in Plan, then Activity has Undo this. It puts back only what nobody has changed since, and says what it left. *Where:* Plan, then Activity.
+
+## 1.20.0 · Sep 27, 2026
+
+See who added what, and what changed.
+
+### New
+
+- **Who added what** (Plan). Everything added to the plan (initiatives, tasks, milestones, gates, notes, meetings, workstreams, sprints, views) records who added it and who last edited it. Each card says so, and initiatives added here show the initials of whoever added them. Things moved automatically, for example by a dependency, aren't counted as anyone's edit. Items from before this version say so. *Where:* Every card; the timeline.
+- **Activity** (Plan). Plan, then Activity lists every quick update and save from the last 30 days, newest first: who, when, and what changed. You can show one person's. It's a record kept in the plan file, so it's a guide, not proof. *Where:* Plan, then Activity.
+- **Mine** (Timeline). Next to Everyone and Jira only, Mine shows Jira's work plus what you added. A line says how many items added by others are hidden, and how many have no recorded author. *Where:* Timeline.
+
+### Improved
+
+- **A note's author stays its author** (Notes). The author is shown, not editable. Editing someone else's note reminds you they're their words. *Where:* A note's card.
+- **Put back what an older copy dropped** (Saving). If a copy of Sightline older than 1.19 saves over the plan and drops who added what or the activity log, the page offers Put them back. *Where:* The banner at the top.
+- **Everyone needs this version to edit** (Saving). Plans with who added what open read-only in Sightline 1.19, and older copies drop it when they save, so update every copy. *Where:* Everyone's copy.
+
+## 1.19.0 · Sep 27, 2026
+
+Groundwork: safer saves across versions, bigger plans.
+
+### Improved
+
+- **Plans saved by a newer Sightline open read-only** (Saving). A copy that finds parts it doesn't know opens the plan read-only and says why, so nothing is lost. Update the copy to edit. *Where:* The banner at the top.
+- **You'll know when an older copy saved over the plan** (Saving). Each save records which Sightline wrote it. If a copy from before this version saves over the plan, the page says so, so you can ask everyone to update. *Where:* The banner at the top.
+- **Bigger plans open** (Saving). Plans up to 5 MB open. Saving still keeps a plan under 2 MB, so every copy of Sightline can open it. *Where:* Opening a plan.
+- **Undo uses less memory on big plans** (Performance). Undo keeps as many steps as fit in a fixed amount of memory, newest first, instead of 200 whole copies of the plan. *Where:* Undo.
+- **Groundwork for a shared database** (Saving). Behind the scenes, reading, saving, merging and drafts now go through one place, so the plan can later live in a database instead of a file without changing how you work. *Where:* Nothing to do.
+
+## 1.18.0 · Sep 27, 2026
+
+Jira's titles and assignees, always current; drag milestones and gates anywhere.
+
+### New
+
+- **The plan's own name on the chart, and its own lead** (Jira). A Jira item can carry a short name on the chart and a lead, both the plan's. Owners that were only a copy of the assignee aren't shown as a lead. The people filter and people rows count Jira's assignee. *Where:* The card of a Jira item.
+- **Review titles that differ from Jira** (Jira). Plan, then Epics lists items whose stored title differs from Jira's. For each one, keep the plan's name on the chart, or let it follow Jira. Nothing is rewritten on its own. *Where:* Plan, then Epics.
+
+### Improved
+
+- **Titles and assignees always match Jira** (Jira). A Jira item's title and assignee are read from the latest sync everywhere: the timeline, cards, the hover, Find and Today. The card shows them read-only, marked as from Jira. Without the Jira files, the title from when it was added shows, marked as not current. *Where:* Everywhere a Jira item appears.
+- **Jira's sprint names can't be edited here** (Sprints). Once the plan follows Jira's sprints, their names and goals are read-only in Sightline. The plan's own timeboxes stay editable. *Where:* Plan, then Sprints.
+- **Nothing added around a Jira item is lost if Jira drops it** (Jira). If a sync stops returning an issue, everything the team added around it stays and reattaches when the issue comes back. This is now in the product charter. *Where:* Everywhere.
+
+### Fixed
+
+- **Drag milestones, gates and notes** (Timeline). Drag them along their row to another day. A click still opens them. A milestone that follows initiatives says so instead of moving. *Where:* Timeline, Days and Weeks.
+- **Unsaved changes you can see, and count** (Editing). The strip counts what's changed since the last save ("3 unsaved changes"), and clicking the count lists each change. Undoing all the way back, or putting something back as it was, reads as saved. *Where:* The editing strip.
+
+## 1.17.0 · Sep 27, 2026
+
+See what comes from Jira, and what was added here.
+
+### New
+
+- **From Jira and Added here look different** (Timeline). What comes from Jira is outlined in its workstream's color, with its Jira key. What was added here stays filled. This holds in Weeks, Days and the people rows, for initiatives, tasks and stories. The key explains both. *Where:* Timeline.
+- **Show only what comes from Jira** (Timeline). Everyone / Jira only, next to the other view controls, shows the official Jira work on its own. A line under the controls says how many items added here are hidden, with Show everyone. Each plan remembers its own choice in your browser, and a saved view can keep it. *Where:* Timeline.
+
+### Improved
+
+- **Progress says what it counts** (Timeline). Bars show 5/9 stories for Jira work and 2/5 tasks (or items) for work added here, and the fill matches the count. The weighted percentage is in the hover and the card, marked as by task-days. *Where:* Timeline.
+- **Jira's sprints and the plan's own timeboxes** (Sprints). When the plan follows Jira's sprints, a timebox the plan added (after Jira's last sprint, say) shows in italics. Hovering a Jira sprint shows Jira's exact dates. *Where:* Timeline sprint headers.
+- **Parked initiatives are counted** (Timeline). A line says how many are parked, with a link to Plan, then Epics. *Where:* Timeline.
+
+## 1.16.1 · Sep 27, 2026
+
+Undo quick updates, and groups that stay open.
+
+### Fixed
+
+- **Undo works on Park, Put on the board, and switching stories** (Jira). Undo (and Ctrl+Z) reverses the last quick update in the shared file, key by key, so a teammate's newer changes stay. Redo puts it back, and a toast after each decision offers Undo. The Undo button names what it will undo. *Where:* Plan, then Epics; the initiative and story cards.
+- **Epics groups stay the way you left them** (Jira). Each group remembers being opened or closed. *Where:* Plan, then Epics.
+- **Sprints after Jira's last one continue its numbering** (Sprints). Numbered sprints continue from Jira (Sprint 46, 47…), and a named one like Hardening keeps its name. The weeks before Jira's first sprint say so, with a note on how to start the plan there instead. *Where:* Settings, then Jira, then Sprints from Jira.
+
+## 1.16.0 · Sep 26, 2026
+
+Finished epics stay out of your way.
+
+### New
+
+- **Sightline knows when an epic is finished** (Jira). The sync counts the stories under every epic your searches find. An epic whose stories are all done or abandoned goes into a closed Finished in Jira group: it isn't in Unsorted, isn't counted as to sort, and isn't touched by Park all. A new epic with no stories yet stays in Unsorted. Each row says how many stories are open. *Where:* Plan, then Epics.
+- **Park finished epics in one click** (Jira). When epics on the board are finished in Jira, Epics says how many and offers Park N finished. It keeps their initiatives and notes, and takes them off the timeline. *Where:* Plan, then Epics.
+
+### Improved
+
+- **Counts for every epic a search finds** (Jira sync). Epics on the board are counted first (with their stories listed), then the other epics your searches found (counted only), all within the same 5,000-story limit. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+
+## 1.15.1 · Sep 26, 2026
+
+Sorting that respects your picks, and a lighter page.
+
+### Improved
+
+- **Stories are easy to find from Weeks** (Timeline). An initiative's card has See N on the timeline, which opens Days at its stories, and its hover card says how many are in sprints. Find says when a story is switched off, has no sprint yet, or is outside this plan. *Where:* Timeline, and Find.
+- **Shorter, clearer words** (Jira). Stories switch off and on with Switch off and Switch on. The health warnings are one line each, and Settings says Reconnect when the folder needs your OK. *Where:* Initiative and story cards, Epics, Settings.
+- **Less work while you wait** (Performance). It redraws only when a Jira file changes. Epic counts and ownership are worked out once per draw instead of several times. *Where:* Everywhere.
+
+### Fixed
+
+- **Parking the rest leaves your picks alone** (Jira). With epics picked, the button parks only the ones you haven't picked, and says how many. *Where:* Plan, then Epics.
+
+## 1.15.0 · Sep 26, 2026
+
+See whether Jira is keeping up.
+
+### New
+
+- **Sync health** (Jira). Epics and Settings show when Jira last synced, whether by watch (and how often) or by hand, and from which server and board, with a green, amber or red dot. When a watch is more than twice its interval late, the page says so and what to check: that the computer running it is on and signed in. It updates every minute while the page is open. *Where:* Plan, then Epics; and Settings.
+- **Flags Jira files made for another plan** (Jira). If you copied or renamed the plan's folder, the page says the Jira files were made for the other plan and how to set up the sync for this one. *Where:* Plan, then Epics; and Settings.
+
+### Improved
+
+- **The sync says how it runs** (Jira sync). status.json records whether watch or a one-off sync wrote it, its interval, and the plan's file name. It records no computer or user names. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+
+## 1.14.1 · Sep 26, 2026
+
+Stories: counts that agree, and switches that stick.
+
+### Improved
+
+- **A new epic says its stories are coming** (Jira). Until the next sync lists them, the card says the stories show after the next Jira sync, and when the last one ran. *Where:* The initiative's card.
+
+### Fixed
+
+- **Reconnect Jira in one click** (Jira). Epics shows a Reconnect button for your folder, and one click brings everything back. When you open the page, the status line says Jira is paused until you reconnect. Plan opens on Epics for plans that use Jira. Your browser may offer to allow the folder on every visit, so you won't be asked again. *Where:* Plan, then Epics.
+- **Two people switching stories off at once both count** (Jira). A retried update adds and removes just its own keys, so everyone's changes survive. *Where:* Off for now, Park, and the status map.
+- **A date filter shows stories in that range** (Filters). The initiative shows with its matching stories, and Find clears a filter that would hide the story it goes to. *Where:* Filters, Find.
+- **Every count agrees** (Jira). The same rule counts everywhere, off for now is shown on each epic, each story counts once, and no count goes below zero. Needs the updated sync script for the two-epics fix. *Where:* The initiative's card, and Plan, then Epics.
+- **No silent limit on stories off** (Jira). It says the limit was reached instead. *Where:* Off for now.
+
+## 1.14.0 · Sep 26, 2026
+
+An epic's stories, inside its initiative.
+
+### New
+
+- **Stories from Jira show inside their initiative** (Timeline). In the Days view, each story in a sprint shows inside its initiative: its sprint sets the dates and Jira sets the status. Stories have a dashed outline and their Jira key. Click one for its card. They're read-only, so change them in Jira. They aren't copied into the plan, and a story that's already a task in the plan shows as the task. *Where:* Timeline, Days view.
+- **Switch a story off for now** (Jira). Every initiative with epics lists its stories: in a sprint, not scheduled here, off for now, and abandoned in Jira. Off for now hides a story from the timeline and from progress, without changing Jira. Anyone can do it without Start editing, and two people's changes both count. Everyone should use this version, because older copies drop the list when they save. *Where:* The initiative's card, or the story's card.
+
+### Improved
+
+- **Progress counts what's switched on** (Jira). Only stories that are switched on count. Plan, then Epics shows how many are off for now. Switching off every story no longer marks the initiative abandoned. *Where:* Initiatives, and Plan, then Epics.
+- **Find and filters include stories** (Find). Find lists each story by its key, name and assignee. Status and people filters show the stories that match. *Where:* Find, and Filters.
+- **The sync lists each epic's stories** (Jira sync). For epics on the board, the status file lists up to 3,000 stories with their sprint and status. Parked epics are counted but not listed. Copy the updated sightline-jira-sync.py and run install again. *Where:* sightline-jira-sync.py.
+
+## 1.13.1 · Sep 26, 2026
+
+Epic decisions that stick, and a sync that keeps going.
+
+### Fixed
+
+- **Park means parked** (Jira). Each epic belongs to one initiative, however it was linked. Park and Park all switch it off everywhere, and On… won't make a second initiative for an epic that's already on the board. *Where:* Plan, then Epics.
+- **Messages say what really happened** (Jira). If it didn't save, your picks stay. In an editing session it says the change waits for Save. Back on explains when the epic's initiative was removed. *Where:* Plan, then Epics.
+- **Scheduling leaves Jira stories in their sprint** (Timeline). Jira's sprint dates stay fixed when the plan schedules itself. A clash shows as a warning instead. *Where:* Timeline.
+- **Statuses with a | in their name** (Jira). It's counted under its real name. Needs the updated sync script. *Where:* Epic progress and the status map.
+- **watch keeps going** (Jira sync). A failure is reported for that plan only and retried after a minute, then less often. Only one watch runs on a computer, and one that loses the lock stops. *Where:* sightline-jira-sync.py watch.
+- **sync --save changes only what you give it** (Jira sync). Each option replaces just that setting, and settings are saved only after a sync works. When several searches fill the file, the later ones say they were skipped. *Where:* sightline-jira-sync.py sync.
+
+## 1.13.0 · Sep 26, 2026
+
+Workstreams, a Settings page, and sorting many epics at once.
+
+### New
+
+- **Pick several epics, then decide once** (Jira). Tick epics (or Pick all), choose a workstream, and put them all on the board, or park them all, in one save. *Where:* Plan, then Epics.
+- **Make a workstream while you sort** (Jira). + New workstream is in the picked bar and in each epic's On… menu. *Where:* Plan, then Epics.
+- **One Settings page** (Settings). The plan's dates and sprints, and everything about connecting Jira (the folder, the status map, sprints from the board, your searches), are on one page. *Where:* The gear button at the top, or File, then Jira status.
+
+### Improved
+
+- **Lanes are now called workstreams** (Timeline). A workstream is an area or priority the team's work belongs to, lasting quarters. Initiatives sit inside it, and stories inside those. Only the name changed: plans and older copies keep working. *Where:* Everywhere lanes used to be named.
+- **Epics live under Plan** (Jira). Sorting epics is planning work, so it's a list under Plan, next to Milestones and Risks. The Plan tab's badge counts epics waiting to be sorted. *Where:* Plan, then Epics.
+
+## 1.12.1 · Sep 26, 2026
+
+Tidier meeting attendees.
+
+### Fixed
+
+- **Adding a group tidies the People list** (Meetings). People the group already brings are taken off the People list; nobody is dropped from the meeting. A meeting that already lists group members one by one says so, with a one-click fix. *Where:* A meeting's details panel, under Groups and People.
+- **Names in lists no longer run together** (Meetings). Each name has room, and long lists wrap. *Where:* Plan, then Meetings and Team.
+
+## 1.12.0 · Sep 26, 2026
+
+A Jira tab for putting epics on the board.
+
+### New
+
+- **A Jira tab: epics on the board, parked, or not sorted yet** (Jira). Every epic your searches find is in one of three groups. Switch one on as a new initiative in a lane, or add it to an initiative you already have (the closest names are suggested). Park the ones that don't matter right now; switch any back on later. The tab's badge counts epics nobody has sorted. *Where:* The Jira tab, next to Plan (or press 5).
+- **Sort your epics once** (Jira). The first time, switch on the epics this plan tracks and park the rest in one go. After that, only new epics wait to be sorted. *Where:* The Jira tab.
+- **Parking never deletes** (Jira). Parking an epic that has its own initiative hides the initiative, with its notes and links kept, until you switch it back on. An initiative that holds other work just lets go of the epic. *Where:* The Jira tab, Park and Back on.
+
+### Improved
+
+- **Anyone can sort epics** (Jira). Switching epics on and off are quick updates: no Start editing, and two people's choices both count. *Where:* The Jira tab.
+- **Epic initiatives follow their stories' sprints** (Timeline). An initiative made of epics covers its stories' sprints on its own, and can't be dragged away from them. *Where:* Timeline.
+- **Setup moved to the Jira tab** (Jira). The folder, status map, sprints and all search results are in the tab's Setup section. *Where:* The Jira tab, Setup.
+
+## 1.11.0 · Sep 26, 2026
+
+Several Jira searches per plan.
+
+### New
+
+- **Keep several Jira searches side by side** (Jira). Give the sync as many named searches as you need, like Epics, This sprint and No epic. The Jira window has a button for each, with how many are new, and Today says how many are new in each. *Where:* python sightline-jira-sync.py sync PLAN --search "Epics=..." --search "This sprint=..." --save
+
+## 1.10.0 · Sep 26, 2026
+
+Jira keeps itself in sync, and every project carries its own jira folder.
+
+### New
+
+- **A plan's Jira files live in a jira folder next to it** (Jira). The sync writes the plan's Jira files into a jira folder next to the plan, so the folder can be copied for another project. Connect that folder once and Sightline reads everything in it, every minute. *Where:* File, then Jira status, then Connect the Jira folder.
+- **Set it up once; it keeps itself in sync** (Jira). sync --save remembers a plan's board and search on your computer. install starts watch when you sign in: every saved plan syncs on its schedule, and again shortly after anyone saves the plan. *Where:* python sightline-jira-sync.py install
+- **More than one Jira** (Jira). Set up as many Jira servers as you need (setup --jira URL). Each plan remembers which one it uses, with that server's own fields. *Where:* python sightline-jira-sync.py setup --jira https://...
+
+### Improved
+
+- **Your token only runs your own copy of the sync** (Security). install keeps your own copy in your profile, and the sync warns when it's run from anywhere else. *Where:* python sightline-jira-sync.py install
+
+### Fixed
+
+- **Clearer when nothing is linked yet** (Jira). It says nothing in the plan is linked to Jira yet. *Where:* File, then Jira status.
+
+## 1.9.1 · Sep 26, 2026
+
+Sightline survives being copied, and says so when it can't start.
+
+### Improved
+
+- **A clear message when Sightline can't start** (What's new). The page says Sightline didn't start, why that usually happens, and how to check and fix the copy. Your plan file isn't affected. *Where:* Opening a damaged copy of timeline-planner.html.
+
+### Fixed
+
+- **A copy that re-encodes the file no longer stops Sightline** (Security). The code is written in plain ASCII, so re-encoding the file can't change it. A checksum file comes with each copy. *Where:* timeline-planner.html and timeline-planner.html.sha256.
+
+## 1.9.0 · Sep 26, 2026
+
+Jira statuses show the way your board does, and abandoned work stops counting as done.
+
+### New
+
+- **Statuses follow your board's columns** (Jira). Run the sync with --board and Sightline reads the board's columns: early columns are not started, middle ones are in progress (shown by the column's name, like Awaiting review), the last is done. Abandoned statuses in the Done column show as Abandoned. *Where:* Everywhere a Jira status shows.
+- **A status map the team shares** (Jira). The Jira window lists every status and resolution your issues use, how each shows here, and why. Change any that are wrong; the whole team sees the same, and counts update at once. *Where:* File, then Jira status, under How Jira statuses show in Sightline.
+
+### Fixed
+
+- **Abandoned work is no longer counted as done** (Jira). Work closed as Won't Do, Duplicate or Cancelled is shown as Abandoned: struck through, and left out of progress and story counts. Initiatives say how many were abandoned. *Where:* The chart, an initiative's Jira epics, and progress.
+- **Parking-lot sprints don't schedule anything** (Sprints & process). A future sprint whose dates have passed (like Parking lot) no longer sets an issue's dates or shapes the plan's sprints. Its issues say they're not in a scheduled sprint. *Where:* Timeline, and Sprints from your Jira board.
+
+## 1.8.0 · Sep 26, 2026
+
+Sprints from Jira, and Jira issues stay where Jira puts them.
+
+### New
+
+- **The plan's sprints follow your Jira board** (Sprints & process). Run the sync with --board and the Jira window shows the plan's sprints next to Jira's. One click makes them match. Jira is the source of truth for sprint names and dates; the plan keeps its own sprints after Jira's last one. *Where:* File, then Jira status, under Sprints from your Jira board.
+- **Jira issues sit in their sprint** (Jira). An initiative or task linked to a Jira issue sits in that issue's sprint, and can't be dragged or resized. To move it, change its sprint in Jira. Issues not in a sprint yet can still be moved. *Where:* Timeline, on items linked to Jira.
+- **Status comes from Jira** (Jira). Its status follows Jira's. An initiative made of epics follows its stories. At risk and Blocked are still yours to set. *Where:* The details panel, and Today.
+- **Stretch an initiative to cover its stories' sprints** (Jira). An initiative made of epics says which sprints its stories are in, and one click stretches the bar to cover them. It never moves on its own. *Where:* An initiative's Jira epics.
+
+### Improved
+
+- **Today sends you to Jira for Jira's items** (Today). Items whose dates and status come from Jira say Update it in Jira instead of offering Start, Done or Next week. Unblock still works. *Where:* Today.
+
+## 1.7.0 · Sep 26, 2026
+
+A review of the Jira work: fixes, and room for big backlogs.
+
+### Improved
+
+- **Filter a long list of Jira issues** (Jira). Every issue is listed. Type to filter by key, summary, type, status, person or epic. Select all picks just the ones shown, and the buttons say how many you picked. *Where:* File, then Jira status.
+- **Story counts say where they come from** (Jira). They show when they were counted, and that only issues the person running the sync can see are included. *Where:* An initiative's Jira epics.
+
+### Fixed
+
+- **An epic already linked isn't offered again** (Jira). Epics linked either way count as in the plan. *Where:* File, then Jira status.
+- **Owners come only from linked Jira users** (People). Owners are only set from a person's Jira link. Two people with the same name can't be mixed up. *Where:* Adding issues from Jira, and Mine on Today.
+- **Skips and epic links from two people both survive** (Saving). Both are kept, and a skip or link you removed stays removed. *Where:* When Sightline brings in a teammate's changes.
+- **Issues with an unknown status aren't counted as to do** (Jira). They're counted separately, and the initiative says how many. *Where:* An initiative's Jira epics.
+- **The two Jira files must belong together** (Jira). Sightline says when the issues file is from an earlier sync, and refuses a pair from different Jira servers. *Where:* File, then Jira status.
+- **No email addresses in names, either** (Security). The sync script uses their user name instead, or "Jira user". *Where:* The Jira sync script, tools/sightline-jira-sync.py.
+
+## 1.6.0 · Sep 26, 2026
+
+See how far along each initiative's Jira epics are.
+
+### New
+
+- **Link initiatives to their Jira epics** (Jira). Link as many epics as the work spans. The sync script counts their stories by status and adds up story points. The initiative shows how many are done, with a progress bar. *Where:* An initiative's details panel, under Jira epics.
+- **Stories done, right on the bar** (Timeline). An initiative with Jira epics shows stories done out of the total, like 17/45. Hover for what's in progress and the points. *Where:* Timeline, on the initiative's bar.
+
+### Improved
+
+- **Select all issues at once** (Jira). A Select all checkbox heads the list. It shows when only some are picked. *Where:* File, then Jira status, while you're editing.
+
+### Fixed
+
+- **An epic's own status no longer causes false alarms** (Jira). Initiatives linked to epics are compared with their stories: all done means done, any started means in progress. *Where:* Jira and the plan disagree, in the Jira window and on Today.
+- **Epics are recognized even when your admins renamed the type** (Jira). The sync script knows epics by their Epic Name field, whatever the type is called. An epic added from your Jira search is linked as that initiative's epic, so its stories are counted. *Where:* Run python sightline-jira-sync.py fields once to pick up the Epic Name field.
+
+## 1.5.0 · Sep 26, 2026
+
+Sightline learns your Jira's fields.
+
+### New
+
+- **The sync script finds your Jira's Epic Link, Sprint and Story Points** (Jira). Setup looks them up by type and saves them on your computer. Run fields to look again, or fields --set to choose one yourself. *Where:* python sightline-jira-sync.py fields
+
+### Improved
+
+- **See each issue's epic, sprint and story points** (Jira). Issues from your Jira search show their epic, current sprint and points. An item's Jira line shows its sprint and points too. *Where:* File, then Jira status, and the details panel under the Jira key.
+
+## 1.4.0 · Sep 26, 2026
+
+Link your team to their Jira users.
+
+### New
+
+- **Link people to their Jira users** (People). Link each person to their Jira user once. Sightline suggests the likely match, and nothing links until you click Link. Links are saved in the plan, so the whole team shares them. *Where:* The person's panel, or People, then Jira users.
+- **See everyone assigned in Jira** (People). People lists everyone the Jira files have work assigned to, how many issues each has, and who isn't linked yet. Link them to someone on the team, or add them to the team. *Where:* People, then Jira users. It appears once a Jira file is connected.
+
+### Improved
+
+- **Issues from Jira get the right owner** (Jira). A linked assignee becomes the owner even when their Jira name is different. An assignee who isn't linked is never guessed from their name. *Where:* File, then Jira status, then Add picked.
+- **Mine includes what Jira assigns to you** (Today). Once you're linked, Today's Mine view includes plan items whose Jira issue is assigned to you, even if you're not an owner in the plan. *Where:* Today, then Mine.
+- **Spot work Jira assigns to someone else** (Jira). An item's Jira line says "not an owner here" when Jira's assignee isn't one of its owners. *Where:* The details panel, under the Jira key.
+- **No email addresses in the Jira files** (Security). The sync script writes each assignee's Jira key and user name, never their email. If your Jira uses email addresses as user names, the script writes a one-way code instead, which still links but can't be turned back into the address. *Where:* The Jira sync script, tools/sightline-jira-sync.py.
+
+## 1.3.0 · Sep 26, 2026
+
+Bring in Jira issues from a filter.
+
+### New
+
+- **Bring in issues from a Jira filter** (Jira). Give the sync script a saved filter or a search, and it writes what it finds to its own file, jira-issues.json. Connect that file in the Jira window to see the issues that aren't in the plan yet, then add them as initiatives in a lane or as tasks in an initiative. Each starts today, ends on its due date, and gets its owner when the assignee is on the team. *Where:* File, then Jira status. Run the script with --filter 12345 or --jql "...", then Connect jira-issues.json.
+- **Skip issues that don't belong in the plan** (Jira). Skip picked issues to leave them out. Skips are saved in the plan, so the whole team sees the same list. Show them again any time. *Where:* File, then Jira status.
+- **Today tells you when Jira has something new** (Today). When the filter finds issues that aren't in the plan, Today says how many, with a Review button. *Where:* Today, in the right-hand column.
+
+### Fixed
+
+- **The Jira window's lists are easier to read** (Jira). They're in normal text, like the rest of the window. *Where:* File, then Jira status.
+
+## 1.2.0 · Sep 26, 2026
+
+More room for your plan, and Today leads with what needs you.
+
+### Improved
+
+- **Today leads with what needs you** (Today). Sections with work in them come first. Empty ones are named together on one line, and a clear day says so. *Where:* Today.
+- **The details panel no longer covers other pages** (Details panel). Picking another tab closes it. When you open something on Today, People, or Plan, the page moves over to make room. *Where:* The details panel on the right.
+- **Gates on the same day share one chip** (Timeline). They share one chip, like "Mar 5 Security review +1". Click it to pick the gate you want. *Where:* Timeline, the Gates row.
+- **The key folds away** (Timeline). It folds behind a Key button, and remembers if you leave it open. The milestone that waits on a gate is now "Gated milestone", so no two entries share a name. *Where:* Key, at the bottom of the Timeline.
+- **Bars show a short name when the title doesn't fit** (Timeline). If you haven't set a chart name, the bar shows the part before " · " or ":", the same one the panel suggests. Hover for the full title. *Where:* Timeline, Weeks zoom.
+- **One name for notes** (Notes). They're called Notes everywhere. Updates are still separate: dated progress on an item. *Where:* The details panel, and Notes in the toolbar.
+- **It's clear when your plan isn't shared** (Saving). It's drawn as a warning and says "Share…". Click it to save the plan as a shared plan, or open one your team already shares. *Where:* The chip at the top of the page.
+- **Risks show how serious they are** (Risks). High is red and medium is amber. The risk wraps onto more lines, and Enter finishes the edit. *Where:* Plan, then Risks. Decisions wrap too.
+- **The line by the tabs says where you are in the sprint** (Timeline). It says where today falls in its sprint, like "S1 · day 4 of 10", then any filters. *Where:* Next to the Today, Timeline, People, and Plan tabs.
+- **Line icons on Today and the details panel** (Accessibility). They use Sightline's own line icons, colored by what needs attention. *Where:* Today, and Mark blocked in the details panel.
+
+## 1.1.0 · Sep 26, 2026
+
+Safer saving, a cleaner Process row, and release notes.
+
+### New
+
+- **See what changed in each version** (What's new). Every release is listed here, newest first. Search it, or filter by kind or area. A dot on What's new means there's a release you haven't seen yet. *Where:* What's new, at the top right.
+
+### Improved
+
+- **The Process row reads at a glance** (Timeline). Each freeze is a band as wide as its days and each release is a pin on top of it, all on one line. The header names each kind in its color. *Where:* Timeline, Weeks zoom, the Process row.
+- **Focus stays on the dropdown you just changed** (Accessibility). Focus stays on the dropdown, so you can keep working from the keyboard. *Where:* The details panel on the right, for example Status.
+- **Sightline only runs its own code** (Security). The page runs only the two scripts it ships with. The browser blocks anything else. *Where:* Nothing to do. It's automatic.
+
+### Fixed
+
+- **The + no longer covers what's already there** (Timeline). The + shows only in open space. If the spot is taken, it moves to the nearest open space in the row, or doesn't show. *Where:* Point at an empty spot on any timeline row.
+- **Very large plans can't break the file anymore** (Saving). Sightline refuses the save and tells you how large the plan would be, so the file stays safe. *Where:* Save, quick updates, and Start a new shared plan.
+- **Your edits are backed up when a teammate's change wins** (Saving). Theirs is still kept, but your version is downloaded as a backup first. *Where:* When Sightline brings in a teammate's changes.
+- **A teammate's undo is no longer reversed** (Saving). A change made after seeing yours is left alone. *Where:* Quick updates, like marking something done.
+- **When a save is refused, you can see why** (Saving). The reason stays in the status line. *Where:* The status line at the bottom of the page.
+- **No more "null" in menus** (Menus). Those menus show only what belongs there. *Where:* + on the timeline, Notes, Filters, and Jira status.
+- **Sprint rules stay inside their sprint** (Sprints & process). It lands on the sprint's last working day instead. *Where:* Process blocks that repeat from a sprint rule.
+- **Tasks that wait on each other stay put** (Timeline). They stay where they are and are listed as a dependency loop to fix. *Where:* The review banner above the timeline.
+- **Your Jira token stays private** (Jira). Redirects are refused, and the token is handed over privately. *Where:* The Jira sync script, tools/sightline-jira-sync.py.
+
+## 1.0.0 · Sep 26, 2026
+
+The planner gets a name.
+
+### New
+
+- **Meet Sightline** (What's new). The planner is now called Sightline: your team's work, in plain sight. *Where:* The top left of the page and the browser tab.
+- **One plan file your whole team shares** (Saving). Link a plan file your team shares. One person edits at a time, anyone can make quick updates, and nothing is overwritten without a backup. *Where:* File, then Link a file.
+- **Your plan by lane or by person** (Timeline). See work by lane or by person, zoom from weeks to days, and plan around holidays and time off. *Where:* The Timeline and People tabs.
+- **Sprints, meetings, and team rhythms** (Sprints & process). Set up sprints, repeating meetings, and process blocks like code freezes and releases that repeat every sprint from a rule. *Where:* Plan, then Sprints.
+- **Jira status next to your plan** (Jira). Show each item's Jira status beside it. A small script fetches it, so the page never sees your token. *Where:* File, then Jira status.