Adom Gantt

@@ -4,9 +4,9 @@ Interactive Gantt chart viewer for project timelines. Data-driven, dark by defau  ## Features -**Auto-schedule the whole plan, by pushing later only.** One press of **Auto-schedule** moves every task out until it starts no earlier than the work it waits on has finished, and so that nothing starts or ends on a Saturday, a Sunday or a US federal holiday. The handoff is a MINIMUM rather than an answer. A task that starts BEFORE its latest dependency's end is pushed out to it, so the two bars meet on the chart with no column of white between them; a task that already starts on or after it is LEFT EXACTLY WHERE IT IS. That is what keeps a gap you meant: an order placed on the Monday and the parts that arrive on the Thursday keep their three days, because a lead time is real elapsed time and not a tidying-up job. Nothing is ever pulled EARLIER, so a plan cannot drift backwards over a press and a second press moves nothing at all. Pushes cascade, so a task moved out moves its own successors, measured against where they landed. A task with no dependencies is an anchor and keeps its start, since that is the one thing the plan cannot derive. Durations are preserved in WORKING days, so a five-day task laid across a weekend, or across Labor Day, still takes five working days: a predecessor that ends on the Friday hands off on the Friday, and the weekend sits inside the successor's span rather than between the two of them. Milestones take the same rule with no duration. Cancelled work is out of the pass entirely: it never moves, and it constrains nobody, so a task whose only dependency is cancelled behaves like an anchor and the toast counts the excluded rows as their own number. The dependency graph crosses sections freely and so does the schedule. A cycle is left exactly as it is, named in the toast, because there is no honest answer for a row that waits on itself. It is one Ctrl+Z for the whole pass and one line in the changelog, and pressing it on an already aligned plan reports "0 tasks moved" and writes nothing.+**Auto-schedule the whole plan, by pushing later only.** One press of **Auto-schedule** moves every task out until it starts no earlier than the work it waits on has finished, and so that nothing starts or ends on a Saturday, a Sunday or one of the plan's days off (the US federal holidays unless the plan works them, see Working calendar). The handoff is a MINIMUM rather than an answer. A task that starts BEFORE its latest dependency's end is pushed out to it, so the two bars meet on the chart with no column of white between them; a task that already starts on or after it is LEFT EXACTLY WHERE IT IS. That is what keeps a gap you meant: an order placed on the Monday and the parts that arrive on the Thursday keep their three days, because a lead time is real elapsed time and not a tidying-up job. Nothing is ever pulled EARLIER, so a plan cannot drift backwards over a press and a second press moves nothing at all. Pushes cascade, so a task moved out moves its own successors, measured against where they landed. A task with no dependencies is an anchor and keeps its start, since that is the one thing the plan cannot derive. Durations are preserved in WORKING days, so a five-day task laid across a weekend, or across Labor Day, still takes five working days: a predecessor that ends on the Friday hands off on the Friday, and the weekend sits inside the successor's span rather than between the two of them. Milestones take the same rule with no duration. Cancelled work is out of the pass entirely: it never moves, and it constrains nobody, so a task whose only dependency is cancelled behaves like an anchor and the toast counts the excluded rows as their own number. The dependency graph crosses sections freely and so does the schedule. A cycle is left exactly as it is, named in the toast, because there is no honest answer for a row that waits on itself. It is one Ctrl+Z for the whole pass and one line in the changelog, and pressing it on an already aligned plan reports "0 tasks moved" and writes nothing. -**Critical path, one per section.** **Critical** lights up the LONGEST run of work inside every section at once: the bars, the dependency arrows along it and any milestone on it glow white and breathe, in a saturated indigo on paper. The dependency graph is read as a DAG, a task weighs its duration in WORKING days (weekends and US federal holidays excluded) and a milestone weighs nothing, and the critical path is the maximum-weight path through it. So it is the hardest run of work and not merely whatever chain happens to end last. A gap between two tasks adds no weight, because the length is the sum of the work along the path and not the calendar it is spread over, so the gaps Auto-schedule now preserves cannot promote or demote a chain. Cancelled work is not in the graph: it can never glow, it carries no weight, and a chain that ran through it is broken at that row, so the section falls back to whatever the longest run through the work that is still live turns out to be. Un-cancelling puts the row, its links and every path through it straight back, because nothing was deleted. Nothing is rescheduled: it reads the dates the plan has right now, independently of Auto-schedule.+**Critical path, one per section.** **Critical** lights up the LONGEST run of work inside every section at once: the bars, the dependency arrows along it and any milestone on it glow white and breathe, in a saturated indigo on paper. The dependency graph is read as a DAG, a task weighs its duration in WORKING days (weekends and the plan's days off excluded) and a milestone weighs nothing, and the critical path is the maximum-weight path through it. So it is the hardest run of work and not merely whatever chain happens to end last. A gap between two tasks adds no weight, because the length is the sum of the work along the path and not the calendar it is spread over, so the gaps Auto-schedule now preserves cannot promote or demote a chain. Cancelled work is not in the graph: it can never glow, it carries no weight, and a chain that ran through it is broken at that row, so the section falls back to whatever the longest run through the work that is still live turns out to be. Un-cancelling puts the row, its links and every path through it straight back, because nothing was deleted. Nothing is rescheduled: it reads the dates the plan has right now, independently of Auto-schedule.  A plain on/off toggle. Each lane is answered on its OWN subgraph, so a dependency that crosses sections is not an edge and never lights up, and a section with no dependencies among its own rows lights its longest single row. Ties are broken deterministically: more working days, then a greater calendar span, then more rows, then whichever starts earlier in the plan. Everything else stays exactly as it was, selection and dependency mode included, the glow recomputes as you edit, and the state is remembered across reloads. @@ -74,9 +74,11 @@ A plain on/off toggle. Each lane is answered on its OWN subgraph, so a dependenc  **Current and Overdue.** Two chips in the legend, for reviewing a plan with the team. **Current** (0.70.0) shows only what has started (start date today or earlier) and is not complete or cancelled: the work under way, plus anything that should have started and has not. Future and finished rows are hidden, in the chart and the table. **Overdue** shows only what is past its deadline and not done. Turn both on for just the overdue rows. Each counts tasks and milestones separately, and neither changes the plan. -**Legend filtering.** Click any phase, "Milestone", "Dependencies" or "Today" in the legend bar to toggle visibility. Dimmed items fade to 15% opacity; hiding "Today" removes the marker line. The legend wraps onto as many lines as the plan needs, so a plan with twenty sections shows all twenty chips. When the sections carry tags (0.59.0), the legend leads with a chip per tag and the twenty section chips fold behind one "20 sections" chip; pick a tag and only the sections carrying it are shown, in the chart and the table, with their own chips back in the legend. Pick several to see any of them; Clear tags shows everything. It is your view only, and it survives a refresh. Since 0.64.0 the legend also leads with an **Owner** pick (every owner with their row count, plus **Unassigned**, shared with the table's owner filter) and an **Overdue** chip: rows whose end date or milestone date has passed without being marked complete or cancelled get a red edge and ring, and the chip shows only them. Overdue is worked out from the dates every time the page draws and at midnight; it is never written into the plan.+**Legend filtering.** Click any phase, "Milestone", "Dependencies" or "Today" in the legend bar to toggle visibility. Dimmed items fade to 15% opacity; hiding "Today" removes the marker line. The legend wraps onto as many lines as the plan needs, so a plan with twenty sections shows all twenty chips. When the sections carry tags (0.59.0), the legend leads with a chip per tag and the twenty section chips fold behind one "20 sections" chip; pick a tag and only the sections carrying it are shown, in the chart and the table, with their own chips back in the legend. Pick several to see any of them; Clear tags shows everything. It is your view only, and it survives a refresh. Since 0.64.0 the legend also leads with an **Owner** pick (every owner with their row count, plus **Unassigned**, shared with the table's owner filter) and an **Overdue** chip: rows whose end date or milestone date has passed without being marked complete or cancelled get a red edge and ring, and the chip shows only them. Overdue is worked out from the dates every time the page draws and at midnight; it is never written into the plan. Changing any of these filters, or Collapse all and Expand all, keeps your place: the row at the top of the chart stays where it is, or, if the filter hides it, the nearest row above it that still shows takes its spot. A row someone else adds or deletes above you does not move your view either (0.74.1). Scrolled all the way up, you stay at the top, and a section's chevron stays under the pointer when it folds (0.74.2). -**Project dates.** The first card on Setup holds the project's start and end (0.75.0). Project Duration runs from the start to the end and Time Remaining from today to the end, so the clock in the header is the project's commitment rather than wherever the rows happen to reach. The chart marks both dates with a dashed amber line and hatches the time outside them, so a bar that runs past the end is hatched where it does, the header readouts turn amber, and the card lists every row outside the dates with a link to it. Only the plan's owner can change them. With no dates set, everything counts from the rows as before. They replace the header's start button, which moved the whole plan for everyone. Changing any of these filters, or Collapse all and Expand all, keeps your place: the row at the top of the chart stays where it is, or, if the filter hides it, the nearest row above it that still shows takes its spot. A row someone else adds or deletes above you does not move your view either (0.74.1). Scrolled all the way up, you stay at the top, and a section's chevron stays under the pointer when it folds (0.74.2).+**Project dates.** The first card on Setup holds the project's start and end (0.75.0). Project Duration runs from the start to the end and Time Remaining from today to the end, so the clock in the header is the project's commitment rather than wherever the rows happen to reach. The chart marks both dates with a dashed amber line and hatches the time outside them, so a bar that runs past the end is hatched where it does, the header readouts turn amber, and the card lists every row outside the dates with a link to it. Only the plan's owner can change them. With no dates set, everything counts from the rows as before. They replace the header's start button, which moved the whole plan for everyone.++**Working calendar.** The second card on Setup says which days this plan works (0.76.0). Weekends are always off, and by default so are all eleven US federal holidays; untick one your team works (Adom works Columbus Day and Veterans Day) and it becomes a normal working day for this plan. Add the weekdays the whole team is off, like a year-end shutdown, and they become days off. Auto-schedule, the critical path, every hours and workdays figure, and the day grain's shading all follow it, so a worked holiday is not shaded and an extra day off is. Only the plan's owner can change it; every change is one Ctrl+Z and one changelog line.  **How long, and how long left.** The header says **Project Duration** and **Time Remaining**, worked out from the plan's own first and last dates and today, never from the cell size, leaving cancelled work out, and updated on every edit. They stay whole at every window width: the header sheds button words, then wraps, before it lets them be cut. A printed chart names the plan in a title line of its own. Hover either for the exact dates and the calendar and working-day counts. The plan itself is named once, in the brand block at the far left; its title and description are on that block's tooltip. @@ -96,13 +98,11 @@ A plain on/off toggle. Each lane is answered on its OWN subgraph, so a dependenc  **Brand phase colors.** A phase with no explicit `color` cycles the three Adom hues: teal, purple, blue. There is no background band behind a phase: the bar colour and the group header carry the section on their own, so colour on the chart means exactly one thing, which phase a bar belongs to. The hues are theme-aware, so the same plan is on-brand on screen and legible on paper. -**Move the whole plan.** The project start sits in the header, as an exact date at every cell size. Change it and every task, milestone and phase shifts by the same number of days, so durations and the gaps between them survive. Revert puts the plan back to the data file's own start. It is one undo step and one changelog entry, not 26.- **Text size.** A-minus and A-plus at the right end of the header step the whole app between 85% and 150% in seven steps, chart and table together. The percentage between them is the reset. Rows, bars and the axis grow with the type, so nothing is clipped, and the choice persists across a refresh, in the live app and in an exported HTML snapshot alike.  **Fit to the pane.** One click on Fit picks the finest cell size that shows the whole plan without scrolling sideways, then stretches the cells to fill the width exactly. Click it again after resizing the window to re-fit. -**Cell size.** Days, Weeks, Months, Quarters or Years. Each grain carries its own minimum cell width, sized to the widest label it draws, so a fine grain scrolls rather than squashing and a coarse one stretches to fill. Days adds weekend shading, a differently coloured band on every US federal holiday with its name in a tooltip, and a full calendar picker.+**Cell size.** Days, Weeks, Months, Quarters or Years. Each grain carries its own minimum cell width, sized to the widest label it draws, so a fine grain scrolls rather than squashing and a coarse one stretches to fill. Days adds weekend shading, a differently coloured band on each of the plan's days off (the federal holidays it takes, with the name in a tooltip, and its extra days off), and a full calendar picker.  **Editable milestones.** Drag a milestone sideways to move its date, or click it to edit its name, date and description. Line style is the default: the tag on the dashed rule is the handle and the milestone's own row is hidden, since the rule already spans the chart. Long titles wrap, and a tag that would still collide with its neighbour drops to a second row. Diamond style keeps the row. @@ -150,7 +150,8 @@ Create a JSON file with three sections:     "title": "My Project",     "subtitle": "Short description",     "start": "2026-01-05",-    "end": "2026-06-30"+    "end": "2026-06-30",+    "calendar": { "workHolidays": ["Columbus Day", "Veterans Day"], "extraDaysOff": ["2026-12-24"] }   },   "phases": [     { "name": "Phase 1 — Build", "lead": "the long pole (Adonis)", "start": "2026-01", "end": "2026-06" }@@ -164,6 +165,8 @@ Create a JSON file with three sections:  <!-- prose-lint-enable --> +`project.start` and `project.end` are the project dates and `project.calendar` the working calendar, all optional and all normally set on Setup. In the calendar, `workHolidays` names the federal holidays the plan works, spelled as the app lists them (`New Year's Day`, `Martin Luther King, Jr. Day`, `Washington's Birthday`, `Memorial Day`, `Juneteenth National Independence Day`, `Independence Day`, `Labor Day`, `Columbus Day`, `Veterans Day`, `Thanksgiving Day`, `Christmas Day`), and `extraDaysOff` lists `YYYY-MM-DD` days nobody works. Unknown names and malformed days are dropped. Without a calendar every federal holiday is a day off.+ **Tags** are optional on a phase and on a task or milestone: `"tags": ["Tech"]`, a short list of short strings. The server trims them, drops duplicates that differ only in case (the first spelling wins), caps each at 32 characters and the list at 12, turns a `;` inside a tag into a space (`;` separates tags in the CSV), and@@ -436,7 +439,7 @@ table, the item editor or the batch editor are taken exactly as typed. | Drag a section row on Setup | Move the section; a line shows where it lands. Alt+Up / Alt+Down move a focused row. One Ctrl+Z | | Click a section's name or aside on Setup | Edit it in place: Enter or click away commits, Escape cancels | | Fit | Fit the whole plan into the pane, no horizontal scrolling |-| Auto-schedule | Push every task out to its dependencies, finish to start, skipping weekends and US federal holidays. Never pulls work earlier, so intentional gaps survive. One undo. Disabled when the plan has no dependencies |+| Auto-schedule | Push every task out to its dependencies, finish to start, skipping weekends and the plan's days off (Setup, Working calendar). Never pulls work earlier, so intentional gaps survive. One undo. Disabled when the plan has no dependencies | | Critical | Light up the longest run of work inside every section, cancelled work left out. On/off, and it recomputes as the plan changes | | A- / A+ | Step the text size for both views. Click the percentage to reset | | Collapse all / Expand all | Fold every section to its header, or open them all. Start of the legend |

@@ -237,8 +237,8 @@ rather than a category. - **Project Duration and Time Remaining** in the header, stacked, beside the lens switch (0.57.0, replacing the old "25 weeks" axis-cell count, which changed with the grain and counted the axis padding). Both come from the plan's own dates and never from the grain: Duration runs from the earliest task start or milestone date to the latest task end or milestone date, both days counted, and Remaining runs from today to that last date, today counted. **Cancelled rows are left out**, as Auto-schedule, the critical path and the hours totals leave them out, and the tooltip says how many were; if every dated row is cancelled both read `none` and the tooltip says why. Since 0.75.0 the **project dates** (Setup) win where they are set: Duration runs from the project start to the project end and Remaining from today to the project end, and the rows only stand in for an end that is not set (never on the wrong side of the one that is). Rows that fall outside the dates turn both readouts amber and are counted in the tooltip. (The Analytics "calendar span" card still includes them; it was not changed.) Format: days under two weeks, `16w 4d` style under half a year, then months and years to one decimal. The tooltips give the exact calendar and working-day counts and both dates. Remaining reads `ended` once the last date is past; before the first date it still counts from today, so it can be longer than Duration, and a small `not started` note sits on the readout itself to say why. Both read `none` for a plan with no dated rows. They update on every edit that can move a date (drag, editor, table edit, project dates, auto-schedule, create, delete, paste, undo, redo) and at midnight on a tab left open. The header FITS ITSELF to its content rather than to pixel breakpoints (`fitHeader`): it measures the row and, only while the content is wider than the window, sheds in order the version, the button words and the long labels (Duration, Remaining). If that still does not fit, it wraps onto a second row with the long labels back, and with the button words back too whenever they cost no extra row (they stay off on a phone, where they would). The readouts never shrink, so they are whole at every width; the suite sweeps 360 to 2000px with and without an appName at 100% and 150% text to hold that - **Fit** button beside the cell-size picker: picks the finest grain whose whole span fits the pane, so the plan is fully visible with no horizontal scrolling. Chart-only - **Gantt / Table / Analytics / Setup toggle** pinned first in the header, left of every conditional control so its position never shifts. Four lenses over the same items: the chart answers "when", the table answers "whose, and by when", analytics answers "how much, and is any of it in trouble", and Setup is the plan's structure, its sections. See The table view, The analytics view and The setup view below-- **Auto-schedule** button, with the plan-level controls next to Fit, in the chart and the table lenses. One press lays the WHOLE plan out under two rules at once: no task with dependencies starts before its latest predecessor's end date, and no task starts or ends on a Saturday, a Sunday or a US federal holiday. The handoff date is a MINIMUM and not an answer: it is BACK TO BACK for a task that was overlapping and is pushed onto it, and back to back is a statement about the CHART, since a bar runs from its start to its end and the end is the boundary it stops at, so a successor starting on that date draws flush against it with no gap and no overlap. **PUSH ONLY, since 0.53.0.** A task that already starts on or after its handoff is LEFT WHERE IT IS, however wide the gap, because a gap in a real plan is usually somebody's lead time: an order placed on the Monday and the parts that arrive on the Thursday keep their three days. Through 0.52.0 the pass went both ways and closed every one of those, and there was no way to keep one. Nothing is ever pulled EARLIER now, so the plan cannot drift backwards over a press, and the pass reaches a fixed point in ONE press: the second moves nothing. Pushes still cascade, each successor measured against where its predecessor LANDED and not against the date it shipped with. **CANCELLED WORK IS NOT IN THE PASS AT ALL,** also since 0.53.0: it is never moved, so its dates freeze exactly as set even if they violate something, and it constrains nobody, so a task whose only predecessors are cancelled behaves like an anchor and one with a mix is pushed by its LIVE predecessors alone. The toast counts those rows as their own third number ("5 tasks moved, 15 unchanged, 1 cancelled excluded") rather than folding them into the count of work that was already aligned. A task with no dependencies is an ANCHOR and keeps its start (shifted LATER off a weekend or a holiday if it was on one), because that is the one thing in a plan this cannot derive. Duration is preserved in WORKING days, not calendar days, so a five-day task laid across a weekend, or across Labor Day, still takes five working days: a predecessor ending on the Friday hands off on the Friday and the weekend falls inside the successor's own span, never between the two. Milestones take the same rule with no duration: off a weekend or a holiday to the next working day, and on the day their last dependency ends. The graph crosses sections freely and so does the schedule; a section's displayed range just follows its rows. A dependency CYCLE is left exactly as it is, along with anything downstream of it, and the toast names the rows: there is no honest answer for a row that waits on itself. The whole pass is ONE undo entry and ONE changelog event (`action: "auto-schedule"`, with a count and the names of what moved), and a press that moves nothing writes nothing. Deterministic. Disabled, with a tooltip that says why, when the plan has no dependencies-- **Critical** button, next to it: the LONGEST run of work in the plan. The dependency graph is a DAG, a task WEIGHS its duration in working days (weekends and observed US federal holidays out, the same arithmetic everything else in the app counts with) and a milestone weighs nothing, and the critical path is the maximum-weight path through it, found by the classic longest-path DP. It reads the dates the plan has right now, so it is independent of Auto-schedule and never moves anything. **This is not zero-float CPM** and it deliberately stopped being it in 0.49.0: CPM anchors its backward pass on the plan's latest finish, so it always answers "which chain ends last", and on a real plan that picks a short simple chain running into December over a ten-row interconnected build finishing in November. An isolated row is a path of one and can win if it is genuinely the longest thing there is. **One button, an on/off TOGGLE**, with one constant label and the state carried by its pressed treatment: off, or one longest path inside EVERY section at once, all lit together. 0.49.0 offered a plan-wide reading as a third state of the same button and 0.50.0 dropped it, because on a real plan it lights one section's chain and leaves every other section dark, which is a narrower reading than the per-section answer that contains it. With no label to swap, the button sizes off its own content like every other header action rather than being pinned to the widest of three words. Each lane is answered on its OWN subgraph: the nodes are that section's rows and the edges are the dependencies whose two ends are both in it, so a dependency that crosses sections is not an edge there and can never light up in that mode, and a section with no internal dependencies lights its longest single ROW, which is the same rule rather than an exception to it. **CANCELLED WORK IS NOT A NODE, since 0.53.0:** it can never glow, it carries no weight, and a chain that ran through it is BROKEN at that row, since the node is absent and its predecessors and successors are no longer joined by way of it. A section with a second route round the cancelled row is REROUTED onto it; a section whose only route ran through it falls back to the longest single row left, which may be neither of the two stumps' first halves. The longest-single-row fallback ignores cancelled rows for the same reason: they are not there to be considered. Nothing is deleted from the data, so un-cancelling puts the node, its links and every path through it straight back. Ties are broken deterministically, in this order: more working days, then a greater calendar span (first start to last end), then more rows, then whichever begins earlier in plan order, so exactly one path is ever lit per answer. A GAP adds no weight, because a path's length is the sum of the NODES along it and not the calendar it is spread over, so the gaps 0.53.0's push-only Auto-schedule now preserves cannot promote or demote a chain; the calendar span is reachable only by the second tie-break, where it separates two chains already tied on working days and says the one occupying more of the calendar is the more critical, which is the reading it has always had. The bars, the arrows along the path and any milestone on it glow white and breathe on a 2.6s cycle, in a saturated indigo in light mode and on paper, and the table lens marks the same rows on their left edge. Purely additive: selection outlines, dependency-mode amber and armed red all still read on a glowing row, and hit-testing is untouched. It recomputes live as dates and dependencies change, and the state is a saved preference beside the theme and the milestone style; a browser that stored the old plan-wide mode comes back lit, since that reader had the glow on. A collapsed section hides its own glow with its rows and the rest of the plan keeps glowing. Disabled, with the same message it has always used, when the plan has no dependencies at all: a path is a run of work THROUGH dependencies, and a plan where nothing waits on anything has no runs to be longest+- **Auto-schedule** button, with the plan-level controls next to Fit, in the chart and the table lenses. One press lays the WHOLE plan out under two rules at once: no task with dependencies starts before its latest predecessor's end date, and no task starts or ends on a Saturday, a Sunday or one of the plan's days off (the US federal holidays it takes, see Working calendar). The handoff date is a MINIMUM and not an answer: it is BACK TO BACK for a task that was overlapping and is pushed onto it, and back to back is a statement about the CHART, since a bar runs from its start to its end and the end is the boundary it stops at, so a successor starting on that date draws flush against it with no gap and no overlap. **PUSH ONLY, since 0.53.0.** A task that already starts on or after its handoff is LEFT WHERE IT IS, however wide the gap, because a gap in a real plan is usually somebody's lead time: an order placed on the Monday and the parts that arrive on the Thursday keep their three days. Through 0.52.0 the pass went both ways and closed every one of those, and there was no way to keep one. Nothing is ever pulled EARLIER now, so the plan cannot drift backwards over a press, and the pass reaches a fixed point in ONE press: the second moves nothing. Pushes still cascade, each successor measured against where its predecessor LANDED and not against the date it shipped with. **CANCELLED WORK IS NOT IN THE PASS AT ALL,** also since 0.53.0: it is never moved, so its dates freeze exactly as set even if they violate something, and it constrains nobody, so a task whose only predecessors are cancelled behaves like an anchor and one with a mix is pushed by its LIVE predecessors alone. The toast counts those rows as their own third number ("5 tasks moved, 15 unchanged, 1 cancelled excluded") rather than folding them into the count of work that was already aligned. A task with no dependencies is an ANCHOR and keeps its start (shifted LATER off a weekend or a holiday if it was on one), because that is the one thing in a plan this cannot derive. Duration is preserved in WORKING days, not calendar days, so a five-day task laid across a weekend, or across Labor Day, still takes five working days: a predecessor ending on the Friday hands off on the Friday and the weekend falls inside the successor's own span, never between the two. Milestones take the same rule with no duration: off a weekend or a holiday to the next working day, and on the day their last dependency ends. The graph crosses sections freely and so does the schedule; a section's displayed range just follows its rows. A dependency CYCLE is left exactly as it is, along with anything downstream of it, and the toast names the rows: there is no honest answer for a row that waits on itself. The whole pass is ONE undo entry and ONE changelog event (`action: "auto-schedule"`, with a count and the names of what moved), and a press that moves nothing writes nothing. Deterministic. Disabled, with a tooltip that says why, when the plan has no dependencies+- **Critical** button, next to it: the LONGEST run of work in the plan. The dependency graph is a DAG, a task WEIGHS its duration in working days (weekends and the plan's days off out, the same arithmetic everything else in the app counts with) and a milestone weighs nothing, and the critical path is the maximum-weight path through it, found by the classic longest-path DP. It reads the dates the plan has right now, so it is independent of Auto-schedule and never moves anything. **This is not zero-float CPM** and it deliberately stopped being it in 0.49.0: CPM anchors its backward pass on the plan's latest finish, so it always answers "which chain ends last", and on a real plan that picks a short simple chain running into December over a ten-row interconnected build finishing in November. An isolated row is a path of one and can win if it is genuinely the longest thing there is. **One button, an on/off TOGGLE**, with one constant label and the state carried by its pressed treatment: off, or one longest path inside EVERY section at once, all lit together. 0.49.0 offered a plan-wide reading as a third state of the same button and 0.50.0 dropped it, because on a real plan it lights one section's chain and leaves every other section dark, which is a narrower reading than the per-section answer that contains it. With no label to swap, the button sizes off its own content like every other header action rather than being pinned to the widest of three words. Each lane is answered on its OWN subgraph: the nodes are that section's rows and the edges are the dependencies whose two ends are both in it, so a dependency that crosses sections is not an edge there and can never light up in that mode, and a section with no internal dependencies lights its longest single ROW, which is the same rule rather than an exception to it. **CANCELLED WORK IS NOT A NODE, since 0.53.0:** it can never glow, it carries no weight, and a chain that ran through it is BROKEN at that row, since the node is absent and its predecessors and successors are no longer joined by way of it. A section with a second route round the cancelled row is REROUTED onto it; a section whose only route ran through it falls back to the longest single row left, which may be neither of the two stumps' first halves. The longest-single-row fallback ignores cancelled rows for the same reason: they are not there to be considered. Nothing is deleted from the data, so un-cancelling puts the node, its links and every path through it straight back. Ties are broken deterministically, in this order: more working days, then a greater calendar span (first start to last end), then more rows, then whichever begins earlier in plan order, so exactly one path is ever lit per answer. A GAP adds no weight, because a path's length is the sum of the NODES along it and not the calendar it is spread over, so the gaps 0.53.0's push-only Auto-schedule now preserves cannot promote or demote a chain; the calendar span is reachable only by the second tie-break, where it separates two chains already tied on working days and says the one occupying more of the calendar is the more critical, which is the reading it has always had. The bars, the arrows along the path and any milestone on it glow white and breathe on a 2.6s cycle, in a saturated indigo in light mode and on paper, and the table lens marks the same rows on their left edge. Purely additive: selection outlines, dependency-mode amber and armed red all still read on a glowing row, and hit-testing is untouched. It recomputes live as dates and dependencies change, and the state is a saved preference beside the theme and the milestone style; a browser that stored the old plan-wide mode comes back lit, since that reader had the glow on. A collapsed section hides its own glow with its rows and the rest of the plan keeps glowing. Disabled, with the same message it has always used, when the plan has no dependencies at all: a path is a run of work THROUGH dependencies, and a plan where nothing waits on anything has no runs to be longest - **Click legend** to filter phases, milestones, dependency arrows, or the today line. The legend WRAPS onto as many lines as it needs (0.57.0), so every phase chip on a 20-section plan is visible and clickable; until 0.56.0 it was one line and clipped everything past the pane edge. Below 1150px the chips drop their words and keep the colour dot, as before - **Tag chips in the legend** (0.59.0; rows since 0.60.0). When the plan carries tags, on sections or on rows, the legend leads with a chip per tag (`# Tech 32`: the tag and how many rows choosing it would show, counting the rows in its sections and the rows tagged on their own) and the section chips stand BEHIND them: with no tag chosen they fold away behind one "20 sections" chip (click it to open them all; that is remembered as `prefs.legendSecs`), and with a tag chosen the chips of exactly the sections on screen come back after the tags. A section chip whose name prefix is a chosen tag drops the repeat ("Laser workcells" behind "# Tech"). Choosing tags filters by EFFECTIVE tags: a row's effective tags are its own plus its section's, and a row is shown when ANY of them is chosen. So every row of a chosen section is shown, tagged or not; a row tagged "long-lead" in an untagged section is shown by "long-lead", with its section header above it and the section's other rows hidden; and a row whose own tags do not match, in a section that does not match, is hidden. A section header is shown when the section matches or any of its rows does, and while the filter hides some of its rows its count reads "2 of 3". A delete or a tag edit that takes the last carrier of a chosen tag out of the plan drops it from the filter, and its Ctrl+Z puts the filter back with the tag. This holds in the chart and the table alike; the readouts, Analytics and everything else stay whole-plan. It composes with the section chips (which still switch a shown section off) and with Collapse all (which then counts only the shown sections). **Clear tags** shows everything again. The filter is view state, per person, in `prefs.tagFilter`, so it survives a refresh; a tag the plan no longer has drops out of it. A plan with no tags has no tag chips and no fold, and its legend is what it always was - **Current in the legend** (0.70.0), between Owner and Overdue: the working set for a review. A row is **current** when it has STARTED (a task's start, a milestone's date: today or earlier) and is not complete or cancelled, so it is the work under way plus the work that should be (a task still "not started" after its start date shows). Future rows and finished ones are hidden. Counts tasks and milestones apart like Overdue (`data-tasks` / `data-ms`); `prefs.currentOnly`; derived on every render and at midnight, never stored. It ANDs with the other filters, so Current plus Overdue shows the overdue rows (every overdue row is current), and it applies to the table too. A month-only date counts from the first of its month; since 0.70.0 a month-only DEADLINE is due at the end of its month for Overdue (before, such a row could never be overdue).@@ -282,6 +282,7 @@ rather than a category. - **Auto-load** saved state on page refresh - **Dynamic date range** computed from the data every render - **Project dates** (0.75.0) on Setup, the first card: a start and an end, each the browser's date field. They replace the header's start button, which moved the whole plan and was one misclick from shifting every date for the whole team. Owner only (the same rule as Sharing: the page disables the fields for everyone else and the server keeps the owner's dates whatever another save carries). On the chart each date is a dashed amber line with a `start` / `end` tag, and the time outside them is hatched over the bars, so a bar that runs past the end is hatched where it does. The card lists the rows outside the dates (up to 12, each a link that opens the row on the chart), and says when one is not set. Every change is one Ctrl+Z and one changelog line (`plan.dates`). A year still being typed (0002, 0020) is never committed; an end before the start is refused with a reason+- **Working calendar** (0.76.0, issue #3) on Setup, the second card: the eleven federal holidays as checkboxes (ticked = a day off, untick one the team works) and a list of extra days off (a date field and Add day off; each one a chip with a remove button). Stored as `project.calendar = { workHolidays: [names], extraDaysOff: [YYYY-MM-DD] }` in the data file or the sidecar's `calendar` (the sidecar's wins, like the project dates). Owner only, with the same server rule as the dates. Every working-day helper reads it (`isOffDay`, `nextBiz`, `bizBetween`, `addBiz`), so Auto-schedule, Critical, Analytics, the header's workdays and the day grain's shading all follow it. One Ctrl+Z and one changelog line (`plan.calendar`) per change - **Cell size** picker: Days, Weeks, Months, Quarters, Years. Each grain has its own minimum cell width sized to the widest label it draws, so a fine grain scrolls rather than squashing while a coarse one stretches to fill the pane. Day and week positions are exact; month, quarter and year approximate within a month - **Bar labels** put a short label on the bar body (`note`, e.g. `6m`), set in the item editor's "label on the bar" field. The double-click that used to open a one-field label editor on the bar is gone (0.65.0): the first click of it already opens the item editor - **Milestones are editable too**: drag one sideways to move its date, or click it for the item editor, which hides the fields a milestone does not have (start, effort, bar label, dependencies)@@ -471,7 +472,7 @@ one person full time for each working day of it, which put a real plan of 154 ei windows at 38,000 hours. 0 is an estimate (no work), not the same as blank. A milestone is a date rather than work and carries no hours; the owner table counts milestones separately as `+nM`. Working hours LEFT is still calendar capacity: working days from-today to the plan's end, Monday to Friday, never a US federal holiday, at 8h a day.+today to the plan's end, Monday to Friday, never one of the plan's days off, at 8h a day.  Seven cards: @@ -514,7 +515,14 @@ is a Saturday, so it is observed on Friday 31 December 2027. They count as non-working everywhere: Auto-schedule steps over them (forwards, since it only ever pushes later), the critical path weighs its nodes in working days without them, and every hours figure excludes them. On the chart at day grain they get a weekend-style band in a different colour, with the holiday's name in-a tooltip on the shaded date above the chart, and a `US holiday` key in the legend.+a tooltip on the shaded date above the chart, and a `Holiday` key in the legend.++**A plan can keep its own calendar (0.76.0).** `project.calendar.workHolidays` names the+holidays the plan works (Adom works Columbus Day and Veterans Day) and+`project.calendar.extraDaysOff` adds weekdays nobody works; the owner sets both on Setup.+Everything above then reads the plan's days off instead of the federal list: a worked+holiday is a normal working day and is not shaded, and an extra day off is shaded and+skipped like a holiday. Without a calendar it is the federal list, exactly as before.  **Re-running Auto-schedule on a plan written before 0.45.0 may move dates around a holiday. That is intended.**@@ -703,7 +711,8 @@ Each event records the action, the item, the before and after dates, the day shi  Actions are `dates`, `plan.shift`, `auto-schedule`, `milestone`, `milestone.rename`, `note`, `owner`, `status`, `desc`, `effort`, `tags`, `phase.tags`, `tag.create`, `tag.rename`,-`tag.color`, `tag.delete`, `dep.add`, `dep.remove` and `reorder`.+`tag.color`, `tag.delete`, `dep.add`, `dep.remove`, `reorder`, `plan.dates` (0.75.0) and+`plan.calendar` (0.76.0, `from`/`to` each `{ workHolidays, extraDaysOff }`).  The `tag.*` actions (0.61.0) are the tag registry's own: `tag.create` (New tag; `to.color` when it was made with one) reads `Drew created the tag "someday"`, `tag.rename` reads

@@ -60,6 +60,7 @@ Saved by the adom-gantt server and shared with everyone the plan is shared with. | Changelog | Every change, who made it and when, in an append-only file the server checks for tampering | | Backups | Daily, and before every import or compaction; the last 30 are kept | | Project dates | Owner only; the dashed lines and the header's clock follow them |+| Working calendar | Owner only; which holidays the plan works and its extra days off. Every working-day count follows it | | Sharing (only me, the org, anyone signed in) | Owner only | | Google Chat digest | Owner only | | Sign-in sessions and the agent key | Never shown in the page |

@@ -3,6 +3,39 @@ Decisions taken while building, and the places where the plan and the code disagreed. Newest first. +## Build notes, 2026-10-30 (0.76.0, a working calendar per plan, issue #3)++Issue #3 (Drew, 2026-09-29): every observed federal holiday was a day off, hardcoded, and Adom+works Columbus Day and Veterans Day. On an Adom plan Auto-schedule pushed work off 12 Oct and+11 Nov, Critical under-weighted any task across them, and Analytics lost 8 hours per holiday+per task.++- `project.calendar = { workHolidays, extraDaysOff }`, exactly the issue's proposal. The+  owner sets it on Setup (a card after Project dates: eleven checkboxes, and extra days off+  as chips); the sidecar's `calendar` wins over the data file's, the way `dates` does, and+  the server keeps the owner's whatever another save carries.+- One change at the bottom of the arithmetic: `planOffDays(y)` is the federal set minus the+  worked ones plus the extra weekdays, cached per year and cleared on a change, and+  `isHoliday`, `holidayName` and `holidaysBetween` read it. Everything above them (isOffDay,+  nextBiz, bizBetween, addBiz, Auto-schedule, Critical, Analytics, the header) follows with+  no change of its own. An extra day off that is a weekend is left out of the set, so the set+  and the weekend still never overlap and bizBetween's flat subtraction stays right.+- nextBiz/prevBiz gave up after 10 closed days in a row, which was safe when the longest run+  was 3; a two-week shutdown is now possible, so the guard is a year.+- The day grain's bands and the header cell titles follow the calendar (a worked holiday is+  not shaded; an extra day says "a day off on this plan's calendar"), and the grid memo's key+  includes the calendar so a change redraws it.+- The legend key is "Holiday" now, not "US holiday", since it shades the plan's own days off.+- Docs: README's "Move the whole plan" paragraph still described the header start button+  0.75.0 removed; gone. A sentence about keeping your place under filters had been glued+  onto the Project dates paragraph; moved back to Legend filtering.++Tests: ui `--only calendar` (19: card, save, workdays, extra day, duplicates, changelog,+the arithmetic, day-grain shading, Auto-schedule onto Columbus Day, undo/redo, reload,+export, team view read-only, back to default, a data file's calendar with junk dropped);+server (owner sets it with junk dropped, a member's save and an old tab's save keep it,+export, changelog sentences including a malformed event, empty = default).+ ## Build notes, 2026-10-30 (0.75.1, many people at once: the freeze, and a suite for it)  Drew: "when we had about 6 people during the meeting all sign in, it lagged everyone's laptops

@@ -2,7 +2,7 @@   "slug": "adom-gantt",   "title": "Adom Gantt",   "type": "app",-  "version": "0.75.1",+  "version": "0.76.0",   "description": "Interactive Gantt chart viewer for project timelines, with a table view and an analytics page over the same data. Data-driven, dark by default with a print-friendly light mode, and fully editable in the browser: drag bars to move or resize, multi-select and batch-shift dates, manage dependency arrows inline, reorder rows, filter by phase, and undo. One click auto-schedules the whole plan so every dependency lines up finish-to-start on working days, skipping weekends and US federal holidays, pushing work LATER only so a lead-time gap you set on purpose is never closed, and one more lights up the critical path, meaning the longest run of work inside every section at once. Cancelled work is left out of both: it never moves, it constrains nothing and it can never glow. Dependency arrows are coloured by the phase of the task they come out of, so where a chain starts reads at a glance. Toggle to the table for every task and milestone as a row with owner, deadline and status, filtered per owner and edited in place, or to analytics for total, remaining and average hours, one row per person carrying both their hours and their status counts, per-section totals, milestones, dependency stats and what is overdue. Copy and paste rows: Ctrl+C the selected tasks and milestones, Ctrl+V to drop clones directly below a selected row or at the end of the lane you are looking at, with dependencies AMONG the copied rows remapped onto the copies so a duplicated chain is still a chain, links pointing outside it left naming the originals, and the whole paste one undo and one changelog line. Five statuses in lifecycle order, not started, in progress, complete, blocked, cancelled, with cancelled keeping the row and its history on the plan while taking its hours out of every total. Every edit is recorded in an append-only changelog so an AI can read what a human changed and build on it. Imports JSON, CSV, MS Project XML and Jira CSV; exports JSON, CSV, SVG and a self-contained HTML snapshot.",   "main": "server.js",   "bin": {

@@ -2,7 +2,7 @@   "slug": "adom-gantt",   "title": "Adom Gantt",   "type": "app",-  "version": "0.75.1",+  "version": "0.76.0",   "description": "Interactive Gantt chart viewer for project timelines, with a table view and an analytics page over the same data. Data-driven, dark by default with a print-friendly light mode, and fully editable in the browser: drag bars to move or resize, multi-select and batch-shift dates, manage dependency arrows inline, reorder rows, filter by phase, and undo. One click auto-schedules the whole plan so every dependency lines up finish-to-start on working days, skipping weekends and US federal holidays, pushing work LATER only so a lead-time gap you set on purpose is never closed, and one more lights up the critical path, meaning the longest run of work inside every section at once. Cancelled work is left out of both: it never moves, it constrains nothing and it can never glow. Dependency arrows are coloured by the phase of the task they come out of, so where a chain starts reads at a glance. Toggle to the table for every task and milestone as a row with owner, deadline and status, filtered per owner and edited in place, or to analytics for total, remaining and average hours, one row per person carrying both their hours and their status counts, per-section totals, milestones, dependency stats and what is overdue. Copy and paste rows: Ctrl+C the selected tasks and milestones, Ctrl+V to drop clones directly below a selected row or at the end of the lane you are looking at, with dependencies AMONG the copied rows remapped onto the copies so a duplicated chain is still a chain, links pointing outside it left naming the originals, and the whole paste one undo and one changelog line. Five statuses in lifecycle order, not started, in progress, complete, blocked, cancelled, with cancelled keeping the row and its history on the plan while taking its hours out of every total. Every edit is recorded in an append-only changelog so an AI can read what a human changed and build on it. Imports JSON, CSV, MS Project XML and Jira CSV; exports JSON, CSV, SVG and a self-contained HTML snapshot.",   "main": "server.js",   "bin": {

@@ -984,6 +984,19 @@ function describeEvent(e) {     ['start', 'end'].forEach(k => { if (fld('from', k, '') !== fld('to', k, '')) parts.push(`the project ${k} to ${one(k, 'to')} (was ${one(k, 'from')})`); });     return `${who} set ${parts.join(' and ') || 'the project dates'}${via}`;   }+  // The working calendar (0.76.0), set by the owner on Setup.+  if (action === 'plan.calendar') {+    const list = (side, k) => { const v = fld(side, k, []); return Array.isArray(v) ? v.filter(x => typeof x === 'string') : []; };+    const parts = [];+    const wf = list('from', 'workHolidays'), wt = list('to', 'workHolidays');+    wt.filter(n => !wf.includes(n)).forEach(n => parts.push(`works ${n}`));+    wf.filter(n => !wt.includes(n)).forEach(n => parts.push(`takes ${n} off`));+    const xf = list('from', 'extraDaysOff'), xt = list('to', 'extraDaysOff');+    const added = xt.filter(d => !xf.includes(d)), gone = xf.filter(d => !xt.includes(d));+    if (added.length) parts.push(`added ${added.map(fmtDate).join(', ')} as ${added.length === 1 ? 'a day' : 'days'} off`);+    if (gone.length) parts.push(`made ${gone.map(fmtDate).join(', ')} ${gone.length === 1 ? 'a working day' : 'working days'} again`);+    return `${who} changed the working calendar: ${parts.join('; ') || 'no change'}${via}`;+  }   if (action === 'timeline.start') {     const f = fld('from', 'start', ''), t = fld('to', 'start', '');     return `${who} set the timeline to start at ${fmtDate(t)}${f ? ` (was ${fmtDate(f)})` : ''}${via}`;@@ -1365,6 +1378,22 @@ function normalizeDates(v) {   const day = x => (typeof x === 'string' && /^\d{4}-\d{2}-\d{2}$/.test(x) && !isNaN(Date.parse(x + 'T00:00:00Z'))) ? x : '';   return { start: day(v.start), end: day(v.end) }; }+// The working calendar (0.76.0): { workHolidays: [federal holiday names this plan works],+// extraDaysOff: [YYYY-MM-DD weekdays nobody works] }. Unknown names and malformed days+// are dropped, so a bad value can never reach the merged plan.+const FED_HOLIDAY_NAMES = ["New Year's Day", 'Martin Luther King, Jr. Day', "Washington's Birthday", 'Memorial Day',+  'Juneteenth National Independence Day', 'Independence Day', 'Labor Day', 'Columbus Day', 'Veterans Day',+  'Thanksgiving Day', 'Christmas Day'];+function normalizeCalendar(v) {+  if (!v || typeof v !== 'object' || Array.isArray(v)) return undefined;+  const wh = Array.isArray(v.workHolidays) ? v.workHolidays : [];+  const xd = Array.isArray(v.extraDaysOff) ? v.extraDaysOff : [];+  const day = x => (typeof x === 'string' && /^\d{4}-\d{2}-\d{2}$/.test(x) && !isNaN(Date.parse(x + 'T00:00:00Z'))) ? x : '';+  return {+    workHolidays: FED_HOLIDAY_NAMES.filter(n => wh.includes(n)),+    extraDaysOff: [...new Set(xd.map(day).filter(Boolean))].sort(),+  };+} function tidyStateTags(st) {   if (!st || typeof st !== 'object' || Array.isArray(st)) return st;   const side = o => {@@ -1924,6 +1953,13 @@ function mergedData() {     if (!data.project || typeof data.project !== 'object') data.project = {};     ['start', 'end'].forEach(k => { if (dates[k]) data.project[k] = dates[k]; else delete data.project[k]; });   }+  // The working calendar (0.76.0), the same way; an empty one is the default and says nothing.+  const cal = normalizeCalendar(state.calendar);+  if (cal) {+    if (!data.project || typeof data.project !== 'object') data.project = {};+    if (cal.workHolidays.length || cal.extraDaysOff.length) data.project.calendar = cal;+    else delete data.project.calendar;+  }   if (Array.isArray(state.order) && state.order.length === data.items.length) {     const reordered = state.order.map(u => byUid.get(u)).filter(r => r && data.items.includes(r));     // All or nothing. A single unresolved uid would otherwise drop a row.@@ -2808,6 +2844,12 @@ const server = http.createServer(async (req, res) => {           if (now && mayDate) store.dates = now;           else if (was) store.dates = was;           else delete store.dates;+          // The working calendar (0.76.0) is the owner's in exactly the same way.+          let wasCal; try { const old = loadState(); wasCal = old && normalizeCalendar(old.calendar); } catch (e) {}+          const nowCal = normalizeCalendar(store.calendar);+          if (nowCal && mayDate) store.calendar = nowCal;+          else if (wasCal) store.calendar = wasCal;+          else delete store.calendar;         }         store.stateRev = cur + 1;         delete store.baseRev;

@@ -609,6 +609,26 @@ async function main() {   await asPost(drew, '/log', { events: [{ action: 'plan.dates', from: { start: '', end: '' }, to: { start: '2026-09-14', end: '2026-12-18' } }] });   const pdMd = (await as(drew, '/changelog?format=md')).t;   ok(/set the project start to 14-Sep-2026 \(was not set\) and the project end to 18-Dec-2026 \(was not set\)/.test(pdMd), 'the changelog says what was set, in one line', pdMd.slice(-300));+  // The working calendar (0.76.0, issue #3) is the owner's in the same way.+  const sCal = async () => ((await as(drew, '/state')).j || {}).calendar;+  r = await asPost(drew, '/save', Object.assign({}, plain, { dates: { start: '2026-09-14', end: '2026-12-18' }, calendar: { workHolidays: ['Veterans Day', 'Columbus Day', 'Festivus'], extraDaysOff: ['2026-12-24', 'later', '2026-11-27', '2026-12-24'] } }));+  let sc = await sCal();+  ok(r.status === 200 && sc && sc.workHolidays.join() === 'Columbus Day,Veterans Day' && sc.extraDaysOff.join() === '2026-11-27,2026-12-24', 'the owner sets the working calendar; unknown names, bad days and repeats are dropped', sc);+  r = await asPost(ana, '/save', Object.assign({}, plain, { calendar: { workHolidays: ['Christmas Day'], extraDaysOff: [] } }));+  sc = await sCal();+  ok(r.status === 200 && sc && sc.workHolidays.join() === 'Columbus Day,Veterans Day' && sc.extraDaysOff.length === 2, 'a member\'s save keeps the owner\'s calendar, whatever it carries', sc);+  r = await asPost(ana, '/save', plain);+  sc = await sCal();+  ok(r.status === 200 && sc && sc.workHolidays.length === 2, 'and so does a save with no calendar at all (a tab older than 0.76.0)', sc);+  const exc = (await as(drew, '/export/json')).j;+  ok(exc && exc.project && exc.project.calendar && exc.project.calendar.workHolidays.join() === 'Columbus Day,Veterans Day' && exc.project.calendar.extraDaysOff.join() === '2026-11-27,2026-12-24', 'the merged plan carries it as project.calendar', exc && exc.project);+  await asPost(drew, '/log', { events: [{ action: 'plan.calendar', from: { workHolidays: [], extraDaysOff: [] }, to: { workHolidays: ['Columbus Day'], extraDaysOff: ['2026-11-27'] } }] });+  await asPost(drew, '/log', { events: [{ action: 'plan.calendar', from: { workHolidays: ['Columbus Day'] }, to: 'junk' }] });+  const calMd = (await as(drew, '/changelog?format=md')).t;+  ok(/changed the working calendar: works Columbus Day; added 27-Nov-2026 as a day off/.test(calMd) && /changed the working calendar: takes Columbus Day off/.test(calMd), 'the changelog says what changed, and a malformed event still reads', calMd.slice(-400));+  r = await asPost(drew, '/save', Object.assign({}, plain, { dates: { start: '2026-09-14', end: '2026-12-18' }, calendar: { workHolidays: [], extraDaysOff: [] } }));+  const exd = (await as(drew, '/export/json')).j;+  ok(r.status === 200 && exd && exd.project && !('calendar' in exd.project), 'an empty calendar is the default, and the merged plan says nothing', exd && exd.project);   // The live stream of someone the owner stops sharing with is told and closed.   const live = await fetch(S.base + '/live?cid=ana1', { headers: Object.assign({ Cookie: ana.cookie }, XFF) });   const reader = live.body.getReader(); let got = '';