@umriss-ui/schedule 0.7.1 → 0.35.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.7.1
+# @umriss-ui/schedule 0.35.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -915,7 +915,7 @@ npm install @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/installation/
 
-The command brings its two peers along: core for the formats and the wording, charts for the time scale and the operating calendar ([ADR-0022](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0022-the-schedule-is-a-package-that-depends-on-core-and-charts.md)). React 18 or 19 is a peer as well and stays the application's own. The stylesheets load themselves - each package's script imports its own, so there is nothing to import by hand; `@umriss-ui/schedule/styles.css` stays exported for setups that link stylesheets themselves.
+The command brings its two peers along: core for the formats and the wording, charts for the time scale and the operating calendar ([ADR-0022](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0022-the-schedule-is-a-package-that-depends-on-core-and-charts.md)). React 19 or newer is a peer as well and stays the application's own. The stylesheets load themselves - each package's script imports its own, so there is nothing to import by hand; `@umriss-ui/schedule/styles.css` stays exported for setups that link stylesheets themselves.
 
 The plan is plain data ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). A lane is a person, a vehicle or a room, declared in JSX by its id. A task is an id, a colour and a name; a subtask is a main time on one lane, belonging to a task, with an optional lead-in and lead-out; a dependency joins two subtasks of one task with a lag. Times are epoch milliseconds.
 
