@umriss-ui/schedule 0.3.16 → 0.4.0

package/docs/llms-full.md

@@ -1,8 +1,8 @@
-# @umriss-ui/schedule 0.3.16
+# @umriss-ui/schedule 0.4.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
-Install with `pnpm add @umriss-ui/schedule`. This text is generated from the package's demo (https://romanhaendler.github.io/umriss-ui/schedule/): every page with its import line, its examples - the source exactly as it runs, with the package name where the demo imports its own source - its props tables generated from the code, and what it deliberately does not do. The pages index stands in https://romanhaendler.github.io/umriss-ui/schedule/llms.txt.
+Install with `npm install @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts`. This text is generated from the package's demo (https://romanhaendler.github.io/umriss-ui/schedule/): every page with its import line, its examples - the source exactly as it runs, with the package name where the demo imports its own source - its props tables generated from the code, and what it deliberately does not do. The pages index stands in https://romanhaendler.github.io/umriss-ui/schedule/llms.txt.
 
 ## Scenarios
 
@@ -909,11 +909,15 @@ Install the schedule with its two peers and hand it plain data: lanes, tasks, su
 import { Schedule, Lane, Subtasks, Dependencies } from "@umriss-ui/schedule";
 ```
 
+```sh
+npm install @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts
+```
+
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/installation/
 
-Install it with its peers: `pnpm add @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts`, with React 18 or 19. 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 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 plan is plain data (ADR-0023). 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.
+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.
 
 The schedule reports, the application decides. It draws the data it is given and changes none of it: a drag ends in an intent reported to `onIntent`, and only the application's own state update moves a bar. Without `intents` the schedule is read-only - see [Move and lane](#/move-and-lane).
 
@@ -951,9 +955,74 @@ export default function SmallestSchedule() {
 }
 ```
 
-## Plan
+#### Keyboard
 