@@ -1028,7 +1028,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -1278,8 +1278,9 @@ Under forced colours the plot paints itself in the system colours: the work in t
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `height` | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 77 more |
-| `laneHeight` | `number` | `44` | Height of one lane in pixels.<br>Shown in: [Scroll more lanes than fit (Lanes)](#/lane/many-lanes) |
+| `ref` | `Ref<`[`ScheduleHandle`](#type-ScheduleHandle)`>` | — | Receives the `ScheduleHandle` - not an element.<br>Shown in: [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+| `height` | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
+| `laneHeight` | `number` | `44` | Height of one lane in pixels.<br>Shown in: [Scroll more lanes than fit (Lanes)](#/lane/many-lanes), [Measure a plan (Benchmark)](#/benchmark/benchmark) |
 | `headerWidth` | `number` | `160` | Width of the lane headers in pixels - at most 40 % of the schedule, so that on a phone the plot keeps the larger part.<br>Shown in: [What a lane header says (Lanes)](#/lane/lane-headers), [Scroll more lanes than fit (Lanes)](#/lane/many-lanes), [Group lanes under a head (Lane groups)](#/lane-groups/a-group) and 1 more |
 | `calendar` | [`CalendarInput`](#type-CalendarInput) | `[]` | A working calendar: the intervals in which time counts. Nights and weekends outside them are cut out of the axis. Without intervals every hour counts, as on the wall clock.<br>Shown in: [Cut the nights out of the axis (Time axis and calendar)](#/time-axis/working-calendar), [Plan in office hours only (Time axis and calendar)](#/time-axis/office-hours), [Plan the sprint around leave (Scenarios)](#/scenarios/plan-the-sprint-around-leave) |
 | `zoomLimits` | [`ZoomLimits`](#type-ZoomLimits) | one hour to 28 days | The narrowest and widest time span zoom may reach, in milliseconds.<br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |
@@ -1295,20 +1296,20 @@ Under forced colours the plot paints itself in the system colours: the work in t
 | `label` | `(subtask: `[`Subtask`](#/subtasks/type-Subtask)`) => string` | — | What stands written in a bar: a function from a subtask to a line of text, or nothing for bars without text. The text is cut off with an ellipsis where the bar is too narrow for it and left out where even that would say nothing; a bar that began before the view keeps its text at the view's edge.<br>Shown in: [Plan a day in the machine shop](#/schedule/machine-plan), [Plan a sprint for a team (Subtasks)](#/subtasks/a-sprint), [Write into the bars (Bar labels)](#/bar-labels/bar-labels) and 7 more |
 | `tooltip` | `false \| ((target: `[`ScheduleTooltipTarget`](#/tooltip/type-ScheduleTooltipTarget)`) => ReactNode)` | — | The tooltip on a hovered subtask or dependency: its order, its times, its parts and its findings. `false` switches it off; a function receives what the pointer rests on and returns content of the application's own.<br>Shown in: [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is), [Write your own tooltip content (Tooltip)](#/tooltip/own-tooltip), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 1 more |
 | `now` | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there.<br>Shown in: [Plan a day in the machine shop](#/schedule/machine-plan), [Mark the present (Now line)](#/now-line/now-line), [Follow the clock (Now line)](#/now-line/follow-the-clock) and 2 more |
-| `children` | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 77 more |
+| `children` | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
 
 ###### Events
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `onIntent` | `(intent: `[`Intent`](#type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Cut the nights out of the axis (Time axis and calendar)](#/time-axis/working-calendar), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around) and 18 more |
-| `onInteraction` | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu.<br>Shown in: [Report what the pointer is on (Interactions)](#/interactions/report-the-pointer), [Open a context menu (Interactions)](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 2 more |
+| `onInteraction` | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu.<br>Shown in: [Report what the pointer is on (Interactions)](#/interactions/report-the-pointer), [Open a context menu (Interactions)](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 3 more |
 
 ###### Accessibility
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ariaLabel` *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38".<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 77 more |
+| `ariaLabel` *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38".<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
 
 ###### Styling
 
@@ -1319,6 +1320,17 @@ Under forced colours the plot paints itself in the system colours: the work in t
 
 ##### Types on this page
 
+###### `ScheduleHandle`
+
+What a schedule offers a caller imperatively: the arithmetic between a
+point on the screen and a time on a lane. Everything else is props.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `positionAt` *required* | `(clientX: number, clientY: number) => { time: number; lane: string \| null } \| null` | — | The time and the lane at a client point, or null outside the plot.<br>Shown in: [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+| `clientPointOf` *required* | `(time: number, lane?: string) => { x: number; y: number } \| null` | — | The client point of a time - on the middle of a lane where one is named - or null while the schedule is not on screen.<br>Shown in: [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+| `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
+
 ###### `CalendarInput`
 
 From `@umriss-ui/charts`.
@@ -1358,9 +1370,9 @@ type IntentKind = Intent["kind"];
 
 ###### `PlacingItem`
 
-What the application says it is dragging in, while it drags it
-(schedule-refinement 07): the browser hands over the dragged data only on
-the drop, so the ghost before the drop can only come from the caller.
+What the application says it is dragging in, while it drags it: the
+browser hands over the dragged data only on the drop, so the ghost before
+the drop can only come from the caller.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -1498,7 +1510,7 @@ Put the subtask on another lane.
 ###### `PlaceIntent`
 
 Put work on the plan that was not on it: the answer to a drag from outside
-the schedule (schedule-refinement 07). It carries no subtask id - there is
+the schedule. It carries no subtask id - there is
 no subtask yet; the caller creates one, with its own identity, from
 `subtaskFromPlace`.
 
@@ -1654,7 +1666,7 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The identity subtasks name in their `lane`.<br>Shown in: [What a lane header says](#/lane/lane-headers), [Scroll more lanes than fit](#/lane/many-lanes), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 77 more |
+| `id` *required* | `string` | — | The identity subtasks name in their `lane`.<br>Shown in: [What a lane header says](#/lane/lane-headers), [Scroll more lanes than fit](#/lane/many-lanes), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 78 more |
 | `label` | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader.<br>Shown in: [What a lane header says](#/lane/lane-headers), [Scroll more lanes than fit](#/lane/many-lanes), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 77 more |
 
 ### Lane groups
@@ -1671,7 +1683,7 @@ A group is structure, never a lane: nothing sits on it, no finding is reported f
 
 Folded, a group shows a miniature: every lane in it as a thin strip with its work in the tasks' colours. Dependencies still arrive at the right strip, findings are marked on the row, and a strip can be hovered and selected. Labels, appearances and grips need room and wait for the group to open.
 
-Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold - see [View](#/view).
+Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold the planner makes - see [View](#/view).
 
 #### Examples
 
@@ -1765,7 +1777,7 @@ export default function Nesting() {
 
 ##### Fold groups from outside
 
-`foldAll`, `unfoldAll` and `toggleGroup` fold from outside, and `view.folded` says what is folded - start from `initialView`, keep what `onViewChange` reports.
+`foldAll`, `unfoldAll` and `toggleGroup` fold from outside, and `view.folded` says what is folded - start from `initialView`, go to a whole view with `setView`, keep what `onViewChange` reports.
 
 ```tsx
 import { Button, Stack, Text } from "@umriss-ui/core";
@@ -1910,8 +1922,8 @@ import { useSchedule } from "@umriss-ui/schedule";
 import type { Subtask, Task } from "@umriss-ui/schedule";
 
 /* The schedule keeps the fold from here on. To store it, keep what
-   `onViewChange` reports; to steer it, use the setters `useSchedule` hands
-   back. */
+   `onViewChange` reports; to steer it, use `setView` and the setters
+   `useSchedule` hands back. `initialView` is read once. */
 
 const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
 
@@ -2167,21 +2179,21 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` *required* | `readonly `[`Subtask`](#type-Subtask)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 77 more |
-| `tasks` *required* | `readonly `[`Task`](#type-Task)`[]` | — | The tasks the subtasks belong to - their identity and their colour. A subtask whose task is not among them is drawn in a muted colour.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 77 more |
+| `data` *required* | `readonly `[`Subtask`](#type-Subtask)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 78 more |
+| `tasks` *required* | `readonly `[`Task`](#type-Task)`[]` | — | The tasks the subtasks belong to - their identity and their colour. A subtask whose task is not among them is drawn in a muted colour.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 78 more |
 
 ##### `Subtask`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the subtask.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 74 more |
-| `task` *required* | `string` | — | The id of the task it belongs to.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
-| `lane` *required* | `string` | — | The id of the lane it sits on.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
-| `from` *required* | `number` | — | Start of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
-| `to` *required* | `number` | — | End of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
+| `id` *required* | `string` | — | The caller's identity of the subtask.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 75 more |
+| `task` *required* | `string` | — | The id of the task it belongs to.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
+| `lane` *required* | `string` | — | The id of the lane it sits on.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
+| `from` *required* | `number` | — | Start of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
+| `to` *required* | `number` | — | End of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
 | `leadIn` | `number` | — | Duration of the lead-in before the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 25 more |
 | `leadOut` | `number` | — | Duration of the lead-out after the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 22 more |
-| `name` | `string` | — | What the subtask is called, where the schedule names it.<br>Shown in: [Plan a sprint for a team](#/subtasks/a-sprint), [Write into the bars (Bar labels)](#/bar-labels/bar-labels), [Join the stops of a tour (Dependencies)](#/dependencies/stops-of-a-tour) and 27 more |
+| `name` | `string` | — | What the subtask is called, where the schedule names it.<br>Shown in: [Plan a sprint for a team](#/subtasks/a-sprint), [Write into the bars (Bar labels)](#/bar-labels/bar-labels), [Join the stops of a tour (Dependencies)](#/dependencies/stops-of-a-tour) and 28 more |
 | `appearance` | `readonly `[`SubtaskAppearance`](#type-SubtaskAppearance)`[]` | — | What the bar says besides its colour: `"provisional"`, `"fixed"`, `"muted"`, `"open"`. Several hold at once; `"provisional"` and `"fixed"` contradict, and the later one in the list wins.<br>Shown in: [Plan a sprint for a team](#/subtasks/a-sprint), [Provisional (Appearances)](#/appearances/provisional), [Fixed (Appearances)](#/appearances/fixed) and 3 more |
 | `progress` | `number` | — | The share of the work that is done, from 0 to 1, drawn as a filled part of the bar. Without it nothing is claimed - an empty bar and a bar at zero per cent are two different statements.<br>Shown in: [Progress (Appearances)](#/appearances/progress), [Several at once (Appearances)](#/appearances/combinations) |
 
@@ -2189,9 +2201,9 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the task.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 69 more |
-| `color` *required* | `string` | — | Any CSS colour - a literal, a token, `light-dark(…)`. The colour means what the caller's domain needs it to mean.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 69 more |
-| `name` | `string` | — | What the task is called, where the schedule names it.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 69 more |
+| `id` *required* | `string` | — | The caller's identity of the task.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
+| `color` *required* | `string` | — | Any CSS colour - a literal, a token, `light-dark(…)`. The colour means what the caller's domain needs it to mean.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
+| `name` | `string` | — | What the task is called, where the schedule names it.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
 
 ##### Types on this page
 
@@ -2328,7 +2340,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -2642,7 +2654,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -2825,7 +2837,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -3156,16 +3168,16 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` *required* | `readonly `[`Dependency`](#type-Dependency)`[]` | — | The dependencies, as the caller holds them.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
+| `data` *required* | `readonly `[`Dependency`](#type-Dependency)`[]` | — | The dependencies, as the caller holds them.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 28 more |
 
 ##### `Dependency`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the dependency.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 26 more |
-| `from` *required* | `string` | — | The id of the subtask it leaves.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 26 more |
-| `to` *required* | `string` | — | The id of the subtask it arrives at.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 26 more |
-| `lag` *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 26 more |
+| `id` *required* | `string` | — | The caller's identity of the dependency.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
+| `from` *required* | `string` | — | The id of the subtask it leaves.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
+| `to` *required* | `string` | — | The id of the subtask it arrives at.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
+| `lag` *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
 | `leaves` | `"main" \| "leadOut"` | `"leadOut"` | Where it leaves: at the end of the main time, or after the lead-out. The predecessor counts as ended once its lead-out is.<br>Shown in: [Choose what a dependency connects](#/dependencies/anchors), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
 | `arrives` | `"main" \| "leadIn"` | `"leadIn"` | Where it arrives: at the start of the main time, or before the lead-in. The lag must have run out before the successor's lead-in begins.<br>Shown in: [Choose what a dependency connects](#/dependencies/anchors), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 1 more |
 | `route` | [`DependencyRoute`](#type-DependencyRoute)<br>`"curve" \| "straight" \| "orthogonal"` | — | How this one is drawn, where it is not drawn like the rest. It changes the picture and never the finding: whether a dependency is violated follows from `leaves` and `arrives` alone.<br>Shown in: [Per dependency (Routes)](#/routes/per-dependency) |
@@ -3460,7 +3472,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -3803,7 +3815,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4545,7 +4557,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4681,7 +4693,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4916,7 +4928,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -5143,7 +5155,7 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `type` *required* | `"click" \| "contextmenu" \| "hover"` | — | `"hover"` is reported when the target under the pointer changes, not on every movement.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer), [Open a context menu](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 1 more |
-| `hit` *required* | [`ScheduleHit`](#type-ScheduleHit) | — | What the pointer is on.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer), [Open a context menu](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 1 more |
+| `hit` *required* | [`ScheduleHit`](#type-ScheduleHit) | — | What the pointer is on.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer), [Open a context menu](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 2 more |
 | `clientX` *required* | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens.<br>Shown in: [Open a context menu](#/interactions/open-a-context-menu), [Place a mark of your own (The handle)](#/handle/place-a-mark), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
 | `clientY` *required* | `number` | — | The pointer's vertical client coordinate.<br>Shown in: [Open a context menu](#/interactions/open-a-context-menu), [Place a mark of your own (The handle)](#/handle/place-a-mark), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
 | `time` *required* | `number` | — | The wall-clock instant under the pointer.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer) |
@@ -5556,9 +5568,9 @@ import { useSchedule } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/view/
 
-The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#/api/useSchedule) hands back holds it, and `onViewChange` reports every change of it - a pan or zoom at most once per frame; keep it where the application keeps things and hand it back through `initialView`.
+The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#/api/useSchedule) hands back holds it, and `onViewChange` reports every change the planner makes to it - a pan or zoom at most once per frame; keep it where the application keeps things and go back to it with `setView`.
 
-A view that differs in content from the last one handed in applies at once, and what it leaves out goes back to its default; the same one again changes nothing. Without a span the schedule shows the extent of its subtasks, within `zoomLimits`. A group no `LaneGroup` declares falls out.
+`initialView` is the start, read once: a different value on a later render is ignored. `setView(view)` goes to a whole view at once, and what it leaves out goes back to its default; the same view again changes nothing, and `onViewChange` does not hear it. Without a span the schedule shows the extent of its subtasks, within `zoomLimits`. A group no `LaneGroup` declares falls out.
 
 `setDomain`, `toggleGroup`, `foldAll` and `unfoldAll` change the view from outside - a button of the application's own that shows the whole plan or folds every team. The selection is not part of the view (`selectedTask`).
 
@@ -5566,7 +5578,7 @@ A view that differs in content from the last one handed in applies at once, and
 
 ##### Keep and restore a view
 
-`onViewChange` reports the span and the folded groups as one view; keep it - here in the browser's storage, so it outlives a reload - and hand it back through `initialView`. Pan, zoom, fold, keep, reload, restore.
+`onViewChange` reports the span and the folded groups as one view; keep it - here in the browser's storage, so it outlives a reload - and go back to it with `setView`. Pan, zoom, fold, keep, reload, restore.
 
 ```tsx
 import { useState } from "react";
@@ -5612,11 +5624,10 @@ const WORK: Subtask[] = [
 ];
 
 export default function KeepAndRestore() {
-  /* The application holds the view the schedule reports; handing it another
-     one is all it takes to restore. */
-  const [view, setView] = useState<ScheduleView>(START);
+  /* The schedule holds its view; `view` is what it shows now, and `setView`
+     restores a kept one. */
   const [kept, setKept] = useState<ScheduleView | null>(readKept);
-  const { Schedule, Lane, LaneGroup, Subtasks, setDomain } = useSchedule({ initialView: view, onViewChange: setView });
+  const { Schedule, Lane, LaneGroup, Subtasks, view, setView, setDomain } = useSchedule({ initialView: START });
 
   return (
     <Stack gap={3}>
@@ -5677,13 +5688,13 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `initialView` | [`ScheduleView`](#type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 77 more |
+| `initialView` | [`ScheduleView`](#type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 78 more |
 
 ###### Events
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `onViewChange` | `(view: `[`ScheduleView`](#type-ScheduleView)`) => void` | — | Every change of the view, once, always the whole view - the one to keep, or to hand another schedule as its `initialView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
+| `onViewChange` | `(view: `[`ScheduleView`](#type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies.<br>Shown in: [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
 
 ##### `ScheduleView`
 
@@ -5702,7 +5713,7 @@ import { useSchedule } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/linked-schedules/
 
-Each schedule has its own [`useSchedule`](#/api/useSchedule). Hand both the view one of them reports, through `initialView`: a view that differs from the last one handed in applies at once, without a remount, and the same one again changes nothing, so the two never feed each other.
+Each schedule has its own [`useSchedule`](#/api/useSchedule). Send what one reports to the other's `setView`, in both directions: the other goes there at once, without a remount, and `setView` is not reported, so the two never answer each other.
 
 While a drag is in flight the two can stand a frame apart; they settle as soon as it ends.
 
@@ -5710,13 +5721,12 @@ While a drag is in flight the two can stand a frame apart; they settle as soon a
 
 ##### Keep two schedules in step
 
-Hand the view `onViewChange` reports to both schedules' `initialView`: pan or zoom either one and the other follows - no `key`, no remount.
+Send what `onViewChange` reports to the other schedule's `setView`: pan or zoom either one and the other follows - no `key`, no remount.
 
 ```tsx
-import { useState } from "react";
 import { Stack, Text } from "@umriss-ui/core";
 import { useSchedule } from "@umriss-ui/schedule";
-import type { ScheduleView, Subtask, Task } from "@umriss-ui/schedule";
+import type { ScheduleParts, Subtask, Task } from "@umriss-ui/schedule";
 
 const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
 const min = (n: number) => n * 60_000;
@@ -5757,12 +5767,12 @@ const ELECTRIC_LEGS = on(ELECTRIC);
 const time = (instant: number) => new Date(instant).toLocaleTimeString("en-GB", { hour: "2-digit", minute: "2-digit" });
 
 export default function InStep() {
-  /* One view for both: each schedule reports its own, and goes to the other's
-     because it differs from the last one handed in. */
-  const [view, setView] = useState<ScheduleView>({ domain: [at(5, 30), at(18)] });
-  const diesel = useSchedule({ initialView: view, onViewChange: setView });
-  const electric = useSchedule({ initialView: view, onViewChange: setView });
-  const span = view.domain ?? [at(5, 30), at(18)];
+  /* Both start on the same span; each reports what the reader does to it and
+     the other goes there by `setView`, which is not reported in turn. */
+  const start = { domain: [at(5, 30), at(18)] } as const;
+  const diesel: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => electric.setView(v) });
+  const electric: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => diesel.setView(v) });
+  const span = diesel.view.domain ?? start.domain;
   return (
     <Stack gap={2}>
       <diesel.Schedule ariaLabel="Diesel vehicles on Tuesday, 17 March" height={240}>
@@ -5790,10 +5800,9 @@ export default function InStep() {
 Two schedules with different lanes over one span: who was on call, above the incidents they were paged for.
 
 ```tsx
-import { useState } from "react";
 import { Stack } from "@umriss-ui/core";
 import { useSchedule } from "@umriss-ui/schedule";
-import type { ScheduleView, Subtask, Task } from "@umriss-ui/schedule";
+import type { ScheduleParts, Subtask, Task } from "@umriss-ui/schedule";
 
 /* Data from the operations world, written out here so the example runs on its own. */
 
@@ -5920,9 +5929,9 @@ const PAGED: readonly Subtask[] = INCIDENTS.map((incident) => ({
 const HIT = SERVICES.filter((service) => PAGED.some((incident) => incident.lane === service.id));
 
 export default function RotaBesideIncidents() {
-  const [view, setView] = useState<ScheduleView>({ domain: [day(16, 6), day(17, 14)] });
-  const rota = useSchedule({ initialView: view, onViewChange: setView });
-  const incidents = useSchedule({ initialView: view, onViewChange: setView });
+  const start = { domain: [day(16, 6), day(17, 14)] } as const;
+  const rota: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => incidents.setView(v) });
+  const incidents: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => rota.setView(v) });
   return (
     <Stack gap={2}>
       <rota.Schedule ariaLabel="Who was on call" height={140}>
@@ -6003,13 +6012,13 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 ###### Events
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`onViewChange`](#/view/ScheduleOptions-onViewChange) | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Every change of the view, once, always the whole view - the one to keep, or to hand another schedule as its `initialView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with. |
+| [`onViewChange`](#/view/ScheduleOptions-onViewChange) | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6136,6 +6145,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#/schedule/ty
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
+| [`ref`](#/schedule/ScheduleProps-ref) | `Ref<`[`ScheduleHandle`](#/schedule/type-ScheduleHandle)`>` | — | Receives the `ScheduleHandle` - not an element. |
 | [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
 | [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
@@ -6196,7 +6206,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6779,7 +6789,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6962,7 +6972,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7196,7 +7206,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7406,7 +7416,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7827,7 +7837,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -8116,7 +8126,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -8131,6 +8141,419 @@ From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView
 
 What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
+## Measuring
+
+What the schedule costs, measured in this browser rather than claimed.
+
+### Benchmark
+
+A plan of up to five thousand subtasks and as many dependencies, measured in this browser: the first render, and the time and frames of a scripted pointer walk, pan and wheel zoom.
+
+```ts
+import { useSchedule } from "@umriss-ui/schedule";
+```
+
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/benchmark/
+
+The figures in `packages/schedule/docs/capabilities.md` come from here. The page dispatches the pointer and wheel events itself, on the schedule's canvas, and adds no prop to the schedule.
+
+#### Examples
+
+##### Measure a plan
+
+Pick a plan size and run the scripted pointer walk, pan and wheel zoom: the times and frame counts say what drawing and moving it cost here.
+
+```tsx
+/* A plan whose size is set by a button, and the figures of what drawing and
+   moving it cost. Everything is measured from outside: React's profiler, the
+   clock and the frame callbacks; the pointer walk, the pan and the wheel zoom
+   are dispatched on the schedule's canvas by the page itself, so a script only
+   presses a button and waits for the status to read `done`. Not photographed:
+   it measures the moment it runs. */
+
+import { useEffect, useMemo, useRef, useState } from "react";
+import { Button, Text } from "@umriss-ui/core";
+import { useSchedule } from "@umriss-ui/schedule";
+import type { Dependency, ScheduleInteraction, Subtask, Task } from "@umriss-ui/schedule";
+
+const MINUTE = 60_000;
+const HOUR = 60 * MINUTE;
+const T0 = Date.UTC(2026, 2, 16, 6);
+const VIEW: readonly [number, number] = [T0, T0 + 8 * HOUR];
+const HEIGHT = 440;
+const LANE_HEIGHT = 44;
+/* Events per scripted run, one to a frame. */
+const EVENTS = 240;
+
+const SIZES = {
+  small: { lanes: 20, subtasks: 200 },
+  medium: { lanes: 50, subtasks: 1_000 },
+  large: { lanes: 100, subtasks: 5_000 },
+} as const;
+type Size = keyof typeof SIZES;
+
+interface Plan {
+  lanes: readonly string[];
+  tasks: readonly Task[];
+  subtasks: readonly Subtask[];
+  dependencies: readonly Dependency[];
+}
+
+/** Lane 0 holds one long bar, the probe the pointer walk runs along. The other
+    lanes share the remaining subtasks in 20-minute bars every half hour, each
+    lane one task, and every bar after the first on a lane hangs on the bar
+    before it - as many dependencies as there are such pairs. */
+function plan({ lanes, subtasks }: { lanes: number; subtasks: number }): Plan {
+  const laneIds = Array.from({ length: lanes }, (_, i) => `lane-${i}`);
+  const tasks = laneIds.map((_, i): Task => ({ id: `task-${i}`, name: `Task ${i}`, color: `hsl(${(i * 37) % 360} 60% 50%)` }));
+  const work: Subtask[] = [{ id: "probe", task: "task-0", lane: "lane-0", from: T0 + HOUR, to: T0 + 7 * HOUR, name: "Probe" }];
+  const dependencies: Dependency[] = [];
+  const others = lanes - 1;
+  for (let j = 0; j < subtasks; j++) {
+    const lane = 1 + (j % others);
+    const from = T0 + Math.floor(j / others) * 30 * MINUTE;
+    work.push({ id: `s-${j}`, task: `task-${lane}`, lane: `lane-${lane}`, from, to: from + 20 * MINUTE, name: `Work ${j}` });
+    if (j >= others) dependencies.push({ id: `d-${j}`, from: `s-${j - others}`, to: `s-${j}`, lag: 0 });
+  }
+  return { lanes: laneIds, tasks, subtasks: work, dependencies };
+}
+
+type Figures = Record<string, number | undefined>;
+const FIGURES = [
+  ["first-render-ms", "First render, click to frame"],
+  ["walk-bar-ms", "Pointer walk along one bar, ms per event"],
+  ["walk-bar-renders", "Pointer walk along one bar, renders"],
+  ["walk-bar-frame-ms", "Pointer walk along one bar, ms from event to end of its frame"],
+  ["walk-many-ms", "Pointer walk across many bars, ms per event"],
+  ["walk-many-renders", "Pointer walk across many bars, renders"],
+  ["walk-many-frame-ms", "Pointer walk across many bars, ms from event to end of its frame"],
+  ["pan-ms", "Pan, ms per event"],
+  ["pan-frame-ms", "Pan, ms from event to end of its frame"],
+  ["zoom-ms", "Wheel zoom, ms per event"],
+  ["zoom-frame-ms", "Wheel zoom, ms from event to end of its frame"],
+] as const;
+
+/** What the page keeps between renders without drawing it: when the size was
+    asked for, the the target last under the pointer. */
+interface Meter {
+  clickAt: number;
+  hover: ScheduleInteraction | null;
+}
+
+/* One page, one meter: a module value, since no render may read or write it. */
+const meter: Meter = { clickAt: 0, hover: null };
+
+const frame = () => new Promise<void>((resolve) => requestAnimationFrame(() => resolve()));
+const elapsed = (meter: Meter) => performance.now() - meter.clickAt;
+const remember = (e: ScheduleInteraction) => {
+  meter.hover = e;
+};
+const stamp = (meter: Meter) => {
+  meter.clickAt = performance.now();
+};
+
+const pointer = (type: string, target: Element, x: number, y: number) =>
+  target.dispatchEvent(
+    new PointerEvent(type, { bubbles: true, cancelable: true, pointerId: 1, pointerType: "mouse", button: 0, buttons: type === "pointerup" ? 0 : 1, clientX: x, clientY: y }),
+  );
+
+/* The y of lane 0's row: moving down the probe's column until the schedule
+   reports the probe under the pointer. */
+function probeY(meter: Meter, el: Element, rect: DOMRect): number {
+  for (let y = 0; y < HEIGHT; y += 3) {
+    pointer("pointermove", el, rect.left + rect.width / 2, rect.top + y);
+    const h = meter.hover;
+    if (h?.hit.kind === "subtask" && h.hit.subtask.id === "probe") return rect.top + y;
+  }
+  return rect.top + LANE_HEIGHT;
+}
+
+interface Sinks {
+  put: (values: Figures) => void;
+  status: (s: "running" | "done") => void;
+}
+
+type Step = (el: Element, rect: DOMRect, y0: number, i: number) => void;
+
+/* The end of the next frame: a task queued from a frame callback runs after
+   that frame has been drawn, and the schedule's own draw callback, registered
+   by the event before ours, has run by then. */
+const frameEnd = () =>
+  new Promise<void>((resolve) => {
+    const channel = new MessageChannel();
+    channel.port1.onmessage = () => {
+      channel.port1.close();
+      resolve();
+    };
+    requestAnimationFrame(() => channel.port2.postMessage(null));
+  });
+
+/* A scripted measurement: EVENTS events, one to a frame. It reports the time
+   the dispatch itself took per event, the time from the dispatch to the end of
+   the frame that drew it, and the batches of markup changes counted meanwhile.
+   The synthetic pointer id is unknown to the browser, so the plot's pointer
+   capture is switched off for the run. */
+async function measure(name: string, root: HTMLElement | null, meter: Meter, sinks: Sinks, step: Step, drag: boolean): Promise<void> {
+  const el = root?.querySelector("[data-schedule-plot] canvas");
+  const plot = el?.parentElement;
+  if (el === null || el === undefined || plot === null || plot === undefined) return;
+  sinks.status("running");
+  plot.setPointerCapture = () => undefined;
+  const rect = el.getBoundingClientRect();
+  const y0 = probeY(meter, el, rect);
+  const middle = rect.left + rect.width / 2;
+  if (drag) pointer("pointerdown", el, middle, y0);
+  await frame();
+  /* The production build has no profiler; a commit shows as a batch of changes
+     to the schedule's markup, which is what is counted. */
+  let renders = 0;
+  const observer = new MutationObserver(() => renders++);
+  observer.observe(root!, { subtree: true, childList: true, attributes: true, characterData: true });
+  let busy = 0;
+  let drawn = 0;
+  for (let i = 0; i < EVENTS; i++) {
+    await frame();
+    const t = performance.now();
+    step(el, rect, y0, i);
+    busy += performance.now() - t;
+    await frameEnd();
+    drawn += performance.now() - t;
+  }
+  if (drag) pointer("pointerup", el, middle, y0);
+  await frame();
+  observer.disconnect();
+  delete (plot as Partial<HTMLElement>).setPointerCapture;
+  sinks.put({
+    [`${name}-ms`]: busy / EVENTS,
+    [`${name}-frame-ms`]: drawn / EVENTS,
+    ...(name.startsWith("walk") ? { [`${name}-renders`]: renders } : {}),
+  });
+  sinks.status("done");
+}
+
+const rows = Math.max(1, Math.floor(HEIGHT / LANE_HEIGHT) - 1);
+const STEPS: Record<string, { step: Step; drag: boolean }> = {
+  "walk-bar": { step: (el, r, y0, i) => pointer("pointermove", el, r.left + r.width * (0.12 + (0.76 * i) / EVENTS), y0), drag: false },
+  "walk-many": { step: (el, r, y0, i) => pointer("pointermove", el, r.left + r.width * ((i * 0.618) % 1), y0 + (i % rows) * LANE_HEIGHT), drag: false },
+  /* The pan goes left for half the events and back again, so the view ends where it began. */
+  pan: { step: (el, r, y0, i) => pointer("pointermove", el, r.left + r.width / 2 + (i < EVENTS / 2 ? -3 * i : -3 * (EVENTS - i)), y0), drag: true },
+  /* Ctrl held, as a pinch arrives; in and out in turn. */
+  zoom: {
+    step: (el, r, y0, i) =>
+      el.dispatchEvent(
+        new WheelEvent("wheel", { bubbles: true, cancelable: true, ctrlKey: true, deltaY: i % 2 === 0 ? -120 : 120, clientX: r.left + r.width / 2, clientY: y0 }),
+      ),
+    drag: false,
+  },
+};
+const RUNS = [
+  ["walk-bar", "Walk along one bar"],
+  ["walk-many", "Walk across many"],
+  ["pan", "Pan"],
+  ["zoom", "Wheel zoom"],
+] as const;
+
+function Plot({ data, onInteraction }: { data: Plan; onInteraction: (e: ScheduleInteraction) => void }) {
+  const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: VIEW } });
+  return (
+    <Schedule ariaLabel="Benchmark plan" height={HEIGHT} laneHeight={LANE_HEIGHT} onInteraction={onInteraction}>
+        {data.lanes.map((id) => (
+          <Lane key={id} id={id} />
+        ))}
+        <Dependencies data={data.dependencies} />
+        <Subtasks data={data.subtasks} tasks={data.tasks} />
+    </Schedule>
+  );
+}
+
+export default function Benchmark() {
+  const [size, setSize] = useState<Size>("small");
+  /* Pressing a size again draws the plan anew, so the first render can be taken twice. */
+  const [round, setRound] = useState(0);
+  const [status, setStatus] = useState<"idle" | "running" | "done">("running");
+  const [figures, setFigures] = useState<Figures>({});
+  const data = useMemo(() => plan(SIZES[size]), [size]);
+  const host = useRef<HTMLDivElement>(null);
+
+  const sinks: Sinks = {
+    put: (values) => setFigures((f) => ({ ...f, ...values })),
+    status: setStatus,
+  };
+
+  /* The second frame after the commit has the canvases drawn. */
+  useEffect(() => {
+    let live = true;
+    void frame()
+      .then(frame)
+      .then(() => {
+        if (!live) return;
+        setFigures((f) => ({ ...f, "first-render-ms": elapsed(meter) }));
+        setStatus("done");
+      });
+    return () => {
+      live = false;
+    };
+  }, [size, round]);
+
+  const show = (next: Size) => {
+    stamp(meter);
+    setStatus("running");
+    setFigures({});
+    setSize(next);
+    setRound((r) => r + 1);
+  };
+
+  const busy = status === "running";
+  return (
+    <>
+      <div style={{ display: "flex", flexWrap: "wrap", gap: "0.5rem" }}>
+        {(Object.keys(SIZES) as Size[]).map((s) => (
+          <Button key={s} size="sm" data-role={`size-${s}`} disabled={busy} onClick={() => show(s)}>
+            {SIZES[s].subtasks.toLocaleString("en-US")} subtasks
+          </Button>
+        ))}
+        {RUNS.map(([name, label]) => (
+          <Button
+            key={name}
+            size="sm"
+            data-role={`run-${name}`}
+            disabled={busy}
+            onClick={() => void measure(name, host.current, meter, sinks, STEPS[name]!.step, STEPS[name]!.drag)}
+          >
+            {label}
+          </Button>
+        ))}
+      </div>
+      <dl style={{ display: "flex", flexWrap: "wrap", gap: "1.5rem", margin: 0 }}>
+        <div>
+          <Text as="dt">Status</Text>
+          <Text as="dd" mono style={{ margin: 0 }} data-role="status">{status}</Text>
+        </div>
+        <div>
+          <Text as="dt">Lanes</Text>
+          <Text as="dd" mono style={{ margin: 0 }} data-role="plan-lanes">{data.lanes.length}</Text>
+        </div>
+        <div>
+          <Text as="dt">Subtasks</Text>
+          <Text as="dd" mono style={{ margin: 0 }} data-role="plan-subtasks">{data.subtasks.length}</Text>
+        </div>
+        <div>
+          <Text as="dt">Dependencies</Text>
+          <Text as="dd" mono style={{ margin: 0 }} data-role="plan-dependencies">{data.dependencies.length}</Text>
+        </div>
+        {FIGURES.map(([role, name]) => {
+          const value = figures[role];
+          return (
+            <div key={role}>
+              <Text as="dt">{name}</Text>
+              <Text as="dd" mono style={{ margin: 0 }} data-role={role}>{value === undefined ? "-" : value.toFixed(role.endsWith("ms") ? 2 : 0)}</Text>
+            </div>
+          );
+        })}
+      </dl>
+      <div ref={host}>
+        <Plot
+          key={`${size}-${round}`}
+          data={data}
+          onInteraction={remember}
+        />
+      </div>
+    </>
+  );
+}
+```
+
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
+#### Props on this page
+
+From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`laneHeight`](#/schedule/ScheduleProps-laneHeight) | `number` | `44` | Height of one lane in pixels. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onInteraction`](#/schedule/ScheduleProps-onInteraction) | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
+
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`ariaLabel`](#/schedule/ScheduleProps-ariaLabel) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
+From `LaneProps` — the full table stands on [Lanes](#/lane/type-LaneProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/lane/LaneProps-id) *required* | `string` | — | The identity subtasks name in their `lane`. |
+
+From `SubtasksProps` — the full table stands on [Subtasks](#/subtasks/type-SubtasksProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`data`](#/subtasks/SubtasksProps-data) *required* | `readonly `[`Subtask`](#/subtasks/type-Subtask)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#/subtasks/SubtasksProps-tasks) *required* | `readonly `[`Task`](#/subtasks/type-Task)`[]` | — | The tasks the subtasks belong to - their identity and their colour. A subtask whose task is not among them is drawn in a muted colour. |
+
+From `Subtask` — the full table stands on [Subtasks](#/subtasks/type-Subtask).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/subtasks/Subtask-id) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#/subtasks/Subtask-task) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#/subtasks/Subtask-lane) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#/subtasks/Subtask-from) *required* | `number` | — | Start of the main time. |
+| [`to`](#/subtasks/Subtask-to) *required* | `number` | — | End of the main time. |
+| [`name`](#/subtasks/Subtask-name) | `string` | — | What the subtask is called, where the schedule names it. |
+
+From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/subtasks/Task-id) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#/subtasks/Task-color) *required* | `string` | — | Any CSS colour - a literal, a token, `light-dark(…)`. The colour means what the caller's domain needs it to mean. |
+| [`name`](#/subtasks/Task-name) | `string` | — | What the task is called, where the schedule names it. |
+
+From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+
+From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/dependencies/Dependency-id) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#/dependencies/Dependency-from) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#/dependencies/Dependency-to) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#/dependencies/Dependency-lag) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
+
+From `ScheduleInteraction` — the full table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`hit`](#/interactions/ScheduleInteraction-hit) *required* | [`ScheduleHit`](#/interactions/type-ScheduleHit) | — | What the pointer is on. |
+
+From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+
+From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+
 ## API index
 
 Every name the package exports, in one place.
@@ -8147,14 +8570,14 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/api/
 
 Declares a schedule: hands back `Schedule` and the parts declared inside it
 - `Lane`, `LaneGroup`, `Subtasks`, `Dependencies`, `BlockedTimes`, `Milestones` -, its
-`view` and the setters `setDomain`, `toggleGroup`, `foldAll` and
+`view` and the setters `setView`, `setDomain`, `toggleGroup`, `foldAll` and
 `unfoldAll`. A ref on `Schedule` still gives the `ScheduleHandle`.
 
 ```ts
 function useSchedule(options?: ScheduleOptions): ScheduleParts;
 ```
 
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go) and [Ripple](#/ripple).
+Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
 
 #### Functions
 
@@ -8334,7 +8757,7 @@ Its table stands on [Dependencies](#/dependencies/type-DependenciesProps).
 
 Its table stands on [Dependencies](#/dependencies/type-Dependency).
 
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lane groups](#/lane-groups), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Placing from outside](#/placing) and [Ripple](#/ripple).
+Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lane groups](#/lane-groups), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Placing from outside](#/placing), [Ripple](#/ripple) and [Benchmark](#/benchmark).
 
 ##### `DependencyAttachment`
 
@@ -8475,7 +8898,7 @@ Its table stands on [Findings as data](#/findings/type-Overlap).
 ##### `PlaceIntent`
 
 Put work on the plan that was not on it: the answer to a drag from outside
-the schedule (schedule-refinement 07). It carries no subtask id - there is
+the schedule. It carries no subtask id - there is
 no subtask yet; the caller creates one, with its own identity, from
 `subtaskFromPlace`.
 
@@ -8492,9 +8915,9 @@ no subtask yet; the caller creates one, with its own identity, from
 
 ##### `PlacingItem`
 
-What the application says it is dragging in, while it drags it
-(schedule-refinement 07): the browser hands over the dragged data only on
-the drop, so the ghost before the drop can only come from the caller.
+What the application says it is dragging in, while it drags it: the
+browser hands over the dragged data only on the drop, so the ghost before
+the drop can only come from the caller.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -8510,15 +8933,13 @@ Used on [Placing from outside](#/placing) and [Where a subtask may go](#/where-i
 
 What the drawing needs to know, with the contradiction already settled.
 
-The four names are the ones this module was born with, and they are kept so
-that a caller's code does not change because a picture did. Two of them are
-now named after a drawing they no longer use, and the channel each one
-really owns stands beside it.
+Two of the field names (`dashed`, `hatched`) are older than the drawing;
+the channel each one owns stands beside it.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `dashed` *required* | `boolean` | — | `provisional`: the FILL - none at all, so the surface shows through, with a dashed outline in the task colour. Planned, not released. |
-| `hatched` *required* | `boolean` | — | `fixed`: the ENDS - a cap at each end of the main time. Not a hatch any more; a hatch now says "not available" of a refused lane, and the name is kept only so that this type did not change with the picture. |
+| `hatched` *required* | `boolean` | — | `fixed`: the ENDS - a cap at each end of the main time. Not a hatch: a hatch says "not available" of a refused lane. The field keeps the name `hatched`. |
 | `muted` *required* | `boolean` | — | `muted`: the SATURATION - the task colour mixed half into the surface, opaque and at full height. Another team's, another crew's. |
 | `open` *required* | `boolean` | — | `open`: the FADE, where the bar passes the edge of the view. It goes on past what is drawn. |
 
@@ -8552,7 +8973,7 @@ type ScheduleHit =
 
 Its table stands on [Interactions](#/interactions/type-ScheduleInteraction).
 
-Used on [Scenarios](#/), [Interactions](#/interactions) and [Tooltip](#/tooltip).
+Used on [Scenarios](#/), [Interactions](#/interactions), [Tooltip](#/tooltip) and [Benchmark](#/benchmark).
 
 ##### `ScheduleOptions`
 
@@ -8565,19 +8986,22 @@ it, its view and the setters that change it.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `Schedule` *required* | `ForwardRefExoticComponent<`[`ScheduleProps`](#/schedule/type-ScheduleProps)` & RefAttributes<`[`ScheduleHandle`](#type-ScheduleHandle)`>>` | — | The schedule. One per `useSchedule`: a second schedule is a second call.<br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 77 more |
-| `Lane` *required* | `typeof Lane` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 77 more |
+| `Schedule` *required* | `(props: `[`ScheduleProps`](#/schedule/type-ScheduleProps)`) => ReactNode` | — | The schedule. One per `useSchedule`: a second schedule is a second call.<br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
+| `Lane` *required* | `typeof Lane` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
 | `LaneGroup` *required* | `typeof LaneGroup` | — | <br>Shown in: [Group lanes under a head (Lane groups)](#/lane-groups/a-group), [Nest groups to any depth (Lane groups)](#/lane-groups/nesting), [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) and 5 more |
-| `Subtasks` *required* | `typeof Subtasks` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 77 more |
-| `Dependencies` *required* | `typeof Dependencies` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 27 more |
+| `Subtasks` *required* | `typeof Subtasks` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
+| `Dependencies` *required* | `typeof Dependencies` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 28 more |
 | `BlockedTimes` *required* | `typeof BlockedTimes` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Check a sprint against the leave calendar (Blocked time)](#/blocked-time/team-leave) and 5 more |
 | `Milestones` *required* | `typeof Milestones` | — | <br>Shown in: [Mark a handover and a release (Milestones)](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `view` *required* | [`ScheduleView`](#/view/type-ScheduleView) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+| `view` *required* | [`ScheduleView`](#/view/type-ScheduleView) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step) and 1 more |
+| `setView` *required* | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Goes to a whole view; what it leaves out is shown whole again. Not reported through `onViewChange`: two schedules kept in step by `onViewChange: (v) => other.setView(v)` in both directions do not answer each other. A view with the content already shown changes nothing.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
 | `setDomain` *required* | `(span: readonly [number, number] \| null) => void` | — | Puts a span of two wall-clock instants in view; `null` shows the subtasks' extent.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore) |
 | `toggleGroup` *required* | `(id: string) => void` | — | Folds or unfolds one **Lane group**. |
 | `foldAll` *required* | `() => void` | — | Folds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
 | `unfoldAll` *required* | `() => void` | — | Unfolds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
 
+Used on [Linked schedules](#/linked-schedules).
+
 ##### `ScheduleProps`
 
 Its table stands on [First schedule](#/schedule/type-ScheduleProps).
@@ -8592,7 +9016,7 @@ Used on [Milestones](#/milestones) and [Tooltip](#/tooltip).
 
 Its table stands on [View](#/view/type-ScheduleView).
 
-Used on [View](#/view) and [Linked schedules](#/linked-schedules).
+Used on [View](#/view).
 
 ##### `SnapRaster`
 
@@ -8620,7 +9044,7 @@ Stretch the main time at one or both of its edges.
 
 Its table stands on [Subtasks](#/subtasks/type-Subtask).
 
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go) and [Ripple](#/ripple).
+Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
 
 ##### `SubtaskAppearance`
 
@@ -8638,7 +9062,7 @@ Its table stands on [Subtasks](#/subtasks/type-SubtasksProps).
 
 Its table stands on [Subtasks](#/subtasks/type-Task).
 
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go) and [Ripple](#/ripple).
+Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
 
 ##### `ViolatedDependency`