-What the schedule draws: work on lanes, and everything a bar says besides its colour.
+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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`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. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+
+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. |
 
 ### First schedule
 
@@ -969,7 +1038,7 @@ Lanes stand in the order they are declared; a subtask on a lane that is not decl
 
 What cannot work is drawn, never repaired: two subtasks on one lane at once, a dependency whose lag does not fit, work in blocked time. [Findings as data](#/findings) returns the same list for the application to act on.
 
-The plot is one tab stop. The keys walk the subtasks as the pointer would hover them, the tooltip names the active one, and a live region reads it once the keys rest (ADR-0030, ADR-0033).
+The plot is one tab stop. The keys walk the subtasks as the pointer would hover them, the tooltip names the active one, and a live region reads it once the keys rest ([ADR-0030](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0030-a-chart-is-one-tab-stop-that-walks-its-hits.md), [ADR-0033](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0033-the-schedules-keys-walk-past-the-view.md)).
 
 #### Examples
 
@@ -1181,48 +1250,271 @@ export default function MachinePlan() {
 | `Alt+← / Alt+→` | Proposes a move by one step of the raster, where the application handles `move`. |
 | `Alt+Shift+← / →` | Proposes a new end, where the application handles `stretch`. |
 
+#### Accessibility
+
+The schedule is a figure named by `ariaLabel`, and its plot one tab stop with the role `application`, read as "schedule" (`aria-roledescription`), named alike and described by a summary: the lanes, the subtasks in view, the visible span, the findings by kind, then the keys. The canvas is hidden from a reader; the lane headers are text, and a group's fold button is named "Fold group" or "Unfold group" with the group's label. `ariaLabel` is required - name what the plan shows, "Plan of week 38".
+
+When a key comes to rest, a polite live region beside the plot reads the active subtask: its lane, task and name, the day and the times, and every finding on it by name - an overlap, a dependency short by how much, blocked time. On a dependency it reads the task, the lag and where the line runs. A pointer announces nothing; [Findings as data](#/findings) gives the application the same findings to list. The words are core's wording, so under `@umriss-ui/core/wording/de` the plot is read as "Belegungsplan".
+
+Under forced colours the plot paints itself in the system colours: the work in the text colour, told apart by lane and label; the active subtask in the selection colour; findings marked by a dash; grips and the ghost's label outlined. With reduced motion a group's chevron turns without its movement.
+
 #### API
 
 ##### `ScheduleProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ariaLabel` (required) | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
-| `initialDomain` (required) | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
-| `height` | `number` | — | Height in CSS pixels, both bands included. The width is the host's. |
-| `laneHeight` | `number` | — | Height of one lane in pixels. |
-| `headerWidth` | `number` | — | Width of the lane headers in pixels - at most 40 % of the schedule, so that on a phone the plot keeps the larger part. |
-| `calendar` | `CalendarInput` | — | A working calendar: the intervals in which time counts. Nights and weekends outside them are cut out of the axis. Default: the wall clock. |
-| `zoomLimits` | `ZoomLimits` | — | The narrowest and widest time span zoom may reach, in milliseconds. Default: one hour to 28 days. |
-| `snap` | `"ticks" \| number \| SnapRaster \| false` | — | The raster a drag lands on: `"ticks"` - the fine band's current step -, a step in milliseconds from local midnight, a step with an offset (shifts at 06:00, 14:00 and 22:00 are eight hours offset by six), or `false` for none. It shapes the ghost and the intent, never the data. |
-| `intents` | `readonly IntentKind[]` | — | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule (ADR-0023). |
-| `canMoveTo` | `(subtask: Subtask, lane: string) => boolean` | — | Whether a subtask may go to a lane. Without it every lane is open; it narrows `"lane"`, it does not enable it. Asked once per lane when a drag takes hold, and asked again at the drop. The lanes it turns down are marked from the first frame of the drag - a planner sees the refusal before meeting it - and over one of them the ghost stays on the last lane that was allowed, the cursor says no and a line ties the ghost to the pointer. A refused lane costs the lane and nothing else: a drop after it still reports the move in time. It is asked for work dragged in from outside as well, with the key and task the application declared in `placing`. |
-| `onIntent` | `(intent: Intent) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
-| `onInteraction` | `(interaction: 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. |
-| `selectedTask` | `string \| null` | — | The selected task, controlled. Leave it out and the schedule keeps the selection itself. |
-| `onSelectedTaskChange` | `(task: string \| null, subtask: string \| null) => void` | — | Called when a click selects a task or clears the selection, with the subtask that was clicked - null where the click was on a dependency or on nothing. It is called again when another subtask of the same task is clicked. |
-| `collapsedGroups` | `readonly string[]` | — | The **Lane group**s that are folded, controlled. Leave it out and the schedule keeps them itself, starting from `defaultCollapsedGroups`. Folding changes the view and not the plan, which is why it is no intent: a caller that applies every intent it receives must never find a fold among them (ADR-0025). A folded outer group hides the inner ones without their entries leaving the list, so unfolding it gives back the view that was there. |
-| `defaultCollapsedGroups` | `readonly string[]` | — | Which groups are folded when the schedule mounts, where the schedule keeps the state itself. Ignored while `collapsedGroups` is given. |
-| `onCollapsedGroupsChange` | `(groups: readonly string[]) => void` | — | Called with the whole list when the planner folds or unfolds a group. |
-| `onDomainChange` | `(domain: readonly [number, number]) => void` | — | The visible time span after the planner panned or zoomed, as two wall-clock instants - for keeping a second schedule or a chart in step. A span handed in through `initialDomain` is not reported back. |
-| `placing` | `PlacingItem \| null` | — | What the application is dragging in from outside while it drags it - its key, task, the length of its main time, its lead-in and lead-out. The browser hands the dragged data over only on the drop, so the ghost before it can only come from here: set it on your own `dragstart`, clear it on `dragend`. Without `"place"` in `intents` no drop is accepted. |
-| `route` | `DependencyRoute` | — | How the dependencies are drawn: a `"curve"` that leaves and arrives forwards, a `"straight"` line, or `"orthogonal"` segments. A dependency may say otherwise for itself. |
-| `attach` | `DependencyAttachment` | — | Where a dependency's ends sit on their bars: the `"centre"` of both, or the `"nearest"` edge - which is the shortest line between two stops. Within one lane both mean the middle. A dependency may say otherwise for itself. It changes the picture and never a finding: whether a dependency is violated follows from its `leaves` and `arrives` alone. |
-| `ends` | `DependencyEnds` | — | Whether a dependency's two ends carry a dot (`"dot"`, the default) or the line stands alone (`"none"`). The dot says where the line is anchored - a help while a plan is being read, and noise in a plan full of short moves. A dependency may say otherwise for itself. |
-| `label` | `(subtask: 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. |
-| `tooltip` | `false \| ((target: 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. |
-| `now` | `boolean \| number` | — | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there. Off by default. |
+| `initialDomain` *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back.<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 74 more |
+| `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 74 more |
+| `laneHeight` | `number` | `44` | Height of one lane in pixels.<br>Shown in: [Scroll more lanes than fit (Lanes)](#/lane/many-lanes) |
+| `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) |
+| `snap` | `"ticks" \| number \| `[`SnapRaster`](#type-SnapRaster)` \| false` | `"ticks"` | The raster a drag lands on: `"ticks"` - the fine band's current step -, a step in milliseconds from local midnight, a step with an offset (shifts at 06:00, 14:00 and 22:00 are eight hours offset by six), or `false` for none. It shapes the ghost and the intent, never the data.<br>Shown in: [Snap to a duration (Snapping)](#/snapping/snap-to-a-duration), [Snap to handover times (Snapping)](#/snapping/snap-to-handovers), [Place without snapping (Snapping)](#/snapping/no-snapping) |
+| `intents` | `readonly `[`IntentKind`](#type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)).<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 |
+| `canMoveTo` | `(subtask: `[`Subtask`](#/subtasks/type-Subtask)`, lane: string) => boolean` | every lane is open | Whether a subtask may go to a lane. It narrows `"lane"`, it does not enable it. Asked once per lane when a drag takes hold, and asked again at the drop. The lanes it turns down are marked from the first frame of the drag - a planner sees the refusal before meeting it - and over one of them the ghost stays on the last lane that was allowed, the cursor says no and a line ties the ghost to the pointer. A refused lane costs the lane and nothing else: a drop after it still reports the move in time. It is asked for work dragged in from outside as well, with the key and task the application declared in `placing`.<br>Shown in: [Keep work on the lanes that fit (Where a subtask may go)](#/where-it-may-go/lanes-that-fit), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in), [Keep work out of someone's leave (Where a subtask may go)](#/where-it-may-go/around-leave) and 1 more |
+| `selectedTask` | `string \| null` | — | The selected task, controlled. Leave it out and the schedule keeps the selection itself.<br>Shown in: [Control the selection (Selection)](#/selection/control-the-selection) |
+| `onSelectedTaskChange` | `(task: string \| null, subtask: string \| null) => void` | — | Called when a click selects a task or clears the selection, with the subtask that was clicked - null where the click was on a dependency or on nothing. It is called again when another subtask of the same task is clicked.<br>Shown in: [Control the selection (Selection)](#/selection/control-the-selection) |
+| `defaultCollapsedGroups` | `readonly string[]` | — | Which groups are folded when the schedule mounts, where the schedule keeps the state itself. Ignored while `collapsedGroups` is given.<br>Shown in: [Start with groups folded (Lane groups)](#/lane-groups/start-with-groups-folded) |
+| `collapsedGroups` | `readonly string[]` | — | The **Lane group**s that are folded, controlled. Leave it out and the schedule keeps them itself, starting from `defaultCollapsedGroups`. Folding changes the view and not the plan, which is why it is no intent: a caller that applies every intent it receives must never find a fold among them ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)). A folded outer group hides the inner ones without their entries leaving the list, so unfolding it gives back the view that was there.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/controlled), [Read a folded group (Lane groups)](#/lane-groups/the-miniature) |
+| `onCollapsedGroupsChange` | `(groups: readonly string[]) => void` | — | Called with the whole list when the planner folds or unfolds a group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/controlled), [Read a folded group (Lane groups)](#/lane-groups/the-miniature) |
+| `placing` | [`PlacingItem`](#type-PlacingItem)` \| null` | — | What the application is dragging in from outside while it drags it - its key, task, the length of its main time, its lead-in and lead-out. The browser hands the dragged data over only on the drop, so the ghost before it can only come from here: set it on your own `dragstart`, clear it on `dragend`. Without `"place"` in `intents` no drop is accepted.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `route` | [`DependencyRoute`](#type-DependencyRoute)<br>`"curve" \| "straight" \| "orthogonal"` | `"curve"` | How the dependencies are drawn: a `"curve"` that leaves and arrives forwards, a `"straight"` line, or `"orthogonal"` segments. A dependency may say otherwise for itself.<br>Shown in: [Straight (Routes)](#/routes/straight), [Orthogonal (Routes)](#/routes/orthogonal), [Per dependency (Routes)](#/routes/per-dependency) |
+| `attach` | [`DependencyAttachment`](#type-DependencyAttachment)<br>`"centre" \| "nearest"` | `"centre"` | Where a dependency's ends sit on their bars: the `"centre"` of both, or the `"nearest"` edge - which is the shortest line between two stops. Within one lane both mean the middle. A dependency may say otherwise for itself. It changes the picture and never a finding: whether a dependency is violated follows from its `leaves` and `arrives` alone.<br>Shown in: [Choose where a line touches its bars (Dependencies)](#/dependencies/attach), [Mark the ends with a dot (Dependencies)](#/dependencies/ends), [Draw one handover its own way (Dependencies)](#/dependencies/one-handover-drawn-its-own-way) and 3 more |
+| `ends` | [`DependencyEnds`](#type-DependencyEnds)<br>`"dot" \| "none"` | `"dot"` | Whether a dependency's two ends carry a dot (`"dot"`) or the line stands alone (`"none"`). The dot says where the line is anchored - a help while a plan is being read, and noise in a plan full of short moves. A dependency may say otherwise for itself.<br>Shown in: [Mark the ends with a dot (Dependencies)](#/dependencies/ends), [Draw one handover its own way (Dependencies)](#/dependencies/one-handover-drawn-its-own-way) |
+| `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: [Write your own tooltip content (Tooltip)](#/tooltip/own-tooltip), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead), [Say what a bar covers and a line joins (Tooltip)](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `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 74 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 |
+| `onDomainChange` | `(domain: readonly [number, number]) => void` | — | The visible time span after the planner panned or zoomed, as two wall-clock instants - for keeping a second schedule or a chart in step. A span handed in through `initialDomain` is not reported back.<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), [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+
+###### 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 74 more |
+
+###### Styling
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
 | `className` | `string` | — | Goes to the root element. |
 | `style` | `CSSProperties` | — | Goes to the root element. |
-| `children` | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+##### Types on this page
+
+###### `CalendarInput`
+
+From `@umriss-ui/charts`.
+
+Every function of this module takes either: the raw list as it stands on the
+axis, or the calendar built from it.
+
+```ts
+type CalendarInput = WorkingCalendar | readonly WorkingInterval[];
+```
+
+###### `ZoomLimits`
+
+The narrowest and the widest span zoom may reach.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `min` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |
+| `max` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |
+
+###### `SnapRaster`
+
+A raster: a step, and where it starts after local midnight.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `step` *required* | `number` | — | The distance between two lines of the raster, in milliseconds.<br>Shown in: [Snap to handover times (Snapping)](#/snapping/snap-to-handovers) |
+| `offset` *required* | `number` | — | Where the raster starts after local midnight, in milliseconds: six hours for handovers at 06:00, 14:00 and 22:00.<br>Shown in: [Snap to handover times (Snapping)](#/snapping/snap-to-handovers) |
+
+###### `IntentKind`
+
+The names of the intents - the editing API of the schedule.
+
+```ts
+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.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `item` *required* | `string` | — | The caller's key for the dragged item; it comes back in the intent.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `task` *required* | `string` | — | The task the work belongs to.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `duration` *required* | `number` | — | How long its main time is.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `leadIn` | `number` | — | The lead-in it brings. |
+| `leadOut` | `number` | — | The lead-out it brings. |
+
+###### `DependencyRoute`
+
+How a dependency is drawn between its two ends: a curve that leaves and
+arrives forwards, a straight line, or axis-parallel segments.
+
+```ts
+type DependencyRoute = "curve" | "straight" | "orthogonal";
+```
+
+###### `DependencyAttachment`
+
+Where on its bars a dependency's line attaches: the middle of both, or the
+edge that faces the other stop - which is the shortest line between them.
+
+Deliberately not called an anchor: a dependency already HAS two anchors
+(`leaves`, `arrives`), and those decide what it connects and therefore
+whether it is violated. This decides where the line touches, and nothing else.
+The tree has an **Anchor** of its own as well (CONTEXT.md).
+
+```ts
+type DependencyAttachment = "centre" | "nearest";
+```
+
+###### `DependencyEnds`
+
+Whether a dependency's two ends carry a dot. The dot says where the line is
+anchored, which is worth saying while a plan is being read and is noise in a
+plan full of short moves - so it is the caller's choice.
+
+```ts
+type DependencyEnds = "dot" | "none";
+```
+
+###### `Intent`
+
+What the schedule reports when an interaction asks for a change. Every
+intent carries the values it asks for, not a difference: two intents of one
+drop - a move and a lane - give the same data in either order.
+
+```ts
+type Intent = MoveIntent | StretchIntent | LeadInIntent | LeadOutIntent | LaneIntent | PlaceIntent;
+```
+
+###### `WorkingCalendar`
+
+From `@umriss-ui/charts`.
+
+A working calendar: sorted, merged intervals with the working time
+accumulated before each one begins. An empty calendar is no calendar: it maps
+unchanged.
+
+Build once, then pass around: the mapping runs once per point, and were it to
+sort and accumulate every time, the calendar would be the most expensive
+thing about the frame.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `intervals` *required* | `readonly `[`WorkingInterval`](#type-WorkingInterval)`[]` | — |  |
+| `offsets` *required* | `readonly number[]` | — | Working time accumulated before the respective interval begins. |
+| `total` *required* | `number` | — | The whole working time - the axis' extent is [0, total]. |
+
+###### `WorkingInterval`
+
+From `@umriss-ui/charts`.
+
+An interval in which time counts; thought of as half-open, but mappable from
+both sides at its edges: both `from` and `to` have a working time.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `from` *required* | `number` | — |  |
+| `to` *required* | `number` | — |  |
+
+###### `MoveIntent`
+
+Move the subtask in time: the main time keeps its length.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"move"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 8 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 5 more |
+| `from` *required* | `number` | — | The new start of the main time.<br>Shown in: [Push the later stops of a tour (Ripple)](#/ripple/push-the-later-stops), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+| `to` *required* | `number` | — | The new end of the main time.<br>Shown in: [Push the later stops of a tour (Ripple)](#/ripple/push-the-later-stops), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+
+###### `StretchIntent`
+
+Stretch the main time at one or both of its edges.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"stretch"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `from` *required* | `number` | — | The new start of the main time. |
+| `to` *required* | `number` | — | The new end of the main time. |
+
+###### `LeadInIntent`
+
+Change the lead-in on its own.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"leadIn"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `leadIn` *required* | `number` | — | The new duration of the lead-in.<br>Shown in: [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+
+###### `LeadOutIntent`
+
+Change the lead-out on its own.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"leadOut"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `leadOut` *required* | `number` | — | The new duration of the lead-out. |
+
+###### `LaneIntent`
+
+Put the subtask on another lane.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"lane"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `lane` *required* | `string` | — | The id of the new 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
+no subtask yet; the caller creates one, with its own identity, from
+`subtaskFromPlace`.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"place"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `item` *required* | `string` | — | The caller's key for the dragged item, as it declared it while dragging.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+| `task` *required* | `string` | — | The task the work belongs to. |
+| `lane` *required* | `string` | — | The lane it was dropped on.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `from` *required* | `number` | — | Where its main time would start. |
+| `to` *required* | `number` | — | Where its main time would end. |
+| `leadIn` | `number` | — | The lead-in it was declared with. |
+| `leadOut` | `number` | — | The lead-out it was declared with. |
 
 #### Known limits
 
-- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings (ADR-0032).
+- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/)).
 - No milestones yet: a point in time on a lane has no mark of its own.
 - A dependency joins two subtasks of one task; dependencies across tasks are not yet possible.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
+
+## Plan
+
+What the schedule draws: work on lanes, and everything a bar says besides its colour.
 
 ### Lanes
 
@@ -1342,14 +1634,18 @@ export default function ManyLanes() {
 
 - Lanes that belong together, folded into one row → Lane groups
 
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `LaneProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The identity subtasks name in their `lane`. |
-| `label` | `ReactNode` | — | What the lane header says - the person, vehicle or room. Real text, read by a screen reader; without one the header shows the id. |
+| `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 74 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 74 more |
 
 ### Lane groups
 
@@ -1361,7 +1657,7 @@ import { LaneGroup, Lane } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/lane-groups/
 
-A group is structure, never a lane: nothing sits on it, no finding is reported for it and no intent names it (ADR-0025). The lanes keep the order they were declared in, whatever group they are in.
+A group is structure, never a lane: nothing sits on it, no finding is reported for it and no intent names it ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)). The lanes keep the order they were declared in, whatever group they are in.
 
 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.
 
@@ -1605,6 +1901,50 @@ export default function TheMiniature() {
 }
 ```
 
+##### Start with groups folded
+
+`defaultCollapsedGroups` folds groups when the schedule mounts and leaves the rest to the planner: Discovery starts folded, and its chevron opens it.
+
+```tsx
+import { Lane, LaneGroup, Schedule, Subtasks } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+/* Uncontrolled: the schedule keeps the fold from here on. To store it or
+   steer it, pass `collapsedGroups` instead. */
+
+const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
+
+const TASKS: Task[] = [{ id: "release", name: "Release 4.12", color: "light-dark(#0d9488, #3cc7b8)" }];
+
+const WORK: Subtask[] = [
+  { id: "s1", task: "release", lane: "priya", from: at(7), to: at(9) },
+  { id: "s2", task: "release", lane: "jonas", from: at(9, 30), to: at(11) },
+  { id: "s3", task: "release", lane: "tomasz", from: at(11, 30), to: at(13) },
+  { id: "s4", task: "release", lane: "leila", from: at(13), to: at(14, 30) },
+];
+
+export default function StartWithGroupsFolded() {
+  return (
+    <Schedule
+      ariaLabel="Two teams rolling out a release, Discovery folded at the start"
+      initialDomain={[at(6), at(15)]}
+      height={280}
+      defaultCollapsedGroups={["discovery"]}
+    >
+      <LaneGroup id="payments" label="Payments">
+        <Lane id="priya" label="Priya Raman" />
+        <Lane id="jonas" label="Jonas Keller" />
+      </LaneGroup>
+      <LaneGroup id="discovery" label="Discovery">
+        <Lane id="tomasz" label="Tomasz Nowak" />
+        <Lane id="leila" label="Leila Haddad" />
+      </LaneGroup>
+      <Subtasks data={WORK} tasks={TASKS} />
+    </Schedule>
+  );
+}
+```
+
 #### Keyboard
 
 | Key | Action |
@@ -1612,21 +1952,23 @@ export default function TheMiniature() {
 | `Tab` | Reaches each group's fold button - the only buttons the schedule puts in the tab order. |
 | `Enter / Space` | Folds or unfolds the group. |
 
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `LaneGroupProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The group's identity - what `collapsedGroups` names. It is never a lane: no subtask sits on it, no finding is reported for it, and no intent names it (ADR-0025). |
-| `label` | `ReactNode` | — | What the group's header says - the team, the depot, the region. Real text, read by a screen reader; without one the header shows the id. |
-| `children` | `ReactNode` | — | `Lane`s and further `LaneGroup`s, to any depth. |
+| `id` *required* | `string` | — | The group's identity - what `collapsedGroups` names. It is never a lane: no subtask sits on it, no finding is reported for it, and no intent names it ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).<br>Shown in: [Group lanes under a head](#/lane-groups/a-group), [Nest groups to any depth](#/lane-groups/nesting), [Fold groups from outside](#/lane-groups/controlled) and 4 more |
+| `label` | `ReactNode` | `id` | What the group's header says - the team, the depot, the region. Real text, read by a screen reader.<br>Shown in: [Group lanes under a head](#/lane-groups/a-group), [Nest groups to any depth](#/lane-groups/nesting), [Fold groups from outside](#/lane-groups/controlled) and 4 more |
+| `children` | `ReactNode` | — | `Lane`s and further `LaneGroup`s, to any depth.<br>Shown in: [Group lanes under a head](#/lane-groups/a-group), [Nest groups to any depth](#/lane-groups/nesting), [Fold groups from outside](#/lane-groups/controlled) and 4 more |
 
 #### Known limits
 
-- A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact (ADR-0025).
+- A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### Subtasks
 
@@ -1815,37 +2157,51 @@ export default function ASprint() {
 }
 ```
 
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `SubtasksProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` (required) | `readonly Subtask[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
-| `tasks` (required) | `readonly 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. |
+| `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 74 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 74 more |
 
 ##### `Subtask`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The caller's identity of the subtask. |
-| `task` (required) | `string` | — | The id of the task it belongs to. |
-| `lane` (required) | `string` | — | The id of the lane it sits on. |
-| `from` (required) | `number` | — | Start of the main time. |
-| `to` (required) | `number` | — | End of the main time. |
-| `leadIn` | `number` | — | Duration of the lead-in before the main time; none is zero. |
-| `leadOut` | `number` | — | Duration of the lead-out after the main time; none is zero. |
-| `name` | `string` | — | What the subtask is called, where the schedule names it. |
-| `appearance` | `readonly 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. |
-| `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. |
+| `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 71 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 67 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 67 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 67 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 67 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 24 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 21 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 25 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) |
 
 ##### `Task`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The caller's identity of the 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` | `string` | — | What the task is called, where the schedule names it. |
+| `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 66 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 66 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 66 more |
+
+##### Types on this page
+
+###### `SubtaskAppearance`
+
+The appearances a caller may give a subtask.
+
+```ts
+type SubtaskAppearance = "provisional" | "fixed" | "muted" | "open";
+```
 
 ### Bar labels
 
@@ -1913,6 +2269,62 @@ export default function BarLabels() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`label`](#/schedule/ScheduleProps-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. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`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. |
+
 ### Appearances
 
 What a bar says besides its colour: provisional, fixed, muted, running on past the view, and how far the work has got. Each takes one channel of the drawing, so several on one bar stay readable.
@@ -1925,7 +2337,7 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/appearances/
 
 `"provisional"` owns the fill (none at all), `"fixed"` the ends (a cap inside each), `"muted"` the saturation, `"open"` a fade at the edge of the view, and `progress` a rail inside the main time. The faint, outlined fill belongs to a lead-in and a lead-out and to nothing else.
 
-`"provisional"` and `"fixed"` contradict, and the later one in the list wins. `resolveAppearance` is that rule, exported for the application to read as well.
+`"provisional"` and `"fixed"` contradict, and the later one in the list wins. [`resolveAppearance`](#/api/resolveAppearance) is that rule, exported for the application to read as well.
 
 #### Examples
 
@@ -2156,6 +2568,63 @@ export default function Combinations() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`label`](#/schedule/ScheduleProps-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. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`appearance`](#/subtasks/Subtask-appearance) | `readonly `[`SubtaskAppearance`](#/subtasks/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. |
+| [`progress`](#/subtasks/Subtask-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. |
+
+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. |
+
 ### Overlap
 
 Two subtasks claiming one lane at the same time (also called a double booking or conflict): both drawn, offset and marked, never packed into sub-lanes.
@@ -2271,18 +2740,72 @@ export default function ThreeAtOnce() {
 
 - The overlaps as a list to count and act on → Findings as data
 
-#### Known limits
+#### Keyboard
 
-- No stacked layout on request yet: an overlap is always drawn offset, as the finding it is.
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+#### Props on this page
 
-### Dependencies
+From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
 
-Lines from one subtask's end to the next one's start within a task, with the lag that must pass between them (also called links or predecessors). A lag that does not fit is marked, not repaired.
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`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. |
 
-```ts
-import { Dependencies } from "@umriss-ui/schedule";
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+
+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. |
+
+#### Known limits
+
+- No stacked layout on request yet: an overlap is always drawn offset, as the finding it is.
+
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
+
+### Dependencies
+
+Lines from one subtask's end to the next one's start within a task, with the lag that must pass between them (also called links or predecessors). A lag that does not fit is marked, not repaired.
+
+```ts
+import { Dependencies } from "@umriss-ui/schedule";
 ```
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/dependencies/
@@ -2526,37 +3049,124 @@ export default function ViolatedDependency() {
 }
 ```
 
+##### Draw one handover its own way
+
+A dependency's own `attach` and `ends` override the schedule's for that one line: here the sign-off joins the middles and marks its ends, the rest stay quiet.
+
+```tsx
+import { Lane, Schedule, Subtasks, Dependencies } from "@umriss-ui/schedule";
+import type { Subtask, Task, Dependency } from "@umriss-ui/schedule";
+
+/* Picture only, like the schedule's own `attach` and `ends`: the finding
+   follows from `leaves` and `arrives` alone. */
+
+const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
+const min = (n: number) => n * 60_000;
+
+const PROJECTS: Task[] = [{ id: "portal", name: "Member portal", color: "light-dark(#2563eb, #6b9bff)" }];
+
+const WORK: Subtask[] = [
+  { id: "design", task: "portal", lane: "noah", from: at(7), to: at(8), name: "Design" },
+  { id: "build", task: "portal", lane: "arjun", from: at(8, 30), to: at(9, 30), name: "Build" },
+  { id: "test", task: "portal", lane: "eva", from: at(10), to: at(11), name: "Test" },
+  { id: "sign-off", task: "portal", lane: "noah", from: at(11, 30), to: at(12), name: "Sign-off" },
+];
+
+const HANDOVERS: Dependency[] = [
+  { id: "to-build", from: "design", to: "build", lag: min(15) },
+  { id: "to-test", from: "build", to: "test", lag: min(15) },
+  /* The one that matters: the designer signs off what was tested. */
+  { id: "to-sign-off", from: "test", to: "sign-off", lag: min(15), attach: "centre", ends: "dot" },
+];
+
+export default function OneHandoverDrawnItsOwnWay() {
+  return (
+    <Schedule ariaLabel="Design, build, test and a sign-off drawn its own way" initialDomain={[at(6, 30), at(12, 30)]} height={188} attach="nearest" ends="none">
+      <Lane id="noah" label="Noah Fischer" />
+      <Lane id="arjun" label="Arjun Mehta" />
+      <Lane id="eva" label="Eva Novak" />
+      <Dependencies data={HANDOVERS} />
+      <Subtasks data={WORK} tasks={PROJECTS} />
+    </Schedule>
+  );
+}
+```
+
 #### When to use something else
 
 - The shape of the line → Routes
 
+#### Keyboard
+
+| Key | Action |
+|---|---|
+| `] or t` | Out along the active subtask's dependency; pressed again, on to the subtask it arrives at. |
+| `[ or Shift+T` | Back along the dependency to the subtask it leaves. |
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `DependenciesProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` (required) | `readonly Dependency[]` | — | The dependencies, as the caller holds them. |
+| `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 |
 
 ##### `Dependency`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The caller's identity of the dependency. |
-| `from` (required) | `string` | — | The id of the subtask it leaves. |
-| `to` (required) | `string` | — | The id of the subtask it arrives at. |
-| `lag` (required) | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-| `leaves` | `"main" \| "leadOut"` | — | Where it leaves: at the end of the main time, or after the lead-out. Default `"leadOut"` - the predecessor counts as ended once its lead-out is. |
-| `arrives` | `"main" \| "leadIn"` | — | Where it arrives: at the start of the main time, or before the lead-in. Default `"leadIn"` - the lag must have run out before the successor's lead-in begins. |
-| `route` | `DependencyRoute` | — | 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. |
-| `attach` | `DependencyAttachment` | — | Where on the bars this one's line attaches, where it does not attach like the rest. Also picture only, and not to be confused with the two anchors above: those say what the dependency connects, this says where the line touches. |
-| `ends` | `DependencyEnds` | — | Whether this one's ends are marked with a dot, where it is not marked like the rest. Also picture only. |
+| `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 |
+| `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) |
+| `attach` | [`DependencyAttachment`](#type-DependencyAttachment)<br>`"centre" \| "nearest"` | — | Where on the bars this one's line attaches, where it does not attach like the rest. Also picture only, and not to be confused with the two anchors above: those say what the dependency connects, this says where the line touches.<br>Shown in: [Draw one handover its own way](#/dependencies/one-handover-drawn-its-own-way) |
+| `ends` | [`DependencyEnds`](#type-DependencyEnds)<br>`"dot" \| "none"` | — | Whether this one's ends are marked with a dot, where it is not marked like the rest. Also picture only.<br>Shown in: [Draw one handover its own way](#/dependencies/one-handover-drawn-its-own-way) |
+
+##### Types on this page
+
+###### `DependencyRoute`
+
+How a dependency is drawn between its two ends: a curve that leaves and
+arrives forwards, a straight line, or axis-parallel segments.
+
+```ts
+type DependencyRoute = "curve" | "straight" | "orthogonal";
+```
+
+###### `DependencyAttachment`
+
+Where on its bars a dependency's line attaches: the middle of both, or the
+edge that faces the other stop - which is the shortest line between them.
+
+Deliberately not called an anchor: a dependency already HAS two anchors
+(`leaves`, `arrives`), and those decide what it connects and therefore
+whether it is violated. This decides where the line touches, and nothing else.
+The tree has an **Anchor** of its own as well (CONTEXT.md).
+
+```ts
+type DependencyAttachment = "centre" | "nearest";
+```
+
+###### `DependencyEnds`
+
+Whether a dependency's two ends carry a dot. The dot says where the line is
+anchored, which is worth saying while a plan is being read and is noise in a
+plan full of short moves - so it is the caller's choice.
+
+```ts
+type DependencyEnds = "dot" | "none";
+```
 
 #### Known limits
 
-- Only finish-to-start within one task; no dependency types and no critical path (ADR-0032).
+- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### Routes
 
@@ -2727,6 +3337,77 @@ export default function PerDependency() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`route`](#/schedule/ScheduleProps-route) | [`DependencyRoute`](#/schedule/type-DependencyRoute)<br>`"curve" \| "straight" \| "orthogonal"` | `"curve"` | How the dependencies are drawn: a `"curve"` that leaves and arrives forwards, a `"straight"` line, or `"orthogonal"` segments. A dependency may say otherwise for itself. |
+| [`attach`](#/schedule/ScheduleProps-attach) | [`DependencyAttachment`](#/schedule/type-DependencyAttachment)<br>`"centre" \| "nearest"` | `"centre"` | Where a dependency's ends sit on their bars: the `"centre"` of both, or the `"nearest"` edge - which is the shortest line between two stops. Within one lane both mean the middle. A dependency may say otherwise for itself. It changes the picture and never a finding: whether a dependency is violated follows from its `leaves` and `arrives` alone. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`route`](#/dependencies/Dependency-route) | [`DependencyRoute`](#/dependencies/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. |
+
 ## Time
 
 The axis the work stands on: the calendar, blocked time, the now line, and moving through it.
@@ -2979,6 +3660,85 @@ export default function OfficeHours() {
 
 - Time a single lane is not available → Blocked time
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`calendar`](#/schedule/ScheduleProps-calendar) | [`CalendarInput`](#/schedule/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. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`label`](#/schedule/ScheduleProps-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. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`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. |
+
 ### Blocked time
 
 Leave, maintenance and other time a lane is not available: hatched behind the work, a finding where work covers it, and closed to a drag.
@@ -2989,7 +3749,7 @@ import { BlockedTimes, findings } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/blocked-time/
 
-Blocked time is data beside the work: one list, each interval naming its lane, as a leave table or a maintenance plan holds it. `findings` takes the same list as its third argument.
+Blocked time is data beside the work: one list, each interval naming its lane, as a leave table or a maintenance plan holds it. [`findings`](#/api/findings) takes the same list as its third argument.
 
 Work the data already put into blocked time is never locked there: it may be moved within it and out of it, and the finding stays until it is.
 
@@ -3135,7 +3895,7 @@ export default function DragAround() {
 
 ##### Check a sprint against the leave calendar
 
-The team's holidays, sick days and training become `BlockedTimes`, and `findings` confirms that no work item runs into one.
+The team's holidays, sick days and training become `BlockedTimes`, and [`findings`](#/api/findings) confirms that no work item runs into one.
 
 ```tsx
 import { Stack, Text } from "@umriss-ui/core";
@@ -3270,23 +4030,27 @@ export default function TeamLeave() {
 
 - Hours nobody works, on every lane → Time axis and calendar
 
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `BlockedTimesProps`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` (required) | `readonly BlockedTime[]` | — | The blocked time of the lanes - leave, maintenance, unavailability -, as the caller holds it: one list, each interval naming its lane. |
+| `data` *required* | `readonly `[`BlockedTime`](#type-BlockedTime)`[]` | — | The blocked time of the lanes - leave, maintenance, unavailability -, as the caller holds it: one list, each interval naming its lane.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
 
 ##### `BlockedTime`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` (required) | `string` | — | The caller's identity of the interval - what a finding names. |
-| `lane` (required) | `string` | — | The id of the lane it blocks. |
-| `from` (required) | `number` | — | Where it begins. |
-| `to` (required) | `number` | — | Where it ends. |
-| `label` | `string` | — | Why the lane is blocked - "Leave", "Maintenance" -, where the schedule names it. |
+| `id` *required* | `string` | — | The caller's identity of the interval - what a finding names.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
+| `lane` *required* | `string` | — | The id of the lane it blocks.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
+| `from` *required* | `number` | — | Where it begins.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
+| `label` | `string` | — | Why the lane is blocked - "Leave", "Maintenance" -, where the schedule names it.<br>Shown in: [Block out leave and maintenance](#/blocked-time/leave), [Plan work around someone's leave](#/blocked-time/drag-around), [Check a sprint against the leave calendar](#/blocked-time/team-leave) and 5 more |
 
 ### Now line
 
@@ -3502,6 +4266,60 @@ export default function FollowTheClock() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`now`](#/schedule/ScheduleProps-now) | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+
+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. |
+
 ### Pan and zoom
 
 Moving through a plan with the gestures of any scrolling surface: drag, wheel, Ctrl with the wheel, and a pinch. Only the view moves; the plan stays as it is.
@@ -3514,7 +4332,7 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/pan-and-zoom/
 
 Dragging the background pans through time and through the lanes. The wheel scrolls the lanes and hands the scroll back to the page at their end; Shift with the wheel pans through time; Ctrl or ⌘ with the wheel, or a pinch, zooms around the pointer.
 
-Nothing is reported and no intent is raised: pan and zoom change the visible span and nothing else (ADR-0001). `onDomainChange` reports the span for a second view to follow - see [Linked schedules](#/linked-schedules).
+Nothing is reported and no intent is raised: pan and zoom change the visible span and nothing else ([ADR-0001](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0001-affine-scale-contract.md)). `onDomainChange` reports the span for a second view to follow - see [Linked schedules](#/linked-schedules).
 
 #### Examples
 
@@ -3567,6 +4385,66 @@ export default function PanAndZoom() {
 }
 ```
 
+#### Keyboard
+
+| Key | Action |
+|---|---|
+| `Home / End` | The first or last subtask on the lane; the view pans to bring it in. |
+| `PageUp / PageDown` | Along the lane by about a tenth of the visible span, the view following. |
+
+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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`zoomLimits`](#/schedule/ScheduleProps-zoomLimits) | [`ZoomLimits`](#/schedule/type-ZoomLimits) | one hour to 28 days | The narrowest and widest time span zoom may reach, in milliseconds. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+
+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. |
+
 ## Reading
 
 What a planner takes out of the picture: what is selected, what the pointer is on, and what a second view makes of it.
@@ -3721,37 +4599,106 @@ export default function ControlTheSelection() {
 | `Enter or Space` | Selects the active subtask's task, as a click does. |
 | `Escape` | Lets go of the active subtask. |
 
-#### Known limits
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
-- One task at a time: there is no multiple selection.
+#### Props on this page
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
 
-### Interactions
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`selectedTask`](#/schedule/ScheduleProps-selectedTask) | `string \| null` | — | The selected task, controlled. Leave it out and the schedule keeps the selection itself. |
+| [`onSelectedTaskChange`](#/schedule/ScheduleProps-onSelectedTaskChange) | `(task: string \| null, subtask: string \| null) => void` | — | Called when a click selects a task or clears the selection, with the subtask that was clicked - null where the click was on a dependency or on nothing. It is called again when another subtask of the same task is clicked. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
-Reports what the pointer does on the plan - hover, click, right-click - with what it hit and the time and lane under it. Reach for it to open a menu, fill a detail panel or write a status line.
+###### Accessibility
 
-```ts
-import { Schedule } from "@umriss-ui/schedule";
-```
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`ariaLabel`](#/schedule/ScheduleProps-ariaLabel) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/interactions/
+From `LaneProps` — the full table stands on [Lanes](#/lane/type-LaneProps).
 
-A hit names a subtask together with the part of it (lead-in, main time, lead-out), a dependency, a lane, or nothing.
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/lane/LaneProps-id) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
 
-While `onInteraction` is set, a right-click opens no browser menu: your application is expected to answer it.
+From `SubtasksProps` — the full table stands on [Subtasks](#/subtasks/type-SubtasksProps).
 
-#### Examples
+| 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. |
 
-##### Report what the pointer is on
+From `Subtask` — the full table stands on [Subtasks](#/subtasks/type-Subtask).
 
-`onInteraction` hears hover, click and right-click with the target, its part, the time and the lane - here written into a status line.
+| 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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
 
-```tsx
-import { useState } from "react";
-import { Stack, Text } from "@umriss-ui/core";
-import { Dependencies, Lane, Schedule, Subtasks } from "@umriss-ui/schedule";
-import type { Dependency, ScheduleInteraction, Subtask, Task } from "@umriss-ui/schedule";
+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. |
+
+#### Known limits
+
+- One task at a time: there is no multiple selection.
+
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
+
+### Interactions
+
+Reports what the pointer does on the plan - hover, click, right-click - with what it hit and the time and lane under it. Reach for it to open a menu, fill a detail panel or write a status line.
+
+```ts
+import { Schedule } from "@umriss-ui/schedule";
+```
+
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/interactions/
+
+A hit names a subtask together with the part of it (lead-in, main time, lead-out), a dependency, a lane, or nothing.
+
+While `onInteraction` is set, a right-click opens no browser menu: your application is expected to answer it.
+
+#### Examples
+
+##### Report what the pointer is on
+
+`onInteraction` hears hover, click and right-click with the target, its part, the time and the lane - here written into a status line.
+
+```tsx
+import { useState } from "react";
+import { Stack, Text } from "@umriss-ui/core";
+import { Dependencies, Lane, Schedule, Subtasks } from "@umriss-ui/schedule";
+import type { Dependency, ScheduleInteraction, 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;
@@ -3777,9 +4724,9 @@ const describe = (interaction: ScheduleInteraction): string => {
       : hit.kind === "dependency"
         ? `dependency ${hit.dependency.id}`
         : hit.kind === "lane"
-          ? `lane ${hit.lane}`
+          ? "free time"
           : "nothing";
-  return `${interaction.type}: ${target} at ${time}`;
+  return `${interaction.type}: ${target} at ${time}, lane ${interaction.lane ?? "none"}`;
 };
 
 export default function ReportThePointer() {
@@ -3929,18 +4876,36 @@ export default function OpenAContextMenu() {
 - You only need to know which task was picked → Selection
 - You need the time at a point outside an interaction → The handle
 
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `ScheduleInteraction`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `type` (required) | `"click" \| "contextmenu" \| "hover"` | — | `"hover"` is reported when the target under the pointer changes, not on every movement. |
-| `hit` (required) | `ScheduleHit` | — | What the pointer is on. |
-| `clientX` (required) | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens. |
-| `clientY` (required) | `number` | — | The pointer's vertical client coordinate. |
-| `time` (required) | `number` | — | The wall-clock instant under the pointer. |
-| `lane` (required) | `string \| null` | — | The lane under the pointer, or null below the last one. |
+| `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 |
+| `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) |
+| `lane` *required* | `string \| null` | — | The lane under the pointer, or null below the last one.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer) |
+
+##### Types on this page
+
+###### `ScheduleHit`
+
+What a pointer is on.
+
+```ts
+type ScheduleHit =
+  | { readonly kind: "subtask"; readonly subtask: Subtask; readonly part: "leadIn" | "main" | "leadOut" }
+  | { readonly kind: "dependency"; readonly dependency: Dependency }
+  | { readonly kind: "lane"; readonly lane: string }
+  | { readonly kind: "nothing" };
+```
 
 ### Tooltip
 
@@ -4225,22 +5190,99 @@ export default function DetailPanelInstead() {
 }
 ```
 
+##### Say what a bar covers and a line joins
+
+The target says what is hovered: a bar brings its `subtask` and the `blocked` time it covers, a line its `dependency` with the subtasks it joins, `from` and `to`.
+
+```tsx
+import { Stack, Text } from "@umriss-ui/core";
+import { BlockedTimes, Dependencies, Lane, Schedule, Subtasks } from "@umriss-ui/schedule";
+import type { BlockedTime, Dependency, ScheduleTooltipTarget, 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;
+
+const PROJECTS: Task[] = [{ id: "portal", name: "Member portal", color: "light-dark(#2563eb, #6b9bff)" }];
+
+const WORK: Subtask[] = [
+  { id: "design", task: "portal", lane: "noah", from: at(7), to: at(9), name: "Design" },
+  { id: "build", task: "portal", lane: "arjun", from: at(9, 30), to: at(13), name: "Build" },
+  { id: "test", task: "portal", lane: "eva", from: at(13, 30), to: at(15), name: "Test" },
+];
+
+const HANDOVERS: Dependency[] = [
+  { id: "to-build", from: "design", to: "build", lag: min(15) },
+  { id: "to-test", from: "build", to: "test", lag: min(15) },
+];
+
+const LEAVE: BlockedTime[] = [{ id: "arjun-dentist", lane: "arjun", from: at(11), to: at(12), label: "Dentist" }];
+
+const time = (instant: number) => new Date(instant).toLocaleTimeString("en-GB", { hour: "2-digit", minute: "2-digit" });
+
+function Covers({ target }: { target: ScheduleTooltipTarget }) {
+  if (target.kind === "dependency") {
+    return (
+      <Stack gap={1}>
+        <Text size="sm" weight="semibold">
+          Handover {target.dependency.id}
+        </Text>
+        <Text size="xs" tone="secondary">
+          {target.from?.name ?? "?"} → {target.to?.name ?? "?"}
+        </Text>
+      </Stack>
+    );
+  }
+  return (
+    <Stack gap={1}>
+      <Text size="sm" weight="semibold">
+        {target.subtask.name}
+      </Text>
+      <Text size="xs" tone="secondary">
+        {time(target.subtask.from)} – {time(target.subtask.to)}
+      </Text>
+      {target.blocked.map((blocked) => (
+        <Text size="xs" tone="secondary" key={blocked.id}>
+          Covers {blocked.label}, {time(blocked.from)} – {time(blocked.to)}
+        </Text>
+      ))}
+    </Stack>
+  );
+}
+
+export default function SayWhatABarCoversAndALineJoins() {
+  return (
+    <Schedule ariaLabel="Design, build and test, with leave under the build" initialDomain={[at(6, 30), at(15, 30)]} height={188} tooltip={(target) => <Covers target={target} />}>
+      <Lane id="noah" label="Noah Fischer" />
+      <Lane id="arjun" label="Arjun Mehta" />
+      <Lane id="eva" label="Eva Novak" />
+      <BlockedTimes data={LEAVE} />
+      <Dependencies data={HANDOVERS} />
+      <Subtasks data={WORK} tasks={PROJECTS} />
+    </Schedule>
+  );
+}
+```
+
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
 #### API
 
 ##### `ScheduleTooltipTarget`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `kind` (required) | `"subtask" \| "dependency"` | — | A subtask is hovered. A dependency is hovered. |
-| `subtask` | `Subtask` | — | The hovered subtask. |
-| `task` (required) | `Task \| undefined` | — | Its task, where the tasks name it. |
-| `overlapping` | `readonly Subtask[]` | — | The subtasks it overlaps with on its lane. |
-| `violatedDependencies` | `readonly ViolatedDependency[]` | — | The violated dependencies leaving or reaching it. |
-| `blocked` | `readonly BlockedTime[]` | — | The blocked time it covers on its lane. |
-| `dependency` | `Dependency` | — | The hovered dependency. |
-| `from` | `Subtask \| undefined` | — | The subtask it leaves. |
-| `to` | `Subtask \| undefined` | — | The subtask it reaches. |
-| `violated` | `ViolatedDependency \| undefined` | — | Its finding, where it is violated. |
+| `kind` *required* | `"subtask" \| "dependency"` | — | A subtask is hovered. A dependency is hovered.<br>Shown in: [Write your own tooltip content](#/tooltip/own-tooltip), [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `subtask` | [`Subtask`](#/subtasks/type-Subtask) | — | The hovered subtask.<br>Shown in: [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `task` *required* | [`Task`](#/subtasks/type-Task)` \| undefined` | — | Its task, where the tasks name it.<br>Shown in: [Write your own tooltip content](#/tooltip/own-tooltip) |
+| `overlapping` | `readonly `[`Subtask`](#/subtasks/type-Subtask)`[]` | — | The subtasks it overlaps with on its lane.<br>Shown in: [Write your own tooltip content](#/tooltip/own-tooltip) |
+| `violatedDependencies` | `readonly `[`ViolatedDependency`](#/findings/type-ViolatedDependency)`[]` | — | The violated dependencies leaving or reaching it.<br>Shown in: [Write your own tooltip content](#/tooltip/own-tooltip) |
+| `blocked` | `readonly `[`BlockedTime`](#/blocked-time/type-BlockedTime)`[]` | — | The blocked time it covers on its lane.<br>Shown in: [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `dependency` | [`Dependency`](#/dependencies/type-Dependency) | — | The hovered dependency.<br>Shown in: [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `from` | [`Subtask`](#/subtasks/type-Subtask)` \| undefined` | — | The subtask it leaves.<br>Shown in: [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `to` | [`Subtask`](#/subtasks/type-Subtask)` \| undefined` | — | The subtask it reaches.<br>Shown in: [Say what a bar covers and a line joins](#/tooltip/say-what-a-bar-covers-and-a-line-joins) |
+| `violated` | [`ViolatedDependency`](#/findings/type-ViolatedDependency)` \| undefined` | — | Its finding, where it is violated.<br>Shown in: [Write your own tooltip content](#/tooltip/own-tooltip) |
 
 ### Linked schedules
 
@@ -4486,11 +5528,72 @@ export default function RotaBesideIncidents() {
 
 - The lanes belong together in one plan → Lane groups
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`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. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onDomainChange`](#/schedule/ScheduleProps-onDomainChange) | `(domain: readonly [number, number]) => void` | — | The visible time span after the planner panned or zoomed, as two wall-clock instants - for keeping a second schedule or a chart in step. A span handed in through `initialDomain` is not reported back. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`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. |
+
 #### Known limits
 
 - Only the span is shared - not the selection, the hover or the vertical scroll.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### The handle
 
@@ -4597,109 +5700,392 @@ export default function PlaceAMark() {
 
 - You need the time under the pointer during a hover or a click → Interactions
 
-## Editing
+#### Keyboard
 
-Direct manipulation that changes nothing by itself: the schedule reports, the application decides.
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
-### Move and lane
+#### Props on this page
 
-Drag a bar to a new time or onto another lane (also called drag-and-drop rescheduling). A ghost shows where it would land and what that would cause; the drop reports the change for your application to apply.
+From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
 
-```ts
-import { Schedule, applyIntent } from "@umriss-ui/schedule";
-```
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`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. |
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/move-and-lane/
+###### Events
 
-Each name in `intents` enables one gesture. Without `intents` the schedule is read-only, and pressing a bar pans the plot.
+| 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. |
+| [`onDomainChange`](#/schedule/ScheduleProps-onDomainChange) | `(domain: readonly [number, number]) => void` | — | The visible time span after the planner panned or zoomed, as two wall-clock instants - for keeping a second schedule or a chart in step. A span handed in through `initialDomain` is not reported back. |
 
-The schedule never changes your data (ADR-0023): `onIntent` reports a move and a lane change as values, and `applyIntent` is the arithmetic to apply them. A drop across lanes and time reports both, and your handler may apply them, refuse them, or apply one.
+###### Accessibility
 
-Held at the edge of the plot, a drag pans it along; Escape cancels the drag.
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`ariaLabel`](#/schedule/ScheduleProps-ariaLabel) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
-#### Examples
+From `LaneProps` — the full table stands on [Lanes](#/lane/type-LaneProps).
 
-##### Move work in time
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/lane/LaneProps-id) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
 
-List `move` in `intents` and apply what `onIntent` reports with `applyIntent`; the plan changes only in your state.
+From `SubtasksProps` — the full table stands on [Subtasks](#/subtasks/type-SubtasksProps).
 
-```tsx
-import { useState } from "react";
-import { Lane, Schedule, Subtasks, applyIntent } from "@umriss-ui/schedule";
-import type { Subtask, Task } from "@umriss-ui/schedule";
+| 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. |
 
-const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
+From `Subtask` — the full table stands on [Subtasks](#/subtasks/type-Subtask).
 
-const PROJECTS: readonly Task[] = [{ id: "portal", name: "Member portal", color: "light-dark(#7c3aed, #a98bfa)" }];
+| 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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
 
-const START: readonly Subtask[] = [
-  { id: "w-102", task: "portal", lane: "arjun", from: day(17), to: day(18, 17), name: "Profile page" },
-  { id: "w-105", task: "portal", lane: "chloe", from: day(18), to: day(19, 17), name: "Change of address form" },
-];
+From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
 
-export default function MoveInTime() {
-  const [work, setWork] = useState(START);
-  return (
-    <Schedule
-      ariaLabel="Two people's work this week"
-      initialDomain={[day(16, 0), day(21, 0)]}
-      height={140}
-      intents={["move"]}
-      onIntent={(intent) => setWork((current) => current.map((item) => applyIntent(item, intent)))}
-    >
-      <Lane id="arjun" label="Arjun Mehta" />
-      <Lane id="chloe" label="Chloe Durand" />
-      <Subtasks data={work} tasks={PROJECTS} />
-    </Schedule>
-  );
-}
+| 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 `ScheduleInteraction` — the full table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`clientX`](#/interactions/ScheduleInteraction-clientX) *required* | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens. |
+| [`clientY`](#/interactions/ScheduleInteraction-clientY) *required* | `number` | — | The pointer's vertical client coordinate. |
+
+### Findings as data
+
+Lists what is wrong with a plan - double bookings on a lane, dependencies that do not fit, work in blocked time - from the same data the schedule draws. Reach for it to list, count or filter the problems beside the picture.
+
+```ts
+import { findings, overlaps, violatedDependencies, inBlockedTime } from "@umriss-ui/schedule";
 ```
 
-##### Move work onto another lane
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/findings/
 
-Add `lane` to `intents`: a drop reports a move and a lane change separately, and the ghost shows the findings first.
+`findings(subtasks, dependencies, blocked)` returns all three kinds; [`overlaps`](#/api/overlaps), [`violatedDependencies`](#/api/violatedDependencies) and [`inBlockedTime`](#/api/inBlockedTime) return one each. They are pure functions: run them wherever the data changes, with or without a schedule on screen.
+
+Lead-in and lead-out count as occupied time; touching at a shared edge is no overlap.
+
+#### Examples
+
+##### List the findings
+
+[`findings`](#/api/findings) returns what the schedule marks - overlaps, violated dependencies, work in blocked time - as data for a list beside it.
 
 ```tsx
-import { useState } from "react";
 import { Stack, Text } from "@umriss-ui/core";
-import { Dependencies, Lane, Schedule, Subtasks, applyIntent } from "@umriss-ui/schedule";
-import type { Dependency, Intent, 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;
+import { BlockedTimes, Dependencies, Lane, Schedule, Subtasks, findings } from "@umriss-ui/schedule";
+import type { BlockedTime, Dependency, Subtask, Task } from "@umriss-ui/schedule";
 
-const VEHICLES = [
-  { id: "truck-118", label: "Truck FP 118 R" },
-  { id: "van-402", label: "Van FP 402 R" },
-  { id: "truck-520", label: "Truck FP 520 E" },
-  { id: "van-455", label: "E-van FP 455 R" },
-  { id: "van-290", label: "Van FP 290 E" },
-];
+const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
 
-const CONSIGNMENTS: readonly Task[] = [
-  { id: "c-2041", name: "C-2041 Holloway Garden Supplies", color: "light-dark(#2563eb, #6b9bff)" },
-  { id: "c-2043", name: "C-2043 Oakridge Pharmacy", color: "light-dark(#c2410c, #f08a52)" },
-  { id: "c-2045", name: "C-2045 Tamsin's Bakery", color: "light-dark(#be185d, #f06aa6)" },
-  { id: "c-2046", name: "C-2046 Pellham Hardware", color: "light-dark(#4d7c0f, #8fc43e)" },
+const PROJECTS: readonly Task[] = [
+  { id: "shop", name: "Online shop relaunch", color: "light-dark(#2563eb, #6b9bff)" },
+  { id: "portal", name: "Member portal", color: "light-dark(#7c3aed, #a98bfa)" },
 ];
 
-const LEGS: readonly Subtask[] = [
-  { id: "c-2041-1", task: "c-2041", lane: "truck-118", from: at(6), to: at(7), leadIn: min(15), leadOut: min(10) },
-  { id: "c-2043-1", task: "c-2043", lane: "truck-520", from: at(6, 30), to: at(8), leadIn: min(30), leadOut: min(15) },
-  { id: "c-2043-2", task: "c-2043", lane: "van-402", from: at(10), to: at(11, 30), leadIn: min(15) },
-  { id: "c-2046-2", task: "c-2046", lane: "van-402", from: at(13), to: at(14, 30), leadIn: min(20), leadOut: min(10) },
-  { id: "c-2043-3", task: "c-2043", lane: "van-455", from: at(12), to: at(14), leadIn: min(20), leadOut: min(20) },
-  { id: "c-2045-3", task: "c-2045", lane: "van-290", from: at(15, 45), to: at(16, 30) },
+const WORK: readonly Subtask[] = [
+  { id: "design", task: "shop", lane: "noah", from: day(16), to: day(17, 17), name: "Search results layout" },
+  { id: "build", task: "shop", lane: "chloe", from: day(17), to: day(19, 17), name: "Search results page" },
+  { id: "address", task: "portal", lane: "chloe", from: day(18), to: day(19, 17), name: "Change of address form" },
+  { id: "profile", task: "portal", lane: "arjun", from: day(17), to: day(19, 17), name: "Profile page" },
 ];
 
-const TRANSFERS: readonly Dependency[] = [
-  { id: "t-2043-1", from: "c-2043-1", to: "c-2043-2", lag: min(45) },
-  { id: "t-2043-2", from: "c-2043-2", to: "c-2043-3", lag: min(25) },
-];
+/* The build may start only a morning after the design is done. */
+const HANDOVERS: readonly Dependency[] = [{ id: "design-to-build", from: "design", to: "build", lag: 4 * 60 * 60_000 }];
 
-export default function MoveToAnotherLane() {
-  const [legs, setLegs] = useState(LEGS);
-  const [last, setLast] = useState<Intent | null>(null);
+const LEAVE: readonly BlockedTime[] = [{ id: "arjun-holiday", lane: "arjun", from: day(18, 0), to: day(21, 0), label: "Holiday" }];
+
+const when = (instant: number) => new Date(instant).toLocaleString("en-GB", { weekday: "short", hour: "2-digit", minute: "2-digit" });
+const hours = (ms: number) => Math.round(ms / 3_600_000);
+
+export default function ListTheFindings() {
+  const found = findings(WORK, HANDOVERS, LEAVE);
+
+  return (
+    <Stack gap={3}>
+      <Schedule ariaLabel="Three people's week with its findings" initialDomain={[day(16, 0), day(21, 0)]} height={184}>
+        <Lane id="noah" label="Noah Fischer" />
+        <Lane id="chloe" label="Chloe Durand" />
+        <Lane id="arjun" label="Arjun Mehta" />
+        <BlockedTimes data={LEAVE} />
+        <Dependencies data={HANDOVERS} />
+        <Subtasks data={WORK} tasks={PROJECTS} />
+      </Schedule>
+      <ul style={{ margin: 0, paddingLeft: 18 }}>
+        {found.overlaps.map((o) => (
+          <Text as="li" size="sm" key={`${o.first}/${o.second}`}>
+            Double-booked: {o.lane} has {o.first} and {o.second} from {when(o.from)} to {when(o.to)}
+          </Text>
+        ))}
+        {found.violatedDependencies.map((v) => (
+          <Text as="li" size="sm" key={v.dependency}>
+            Too early: {v.dependency} leaves {when(v.departure)} for a start at {when(v.arrival)}, {hours(v.shortBy)} hours short
+          </Text>
+        ))}
+        {found.inBlockedTime.map((b) => (
+          <Text as="li" size="sm" key={`${b.subtask}/${b.blocked}`}>
+            In leave: {b.subtask} covers {b.blocked} from {when(b.from)} to {when(b.to)}
+          </Text>
+        ))}
+      </ul>
+    </Stack>
+  );
+}
+```
+
+##### Say when there is nothing to fix
+
+When all three lists [`findings`](#/api/findings) returns are empty, say so plainly instead of showing an empty list.
+
+```tsx
+import { EmptyState, Stack } from "@umriss-ui/core";
+import { Lane, Schedule, Subtasks, findings } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
+
+const PROJECTS: readonly Task[] = [{ id: "booking", name: "Booking app", color: "light-dark(#0d9488, #3cc7b8)" }];
+
+const WORK: readonly Subtask[] = [
+  { id: "w-111", task: "booking", lane: "hana", from: day(16), to: day(18, 17), name: "Push notifications" },
+  { id: "w-113", task: "booking", lane: "kofi", from: day(16), to: day(18, 17), name: "Calendar sync" },
+];
+
+export default function NothingToFix() {
+  const found = findings(WORK, []);
+  const count = found.overlaps.length + found.violatedDependencies.length + found.inBlockedTime.length;
+
+  return (
+    <Stack gap={3}>
+      <Schedule ariaLabel="Two developers' week, without findings" initialDomain={[day(16, 0), day(21, 0)]} height={140}>
+        <Lane id="hana" label="Hana Sato" />
+        <Lane id="kofi" label="Kofi Mensah" />
+        <Subtasks data={WORK} tasks={PROJECTS} />
+      </Schedule>
+      {count === 0 && <EmptyState title="Nothing to fix" description="Nobody is double-booked, every hand-over fits, and no work falls into leave." />}
+    </Stack>
+  );
+}
+```
+
+##### Count the findings per kind
+
+[`overlaps`](#/api/overlaps) and [`violatedDependencies`](#/api/violatedDependencies) are the halves of [`findings`](#/api/findings) on their own - here as counts above the day's legs.
+
+```tsx
+import { Badge, Stack } from "@umriss-ui/core";
+import { Dependencies, Lane, Schedule, Subtasks, overlaps, violatedDependencies } from "@umriss-ui/schedule";
+import type { Dependency, 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;
+
+const VEHICLES = [
+  { id: "van-402", label: "Van FP 402 R" },
+  { id: "truck-520", label: "Truck FP 520 E" },
+  { id: "van-455", label: "E-van FP 455 R" },
+];
+
+const CONSIGNMENTS: readonly Task[] = [
+  { id: "c-2041", name: "C-2041 Holloway Garden Supplies", color: "light-dark(#2563eb, #6b9bff)" },
+  { id: "c-2043", name: "C-2043 Oakridge Pharmacy", color: "light-dark(#c2410c, #f08a52)" },
+];
+
+const LEGS: readonly Subtask[] = [
+  { id: "c-2041-2", task: "c-2041", lane: "van-402", from: at(8), to: at(10, 30), leadIn: min(30), leadOut: min(15) },
+  { id: "c-2043-1", task: "c-2043", lane: "truck-520", from: at(6, 30), to: at(8), leadIn: min(30), leadOut: min(15) },
+  { id: "c-2043-2", task: "c-2043", lane: "van-402", from: at(10), to: at(11, 30), leadIn: min(15) },
+  { id: "c-2043-3", task: "c-2043", lane: "van-455", from: at(12), to: at(14), leadIn: min(20), leadOut: min(20) },
+];
+
+const TRANSFERS: readonly Dependency[] = [
+  { id: "t-2043-1", from: "c-2043-1", to: "c-2043-2", lag: min(45) },
+  { id: "t-2043-2", from: "c-2043-2", to: "c-2043-3", lag: min(25) },
+];
+
+export default function CountPerKind() {
+  const doubleBooked = overlaps(LEGS).length;
+  const late = violatedDependencies(LEGS, TRANSFERS).length;
+
+  return (
+    <Stack gap={3}>
+      <Stack direction="row" gap={2}>
+        <Badge tone={doubleBooked > 0 ? "warning" : "success"}>{doubleBooked} double-booked</Badge>
+        <Badge tone={late > 0 ? "warning" : "success"}>{late} transfers too short</Badge>
+      </Stack>
+      <Schedule ariaLabel="The day's legs with their findings counted" initialDomain={[at(5, 30), at(18)]} height={196}>
+        {VEHICLES.map((vehicle) => (
+          <Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
+        ))}
+        <Dependencies data={TRANSFERS} />
+        <Subtasks data={LEGS} tasks={CONSIGNMENTS} />
+      </Schedule>
+    </Stack>
+  );
+}
+```
+
+#### Keyboard
+
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+
+#### API
+
+##### `Overlap`
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `lane` *required* | `string` | — | The lane both sit on.<br>Shown in: [List the findings](#/findings/list-the-findings), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) |
+| `first` *required* | `string` | — | The subtask that starts earlier (lead-in included); on a tie, the one that stands first in the data.<br>Shown in: [List the findings](#/findings/list-the-findings), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) |
+| `second` *required* | `string` | — | The other one.<br>Shown in: [List the findings](#/findings/list-the-findings), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) |
+| `from` *required* | `number` | — | Where the covering begins.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+
+##### `ViolatedDependency`
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `dependency` *required* | `string` | — | The id of the dependency.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+| `departure` *required* | `number` | — | When it leaves, by its anchor.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+| `arrival` *required* | `number` | — | When it has to have arrived, by its anchor.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+| `shortBy` *required* | `number` | — | How much time is missing: departure plus lag, minus arrival.<br>Shown in: [List the findings](#/findings/list-the-findings) |
+
+##### `InBlockedTime`
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [List the findings](#/findings/list-the-findings), [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Check a sprint against the leave calendar (Blocked time)](#/blocked-time/team-leave) and 2 more |
+| `blocked` *required* | `string` | — | The id of the blocked time it covers.<br>Shown in: [List the findings](#/findings/list-the-findings), [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Plan the sprint around leave (Scenarios)](#/scenarios/plan-the-sprint-around-leave) |
+| `lane` *required* | `string` | — | The lane both are on.<br>Shown in: [Hand over the on-call week (Scenarios)](#/scenarios/hand-over-the-on-call-week), [Plan the sprint around leave (Scenarios)](#/scenarios/plan-the-sprint-around-leave) |
+| `from` *required* | `number` | — | Where the covering begins.<br>Shown in: [List the findings](#/findings/list-the-findings), [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Hand over the on-call week (Scenarios)](#/scenarios/hand-over-the-on-call-week) |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [List the findings](#/findings/list-the-findings), [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Hand over the on-call week (Scenarios)](#/scenarios/hand-over-the-on-call-week) |
+
+#### Known limits
+
+- Overlapping work is marked, not packed into sub-lanes; stacked overlap is not built yet.
+
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
+
+## Editing
+
+Direct manipulation that changes nothing by itself: the schedule reports, the application decides.
+
+### Move and lane
+
+Drag a bar to a new time or onto another lane (also called drag-and-drop rescheduling). A ghost shows where it would land and what that would cause; the drop reports the change for your application to apply.
+
+```ts
+import { Schedule, applyIntent } from "@umriss-ui/schedule";
+```
+
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/move-and-lane/
+
+Each name in `intents` enables one gesture. Without `intents` the schedule is read-only, and pressing a bar pans the plot.
+
+The schedule never changes your data ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)): `onIntent` reports a move and a lane change as values, and [`applyIntent`](#/api/applyIntent) is the arithmetic to apply them. A drop across lanes and time reports both, and your handler may apply them, refuse them, or apply one.
+
+Held at the edge of the plot, a drag pans it along; Escape cancels the drag.
+
+#### Examples
+
+##### Move work in time
+
+List `move` in `intents` and apply what `onIntent` reports with [`applyIntent`](#/api/applyIntent); the plan changes only in your state.
+
+```tsx
+import { useState } from "react";
+import { Lane, Schedule, Subtasks, applyIntent } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
+
+const PROJECTS: readonly Task[] = [{ id: "portal", name: "Member portal", color: "light-dark(#7c3aed, #a98bfa)" }];
+
+const START: readonly Subtask[] = [
+  { id: "w-102", task: "portal", lane: "arjun", from: day(17), to: day(18, 17), name: "Profile page" },
+  { id: "w-105", task: "portal", lane: "chloe", from: day(18), to: day(19, 17), name: "Change of address form" },
+];
+
+export default function MoveInTime() {
+  const [work, setWork] = useState(START);
+  return (
+    <Schedule
+      ariaLabel="Two people's work this week"
+      initialDomain={[day(16, 0), day(21, 0)]}
+      height={140}
+      intents={["move"]}
+      onIntent={(intent) => setWork((current) => current.map((item) => applyIntent(item, intent)))}
+    >
+      <Lane id="arjun" label="Arjun Mehta" />
+      <Lane id="chloe" label="Chloe Durand" />
+      <Subtasks data={work} tasks={PROJECTS} />
+    </Schedule>
+  );
+}
+```
+
+##### Move work onto another lane
+
+Add `lane` to `intents`: a drop reports a move and a lane change separately, and the ghost shows the findings first.
+
+```tsx
+import { useState } from "react";
+import { Stack, Text } from "@umriss-ui/core";
+import { Dependencies, Lane, Schedule, Subtasks, applyIntent } from "@umriss-ui/schedule";
+import type { Dependency, Intent, 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;
+
+const VEHICLES = [
+  { id: "truck-118", label: "Truck FP 118 R" },
+  { id: "van-402", label: "Van FP 402 R" },
+  { id: "truck-520", label: "Truck FP 520 E" },
+  { id: "van-455", label: "E-van FP 455 R" },
+  { id: "van-290", label: "Van FP 290 E" },
+];
+
+const CONSIGNMENTS: readonly Task[] = [
+  { id: "c-2041", name: "C-2041 Holloway Garden Supplies", color: "light-dark(#2563eb, #6b9bff)" },
+  { id: "c-2043", name: "C-2043 Oakridge Pharmacy", color: "light-dark(#c2410c, #f08a52)" },
+  { id: "c-2045", name: "C-2045 Tamsin's Bakery", color: "light-dark(#be185d, #f06aa6)" },
+  { id: "c-2046", name: "C-2046 Pellham Hardware", color: "light-dark(#4d7c0f, #8fc43e)" },
+];
+
+const LEGS: readonly Subtask[] = [
+  { id: "c-2041-1", task: "c-2041", lane: "truck-118", from: at(6), to: at(7), leadIn: min(15), leadOut: min(10) },
+  { id: "c-2043-1", task: "c-2043", lane: "truck-520", from: at(6, 30), to: at(8), leadIn: min(30), leadOut: min(15) },
+  { id: "c-2043-2", task: "c-2043", lane: "van-402", from: at(10), to: at(11, 30), leadIn: min(15) },
+  { id: "c-2046-2", task: "c-2046", lane: "van-402", from: at(13), to: at(14, 30), leadIn: min(20), leadOut: min(10) },
+  { id: "c-2043-3", task: "c-2043", lane: "van-455", from: at(12), to: at(14), leadIn: min(20), leadOut: min(20) },
+  { id: "c-2045-3", task: "c-2045", lane: "van-290", from: at(15, 45), to: at(16, 30) },
+];
+
+const TRANSFERS: readonly Dependency[] = [
+  { id: "t-2043-1", from: "c-2043-1", to: "c-2043-2", lag: min(45) },
+  { id: "t-2043-2", from: "c-2043-2", to: "c-2043-3", lag: min(25) },
+];
+
+export default function MoveToAnotherLane() {
+  const [legs, setLegs] = useState(LEGS);
+  const [last, setLast] = useState<Intent | null>(null);
 
   return (
     <Stack gap={3}>
@@ -4729,7 +6115,7 @@ export default function MoveToAnotherLane() {
 
 ##### Refuse a move that double-books someone
 
-Your `onIntent` decides: here it applies a drop only when `overlaps` finds no new double booking, and says why otherwise.
+Your `onIntent` decides: here it applies a drop only when [`overlaps`](#/api/overlaps) finds no new double booking, and says why otherwise.
 
 ```tsx
 import { useRef, useState } from "react";
@@ -4876,12 +6262,95 @@ export default function RefuseADoubleBooking() {
 | `Alt+← Alt+→` | Proposes moving the active subtask one raster step earlier or later, stepping over blocked time. |
 | `Escape` | Cancels a drag in flight: the ghost goes and nothing is reported. |
 
-#### Known limits
+The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
-- No undo: your application owns the data, and with it the history (ADR-0032).
-- The keys move work in time only; a lane change needs the pointer.
+#### Props on this page
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`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 `Overlap` — the full table stands on [Findings as data](#/findings/type-Overlap).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`lane`](#/findings/Overlap-lane) *required* | `string` | — | The lane both sit on. |
+| [`first`](#/findings/Overlap-first) *required* | `string` | — | The subtask that starts earlier (lead-in included); on a tie, the one that stands first in the data. |
+| [`second`](#/findings/Overlap-second) *required* | `string` | — | The other one. |
+
+#### Known limits
+
+- No undo: your application owns the data, and with it the history ([ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/)).
+- The keys move work in time only; a lane change needs the pointer.
+
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### Stretch, lead-in, lead-out
 
@@ -4980,11 +6449,71 @@ export default function ChangeLeadInAndLeadOut() {
 |---|---|
 | `Alt+Shift+← Alt+Shift+→` | Proposes ending the active subtask one raster step earlier or later. |
 
+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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+| [`leadIn`](#/subtasks/Subtask-leadIn) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#/subtasks/Subtask-leadOut) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`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. |
+
 #### Known limits
 
 - A main time never becomes shorter than one raster step, or a minute without a raster.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### Snapping
 
@@ -4998,7 +6527,7 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/snapping/
 
 Without `snap` a drag lands on the fine band's step, which follows the zoom. A number is a step in milliseconds; `{ step, offset }` counts from local midnight; `false` places to the minute.
 
-Snapping shapes the ghost and so the intent; it never moves data that is not being dragged. `snapTime` is the same arithmetic for your own use.
+Snapping shapes the ghost and so the intent; it never moves data that is not being dragged. [`snapTime`](#/api/snapTime) is the same arithmetic for your own use.
 
 #### Examples
 
@@ -5142,6 +6671,67 @@ export default function NoSnapping() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`snap`](#/schedule/ScheduleProps-snap) | `"ticks" \| number \| `[`SnapRaster`](#/schedule/type-SnapRaster)` \| false` | `"ticks"` | The raster a drag lands on: `"ticks"` - the fine band's current step -, a step in milliseconds from local midnight, a step with an offset (shifts at 06:00, 14:00 and 22:00 are eight hours offset by six), or `false` for none. It shapes the ghost and the intent, never the data. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+
 ### Placing from outside
 
 Drag work that is not on the plan yet - from a backlog or a list of unassigned jobs - onto a lane, with the browser's own drag and drop. The drop reports where it should go; your application creates it.
@@ -5154,13 +6744,13 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/placing/
 
 The browser hands over dragged data only on the drop, so declare what is being dragged in `placing` on your `dragstart` and clear it on `dragend`. The schedule then shows the ghost at the snapped time, with the findings the drop would create.
 
-A `place` intent carries your item's key, the task, the lane and the times. The id of the new subtask is yours; `subtaskFromPlace` builds it from the intent.
+A `place` intent carries your item's key, the task, the lane and the times. The id of the new subtask is yours; [`subtaskFromPlace`](#/api/subtaskFromPlace) builds it from the intent.
 
 #### Examples
 
 ##### Drag work in from the backlog
 
-Set `placing` on your list's `dragstart` and clear it on `dragend`; the drop reports a `place` intent that `subtaskFromPlace` turns into work.
+Set `placing` on your list's `dragstart` and clear it on `dragend`; the drop reports a `place` intent that [`subtaskFromPlace`](#/api/subtaskFromPlace) turns into work.
 
 ```tsx
 import { useState } from "react";
@@ -5265,6 +6855,82 @@ export default function DragFromTheBacklog() {
 
 - The work is already on the plan → Move and lane
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`placing`](#/schedule/ScheduleProps-placing) | [`PlacingItem`](#/schedule/type-PlacingItem)` \| null` | — | What the application is dragging in from outside while it drags it - its key, task, the length of its main time, its lead-in and lead-out. The browser hands the dragged data over only on the drop, so the ghost before it can only come from here: set it on your own `dragstart`, clear it on `dragend`. Without `"place"` in `intents` no drop is accepted. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+
 ### Where a subtask may go
 
 Marks the lanes and times a piece of work may not go to as soon as a drag begins, and holds the ghost where it is allowed. Reach for it when rules of your domain - equipment, skills, leave - limit where work can stand.
@@ -5598,11 +7264,88 @@ export default function AroundLeave() {
 
 - The rule depends on the result, such as no double booking → Move and lane
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`canMoveTo`](#/schedule/ScheduleProps-canMoveTo) | `(subtask: `[`Subtask`](#/subtasks/type-Subtask)`, lane: string) => boolean` | every lane is open | Whether a subtask may go to a lane. It narrows `"lane"`, it does not enable it. Asked once per lane when a drag takes hold, and asked again at the drop. The lanes it turns down are marked from the first frame of the drag - a planner sees the refusal before meeting it - and over one of them the ghost stays on the last lane that was allowed, the cursor says no and a line ties the ghost to the pointer. A refused lane costs the lane and nothing else: a drop after it still reports the move in time. It is asked for work dragged in from outside as well, with the key and task the application declared in `placing`. |
+| [`placing`](#/schedule/ScheduleProps-placing) | [`PlacingItem`](#/schedule/type-PlacingItem)` \| null` | — | What the application is dragging in from outside while it drags it - its key, task, the length of its main time, its lead-in and lead-out. The browser hands the dragged data over only on the drop, so the ghost before it can only come from here: set it on your own `dragstart`, clear it on `dragend`. Without `"place"` in `intents` no drop is accepted. |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+
+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 `BlockedTimesProps` — the full table stands on [Blocked time](#/blocked-time/type-BlockedTimesProps).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`data`](#/blocked-time/BlockedTimesProps-data) *required* | `readonly `[`BlockedTime`](#/blocked-time/type-BlockedTime)`[]` | — | The blocked time of the lanes - leave, maintenance, unavailability -, as the caller holds it: one list, each interval naming its lane. |
+
+From `BlockedTime` — the full table stands on [Blocked time](#/blocked-time/type-BlockedTime).
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`id`](#/blocked-time/BlockedTime-id) *required* | `string` | — | The caller's identity of the interval - what a finding names. |
+| [`lane`](#/blocked-time/BlockedTime-lane) *required* | `string` | — | The id of the lane it blocks. |
+| [`from`](#/blocked-time/BlockedTime-from) *required* | `number` | — | Where it begins. |
+| [`to`](#/blocked-time/BlockedTime-to) *required* | `number` | — | Where it ends. |
+| [`label`](#/blocked-time/BlockedTime-label) | `string` | — | Why the lane is blocked - "Leave", "Maintenance" -, where the schedule names it. |
+
 #### Known limits
 
 - A rule that changes while a drag runs is noticed at the drop, not before.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
 ### Ripple
 
@@ -5616,13 +7359,13 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/ripple/
 
 `ripple(subtasks, dependencies, intent)` returns move intents down the whole chain, in the order they were pushed. A successor keeps its length and is never pulled earlier: room that opens up is the planner's.
 
-`shiftTask` moves every subtask of one task by the same amount, so all its dependencies keep fitting.
+[`shiftTask`](#/api/shiftTask) moves every subtask of one task by the same amount, so all its dependencies keep fitting.
 
 #### Examples
 
 ##### Push the later stops of a tour
 
-`ripple` returns the moves that push every stop whose drive no longer fits behind a late one; you decide whether to apply them.
+[`ripple`](#/api/ripple) returns the moves that push every stop whose drive no longer fits behind a late one; you decide whether to apply them.
 
 ```tsx
 import { useState } from "react";
@@ -5690,7 +7433,7 @@ export default function PushTheLaterStops() {
 
 ##### Move a whole tour
 
-`shiftTask` returns one move per stop, all by the same amount, so every drive that fitted still fits.
+[`shiftTask`](#/api/shiftTask) returns one move per stop, all by the same amount, so every drive that fitted still fits.
 
 ```tsx
 import { useState } from "react";
@@ -5749,7 +7492,7 @@ export default function MoveAWholeTour() {
 
 ##### Ripple on every drag
 
-Run `ripple` inside `onIntent` and apply its moves with the drop: drag the design later and build and test follow.
+Run [`ripple`](#/api/ripple) inside `onIntent` and apply its moves with the drop: drag the design later and build and test follow.
 
 ```tsx
 import { useState } from "react";
@@ -5799,356 +7542,603 @@ export default function RippleOnEveryDrag() {
 }
 ```
 
+#### 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 |
+|---|---|---|---|
+| [`initialDomain`](#/schedule/ScheduleProps-initialDomain) *required* | `readonly [number, number]` | — | The time in view when the schedule mounts, as two wall-clock instants. Pan and zoom take it from there; a new pair of values puts it back. |
+| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#/schedule/ScheduleProps-intents) | `readonly `[`IntentKind`](#/schedule/type-IntentKind)`[]` | `[]` | The intents the caller handles. Each one enables its interaction; none leaves a read-only schedule ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). |
+| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+
+###### Events
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`onIntent`](#/schedule/ScheduleProps-onIntent) | `(intent: `[`Intent`](#/schedule/type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
+
+###### 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`. |
+| [`label`](#/lane/LaneProps-label) | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader. |
+
+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. |
+
 #### Known limits
 
-- No dependency types, slack or critical path: the schedule is no project-planning engine (ADR-0032).
+- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/)).
 - A dependency joins subtasks of one task, so work of other tasks is never pushed.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/).
 
-## Findings
+## API index
 
-What a planner opens a schedule for, as data beside the picture.
+Every name the package exports, in one place.
 
-### Findings as data
+### API index
 
-Lists what is wrong with a plan - double bookings on a lane, dependencies that do not fit, work in blocked time - from the same data the schedule draws. Reach for it to list, count or filter the problems beside the picture.
+Everything `@umriss-ui/schedule` exports, with its signature. A component's props stand on its own page.
 
-```ts
-import { findings, overlaps, violatedDependencies, inBlockedTime } from "@umriss-ui/schedule";
-```
+Demo page: https://romanhaendler.github.io/umriss-ui/schedule/api/
 
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/findings/
+#### Components
 
-`findings(subtasks, dependencies, blocked)` returns all three kinds; `overlaps`, `violatedDependencies` and `inBlockedTime` return one each. They are pure functions: run them wherever the data changes, with or without a schedule on screen.
+##### `BlockedTimes`
 
-Lead-in and lead-out count as occupied time; touching at a shared edge is no overlap.
+[Blocked time](#/blocked-time) – A layer of blocked time. Wherever it is declared, it is drawn behind every
+subtask and dependency: it is a property of the lane, not something on it.
 
-#### Examples
+Used on [Scenarios](#/), [Blocked time](#/blocked-time), [Tooltip](#/tooltip), [Findings as data](#/findings) and [Where a subtask may go](#/where-it-may-go).
 
-##### List the findings
+##### `Dependencies`
 
-`findings` returns what the schedule marks - overlaps, violated dependencies, work in blocked time - as data for a list beside it.
+[Dependencies](#/dependencies) – Lines from one subtask's end to the next one's start within a task, with the lag that must pass between them (also called links or predecessors). A lag that does not fit is marked, not repaired.
 
-```tsx
-import { Stack, Text } from "@umriss-ui/core";
-import { BlockedTimes, Dependencies, Lane, Schedule, Subtasks, findings } from "@umriss-ui/schedule";
-import type { BlockedTime, Dependency, Subtask, Task } from "@umriss-ui/schedule";
+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).
 
-const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
+##### `Lane`
 
-const PROJECTS: readonly Task[] = [
-  { id: "shop", name: "Online shop relaunch", color: "light-dark(#2563eb, #6b9bff)" },
-  { id: "portal", name: "Member portal", color: "light-dark(#7c3aed, #a98bfa)" },
-];
+[Lanes](#/lane) – One lane: a person, a vehicle, a room. The lanes run top to bottom in the order
+they are declared - whichever group they are declared in.
 
-const WORK: readonly Subtask[] = [
-  { id: "design", task: "shop", lane: "noah", from: day(16), to: day(17, 17), name: "Search results layout" },
-  { id: "build", task: "shop", lane: "chloe", from: day(17), to: day(19, 17), name: "Search results page" },
-  { id: "address", task: "portal", lane: "chloe", from: day(18), to: day(19, 17), name: "Change of address form" },
-  { id: "profile", task: "portal", lane: "arjun", from: day(17), to: day(19, 17), name: "Profile page" },
-];
+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), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [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).
 
-/* The build may start only a morning after the design is done. */
-const HANDOVERS: readonly Dependency[] = [{ id: "design-to-build", from: "design", to: "build", lag: 4 * 60 * 60_000 }];
+##### `LaneGroup`
 
-const LEAVE: readonly BlockedTime[] = [{ id: "arjun-holiday", lane: "arjun", from: day(18, 0), to: day(21, 0), label: "Holiday" }];
+[Lane groups](#/lane-groups) – A group of lanes: structure over them, and never a lane itself.
 
-const when = (instant: number) => new Date(instant).toLocaleString("en-GB", { weekday: "short", hour: "2-digit", minute: "2-digit" });
-const hours = (ms: number) => Math.round(ms / 3_600_000);
+It gives its id to its children through context, so a lane never names its
+group and a group reads in JSX as it reads in the organisation. Folded, it becomes
+one row showing a **Miniature** of everything in it; open, it shows a slim
+head above its lanes. Which groups are folded is `collapsedGroups` on
+`Schedule` - a view state, never an **Intent**.
 
-export default function ListTheFindings() {
-  const found = findings(WORK, HANDOVERS, LEAVE);
+Used on [Scenarios](#/) and [Lane groups](#/lane-groups).
 
-  return (
-    <Stack gap={3}>
-      <Schedule ariaLabel="Three people's week with its findings" initialDomain={[day(16, 0), day(21, 0)]} height={184}>
-        <Lane id="noah" label="Noah Fischer" />
-        <Lane id="chloe" label="Chloe Durand" />
-        <Lane id="arjun" label="Arjun Mehta" />
-        <BlockedTimes data={LEAVE} />
-        <Dependencies data={HANDOVERS} />
-        <Subtasks data={WORK} tasks={PROJECTS} />
-      </Schedule>
-      <ul style={{ margin: 0, paddingLeft: 18 }}>
-        {found.overlaps.map((o) => (
-          <Text as="li" size="sm" key={`${o.first}/${o.second}`}>
-            Double-booked: {o.lane} has {o.first} and {o.second} from {when(o.from)} to {when(o.to)}
-          </Text>
-        ))}
-        {found.violatedDependencies.map((v) => (
-          <Text as="li" size="sm" key={v.dependency}>
-            Too early: {v.dependency} is {hours(v.shortBy)} hours short
-          </Text>
-        ))}
-        {found.inBlockedTime.map((b) => (
-          <Text as="li" size="sm" key={`${b.subtask}/${b.blocked}`}>
-            In leave: {b.subtask} covers {b.blocked} from {when(b.from)} to {when(b.to)}
-          </Text>
-        ))}
-      </ul>
-    </Stack>
-  );
-}
+##### `Schedule`
+
+[First schedule](#/schedule) – A plan of subtasks on lanes over time - people, vehicles, rooms - with
+dependencies between them. The contents are declared as children (`Lane`,
+`LaneGroup`, `Subtasks`, `Dependencies`, `BlockedTimes`); the planner pans,
+zooms and drags, and every drag ends as an **Intent** through `onIntent`.
+The data changes only where the caller applies it; without `intents` the
+schedule is read-only. A ref gives the `ScheduleHandle`.
+
+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), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [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).
+
+##### `Subtasks`
+
+[Subtasks](#/subtasks) – The bars: a main time with an optional lead-in before it and lead-out after it, in the colour of the task they belong to (also called bookings or assignments).
+
+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), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [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).
+
+#### Functions
+
+##### `applyIntent`
+
+The subtask as the intent asks for it. An intent for another subtask leaves
+it as it is.
+
+```ts
+function applyIntent<S extends Subtask>(subtask: S, intent: Intent): S;
 ```
 
-##### Say when there is nothing to fix
+Used on [Scenarios](#/), [Lane groups](#/lane-groups), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Interactions](#/interactions), [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).
 
-When all three lists `findings` returns are empty, say so plainly instead of showing an empty list.
+##### `arrival`
 
-```tsx
-import { EmptyState, Stack } from "@umriss-ui/core";
-import { Lane, Schedule, Subtasks, findings } from "@umriss-ui/schedule";
-import type { Subtask, Task } from "@umriss-ui/schedule";
+When a dependency has to have arrived at its subtask, by its anchor.
 
-const day = (d: number, hours = 9) => new Date(2026, 2, d, hours).getTime();
+```ts
+function arrival(dependency: Dependency, to: Subtask): number;
+```
 
-const PROJECTS: readonly Task[] = [{ id: "booking", name: "Booking app", color: "light-dark(#0d9488, #3cc7b8)" }];
+Used on [Scenarios](#/), [Now line](#/now-line) and [Findings as data](#/findings).
 
-const WORK: readonly Subtask[] = [
-  { id: "w-111", task: "booking", lane: "hana", from: day(16), to: day(18, 17), name: "Push notifications" },
-  { id: "w-113", task: "booking", lane: "kofi", from: day(16), to: day(18, 17), name: "Calendar sync" },
-];
+##### `departure`
 
-export default function NothingToFix() {
-  const found = findings(WORK, []);
-  const count = found.overlaps.length + found.violatedDependencies.length + found.inBlockedTime.length;
+When a dependency leaves its subtask, by its anchor.
 
-  return (
-    <Stack gap={3}>
-      <Schedule ariaLabel="Two developers' week, without findings" initialDomain={[day(16, 0), day(21, 0)]} height={140}>
-        <Lane id="hana" label="Hana Sato" />
-        <Lane id="kofi" label="Kofi Mensah" />
-        <Subtasks data={WORK} tasks={PROJECTS} />
-      </Schedule>
-      {count === 0 && <EmptyState title="Nothing to fix" description="Nobody is double-booked, every hand-over fits, and no work falls into leave." />}
-    </Stack>
-  );
-}
+```ts
+function departure(dependency: Dependency, from: Subtask): number;
 ```
 
-##### Count the findings per kind
+Used on [Findings as data](#/findings).
 
-`overlaps` and `violatedDependencies` are the halves of `findings` on their own - here as counts above the day's legs.
+##### `findings`
 
-```tsx
-import { Badge, Stack } from "@umriss-ui/core";
-import { Dependencies, Lane, Schedule, Subtasks, overlaps, violatedDependencies } from "@umriss-ui/schedule";
-import type { Dependency, Subtask, Task } from "@umriss-ui/schedule";
+Every finding at once. Without blocked time there is none in it.
 
-const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
-const min = (n: number) => n * 60_000;
+```ts
+function findings(subtasks: readonly Subtask[], dependencies: readonly Dependency[], blocked?: readonly BlockedTime[]): Findings;
+```
 
-const VEHICLES = [
-  { id: "van-402", label: "Van FP 402 R" },
-  { id: "truck-520", label: "Truck FP 520 E" },
-  { id: "van-455", label: "E-van FP 455 R" },
-];
+Used on [Scenarios](#/), [First schedule](#/schedule), [Lane groups](#/lane-groups), [Blocked time](#/blocked-time), [Tooltip](#/tooltip) and [Findings as data](#/findings).
 
-const CONSIGNMENTS: readonly Task[] = [
-  { id: "c-2041", name: "C-2041 Holloway Garden Supplies", color: "light-dark(#2563eb, #6b9bff)" },
-  { id: "c-2043", name: "C-2043 Oakridge Pharmacy", color: "light-dark(#c2410c, #f08a52)" },
-];
+##### `inBlockedTime`
 
-const LEGS: readonly Subtask[] = [
-  { id: "c-2041-2", task: "c-2041", lane: "van-402", from: at(8), to: at(10, 30), leadIn: min(30), leadOut: min(15) },
-  { id: "c-2043-1", task: "c-2043", lane: "truck-520", from: at(6, 30), to: at(8), leadIn: min(30), leadOut: min(15) },
-  { id: "c-2043-2", task: "c-2043", lane: "van-402", from: at(10), to: at(11, 30), leadIn: min(15) },
-  { id: "c-2043-3", task: "c-2043", lane: "van-455", from: at(12), to: at(14), leadIn: min(20), leadOut: min(20) },
-];
+Every subtask that covers blocked time on its lane, lead-in and lead-out
+included - once per blocked interval it covers, in the order of the
+subtasks. Touching at a shared edge is not covering.
 
-const TRANSFERS: readonly Dependency[] = [
-  { id: "t-2043-1", from: "c-2043-1", to: "c-2043-2", lag: min(45) },
-  { id: "t-2043-2", from: "c-2043-2", to: "c-2043-3", lag: min(25) },
-];
+```ts
+function inBlockedTime(subtasks: readonly Subtask[], blocked: readonly BlockedTime[]): InBlockedTime[];
+```
 
-export default function CountPerKind() {
-  const doubleBooked = overlaps(LEGS).length;
-  const late = violatedDependencies(LEGS, TRANSFERS).length;
+Used on [Scenarios](#/), [Blocked time](#/blocked-time) and [Findings as data](#/findings).
 
-  return (
-    <Stack gap={3}>
-      <Stack direction="row" gap={2}>
-        <Badge tone={doubleBooked > 0 ? "warning" : "success"}>{doubleBooked} double-booked</Badge>
-        <Badge tone={late > 0 ? "warning" : "success"}>{late} transfers too short</Badge>
-      </Stack>
-      <Schedule ariaLabel="The day's legs with their findings counted" initialDomain={[at(5, 30), at(18)]} height={196}>
-        {VEHICLES.map((vehicle) => (
-          <Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
-        ))}
-        <Dependencies data={TRANSFERS} />
-        <Subtasks data={LEGS} tasks={CONSIGNMENTS} />
-      </Schedule>
-    </Stack>
-  );
-}
+##### `occupied`
+
+The interval a subtask occupies on its lane: lead-in and lead-out included.
+
+```ts
+function occupied(subtask: Subtask): {
+    from: number;
+    to: number;
+};
 ```
 
-#### API
+##### `overlaps`
 
-##### `Overlap`
+Every pair of subtasks that cover each other on a lane. Touching at a
+shared edge is not covering, and a subtask that covers no time covers
+nothing.
 
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `lane` (required) | `string` | — | The lane both sit on. |
-| `first` (required) | `string` | — | The subtask that starts earlier (lead-in included); on a tie, the one that stands first in the data. |
-| `second` (required) | `string` | — | The other one. |
-| `from` (required) | `number` | — | Where the covering begins. |
-| `to` (required) | `number` | — | Where it ends. |
+```ts
+function overlaps(subtasks: readonly Subtask[]): Overlap[];
+```
 
-##### `ViolatedDependency`
+Used on [Scenarios](#/), [Lane groups](#/lane-groups), [Findings as data](#/findings) and [Move and lane](#/move-and-lane).
 
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `dependency` (required) | `string` | — | The id of the dependency. |
-| `departure` (required) | `number` | — | When it leaves, by its anchor. |
-| `arrival` (required) | `number` | — | When it has to have arrived, by its anchor. |
-| `shortBy` (required) | `number` | — | How much time is missing: departure plus lag, minus arrival. |
+##### `resolveAppearance`
 
-##### `InBlockedTime`
+Settles a subtask's appearances into what is drawn. `provisional` and
+`fixed` contradict each other; the later one in the list wins.
 
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `subtask` (required) | `string` | — | The id of the subtask. |
-| `blocked` (required) | `string` | — | The id of the blocked time it covers. |
-| `lane` (required) | `string` | — | The lane both are on. |
-| `from` (required) | `number` | — | Where the covering begins. |
-| `to` (required) | `number` | — | Where it ends. |
+- `appearance` – The subtask's `appearance`, in the order it was given.
+- Returns Which of the four channels are on.
 
-#### Known limits
+```ts
+function resolveAppearance(appearance: readonly SubtaskAppearance[] | undefined): ResolvedAppearance;
+```
 
-- Overlapping work is marked, not packed into sub-lanes; stacked overlap is not built yet.
+Used on [Appearances](#/appearances).
+
+##### `ripple`
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0032-what-umriss-is-not.md).
+The moves that push every successor whose dependency no longer fits after
+`intent` - transitively, in the order they were first pushed. The subtask the
+intent is about is never moved, and a cycle among the successors ends after a
+bounded number of pushes instead of running on.
 
-## The rest of the API
+```ts
+function ripple(subtasks: readonly Subtask[], dependencies: readonly Dependency[], intent: Intent): MoveIntent[];
+```
 
-Exported as well, and named on no page above: the pure modules behind the components, and the types they are made of. Each with its declaration as the package's `.d.ts` carries it.
+Used on [Scenarios](#/), [Dependencies](#/dependencies) and [Ripple](#/ripple).
 
-### `occupied`
+##### `shiftTask`
+
+The moves that carry a whole task in time - every subtask of it by the same
+amount, so that its lengths and the distances between its stops stay as
+they were. The schedule never runs it: apply the moves like any other
+intent, or run [`ripple`](#/api/ripple) over them first.
+
+- `subtasks` – All subtasks; only those of `task` are moved.
+- `task` – The id of the task, as its subtasks name it in `task`.
+- `by` – How far, in milliseconds; negative is earlier.
+- Returns One move intent per subtask of the task - none where `by` is zero
+or not finite.
 
 ```ts
-/** The interval a subtask occupies on its lane: lead-in and lead-out included. */
-function occupied(subtask: Subtask): {
-    from: number;
-    to: number;
-};
+function shiftTask(subtasks: readonly Subtask[], task: string, by: number): MoveIntent[];
 ```
 
-### `LaneIntent`
+Used on [Scenarios](#/) and [Ripple](#/ripple).
+
+##### `snapTime`
+
+`time` onto the nearest line of the raster in local time - a step alone
+starts at local midnight. A step of zero or less is no raster: the time
+stays as it is.
 
 ```ts
-/** Put the subtask on another lane. */
-interface LaneIntent {
-    readonly kind: "lane";
-    /** The id of the subtask. */
-    readonly subtask: string;
-    /** The id of the new lane. */
-    readonly lane: string;
-}
+function snapTime(time: number, raster: number | SnapRaster): number;
 ```
 
-### `LeadInIntent`
+Used on [Snapping](#/snapping).
+
+##### `subtaskFromPlace`
+
+The subtask a place intent asks for, under an id the caller chooses.
 
 ```ts
-/** Change the lead-in on its own. */
-interface LeadInIntent {
-    readonly kind: "leadIn";
-    /** The id of the subtask. */
-    readonly subtask: string;
-    /** The new duration of the lead-in. */
-    readonly leadIn: number;
-}
+function subtaskFromPlace(intent: PlaceIntent, id: string): Subtask;
 ```
 
-### `StretchIntent`
+Used on [Placing from outside](#/placing) and [Where a subtask may go](#/where-it-may-go).
+
+##### `violatedDependencies`
+
+Every dependency whose successor is to be reached before the predecessor's
+departure plus the dependency's lag. A dependency naming a subtask that
+is not in the data is passed over: there is nothing to judge.
 
 ```ts
-/** Stretch the main time at one or both of its edges. */
-interface StretchIntent {
-    readonly kind: "stretch";
-    /** The id of the subtask. */
-    readonly subtask: string;
-    /** The new start of the main time. */
-    readonly from: number;
-    /** The new end of the main time. */
-    readonly to: number;
-}
+function violatedDependencies(subtasks: readonly Subtask[], dependencies: readonly Dependency[]): ViolatedDependency[];
 ```
 
-### `LeadOutIntent`
+Used on [Scenarios](#/), [Lane groups](#/lane-groups), [Tooltip](#/tooltip) and [Findings as data](#/findings).
+
+#### Types
+
+##### `BlockedTime`
+
+Its table stands on [Blocked time](#/blocked-time/type-BlockedTime).
+
+Used on [Scenarios](#/), [Blocked time](#/blocked-time), [Tooltip](#/tooltip), [Findings as data](#/findings) and [Where a subtask may go](#/where-it-may-go).
+
+##### `BlockedTimesProps`
+
+Its table stands on [Blocked time](#/blocked-time/type-BlockedTimesProps).
+
+##### `DependenciesProps`
+
+Its table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+
+##### `Dependency`
+
+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).
+
+##### `DependencyAttachment`
+
+Where on its bars a dependency's line attaches: the middle of both, or the
+edge that faces the other stop - which is the shortest line between them.
+
+Deliberately not called an anchor: a dependency already HAS two anchors
+(`leaves`, `arrives`), and those decide what it connects and therefore
+whether it is violated. This decides where the line touches, and nothing else.
+The tree has an **Anchor** of its own as well (CONTEXT.md).
 
 ```ts
-/** Change the lead-out on its own. */
-interface LeadOutIntent {
-    readonly kind: "leadOut";
-    /** The id of the subtask. */
-    readonly subtask: string;
-    /** The new duration of the lead-out. */
-    readonly leadOut: number;
-}
+type DependencyAttachment = "centre" | "nearest";
 ```
 
-### `Findings`
+Used on [Dependencies](#/dependencies).
+
+##### `DependencyEnds`
+
+Whether a dependency's two ends carry a dot. The dot says where the line is
+anchored, which is worth saying while a plan is being read and is noise in a
+plan full of short moves - so it is the caller's choice.
 
 ```ts
-/** Every kind of finding over the same data. */
-interface Findings {
-    readonly overlaps: readonly Overlap[];
-    readonly violatedDependencies: readonly ViolatedDependency[];
-    readonly inBlockedTime: readonly InBlockedTime[];
-}
+type DependencyEnds = "dot" | "none";
 ```
 
-### `PlaceIntent`
+Used on [Dependencies](#/dependencies).
+
+##### `DependencyRoute`
+
+How a dependency is drawn between its two ends: a curve that leaves and
+arrives forwards, a straight line, or axis-parallel segments.
 
 ```ts
-/** 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
-    no subtask yet; the caller creates one, with its own identity, from
-    `subtaskFromPlace`. */
-interface PlaceIntent {
-    readonly kind: "place";
-    /** The caller's key for the dragged item, as it declared it while dragging. */
-    readonly item: string;
-    /** The task the work belongs to. */
-    readonly task: string;
-    /** The lane it was dropped on. */
-    readonly lane: string;
-    /** Where its main time would start. */
-    readonly from: number;
-    /** Where its main time would end. */
-    readonly to: number;
-    /** The lead-in it was declared with. */
-    readonly leadIn?: number;
-    /** The lead-out it was declared with. */
-    readonly leadOut?: number;
-}
+type DependencyRoute = "curve" | "straight" | "orthogonal";
+```
+
+##### `Findings`
+
+Every kind of finding over the same data.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `overlaps` *required* | `readonly `[`Overlap`](#/findings/type-Overlap)`[]` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [List the findings (Findings as data)](#/findings/list-the-findings), [Say when there is nothing to fix (Findings as data)](#/findings/nothing-to-fix) and 1 more |
+| `violatedDependencies` *required* | `readonly `[`ViolatedDependency`](#/findings/type-ViolatedDependency)`[]` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [List the findings (Findings as data)](#/findings/list-the-findings), [Say when there is nothing to fix (Findings as data)](#/findings/nothing-to-fix) and 1 more |
+| `inBlockedTime` *required* | `readonly `[`InBlockedTime`](#/findings/type-InBlockedTime)`[]` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Check a sprint against the leave calendar (Blocked time)](#/blocked-time/team-leave), [List the findings (Findings as data)](#/findings/list-the-findings) and 3 more |
+
+##### `InBlockedTime`
+
+Its table stands on [Findings as data](#/findings/type-InBlockedTime).
+
+##### `Intent`
+
+What the schedule reports when an interaction asks for a change. Every
+intent carries the values it asks for, not a difference: two intents of one
+drop - a move and a lane - give the same data in either order.
+
+```ts
+type Intent = MoveIntent | StretchIntent | LeadInIntent | LeadOutIntent | LaneIntent | PlaceIntent;
 ```
 
-### `ResolvedAppearance`
+Used on [Scenarios](#/), [Blocked time](#/blocked-time), [Move and lane](#/move-and-lane), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go) and [Ripple](#/ripple).
+
+##### `IntentKind`
+
+The names of the intents - the editing API of the schedule.
 
 ```ts
-/** 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 (`sceneDraw.ts`, "ONE CHANNEL PER
-    STATEMENT"). */
-interface ResolvedAppearance {
-    /** `provisional`: the FILL - none at all, so the surface shows through, with
-        a dashed outline in the task colour. Planned, not released. */
-    readonly dashed: 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. */
-    readonly hatched: boolean;
-    /** `muted`: the SATURATION - the task colour mixed half into the surface,
-        opaque and at full height. Another team's, another crew's. */
-    readonly muted: boolean;
-    /** `open`: the FADE, where the bar passes the edge of the view. It goes on
-        past what is drawn. */
-    readonly open: boolean;
-}
+type IntentKind = Intent["kind"];
+```
+
+##### `LaneGroupProps`
+
+Its table stands on [Lane groups](#/lane-groups/type-LaneGroupProps).
+
+##### `LaneIntent`
+
+Put the subtask on another lane.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"lane"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `lane` *required* | `string` | — | The id of the new lane. |
+
+##### `LaneProps`
+
+Its table stands on [Lanes](#/lane/type-LaneProps).
+
+##### `LeadInIntent`
+
+Change the lead-in on its own.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"leadIn"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `leadIn` *required* | `number` | — | The new duration of the lead-in.<br>Shown in: [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+
+##### `LeadOutIntent`
+
+Change the lead-out on its own.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"leadOut"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `leadOut` *required* | `number` | — | The new duration of the lead-out. |
+
+##### `MoveIntent`
+
+Move the subtask in time: the main time keeps its length.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"move"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 8 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 5 more |
+| `from` *required* | `number` | — | The new start of the main time.<br>Shown in: [Push the later stops of a tour (Ripple)](#/ripple/push-the-later-stops), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+| `to` *required* | `number` | — | The new end of the main time.<br>Shown in: [Push the later stops of a tour (Ripple)](#/ripple/push-the-later-stops), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+
+Used on [Ripple](#/ripple).
+
+##### `Overlap`
+
+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
+no subtask yet; the caller creates one, with its own identity, from
+`subtaskFromPlace`.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"place"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `item` *required* | `string` | — | The caller's key for the dragged item, as it declared it while dragging.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
+| `task` *required* | `string` | — | The task the work belongs to. |
+| `lane` *required* | `string` | — | The lane it was dropped on.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `from` *required* | `number` | — | Where its main time would start. |
+| `to` *required* | `number` | — | Where its main time would end. |
+| `leadIn` | `number` | — | The lead-in it was declared with. |
+| `leadOut` | `number` | — | The lead-out it was declared with. |
+
+##### `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.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `item` *required* | `string` | — | The caller's key for the dragged item; it comes back in the intent.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `task` *required* | `string` | — | The task the work belongs to.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `duration` *required* | `number` | — | How long its main time is.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#/placing/drag-from-the-backlog), [Apply the same rule to work dragged in (Where a subtask may go)](#/where-it-may-go/dragged-in) |
+| `leadIn` | `number` | — | The lead-in it brings. |
+| `leadOut` | `number` | — | The lead-out it brings. |
+
+Used on [Placing from outside](#/placing) and [Where a subtask may go](#/where-it-may-go).
+
+##### `ResolvedAppearance`
+
+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.
+
+| 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. |
+| `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. |
+
+##### `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. |
+
+Used on [The handle](#/handle).
+
+##### `ScheduleHit`
+
+What a pointer is on.
+
+```ts
+type ScheduleHit =
+  | { readonly kind: "subtask"; readonly subtask: Subtask; readonly part: "leadIn" | "main" | "leadOut" }
+  | { readonly kind: "dependency"; readonly dependency: Dependency }
+  | { readonly kind: "lane"; readonly lane: string }
+  | { readonly kind: "nothing" };
+```
+
+##### `ScheduleInteraction`
+
+Its table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+
+Used on [Scenarios](#/), [Interactions](#/interactions) and [Tooltip](#/tooltip).
+
+##### `ScheduleProps`
+
+Its table stands on [First schedule](#/schedule/type-ScheduleProps).
+
+##### `ScheduleTooltipTarget`
+
+Its table stands on [Tooltip](#/tooltip/type-ScheduleTooltipTarget).
+
+Used on [Tooltip](#/tooltip).
+
+##### `SnapRaster`
+
+A raster: a step, and where it starts after local midnight.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `step` *required* | `number` | — | The distance between two lines of the raster, in milliseconds.<br>Shown in: [Snap to handover times (Snapping)](#/snapping/snap-to-handovers) |
+| `offset` *required* | `number` | — | Where the raster starts after local midnight, in milliseconds: six hours for handovers at 06:00, 14:00 and 22:00.<br>Shown in: [Snap to handover times (Snapping)](#/snapping/snap-to-handovers) |
+
+Used on [Snapping](#/snapping).
+
+##### `StretchIntent`
+
+Stretch the main time at one or both of its edges.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `kind` *required* | `"stretch"` | — | <br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Refuse a move that double-books someone (Move and lane)](#/move-and-lane/refuse-a-double-booking) and 4 more |
+| `from` *required* | `number` | — | The new start of the main time. |
+| `to` *required* | `number` | — | The new end of the main time. |
+
+##### `Subtask`
+
+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), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [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).
+
+##### `SubtaskAppearance`
+
+The appearances a caller may give a subtask.
+
+```ts
+type SubtaskAppearance = "provisional" | "fixed" | "muted" | "open";
 ```
+
+##### `SubtasksProps`
+
+Its table stands on [Subtasks](#/subtasks/type-SubtasksProps).
+
+##### `Task`
+
+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), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [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).
+
+##### `ViolatedDependency`
+
+Its table stands on [Findings as data](#/findings/type-ViolatedDependency).
+
+Used on [Dependencies](#/dependencies).
+
+##### `ZoomLimits`
+
+The narrowest and the widest span zoom may reach.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `min` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |
+| `max` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |