npm - @umriss-ui/schedule - Versions diffs - 0.41.0 → 0.42.0 - Mend

@umriss-ui/schedule 0.41.0 → 0.42.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (5) hide show

package/docs/llms-full.md CHANGED Viewed

@@ -1,8 +1,8 @@
-# @umriss-ui/schedule 0.41.0
+# @umriss-ui/schedule 0.42.0
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
-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.
+Install with `npm install @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts`. This text is generated from the package's demo: 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.
 ## Scenarios
@@ -913,13 +913,11 @@ import { useSchedule } from "@umriss-ui/schedule";
 npm install @umriss-ui/schedule @umriss-ui/core @umriss-ui/charts
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/installation/
 The command brings its two peers along: core for the formats and the wording, charts for the time scale and the operating calendar ([ADR-0022](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0022-the-schedule-is-a-package-that-depends-on-core-and-charts.md)). React 19 or newer is a peer as well and stays the application's own. The stylesheets load themselves - each package's script imports its own, so there is nothing to import by hand; `@umriss-ui/schedule/styles.css` stays exported for setups that link stylesheets themselves.
 The plan is plain data ([ADR-0023](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0023-editing-is-controlled-the-schedule-reports-intents.md)). A lane is a person, a vehicle or a room, declared in JSX by its id. A task is an id, a colour and a name; a subtask is a main time on one lane, belonging to a task, with an optional lead-in and lead-out; a dependency joins two subtasks of one task with a lag. Times are epoch milliseconds.
-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).
+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).
 #### Examples
@@ -958,83 +956,83 @@ export default function SmallestSchedule() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`children`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### First schedule
@@ -1044,11 +1042,9 @@ Work on lanes over time, with a day band above and time ticks that follow the zo
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/schedule/
 Lanes stand in the order they are declared; a subtask on a lane that is not declared is not drawn. Declare `Dependencies` before `Subtasks` and its lines run beneath the bars.
-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.
+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-as-data) 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](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)).
@@ -1268,7 +1264,7 @@ export default function MachinePlan() {
 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".
+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-as-data) 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.
@@ -1278,38 +1274,38 @@ Under forced colours the plot paints itself in the system colours: the work in t
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ref` | `Ref<`[`ScheduleHandle`](#type-ScheduleHandle)`>` | — | Receives the `ScheduleHandle` - not an element.<br>Shown in: [Place a mark of your own (The handle)](#/handle/place-a-mark) |
-| `height` | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
-| `laneHeight` | `number` | `44` | Height of one lane in pixels at the default font size of 16 px; the schedule multiplies it by the root font size over 16 px when that ratio is above 1, so lane names keep their room in a reader's larger font.<br>Shown in: [Scroll more lanes than fit (Lanes)](#/lane/many-lanes), [Measure a plan (Benchmark)](#/benchmark/benchmark) |
-| `headerWidth` | `number` | `160` | Width of the lane headers in pixels - at most 40 % of the schedule, so that on a phone the plot keeps the larger part.<br>Shown in: [What a lane header says (Lanes)](#/lane/lane-headers), [Scroll more lanes than fit (Lanes)](#/lane/many-lanes), [Group lanes under a head (Lane groups)](#/lane-groups/a-group) and 1 more |
-| `calendar` | [`CalendarInput`](#type-CalendarInput) | `[]` | A working calendar: the intervals in which time counts. Nights and weekends outside them are cut out of the axis. Without intervals every hour counts, as on the wall clock.<br>Shown in: [Cut the nights out of the axis (Time axis and calendar)](#/time-axis/working-calendar), [Plan in office hours only (Time axis and calendar)](#/time-axis/office-hours), [Plan the sprint around leave (Scenarios)](#/scenarios/plan-the-sprint-around-leave) |
-| `zoomLimits` | [`ZoomLimits`](#type-ZoomLimits) | one hour to 28 days | The narrowest and widest time span zoom may reach, in milliseconds.<br>Shown in: [Move through the plan (Pan and zoom)](#/pan-and-zoom/pan-and-zoom) |
-| `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) |
-| `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: [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is), [Write your own tooltip content (Tooltip)](#/tooltip/own-tooltip), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 1 more |
-| `now` | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there.<br>Shown in: [Plan a day in the machine shop](#/schedule/machine-plan), [Mark the present (Now line)](#/now-line/now-line), [Follow the clock (Now line)](#/now-line/follow-the-clock) and 2 more |
-| `children` | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn.<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
+| `ref` | `Ref<``ScheduleHandle``>` | — | Receives the `ScheduleHandle` - not an element.<br>Shown in: [Place a mark of your own (The handle)](#the-handle) |
+| `height` | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's.<br>Shown in: [A day of tours](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 78 more |
+| `laneHeight` | `number` | `44` | Height of one lane in pixels at the default font size of 16 px; the schedule multiplies it by the root font size over 16 px when that ratio is above 1, so lane names keep their room in a reader's larger font.<br>Shown in: [Scroll more lanes than fit (Lanes)](#lanes), [Measure a plan (Benchmark)](#benchmark) |
+| `headerWidth` | `number` | `160` | Width of the lane headers in pixels - at most 40 % of the schedule, so that on a phone the plot keeps the larger part.<br>Shown in: [What a lane header says (Lanes)](#lanes), [Scroll more lanes than fit (Lanes)](#lanes), [Group lanes under a head (Lane groups)](#lane-groups) and 1 more |
+| `calendar` | `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-and-calendar), [Plan in office hours only (Time axis and calendar)](#time-axis-and-calendar), [Plan the sprint around leave (Scenarios)](#plan-the-sprint-around-leave) |
+| `zoomLimits` | `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) |
+| `snap` | `"ticks" \| number \| ``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 handover times (Snapping)](#snapping), [Place without snapping (Snapping)](#snapping) |
+| `intents` | `readonly ``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), [Cut the nights out of the axis (Time axis and calendar)](#time-axis-and-calendar), [Plan work around someone's leave (Blocked time)](#blocked-time) and 18 more |
+| `canMoveTo` | `(subtask: `[`Subtask`](#subtasks)`, 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-a-subtask-may-go), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go), [Keep work out of someone's leave (Where a subtask may go)](#where-a-subtask-may-go) 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) |
+| `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) |
+| `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.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
+| `route` | `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), [Orthogonal (Routes)](#routes), [Per dependency (Routes)](#routes) |
+| `attach` | `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), [Mark the ends with a dot (Dependencies)](#dependencies), [Draw one handover its own way (Dependencies)](#dependencies) and 3 more |
+| `ends` | `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), [Draw one handover its own way (Dependencies)](#dependencies) |
+| `label` | `(subtask: `[`Subtask`](#subtasks)`) => 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](#first-schedule), [Plan a sprint for a team (Subtasks)](#subtasks), [Write into the bars (Bar labels)](#bar-labels) and 7 more |
+| `tooltip` | `false \| ((target: `[`ScheduleTooltipTarget`](#tooltip)`) => ReactNode)` | — | The tooltip on a hovered subtask or dependency: its order, its times, its parts and its findings. `false` switches it off; a function receives what the pointer rests on and returns content of the application's own.<br>Shown in: [Say what a milestone is in your own tooltip (Milestones)](#milestones), [Write your own tooltip content (Tooltip)](#tooltip), [Show a detail panel instead (Tooltip)](#tooltip) and 1 more |
+| `now` | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there.<br>Shown in: [Plan a day in the machine shop](#first-schedule), [Mark the present (Now line)](#now-line), [Follow the clock (Now line)](#now-line) 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](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 78 more |
 ###### Events
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `onIntent` | `(intent: `[`Intent`](#type-Intent)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it.<br>Shown in: [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Cut the nights out of the axis (Time axis and calendar)](#/time-axis/working-calendar), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around) and 18 more |
-| `onInteraction` | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu.<br>Shown in: [Report what the pointer is on (Interactions)](#/interactions/report-the-pointer), [Open a context menu (Interactions)](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 3 more |
+| `onIntent` | `(intent: ``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), [Cut the nights out of the axis (Time axis and calendar)](#time-axis-and-calendar), [Plan work around someone's leave (Blocked time)](#blocked-time) and 18 more |
+| `onInteraction` | `(interaction: `[`ScheduleInteraction`](#interactions)`) => 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), [Open a context menu (Interactions)](#interactions), [Show a detail panel instead (Tooltip)](#tooltip) and 3 more |
 ###### Accessibility
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ariaLabel` *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38".<br>Shown in: [A day of tours](#/schedule/first-schedule), [Start from an empty plan](#/schedule/no-work-yet), [Plan a day in the machine shop](#/schedule/machine-plan) and 78 more |
+| `ariaLabel` *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38".<br>Shown in: [A day of tours](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 78 more |
 ###### Styling
@@ -1327,8 +1323,8 @@ 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) |
+| `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)](#the-handle) |
+| `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)](#the-handle) |
 | `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
 ###### `CalendarInput`
@@ -1348,8 +1344,8 @@ 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) |
+| `min` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#pan-and-zoom) |
+| `max` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#pan-and-zoom) |
 ###### `SnapRaster`
@@ -1357,8 +1353,8 @@ 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) |
+| `step` *required* | `number` | — | The distance between two lines of the raster, in milliseconds.<br>Shown in: [Snap to handover times (Snapping)](#snapping) |
+| `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) |
 ###### `IntentKind`
@@ -1376,9 +1372,9 @@ 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) |
+| `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-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
+| `task` *required* | `string` | — | The task the work belongs to.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
+| `duration` *required* | `number` | — | How long its main time is.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
 | `leadIn` | `number` | — | The lead-in it brings. |
 | `leadOut` | `number` | — | The lead-out it brings. |
@@ -1439,7 +1435,7 @@ thing about the frame.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `intervals` *required* | `readonly `[`WorkingInterval`](#type-WorkingInterval)`[]` | — |  |
+| `intervals` *required* | `readonly ``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]. |
@@ -1461,10 +1457,10 @@ 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) |
+| `kind` *required* | `"move"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 8 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) 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), [Replan the day on the line (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), [Replan the day on the line (Scenarios)](#replan-the-day-on-the-line) |
 ###### `StretchIntent`
@@ -1472,8 +1468,8 @@ 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 |
+| `kind` *required* | `"stretch"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
 | `from` *required* | `number` | — | The new start of the main time. |
 | `to` *required* | `number` | — | The new end of the main time. |
@@ -1483,9 +1479,9 @@ 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) |
+| `kind` *required* | `"leadIn"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
+| `leadIn` *required* | `number` | — | The new duration of the lead-in.<br>Shown in: [Replan the day on the line (Scenarios)](#replan-the-day-on-the-line) |
 ###### `LeadOutIntent`
@@ -1493,8 +1489,8 @@ 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 |
+| `kind` *required* | `"leadOut"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
 | `leadOut` *required* | `number` | — | The new duration of the lead-out. |
 ###### `LaneIntent`
@@ -1503,8 +1499,8 @@ 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 |
+| `kind` *required* | `"lane"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
 | `lane` *required* | `string` | — | The id of the new lane. |
 ###### `PlaceIntent`
@@ -1516,10 +1512,10 @@ no subtask yet; the caller creates one, with its own identity, from
 | 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) |
+| `kind` *required* | `"place"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) 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-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go), [Replan the day on the line (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) |
+| `lane` *required* | `string` | — | The lane it was dropped on.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
 | `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. |
@@ -1527,11 +1523,11 @@ no subtask yet; the caller creates one, with its own identity, from
 #### 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](https://romanhaendler.github.io/umriss-ui/what-umriss-ui-is-not/)).
+- 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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
 - 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://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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ## Plan
@@ -1545,11 +1541,9 @@ One row per person, vehicle or room, named by its header and kept in the order i
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/lane/
 A lane is declared by its id, the one subtasks name, and a label. The label is content, not a string: a name with a plate number, a status beside it. It is real text, read by a screen reader, and it stays at the left edge while the plot pans.
-A lane keeps its height whatever lies on it. Nothing is moved to another lane to make room: two subtasks on one lane at once are a finding (see [Overlap](#/overlap)).
+A lane keeps its height whatever lies on it. Nothing is moved to another lane to make room: two subtasks on one lane at once are a finding (see [Overlap](#overlap)).
 #### Examples
@@ -1658,7 +1652,7 @@ export default function ManyLanes() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -1666,8 +1660,8 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The identity subtasks name in their `lane`.<br>Shown in: [What a lane header says](#/lane/lane-headers), [Scroll more lanes than fit](#/lane/many-lanes), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 78 more |
-| `label` | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader.<br>Shown in: [What a lane header says](#/lane/lane-headers), [Scroll more lanes than fit](#/lane/many-lanes), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 77 more |
+| `id` *required* | `string` | — | The identity subtasks name in their `lane`.<br>Shown in: [What a lane header says](#lanes), [Scroll more lanes than fit](#lanes), [The smallest schedule (Installation)](#installation) and 78 more |
+| `label` | `ReactNode` | `id` | What the lane header says - the person, vehicle or room. Real text, read by a screen reader.<br>Shown in: [What a lane header says](#lanes), [Scroll more lanes than fit](#lanes), [The smallest schedule (Installation)](#installation) and 77 more |
 ### Lane groups
@@ -1677,13 +1671,11 @@ Teams, depots or regions over the lanes, to any depth, folded into one row when
 import { useSchedule } 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](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.
-Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold the planner makes - see [View](#/view).
+Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold the planner makes - see [View](#view).
 #### Examples
@@ -1961,7 +1953,7 @@ export default function StartWithGroupsFolded() {
 | `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.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -1969,15 +1961,15 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The group's identity - what the view's `folded` 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/fold-from-outside) and 5 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/fold-from-outside) and 5 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/fold-from-outside) and 5 more |
+| `id` *required* | `string` | — | The group's identity - what the view's `folded` 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), [Nest groups to any depth](#lane-groups), [Fold groups from outside](#lane-groups) and 5 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), [Nest groups to any depth](#lane-groups), [Fold groups from outside](#lane-groups) and 5 more |
+| `children` | `ReactNode` | — | `Lane`s and further `LaneGroup`s, to any depth.<br>Shown in: [Group lanes under a head](#lane-groups), [Nest groups to any depth](#lane-groups), [Fold groups from outside](#lane-groups) and 5 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](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://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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Subtasks
@@ -1987,8 +1979,6 @@ The bars: a main time with an optional lead-in before it and lead-out after it,
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/subtasks/
 Lead-in and lead-out are durations beside the main time, not times of their own: moving the subtask takes them along. They are drawn faint in the task's colour, so preparation reads as belonging to the work and as not being it, and they occupy the lane as the main time does.
 #### Examples
@@ -2171,7 +2161,7 @@ export default function ASprint() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -2179,31 +2169,31 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` *required* | `readonly `[`Subtask`](#type-Subtask)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 78 more |
-| `tasks` *required* | `readonly `[`Task`](#type-Task)`[]` | — | The tasks the subtasks belong to - their identity and their colour. A subtask whose task is not among them is drawn in a muted colour.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 78 more |
+| `data` *required* | `readonly ``Subtask``[]` | — | The subtasks, as the caller holds them. The schedule never changes one.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [Plan a sprint for a team](#subtasks) and 78 more |
+| `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.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [Plan a sprint for a team](#subtasks) and 78 more |
 ##### `Subtask`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the subtask.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [Plan a sprint for a team](#/subtasks/a-sprint) and 75 more |
-| `task` *required* | `string` | — | The id of the task it belongs to.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
-| `lane` *required* | `string` | — | The id of the lane it sits on.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
-| `from` *required* | `number` | — | Start of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
-| `to` *required* | `number` | — | End of the main time.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 71 more |
-| `leadIn` | `number` | — | Duration of the lead-in before the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 25 more |
-| `leadOut` | `number` | — | Duration of the lead-out after the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 22 more |
-| `name` | `string` | — | What the subtask is called, where the schedule names it.<br>Shown in: [Plan a sprint for a team](#/subtasks/a-sprint), [Write into the bars (Bar labels)](#/bar-labels/bar-labels), [Join the stops of a tour (Dependencies)](#/dependencies/stops-of-a-tour) and 28 more |
-| `appearance` | `readonly `[`SubtaskAppearance`](#type-SubtaskAppearance)`[]` | — | What the bar says besides its colour: `"provisional"`, `"fixed"`, `"muted"`, `"open"`. Several hold at once; `"provisional"` and `"fixed"` contradict, and the later one in the list wins.<br>Shown in: [Plan a sprint for a team](#/subtasks/a-sprint), [Provisional (Appearances)](#/appearances/provisional), [Fixed (Appearances)](#/appearances/fixed) and 3 more |
-| `progress` | `number` | — | The share of the work that is done, from 0 to 1, drawn as a filled part of the bar. Without it nothing is claimed - an empty bar and a bar at zero per cent are two different statements.<br>Shown in: [Progress (Appearances)](#/appearances/progress), [Several at once (Appearances)](#/appearances/combinations) |
+| `id` *required* | `string` | — | The caller's identity of the subtask.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [Plan a sprint for a team](#subtasks) and 75 more |
+| `task` *required* | `string` | — | The id of the task it belongs to.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 71 more |
+| `lane` *required* | `string` | — | The id of the lane it sits on.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 71 more |
+| `from` *required* | `number` | — | Start of the main time.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 71 more |
+| `to` *required* | `number` | — | End of the main time.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 71 more |
+| `leadIn` | `number` | — | Duration of the lead-in before the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule) and 25 more |
+| `leadOut` | `number` | — | Duration of the lead-out after the main time; none is zero.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule) and 22 more |
+| `name` | `string` | — | What the subtask is called, where the schedule names it.<br>Shown in: [Plan a sprint for a team](#subtasks), [Write into the bars (Bar labels)](#bar-labels), [Join the stops of a tour (Dependencies)](#dependencies) and 28 more |
+| `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.<br>Shown in: [Plan a sprint for a team](#subtasks), [Provisional (Appearances)](#appearances), [Fixed (Appearances)](#appearances) 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), [Several at once (Appearances)](#appearances) |
 ##### `Task`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the task.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
-| `color` *required* | `string` | — | Any CSS colour - a literal, a token, `light-dark(…)`. The colour means what the caller's domain needs it to mean.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
-| `name` | `string` | — | What the task is called, where the schedule names it.<br>Shown in: [Main time, lead-in and lead-out](#/subtasks/lead-in-and-lead-out), [Colour by what the task means](#/subtasks/task-colours), [The smallest schedule (Installation)](#/installation/smallest-schedule) and 70 more |
+| `id` *required* | `string` | — | The caller's identity of the task.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 70 more |
+| `color` *required* | `string` | — | Any CSS colour - a literal, a token, `light-dark(…)`. The colour means what the caller's domain needs it to mean.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 70 more |
+| `name` | `string` | — | What the task is called, where the schedule names it.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [Colour by what the task means](#subtasks), [The smallest schedule (Installation)](#installation) and 70 more |
 ##### Types on this page
@@ -2223,8 +2213,6 @@ A line of text inside each bar: cut off where the bar is too narrow, left out wh
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/bar-labels/
 The text lies on the main time, not on the lead-in. Its colour follows the bar: light text on a dark bar, dark text on a pale one, measured by contrast in either theme.
 #### Examples
@@ -2283,70 +2271,70 @@ export default function BarLabels() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`label`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`) => 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`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Appearances
@@ -2356,11 +2344,9 @@ What a bar says besides its colour: provisional, fixed, muted, running on past t
 import { useSchedule, resolveAppearance } from "@umriss-ui/schedule";
 ```
-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`](#/api/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-index-1) is that rule, exported for the application to read as well.
 #### Examples
@@ -2596,71 +2582,71 @@ export default function Combinations() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`label`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`) => 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`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`appearance`](#subtasks) | `readonly `[`SubtaskAppearance`](#subtasks)`[]` | — | 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) | `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).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Overlap
@@ -2670,8 +2656,6 @@ Two subtasks claiming one lane at the same time (also called a double booking or
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/overlap/
 The later bar is offset a few pixels and edged, and the shared time is marked across the lane. Lead-in and lead-out occupy the lane too, so a lead-out meeting the next lead-in is an overlap. The offset stops at three levels and never leaks into the lane below.
 #### Examples
@@ -2782,74 +2766,74 @@ export default function ThreeAtOnce() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`children`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### 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/).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Dependencies
@@ -2859,11 +2843,9 @@ Lines from one subtask's end to the next one's start within a task, with the lag
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/dependencies/
 `leaves` and `arrives` say what a dependency connects - the main time, or the outer edge of the lead-out and the lead-in - and so decide whether it is violated. `attach`, `ends` and `route` only change how the line is drawn.
-Nothing moves to make a dependency fit. [Ripple](#/ripple) computes the moves that would, for the application to run or not.
+Nothing moves to make a dependency fit. [Ripple](#ripple) computes the moves that would, for the application to run or not.
 #### Examples
@@ -3160,7 +3142,7 @@ export default function OneHandoverDrawnItsOwnWay() {
 | `] 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.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -3168,21 +3150,21 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` *required* | `readonly `[`Dependency`](#type-Dependency)`[]` | — | The dependencies, as the caller holds them.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 28 more |
+| `data` *required* | `readonly ``Dependency``[]` | — | The dependencies, as the caller holds them.<br>Shown in: [Join the stops of a tour](#dependencies), [Choose what a dependency connects](#dependencies), [Choose where a line touches its bars](#dependencies) and 28 more |
 ##### `Dependency`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the dependency.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
-| `from` *required* | `string` | — | The id of the subtask it leaves.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
-| `to` *required* | `string` | — | The id of the subtask it arrives at.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
-| `lag` *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends.<br>Shown in: [Join the stops of a tour](#/dependencies/stops-of-a-tour), [Choose what a dependency connects](#/dependencies/anchors), [Choose where a line touches its bars](#/dependencies/attach) and 27 more |
-| `leaves` | `"main" \| "leadOut"` | `"leadOut"` | Where it leaves: at the end of the main time, or after the lead-out. The predecessor counts as ended once its lead-out is.<br>Shown in: [Choose what a dependency connects](#/dependencies/anchors), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
-| `arrives` | `"main" \| "leadIn"` | `"leadIn"` | Where it arrives: at the start of the main time, or before the lead-in. The lag must have run out before the successor's lead-in begins.<br>Shown in: [Choose what a dependency connects](#/dependencies/anchors), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 1 more |
-| `route` | [`DependencyRoute`](#type-DependencyRoute)<br>`"curve" \| "straight" \| "orthogonal"` | — | How this one is drawn, where it is not drawn like the rest. It changes the picture and never the finding: whether a dependency is violated follows from `leaves` and `arrives` alone.<br>Shown in: [Per dependency (Routes)](#/routes/per-dependency) |
-| `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) |
+| `id` *required* | `string` | — | The caller's identity of the dependency.<br>Shown in: [Join the stops of a tour](#dependencies), [Choose what a dependency connects](#dependencies), [Choose where a line touches its bars](#dependencies) and 27 more |
+| `from` *required* | `string` | — | The id of the subtask it leaves.<br>Shown in: [Join the stops of a tour](#dependencies), [Choose what a dependency connects](#dependencies), [Choose where a line touches its bars](#dependencies) and 27 more |
+| `to` *required* | `string` | — | The id of the subtask it arrives at.<br>Shown in: [Join the stops of a tour](#dependencies), [Choose what a dependency connects](#dependencies), [Choose where a line touches its bars](#dependencies) and 27 more |
+| `lag` *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends.<br>Shown in: [Join the stops of a tour](#dependencies), [Choose what a dependency connects](#dependencies), [Choose where a line touches its bars](#dependencies) and 27 more |
+| `leaves` | `"main" \| "leadOut"` | `"leadOut"` | Where it leaves: at the end of the main time, or after the lead-out. The predecessor counts as ended once its lead-out is.<br>Shown in: [Choose what a dependency connects](#dependencies), [Plan a day in the machine shop (First schedule)](#first-schedule), [Replan the day on the line (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), [A day of tours (First schedule)](#first-schedule), [Plan a day in the machine shop (First schedule)](#first-schedule) and 1 more |
+| `route` | `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) |
+| `attach` | `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) |
+| `ends` | `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) |
 ##### Types on this page
@@ -3221,9 +3203,9 @@ type DependencyEnds = "dot" | "none";
 #### Known limits
-- 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/)).
+- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/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/).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Routes
@@ -3233,8 +3215,6 @@ The shape of a dependency's line: a curve that leaves and arrives forwards, a st
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/routes/
 #### Examples
 ##### Curve
@@ -3400,85 +3380,85 @@ export default function PerDependency() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`route`](#first-schedule) | [`DependencyRoute`](#first-schedule)<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`](#first-schedule) | [`DependencyAttachment`](#first-schedule)<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`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
+| [`route`](#dependencies) | [`DependencyRoute`](#dependencies)<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. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ## Time
@@ -3492,8 +3472,6 @@ A day band that names the days and a time band whose ticks follow the zoom, from
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/time-axis/
 The calendar is a list of intervals in which time counts, nothing more; deriving it from opening hours and holidays is the application's business. A dotted line marks each seam, and a drag that would end in removed time stops at the seam where time counts again.
 #### Examples
@@ -3735,93 +3713,93 @@ export default function OfficeHours() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`calendar`](#first-schedule) | [`CalendarInput`](#first-schedule) | `[]` | 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`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`) => 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Blocked time
@@ -3831,9 +3809,7 @@ Leave, maintenance and other time a lane is not available: hatched behind the wo
 import { useSchedule, 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`](#/api/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-index-1) 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.
@@ -3980,7 +3956,7 @@ export default function DragAround() {
 ##### Check a sprint against the leave calendar
-The team's holidays, sick days and training become `BlockedTimes`, and [`findings`](#/api/findings) confirms that no work item runs into one.
+The team's holidays, sick days and training become `BlockedTimes`, and [`findings`](#api-index-1) confirms that no work item runs into one.
 ```tsx
 import { Stack, Text } from "@umriss-ui/core";
@@ -4118,7 +4094,7 @@ export default function TeamLeave() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -4126,17 +4102,17 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `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.<br>Shown in: [Block out leave and maintenance](#blocked-time), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) and 5 more |
 ##### `BlockedTime`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `id` *required* | `string` | — | The caller's identity of the interval - what a finding names.<br>Shown in: [Block out leave and maintenance](#blocked-time), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) and 5 more |
+| `lane` *required* | `string` | — | The id of the lane it blocks.<br>Shown in: [Block out leave and maintenance](#blocked-time), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) and 5 more |
+| `from` *required* | `number` | — | Where it begins.<br>Shown in: [Block out leave and maintenance](#blocked-time), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) and 5 more |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [Block out leave and maintenance](#blocked-time), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) 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), [Plan work around someone's leave](#blocked-time), [Check a sprint against the leave calendar](#blocked-time) and 5 more |
 ### Milestones
@@ -4146,8 +4122,6 @@ A point in time on a lane - a handover, a release, a deadline - drawn as a diamo
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/milestones/
 A milestone is data beside the work: one list, each point naming its lane and the instant it stands at (`{ id, lane, at, label? }`). It has no duration, no task and no tone; it is not dragged and reports no intent, and work beside it is never a finding.
 The keys walk to it in time order among the subtasks of its lane, the tooltip names it by its label and time, and the live region reads its lane, label and time. It is named by its label, or its id without one.
@@ -4265,7 +4239,7 @@ export default function SayWhatAMilestoneIs() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -4273,16 +4247,16 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `data` *required* | `readonly `[`Milestone`](#type-Milestone)`[]` | — | The milestones of the lanes, as the caller holds them: one list, each naming its lane and the instant it stands at.<br>Shown in: [Mark a handover and a release](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip](#/milestones/say-what-a-milestone-is) |
+| `data` *required* | `readonly ``Milestone``[]` | — | The milestones of the lanes, as the caller holds them: one list, each naming its lane and the instant it stands at.<br>Shown in: [Mark a handover and a release](#milestones), [Say what a milestone is in your own tooltip](#milestones) |
 ##### `Milestone`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the milestone.<br>Shown in: [Mark a handover and a release](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip](#/milestones/say-what-a-milestone-is) |
-| `lane` *required* | `string` | — | The id of the lane it stands on.<br>Shown in: [Mark a handover and a release](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip](#/milestones/say-what-a-milestone-is) |
-| `at` *required* | `number` | — | The instant it stands at.<br>Shown in: [Mark a handover and a release](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip](#/milestones/say-what-a-milestone-is) |
-| `label` | `string` | — | What it is called, where the schedule names it; without it, its id.<br>Shown in: [Mark a handover and a release](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip](#/milestones/say-what-a-milestone-is) |
+| `id` *required* | `string` | — | The caller's identity of the milestone.<br>Shown in: [Mark a handover and a release](#milestones), [Say what a milestone is in your own tooltip](#milestones) |
+| `lane` *required* | `string` | — | The id of the lane it stands on.<br>Shown in: [Mark a handover and a release](#milestones), [Say what a milestone is in your own tooltip](#milestones) |
+| `at` *required* | `number` | — | The instant it stands at.<br>Shown in: [Mark a handover and a release](#milestones), [Say what a milestone is in your own tooltip](#milestones) |
+| `label` | `string` | — | What it is called, where the schedule names it; without it, its id.<br>Shown in: [Mark a handover and a release](#milestones), [Say what a milestone is in your own tooltip](#milestones) |
 ### Now line
@@ -4292,8 +4266,6 @@ A line across the lanes at the present moment, so that whatever should have happ
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/now-line/
 #### Examples
 ##### Mark the present
@@ -4502,68 +4474,68 @@ export default function FollowTheClock() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`now`](#first-schedule) | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there. |
+| [`children`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Pan and zoom
@@ -4573,11 +4545,9 @@ Moving through a plan with the gestures of any scrolling surface: drag, wheel, C
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-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.
-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)). The span is part of the schedule's view, which `onViewChange` reports at most once per frame - see [View](#/view) and [Linked schedules](#/linked-schedules).
+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)). The span is part of the schedule's view, which `onViewChange` reports at most once per frame - see [View](#view) and [Linked schedules](#linked-schedules).
 #### Examples
@@ -4637,69 +4607,69 @@ export default function PanAndZoom() {
 | `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.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`zoomLimits`](#first-schedule) | [`ZoomLimits`](#first-schedule) | one hour to 28 days | The narrowest and widest time span zoom may reach, in milliseconds. |
+| [`children`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ## Reading
@@ -4713,8 +4683,6 @@ A click on a bar selects its whole task on every lane, so a planner sees every p
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/selection/
 The schedule keeps the selection itself unless you pass `selectedTask`; then your state holds it and every change is reported. The report also names the subtask that was clicked, the one the editing grips belong to.
 Selection and hover are two different marks: the selected task is outlined, the one under the pointer washed, and both show at once.
@@ -4856,91 +4824,91 @@ export default function ControlTheSelection() {
 | `Enter or Space` | Selects the active subtask's task, as a click does. |
 | `Escape` | Lets go of the active subtask. |
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`selectedTask`](#first-schedule) | `string \| null` | — | The selected task, controlled. Leave it out and the schedule keeps the selection itself. |
+| [`onSelectedTaskChange`](#first-schedule) | `(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`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### 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/).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Interactions
@@ -4950,8 +4918,6 @@ Reports what the pointer does on the plan - hover, click, right-click - with wha
 import { useSchedule } 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.
@@ -5146,7 +5112,7 @@ export default function OpenAContextMenu() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -5154,12 +5120,12 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `type` *required* | `"click" \| "contextmenu" \| "hover"` | — | `"hover"` is reported when the target under the pointer changes, not on every movement.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer), [Open a context menu](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 1 more |
-| `hit` *required* | [`ScheduleHit`](#type-ScheduleHit) | — | What the pointer is on.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer), [Open a context menu](#/interactions/open-a-context-menu), [Show a detail panel instead (Tooltip)](#/tooltip/detail-panel-instead) and 2 more |
-| `clientX` *required* | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens.<br>Shown in: [Open a context menu](#/interactions/open-a-context-menu), [Place a mark of your own (The handle)](#/handle/place-a-mark), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
-| `clientY` *required* | `number` | — | The pointer's vertical client coordinate.<br>Shown in: [Open a context menu](#/interactions/open-a-context-menu), [Place a mark of your own (The handle)](#/handle/place-a-mark), [Replan the day on the line (Scenarios)](#/scenarios/replan-the-day-on-the-line) |
-| `time` *required* | `number` | — | The wall-clock instant under the pointer.<br>Shown in: [Report what the pointer is on](#/interactions/report-the-pointer) |
-| `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) |
+| `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), [Open a context menu](#interactions), [Show a detail panel instead (Tooltip)](#tooltip) and 1 more |
+| `hit` *required* | `ScheduleHit` | — | What the pointer is on.<br>Shown in: [Report what the pointer is on](#interactions), [Open a context menu](#interactions), [Show a detail panel instead (Tooltip)](#tooltip) and 2 more |
+| `clientX` *required* | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens.<br>Shown in: [Open a context menu](#interactions), [Place a mark of your own (The handle)](#the-handle), [Replan the day on the line (Scenarios)](#replan-the-day-on-the-line) |
+| `clientY` *required* | `number` | — | The pointer's vertical client coordinate.<br>Shown in: [Open a context menu](#interactions), [Place a mark of your own (The handle)](#the-handle), [Replan the day on the line (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) |
+| `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) |
 ##### Types on this page
@@ -5184,8 +5150,6 @@ Names what the pointer rests on - a subtask with its times and findings, a depen
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/tooltip/
 Its words come from the wording of @umriss-ui/core and its numbers from its formats, so a provider switches it with everything else. It steps aside while a drag is in flight and is placed where it has room.
 The keyboard's active subtask shows the same tooltip as the pointer.
@@ -5538,7 +5502,7 @@ export default function SayWhatABarCoversAndALineJoins() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -5546,17 +5510,17 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `kind` *required* | `"subtask" \| "milestone" \| "dependency"` | — | A subtask is hovered. A milestone 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), [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `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), [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `task` | [`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) |
-| `milestone` | [`Milestone`](#/milestones/type-Milestone) | — | The hovered milestone.<br>Shown in: [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `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) |
+| `kind` *required* | `"subtask" \| "milestone" \| "dependency"` | — | A subtask is hovered. A milestone is hovered. A dependency is hovered.<br>Shown in: [Write your own tooltip content](#tooltip), [Say what a bar covers and a line joins](#tooltip), [Say what a milestone is in your own tooltip (Milestones)](#milestones) |
+| `subtask` | [`Subtask`](#subtasks) | — | The hovered subtask.<br>Shown in: [Say what a bar covers and a line joins](#tooltip), [Say what a milestone is in your own tooltip (Milestones)](#milestones) |
+| `task` | [`Task`](#subtasks)` \| undefined` | — | Its task, where the tasks name it.<br>Shown in: [Write your own tooltip content](#tooltip) |
+| `overlapping` | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks it overlaps with on its lane.<br>Shown in: [Write your own tooltip content](#tooltip) |
+| `violatedDependencies` | `readonly `[`ViolatedDependency`](#findings-as-data)`[]` | — | The violated dependencies leaving or reaching it.<br>Shown in: [Write your own tooltip content](#tooltip) |
+| `blocked` | `readonly `[`BlockedTime`](#blocked-time)`[]` | — | The blocked time it covers on its lane.<br>Shown in: [Say what a bar covers and a line joins](#tooltip) |
+| `milestone` | [`Milestone`](#milestones) | — | The hovered milestone.<br>Shown in: [Say what a milestone is in your own tooltip (Milestones)](#milestones) |
+| `dependency` | [`Dependency`](#dependencies) | — | The hovered dependency.<br>Shown in: [Say what a bar covers and a line joins](#tooltip) |
+| `from` | [`Subtask`](#subtasks)` \| undefined` | — | The subtask it leaves.<br>Shown in: [Say what a bar covers and a line joins](#tooltip) |
+| `to` | [`Subtask`](#subtasks)` \| undefined` | — | The subtask it reaches.<br>Shown in: [Say what a bar covers and a line joins](#tooltip) |
+| `violated` | [`ViolatedDependency`](#findings-as-data)` \| undefined` | — | Its finding, where it is violated.<br>Shown in: [Write your own tooltip content](#tooltip) |
 ### View
@@ -5566,9 +5530,7 @@ How the planner is looking at the plan - the span in view and the folded lane gr
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/view/
-The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#/api/useSchedule) hands back holds it, and `onViewChange` reports every change the planner makes to it - a pan or zoom at most once per frame; keep it where the application keeps things and go back to it with `setView`.
+The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#api-index-1) hands back holds it, and `onViewChange` reports every change the planner makes to it - a pan or zoom at most once per frame; keep it where the application keeps things and go back to it with `setView`.
 `initialView` is the start, read once: a different value on a later render is ignored. `setView(view)` goes to a whole view at once, and what it leaves out goes back to its default; the same view again changes nothing, and `onViewChange` does not hear it. Without a span the schedule shows the extent of its subtasks, within `zoomLimits`. A group no `LaneGroup` declares falls out.
@@ -5680,7 +5642,7 @@ export default function KeepAndRestore() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -5688,20 +5650,20 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `initialView` | [`ScheduleView`](#type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 78 more |
+| `initialView` | `ScheduleView` | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#view), [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule) and 78 more |
 ###### Events
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `onViewChange` | `(view: `[`ScheduleView`](#type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies.<br>Shown in: [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
+| `onViewChange` | `(view: ``ScheduleView``) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies.<br>Shown in: [Keep two schedules in step (Linked schedules)](#linked-schedules), [Read a rota beside the incidents (Linked schedules)](#linked-schedules) |
 ##### `ScheduleView`
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `domain` | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 77 more |
-| `folded` | `readonly string[]` | — | The **Lane group**s that are folded, by id. An id no group carries falls out. A folded outer group hides the inner ones without their ids leaving the list, so unfolding it gives back the view that was there.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Start with groups folded (Lane groups)](#/lane-groups/start-with-groups-folded) |
+| `domain` | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`.<br>Shown in: [Keep and restore a view](#view), [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule) and 77 more |
+| `folded` | `readonly string[]` | — | The **Lane group**s that are folded, by id. An id no group carries falls out. A folded outer group hides the inner ones without their ids leaving the list, so unfolding it gives back the view that was there.<br>Shown in: [Fold groups from outside (Lane groups)](#lane-groups), [Read a folded group (Lane groups)](#lane-groups), [Start with groups folded (Lane groups)](#lane-groups) |
 ### Linked schedules
@@ -5711,9 +5673,7 @@ Keeps two schedules on the same hours: pan or zoom one and the other follows (al
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/linked-schedules/
-Each schedule has its own [`useSchedule`](#/api/useSchedule). Send what one reports to the other's `setView`, in both directions: the other goes there at once, without a remount, and `setView` is not reported, so the two never answer each other.
+Each schedule has its own [`useSchedule`](#api-index-1). Send what one reports to the other's `setView`, in both directions: the other goes there at once, without a remount, and `setView` is not reported, so the two never answer each other.
 While a drag is in flight the two can stand a frame apart; they settle as soon as it ends.
@@ -5956,81 +5916,81 @@ export default function RotaBesideIncidents() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`children`](#first-schedule) | `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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 ###### Events
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`onViewChange`](#/view/ScheduleOptions-onViewChange) | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies. |
+| [`onViewChange`](#view) | `(view: `[`ScheduleView`](#view)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### Known limits
 - Only the view is shared - the span and the folded groups, not the selection, the hover or the vertical scroll.
-What umriss deliberately does not build, and why: [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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### The handle
@@ -6040,8 +6000,6 @@ Converts between a point on the screen and a time on a lane, so marks of your ow
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/handle/
 The handle holds three functions and nothing else: `clientPointOf(time, lane?)`, `positionAt(clientX, clientY)` and `visibleDomain()`. Everything else the schedule does is props.
 Place your marks again whenever `view.domain` changes.
@@ -6137,82 +6095,82 @@ export default function PlaceAMark() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ref`](#/schedule/ScheduleProps-ref) | `Ref<`[`ScheduleHandle`](#/schedule/type-ScheduleHandle)`>` | — | Receives the `ScheduleHandle` - not an element. |
-| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
-| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+| [`ref`](#first-schedule) | `Ref<`[`ScheduleHandle`](#first-schedule)`>` | — | Receives the `ScheduleHandle` - not an element. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 ###### Events
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`onInteraction`](#/schedule/ScheduleProps-onInteraction) | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
+| [`onInteraction`](#first-schedule) | `(interaction: `[`ScheduleInteraction`](#interactions)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
 ###### Accessibility
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#/schedule/ScheduleProps-ariaLabel) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleInteraction` — the full table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+From `ScheduleInteraction` — the full table stands on [Interactions](#interactions).
 | 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. |
+| [`clientX`](#interactions) *required* | `number` | — | The pointer's horizontal client coordinate - where a `ContextMenu` opens. |
+| [`clientY`](#interactions) *required* | `number` | — | The pointer's vertical client coordinate. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Findings as data
@@ -6222,9 +6180,7 @@ Lists what is wrong with a plan - double bookings on a lane, dependencies that d
 import { findings, overlaps, violatedDependencies, inBlockedTime } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/findings/
-`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.
+`findings(subtasks, dependencies, blocked)` returns all three kinds; [`overlaps`](#api-index-1), [`violatedDependencies`](#api-index-1) and [`inBlockedTime`](#api-index-1) 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.
@@ -6232,7 +6188,7 @@ Lead-in and lead-out count as occupied time; touching at a shared edge is no ove
 ##### 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.
+[`findings`](#api-index-1) returns what the schedule marks - overlaps, violated dependencies, work in blocked time - as data for a list beside it.
 ```tsx
 import { Stack, Text } from "@umriss-ui/core";
@@ -6299,7 +6255,7 @@ export default function ListTheFindings() {
 ##### 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.
+When all three lists [`findings`](#api-index-1) returns are empty, say so plainly instead of showing an empty list.
 ```tsx
 import { EmptyState, Stack } from "@umriss-ui/core";
@@ -6335,7 +6291,7 @@ export default function NothingToFix() {
 ##### 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.
+[`overlaps`](#api-index-1) and [`violatedDependencies`](#api-index-1) are the halves of [`findings`](#api-index-1) on their own - here as counts above the day's legs.
 ```tsx
 import { Badge, Stack } from "@umriss-ui/core";
@@ -6393,7 +6349,7 @@ export default function CountPerKind() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### API
@@ -6401,36 +6357,36 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 | 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) |
+| `lane` *required* | `string` | — | The lane both sit on.<br>Shown in: [List the findings](#findings-as-data), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) |
+| `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-as-data), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) |
+| `second` *required* | `string` | — | The other one.<br>Shown in: [List the findings](#findings-as-data), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) |
+| `from` *required* | `number` | — | Where the covering begins.<br>Shown in: [List the findings](#findings-as-data) |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [List the findings](#findings-as-data) |
 ##### `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) |
+| `dependency` *required* | `string` | — | The id of the dependency.<br>Shown in: [List the findings](#findings-as-data) |
+| `departure` *required* | `number` | — | When it leaves, by its anchor.<br>Shown in: [List the findings](#findings-as-data) |
+| `arrival` *required* | `number` | — | When it has to have arrived, by its anchor.<br>Shown in: [List the findings](#findings-as-data) |
+| `shortBy` *required* | `number` | — | How much time is missing: departure plus lag, minus arrival.<br>Shown in: [List the findings](#findings-as-data) |
 ##### `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) |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [List the findings](#findings-as-data), [Block out leave and maintenance (Blocked time)](#blocked-time), [Check a sprint against the leave calendar (Blocked time)](#blocked-time) and 2 more |
+| `blocked` *required* | `string` | — | The id of the blocked time it covers.<br>Shown in: [List the findings](#findings-as-data), [Block out leave and maintenance (Blocked time)](#blocked-time), [Plan the sprint around leave (Scenarios)](#plan-the-sprint-around-leave) |
+| `lane` *required* | `string` | — | The lane both are on.<br>Shown in: [Hand over the on-call week (Scenarios)](#hand-over-the-on-call-week), [Plan the sprint around leave (Scenarios)](#plan-the-sprint-around-leave) |
+| `from` *required* | `number` | — | Where the covering begins.<br>Shown in: [List the findings](#findings-as-data), [Block out leave and maintenance (Blocked time)](#blocked-time), [Hand over the on-call week (Scenarios)](#hand-over-the-on-call-week) |
+| `to` *required* | `number` | — | Where it ends.<br>Shown in: [List the findings](#findings-as-data), [Block out leave and maintenance (Blocked time)](#blocked-time), [Hand over the on-call week (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/).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ## Editing
@@ -6444,11 +6400,9 @@ Drag a bar to a new time or onto another lane (also called drag-and-drop resched
 import { useSchedule, 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.
+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-index-1) 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.
@@ -6456,7 +6410,7 @@ Held at the edge of the plot, a drag pans it along; Escape cancels the drag.
 ##### Move work in time
-List `move` in `intents` and apply what `onIntent` reports with [`applyIntent`](#/api/applyIntent); the plan changes only in your state.
+List `move` in `intents` and apply what `onIntent` reports with [`applyIntent`](#api-index-1); the plan changes only in your state.
 ```tsx
 import { useState } from "react";
@@ -6564,7 +6518,7 @@ export default function MoveToAnotherLane() {
 ##### Refuse a move that double-books someone
-Your `onIntent` decides: here it applies a drop only when [`overlaps`](#/api/overlaps) finds no new double booking, and says why otherwise.
+Your `onIntent` decides: here it applies a drop only when [`overlaps`](#api-index-1) finds no new double booking, and says why otherwise.
 ```tsx
 import { useRef, useState } from "react";
@@ -6711,106 +6665,106 @@ 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. |
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
-From `Overlap` — the full table stands on [Findings as data](#/findings/type-Overlap).
+From `Overlap` — the full table stands on [Findings as data](#findings-as-data).
 | 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. |
+| [`lane`](#findings-as-data) *required* | `string` | — | The lane both sit on. |
+| [`first`](#findings-as-data) *required* | `string` | — | The subtask that starts earlier (lead-in included); on a tie, the one that stands first in the data. |
+| [`second`](#findings-as-data) *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/)).
+- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
 - 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/).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Stretch, lead-in, lead-out
@@ -6820,8 +6774,6 @@ Change how long work takes, or how long its preparation and its wrap-up take, by
 import { useSchedule, applyIntent } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/stretch/
 `stretch` enables the two edges of the main time. `leadIn` and `leadOut` add a grip at the outer edge of each; the grips show on the selected subtask only, so click a bar first.
 Stretching the main time leaves the lead-in and the lead-out as long as they were.
@@ -6909,82 +6861,82 @@ 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.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`leadIn`](#subtasks) | `number` | — | Duration of the lead-in before the main time; none is zero. |
+| [`leadOut`](#subtasks) | `number` | — | Duration of the lead-out after the main time; none is zero. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### 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://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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Snapping
@@ -6994,11 +6946,9 @@ Makes a drag land on a raster - the axis' own step, a fixed duration, or a patte
 import { useSchedule, snapTime } from "@umriss-ui/schedule";
 ```
-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`](#/api/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-index-1) is the same arithmetic for your own use.
 #### Examples
@@ -7144,75 +7094,75 @@ export default function NoSnapping() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`snap`](#first-schedule) | `"ticks" \| number \| `[`SnapRaster`](#first-schedule)` \| 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`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Placing from outside
@@ -7222,17 +7172,15 @@ Drag work that is not on the plan yet - from a backlog or a list of unassigned j
 import { useSchedule, subtaskFromPlace } from "@umriss-ui/schedule";
 ```
-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`](#/api/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-index-1) 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`](#/api/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-index-1) turns into work.
 ```tsx
 import { useState } from "react";
@@ -7339,90 +7287,90 @@ export default function DragFromTheBacklog() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | [`PlacingItem`](#first-schedule)` \| 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ### Where a subtask may go
@@ -7432,8 +7380,6 @@ Marks the lanes and times a piece of work may not go to as soon as a drag begins
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/where-it-may-go/
 `canMoveTo(subtask, lane)` is asked once per lane when a drag takes hold, and again at the drop. Refused lanes are drawn back and hatched; over one, the ghost stays on the last lane allowed, tied to the pointer by a line.
 Blocked time refuses a place in time rather than a lane: a drag cannot put work into it, and Alt with an arrow key steps over it. Work the data already put there is never locked in.
@@ -7759,97 +7705,97 @@ export default function AroundLeave() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`, 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`](#first-schedule) | [`PlacingItem`](#first-schedule)` \| 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `BlockedTimesProps` — the full table stands on [Blocked time](#/blocked-time/type-BlockedTimesProps).
+From `BlockedTimesProps` — the full table stands on [Blocked time](#blocked-time).
 | 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. |
+| [`data`](#blocked-time) *required* | `readonly `[`BlockedTime`](#blocked-time)`[]` | — | 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).
+From `BlockedTime` — the full table stands on [Blocked time](#blocked-time).
 | 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. |
+| [`id`](#blocked-time) *required* | `string` | — | The caller's identity of the interval - what a finding names. |
+| [`lane`](#blocked-time) *required* | `string` | — | The id of the lane it blocks. |
+| [`from`](#blocked-time) *required* | `number` | — | Where it begins. |
+| [`to`](#blocked-time) *required* | `number` | — | Where it ends. |
+| [`label`](#blocked-time) | `string` | — | Why the lane is blocked - "Leave", "Maintenance" -, where the schedule names it. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### 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://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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ### Ripple
@@ -7859,17 +7805,15 @@ Works out which later work has to move when one piece moves: every successor who
 import { ripple, shiftTask, applyIntent } from "@umriss-ui/schedule";
 ```
-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`](#/api/shiftTask) moves every subtask of one task by the same amount, so all its dependencies keep fitting.
+[`shiftTask`](#api-index-1) 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`](#/api/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-index-1) 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";
@@ -7938,7 +7882,7 @@ export default function PushTheLaterStops() {
 ##### Move a whole tour
-[`shiftTask`](#/api/shiftTask) returns one move per stop, all by the same amount, so every drive that fitted still fits.
+[`shiftTask`](#api-index-1) returns one move per stop, all by the same amount, so every drive that fitted still fits.
 ```tsx
 import { useState } from "react";
@@ -7998,7 +7942,7 @@ export default function MoveAWholeTour() {
 ##### Ripple on every drag
-Run [`ripple`](#/api/ripple) inside `onIntent` and apply its moves with the drop: drag the design later and build and test follow.
+Run [`ripple`](#api-index-1) inside `onIntent` and apply its moves with the drop: drag the design later and build and test follow.
 ```tsx
 import { useState } from "react";
@@ -8050,96 +7994,96 @@ export default function RippleOnEveryDrag() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`intents`](#first-schedule) | `readonly `[`IntentKind`](#first-schedule)`[]` | `[]` | 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`](#first-schedule) | `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. |
+| [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => 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". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | 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. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`label`](#lanes) | `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).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 #### Known limits
-- 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/)).
+- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
 - 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://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/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
 ## Measuring
@@ -8153,8 +8097,6 @@ A plan of up to five thousand subtasks and as many dependencies, measured in thi
 import { useSchedule } from "@umriss-ui/schedule";
 ```
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/benchmark/
 The figures in `packages/schedule/docs/capabilities.md` come from here. The page dispatches the pointer and wheel events itself, on the schedule's canvas, and adds no prop to the schedule.
 #### Examples
@@ -8465,94 +8407,94 @@ export default function Benchmark() {
 #### Keyboard
-The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
+The keys of [First schedule](#first-schedule) apply here.
 #### Props on this page
-From `ScheduleProps` — the full table stands on [First schedule](#/schedule/type-ScheduleProps).
+From `ScheduleProps` — the full table stands on [First schedule](#first-schedule).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#/schedule/ScheduleProps-height) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
-| [`laneHeight`](#/schedule/ScheduleProps-laneHeight) | `number` | `44` | Height of one lane in pixels at the default font size of 16 px; the schedule multiplies it by the root font size over 16 px when that ratio is above 1, so lane names keep their room in a reader's larger font. |
-| [`children`](#/schedule/ScheduleProps-children) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
+| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`laneHeight`](#first-schedule) | `number` | `44` | Height of one lane in pixels at the default font size of 16 px; the schedule multiplies it by the root font size over 16 px when that ratio is above 1, so lane names keep their room in a reader's larger font. |
+| [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 ###### Events
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`onInteraction`](#/schedule/ScheduleProps-onInteraction) | `(interaction: `[`ScheduleInteraction`](#/interactions/type-ScheduleInteraction)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
+| [`onInteraction`](#first-schedule) | `(interaction: `[`ScheduleInteraction`](#interactions)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
 ###### Accessibility
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#/schedule/ScheduleProps-ariaLabel) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`ariaLabel`](#first-schedule) *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).
+From `LaneProps` — the full table stands on [Lanes](#lanes).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`id`](#/lane/LaneProps-id) *required* | `string` | — | The identity subtasks name in their `lane`. |
+| [`id`](#lanes) *required* | `string` | — | The identity subtasks name in their `lane`. |
-From `SubtasksProps` — the full table stands on [Subtasks](#/subtasks/type-SubtasksProps).
+From `SubtasksProps` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`data`](#subtasks) *required* | `readonly `[`Subtask`](#subtasks)`[]` | — | The subtasks, as the caller holds them. The schedule never changes one. |
+| [`tasks`](#subtasks) *required* | `readonly `[`Task`](#subtasks)`[]` | — | 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).
+From `Subtask` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the subtask. |
+| [`task`](#subtasks) *required* | `string` | — | The id of the task it belongs to. |
+| [`lane`](#subtasks) *required* | `string` | — | The id of the lane it sits on. |
+| [`from`](#subtasks) *required* | `number` | — | Start of the main time. |
+| [`to`](#subtasks) *required* | `number` | — | End of the main time. |
+| [`name`](#subtasks) | `string` | — | What the subtask is called, where the schedule names it. |
-From `Task` — the full table stands on [Subtasks](#/subtasks/type-Task).
+From `Task` — the full table stands on [Subtasks](#subtasks).
 | 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. |
+| [`id`](#subtasks) *required* | `string` | — | The caller's identity of the task. |
+| [`color`](#subtasks) *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) | `string` | — | What the task is called, where the schedule names it. |
-From `DependenciesProps` — the full table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+From `DependenciesProps` — the full table stands on [Dependencies](#dependencies).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`data`](#/dependencies/DependenciesProps-data) *required* | `readonly `[`Dependency`](#/dependencies/type-Dependency)`[]` | — | The dependencies, as the caller holds them. |
+| [`data`](#dependencies) *required* | `readonly `[`Dependency`](#dependencies)`[]` | — | The dependencies, as the caller holds them. |
-From `Dependency` — the full table stands on [Dependencies](#/dependencies/type-Dependency).
+From `Dependency` — the full table stands on [Dependencies](#dependencies).
 | 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. |
+| [`id`](#dependencies) *required* | `string` | — | The caller's identity of the dependency. |
+| [`from`](#dependencies) *required* | `string` | — | The id of the subtask it leaves. |
+| [`to`](#dependencies) *required* | `string` | — | The id of the subtask it arrives at. |
+| [`lag`](#dependencies) *required* | `number` | — | The least time between the two anchors; zero where the successor may begin as soon as the predecessor ends. |
-From `ScheduleInteraction` — the full table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+From `ScheduleInteraction` — the full table stands on [Interactions](#interactions).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`hit`](#/interactions/ScheduleInteraction-hit) *required* | [`ScheduleHit`](#/interactions/type-ScheduleHit) | — | What the pointer is on. |
+| [`hit`](#interactions) *required* | [`ScheduleHit`](#interactions) | — | What the pointer is on. |
-From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleOptions).
+From `ScheduleOptions` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#view) | [`ScheduleView`](#view) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
-From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
+From `ScheduleView` — the full table stands on [View](#view).
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`domain`](#/view/ScheduleView-domain) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
+| [`domain`](#view) | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`. |
 ## API index
@@ -8562,8 +8504,6 @@ Every name the package exports, in one place.
 Everything `@umriss-ui/schedule` exports, with its signature. A component's props stand on its own page.
-Demo page: https://romanhaendler.github.io/umriss-ui/schedule/api/
 #### Hooks
 ##### `useSchedule`
@@ -8577,7 +8517,7 @@ Declares a schedule: hands back `Schedule` and the parts declared inside it
 function useSchedule(options?: ScheduleOptions): ScheduleParts;
 ```
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
+Used on [Scenarios](#scenarios), [Installation](#installation), [First schedule](#first-schedule), [Lanes](#lanes), [Lane groups](#lane-groups), [Subtasks](#subtasks), [Bar labels](#bar-labels), [Appearances](#appearances), [Overlap](#overlap), [Dependencies](#dependencies), [Routes](#routes), [Time axis and calendar](#time-axis-and-calendar), [Blocked time](#blocked-time), [Milestones](#milestones), [Now line](#now-line), [Pan and zoom](#pan-and-zoom), [Selection](#selection), [Interactions](#interactions), [Tooltip](#tooltip), [View](#view), [Linked schedules](#linked-schedules), [The handle](#the-handle), [Findings as data](#findings-as-data), [Move and lane](#move-and-lane), [Stretch, lead-in, lead-out](#stretch-lead-in-lead-out), [Snapping](#snapping), [Placing from outside](#placing-from-outside), [Where a subtask may go](#where-a-subtask-may-go), [Ripple](#ripple) and [Benchmark](#benchmark).
 #### Functions
@@ -8590,7 +8530,7 @@ it as it is.
 function applyIntent<S extends Subtask>(subtask: S, intent: Intent): S;
 ```
-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).
+Used on [Scenarios](#scenarios), [Lane groups](#lane-groups), [Time axis and calendar](#time-axis-and-calendar), [Blocked time](#blocked-time), [Interactions](#interactions), [Move and lane](#move-and-lane), [Stretch, lead-in, lead-out](#stretch-lead-in-lead-out), [Snapping](#snapping), [Placing from outside](#placing-from-outside), [Where a subtask may go](#where-a-subtask-may-go) and [Ripple](#ripple).
 ##### `arrival`
@@ -8600,7 +8540,7 @@ When a dependency has to have arrived at its subtask, by its anchor.
 function arrival(dependency: Dependency, to: Subtask): number;
 ```
-Used on [Scenarios](#/), [Now line](#/now-line) and [Findings as data](#/findings).
+Used on [Scenarios](#scenarios), [Now line](#now-line) and [Findings as data](#findings-as-data).
 ##### `departure`
@@ -8610,7 +8550,7 @@ When a dependency leaves its subtask, by its anchor.
 function departure(dependency: Dependency, from: Subtask): number;
 ```
-Used on [Findings as data](#/findings).
+Used on [Findings as data](#findings-as-data).
 ##### `findings`
@@ -8620,7 +8560,7 @@ Every finding at once. Without blocked time there is none in it.
 function findings(subtasks: readonly Subtask[], dependencies: readonly Dependency[], blocked?: readonly BlockedTime[]): Findings;
 ```
-Used on [Scenarios](#/), [First schedule](#/schedule), [Lane groups](#/lane-groups), [Blocked time](#/blocked-time), [Tooltip](#/tooltip) and [Findings as data](#/findings).
+Used on [Scenarios](#scenarios), [First schedule](#first-schedule), [Lane groups](#lane-groups), [Blocked time](#blocked-time), [Tooltip](#tooltip) and [Findings as data](#findings-as-data).
 ##### `inBlockedTime`
@@ -8632,7 +8572,7 @@ subtasks. Touching at a shared edge is not covering.
 function inBlockedTime(subtasks: readonly Subtask[], blocked: readonly BlockedTime[]): InBlockedTime[];
 ```
-Used on [Scenarios](#/), [Blocked time](#/blocked-time) and [Findings as data](#/findings).
+Used on [Scenarios](#scenarios), [Blocked time](#blocked-time) and [Findings as data](#findings-as-data).
 ##### `occupied`
@@ -8655,7 +8595,7 @@ nothing.
 function overlaps(subtasks: readonly Subtask[]): Overlap[];
 ```
-Used on [Scenarios](#/), [Lane groups](#/lane-groups), [Findings as data](#/findings) and [Move and lane](#/move-and-lane).
+Used on [Scenarios](#scenarios), [Lane groups](#lane-groups), [Findings as data](#findings-as-data) and [Move and lane](#move-and-lane).
 ##### `resolveAppearance`
@@ -8669,7 +8609,7 @@ Settles a subtask's appearances into what is drawn. `provisional` and
 function resolveAppearance(appearance: readonly SubtaskAppearance[] | undefined): ResolvedAppearance;
 ```
-Used on [Appearances](#/appearances).
+Used on [Appearances](#appearances).
 ##### `ripple`
@@ -8682,14 +8622,14 @@ bounded number of pushes instead of running on.
 function ripple(subtasks: readonly Subtask[], dependencies: readonly Dependency[], intent: Intent): MoveIntent[];
 ```
-Used on [Scenarios](#/), [Dependencies](#/dependencies) and [Ripple](#/ripple).
+Used on [Scenarios](#scenarios), [Dependencies](#dependencies) and [Ripple](#ripple).
 ##### `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.
+intent, or run [`ripple`](#api-index-1) 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`.
@@ -8701,7 +8641,7 @@ or not finite.
 function shiftTask(subtasks: readonly Subtask[], task: string, by: number): MoveIntent[];
 ```
-Used on [Scenarios](#/) and [Ripple](#/ripple).
+Used on [Scenarios](#scenarios) and [Ripple](#ripple).
 ##### `snapTime`
@@ -8713,7 +8653,7 @@ stays as it is.
 function snapTime(time: number, raster: number | SnapRaster): number;
 ```
-Used on [Snapping](#/snapping).
+Used on [Snapping](#snapping).
 ##### `subtaskFromPlace`
@@ -8723,7 +8663,7 @@ The subtask a place intent asks for, under an id the caller chooses.
 function subtaskFromPlace(intent: PlaceIntent, id: string): Subtask;
 ```
-Used on [Placing from outside](#/placing) and [Where a subtask may go](#/where-it-may-go).
+Used on [Placing from outside](#placing-from-outside) and [Where a subtask may go](#where-a-subtask-may-go).
 ##### `violatedDependencies`
@@ -8735,29 +8675,29 @@ is not in the data is passed over: there is nothing to judge.
 function violatedDependencies(subtasks: readonly Subtask[], dependencies: readonly Dependency[]): ViolatedDependency[];
 ```
-Used on [Scenarios](#/), [Lane groups](#/lane-groups), [Tooltip](#/tooltip) and [Findings as data](#/findings).
+Used on [Scenarios](#scenarios), [Lane groups](#lane-groups), [Tooltip](#tooltip) and [Findings as data](#findings-as-data).
 #### Types
 ##### `BlockedTime`
-Its table stands on [Blocked time](#/blocked-time/type-BlockedTime).
+Its table stands on [Blocked time](#blocked-time).
-Used on [Scenarios](#/), [Blocked time](#/blocked-time), [Tooltip](#/tooltip), [Findings as data](#/findings) and [Where a subtask may go](#/where-it-may-go).
+Used on [Scenarios](#scenarios), [Blocked time](#blocked-time), [Tooltip](#tooltip), [Findings as data](#findings-as-data) and [Where a subtask may go](#where-a-subtask-may-go).
 ##### `BlockedTimesProps`
-Its table stands on [Blocked time](#/blocked-time/type-BlockedTimesProps).
+Its table stands on [Blocked time](#blocked-time).
 ##### `DependenciesProps`
-Its table stands on [Dependencies](#/dependencies/type-DependenciesProps).
+Its table stands on [Dependencies](#dependencies).
 ##### `Dependency`
-Its table stands on [Dependencies](#/dependencies/type-Dependency).
+Its table stands on [Dependencies](#dependencies).
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lane groups](#/lane-groups), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Placing from outside](#/placing), [Ripple](#/ripple) and [Benchmark](#/benchmark).
+Used on [Scenarios](#scenarios), [Installation](#installation), [First schedule](#first-schedule), [Lane groups](#lane-groups), [Dependencies](#dependencies), [Routes](#routes), [Time axis and calendar](#time-axis-and-calendar), [Selection](#selection), [Interactions](#interactions), [Tooltip](#tooltip), [Findings as data](#findings-as-data), [Move and lane](#move-and-lane), [Placing from outside](#placing-from-outside), [Ripple](#ripple) and [Benchmark](#benchmark).
 ##### `DependencyAttachment`
@@ -8773,7 +8713,7 @@ The tree has an **Anchor** of its own as well (CONTEXT.md).
 type DependencyAttachment = "centre" | "nearest";
 ```
-Used on [Dependencies](#/dependencies).
+Used on [Dependencies](#dependencies).
 ##### `DependencyEnds`
@@ -8785,7 +8725,7 @@ plan full of short moves - so it is the caller's choice.
 type DependencyEnds = "dot" | "none";
 ```
-Used on [Dependencies](#/dependencies).
+Used on [Dependencies](#dependencies).
 ##### `DependencyRoute`
@@ -8802,13 +8742,13 @@ 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 |
+| `overlaps` *required* | `readonly `[`Overlap`](#findings-as-data)`[]` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [List the findings (Findings as data)](#findings-as-data), [Say when there is nothing to fix (Findings as data)](#findings-as-data) and 1 more |
+| `violatedDependencies` *required* | `readonly `[`ViolatedDependency`](#findings-as-data)`[]` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [List the findings (Findings as data)](#findings-as-data), [Say when there is nothing to fix (Findings as data)](#findings-as-data) and 1 more |
+| `inBlockedTime` *required* | `readonly `[`InBlockedTime`](#findings-as-data)`[]` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#blocked-time), [Check a sprint against the leave calendar (Blocked time)](#blocked-time), [List the findings (Findings as data)](#findings-as-data) and 3 more |
 ##### `InBlockedTime`
-Its table stands on [Findings as data](#/findings/type-InBlockedTime).
+Its table stands on [Findings as data](#findings-as-data).
 ##### `Intent`
@@ -8820,7 +8760,7 @@ drop - a move and a lane - give the same data in either order.
 type Intent = MoveIntent | StretchIntent | LeadInIntent | LeadOutIntent | LaneIntent | PlaceIntent;
 ```
-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).
+Used on [Scenarios](#scenarios), [Blocked time](#blocked-time), [Move and lane](#move-and-lane), [Placing from outside](#placing-from-outside), [Where a subtask may go](#where-a-subtask-may-go) and [Ripple](#ripple).
 ##### `IntentKind`
@@ -8832,7 +8772,7 @@ type IntentKind = Intent["kind"];
 ##### `LaneGroupProps`
-Its table stands on [Lane groups](#/lane-groups/type-LaneGroupProps).
+Its table stands on [Lane groups](#lane-groups).
 ##### `LaneIntent`
@@ -8840,13 +8780,13 @@ 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 |
+| `kind` *required* | `"lane"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
 | `lane` *required* | `string` | — | The id of the new lane. |
 ##### `LaneProps`
-Its table stands on [Lanes](#/lane/type-LaneProps).
+Its table stands on [Lanes](#lanes).
 ##### `LeadInIntent`
@@ -8854,9 +8794,9 @@ 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) |
+| `kind` *required* | `"leadIn"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
+| `leadIn` *required* | `number` | — | The new duration of the lead-in.<br>Shown in: [Replan the day on the line (Scenarios)](#replan-the-day-on-the-line) |
 ##### `LeadOutIntent`
@@ -8864,19 +8804,19 @@ 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 |
+| `kind` *required* | `"leadOut"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 4 more |
 | `leadOut` *required* | `number` | — | The new duration of the lead-out. |
 ##### `Milestone`
-Its table stands on [Milestones](#/milestones/type-Milestone).
+Its table stands on [Milestones](#milestones).
-Used on [Milestones](#/milestones).
+Used on [Milestones](#milestones).
 ##### `MilestonesProps`
-Its table stands on [Milestones](#/milestones/type-MilestonesProps).
+Its table stands on [Milestones](#milestones).
 ##### `MoveIntent`
@@ -8884,16 +8824,16 @@ 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) |
+| `kind` *required* | `"move"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 8 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) 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), [Replan the day on the line (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), [Replan the day on the line (Scenarios)](#replan-the-day-on-the-line) |
-Used on [Ripple](#/ripple).
+Used on [Ripple](#ripple).
 ##### `Overlap`
-Its table stands on [Findings as data](#/findings/type-Overlap).
+Its table stands on [Findings as data](#findings-as-data).
 ##### `PlaceIntent`
@@ -8904,10 +8844,10 @@ no subtask yet; the caller creates one, with its own identity, from
 | 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) |
+| `kind` *required* | `"place"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) 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-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go), [Replan the day on the line (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) |
+| `lane` *required* | `string` | — | The lane it was dropped on.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
 | `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. |
@@ -8921,13 +8861,13 @@ 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) |
+| `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-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
+| `task` *required* | `string` | — | The task the work belongs to.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
+| `duration` *required* | `number` | — | How long its main time is.<br>Shown in: [Drag work in from the backlog (Placing from outside)](#placing-from-outside), [Apply the same rule to work dragged in (Where a subtask may go)](#where-a-subtask-may-go) |
 | `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).
+Used on [Placing from outside](#placing-from-outside) and [Where a subtask may go](#where-a-subtask-may-go).
 ##### `ResolvedAppearance`
@@ -8950,11 +8890,11 @@ 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) |
+| `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)](#the-handle) |
+| `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)](#the-handle) |
 | `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
-Used on [The handle](#/handle).
+Used on [The handle](#the-handle).
 ##### `ScheduleHit`
@@ -8971,13 +8911,13 @@ type ScheduleHit =
 ##### `ScheduleInteraction`
-Its table stands on [Interactions](#/interactions/type-ScheduleInteraction).
+Its table stands on [Interactions](#interactions).
-Used on [Scenarios](#/), [Interactions](#/interactions), [Tooltip](#/tooltip) and [Benchmark](#/benchmark).
+Used on [Scenarios](#scenarios), [Interactions](#interactions), [Tooltip](#tooltip) and [Benchmark](#benchmark).
 ##### `ScheduleOptions`
-Its table stands on [View](#/view/type-ScheduleOptions).
+Its table stands on [View](#view).
 ##### `ScheduleParts`
@@ -8986,37 +8926,37 @@ it, its view and the setters that change it.
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `Schedule` *required* | `(props: `[`ScheduleProps`](#/schedule/type-ScheduleProps)`) => ReactNode` | — | The schedule. One per `useSchedule`: a second schedule is a second call.<br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
-| `Lane` *required* | `typeof Lane` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
-| `LaneGroup` *required* | `typeof LaneGroup` | — | <br>Shown in: [Group lanes under a head (Lane groups)](#/lane-groups/a-group), [Nest groups to any depth (Lane groups)](#/lane-groups/nesting), [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) and 5 more |
-| `Subtasks` *required* | `typeof Subtasks` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Start from an empty plan (First schedule)](#/schedule/no-work-yet) and 78 more |
-| `Dependencies` *required* | `typeof Dependencies` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 28 more |
-| `BlockedTimes` *required* | `typeof BlockedTimes` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Check a sprint against the leave calendar (Blocked time)](#/blocked-time/team-leave) and 5 more |
-| `Milestones` *required* | `typeof Milestones` | — | <br>Shown in: [Mark a handover and a release (Milestones)](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `view` *required* | [`ScheduleView`](#/view/type-ScheduleView) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step) and 1 more |
-| `setView` *required* | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Goes to a whole view; what it leaves out is shown whole again. Not reported through `onViewChange`: two schedules kept in step by `onViewChange: (v) => other.setView(v)` in both directions do not answer each other. A view with the content already shown changes nothing.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
-| `setDomain` *required* | `(span: readonly [number, number] \| null) => void` | — | Puts a span of two wall-clock instants in view; `null` shows the subtasks' extent.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore) |
+| `Schedule` *required* | `(props: `[`ScheduleProps`](#first-schedule)`) => ReactNode` | — | The schedule. One per `useSchedule`: a second schedule is a second call.<br>Shown in: [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule), [Start from an empty plan (First schedule)](#first-schedule) and 78 more |
+| `Lane` *required* | `typeof Lane` | — | <br>Shown in: [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule), [Start from an empty plan (First schedule)](#first-schedule) and 78 more |
+| `LaneGroup` *required* | `typeof LaneGroup` | — | <br>Shown in: [Group lanes under a head (Lane groups)](#lane-groups), [Nest groups to any depth (Lane groups)](#lane-groups), [Fold groups from outside (Lane groups)](#lane-groups) and 5 more |
+| `Subtasks` *required* | `typeof Subtasks` | — | <br>Shown in: [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule), [Start from an empty plan (First schedule)](#first-schedule) and 78 more |
+| `Dependencies` *required* | `typeof Dependencies` | — | <br>Shown in: [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule), [Plan a day in the machine shop (First schedule)](#first-schedule) and 28 more |
+| `BlockedTimes` *required* | `typeof BlockedTimes` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#blocked-time), [Plan work around someone's leave (Blocked time)](#blocked-time), [Check a sprint against the leave calendar (Blocked time)](#blocked-time) and 5 more |
+| `Milestones` *required* | `typeof Milestones` | — | <br>Shown in: [Mark a handover and a release (Milestones)](#milestones), [Say what a milestone is in your own tooltip (Milestones)](#milestones) |
+| `view` *required* | [`ScheduleView`](#view) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#lane-groups), [Keep and restore a view (View)](#view), [Keep two schedules in step (Linked schedules)](#linked-schedules) and 1 more |
+| `setView` *required* | `(view: `[`ScheduleView`](#view)`) => void` | — | Goes to a whole view; what it leaves out is shown whole again. Not reported through `onViewChange`: two schedules kept in step by `onViewChange: (v) => other.setView(v)` in both directions do not answer each other. A view with the content already shown changes nothing.<br>Shown in: [Keep and restore a view (View)](#view), [Keep two schedules in step (Linked schedules)](#linked-schedules), [Read a rota beside the incidents (Linked schedules)](#linked-schedules) |
+| `setDomain` *required* | `(span: readonly [number, number] \| null) => void` | — | Puts a span of two wall-clock instants in view; `null` shows the subtasks' extent.<br>Shown in: [Keep and restore a view (View)](#view) |
 | `toggleGroup` *required* | `(id: string) => void` | — | Folds or unfolds one **Lane group**. |
-| `foldAll` *required* | `() => void` | — | Folds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
-| `unfoldAll` *required* | `() => void` | — | Unfolds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
+| `foldAll` *required* | `() => void` | — | Folds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#lane-groups) |
+| `unfoldAll` *required* | `() => void` | — | Unfolds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#lane-groups) |
-Used on [Linked schedules](#/linked-schedules).
+Used on [Linked schedules](#linked-schedules).
 ##### `ScheduleProps`
-Its table stands on [First schedule](#/schedule/type-ScheduleProps).
+Its table stands on [First schedule](#first-schedule).
 ##### `ScheduleTooltipTarget`
-Its table stands on [Tooltip](#/tooltip/type-ScheduleTooltipTarget).
+Its table stands on [Tooltip](#tooltip).
-Used on [Milestones](#/milestones) and [Tooltip](#/tooltip).
+Used on [Milestones](#milestones) and [Tooltip](#tooltip).
 ##### `ScheduleView`
-Its table stands on [View](#/view/type-ScheduleView).
+Its table stands on [View](#view).
-Used on [View](#/view).
+Used on [View](#view).
 ##### `SnapRaster`
@@ -9024,10 +8964,10 @@ 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) |
+| `step` *required* | `number` | — | The distance between two lines of the raster, in milliseconds.<br>Shown in: [Snap to handover times (Snapping)](#snapping) |
+| `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) |
-Used on [Snapping](#/snapping).
+Used on [Snapping](#snapping).
 ##### `StretchIntent`
@@ -9035,16 +8975,16 @@ 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 |
+| `kind` *required* | `"stretch"` | — | <br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) and 7 more |
+| `subtask` *required* | `string` | — | The id of the subtask.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Plan work around someone's leave (Blocked time)](#blocked-time), [Refuse a move that double-books someone (Move and lane)](#move-and-lane) 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).
+Its table stands on [Subtasks](#subtasks).
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
+Used on [Scenarios](#scenarios), [Installation](#installation), [First schedule](#first-schedule), [Lanes](#lanes), [Lane groups](#lane-groups), [Subtasks](#subtasks), [Bar labels](#bar-labels), [Appearances](#appearances), [Overlap](#overlap), [Dependencies](#dependencies), [Routes](#routes), [Time axis and calendar](#time-axis-and-calendar), [Blocked time](#blocked-time), [Milestones](#milestones), [Now line](#now-line), [Pan and zoom](#pan-and-zoom), [Selection](#selection), [Interactions](#interactions), [Tooltip](#tooltip), [View](#view), [Linked schedules](#linked-schedules), [The handle](#the-handle), [Findings as data](#findings-as-data), [Move and lane](#move-and-lane), [Stretch, lead-in, lead-out](#stretch-lead-in-lead-out), [Snapping](#snapping), [Placing from outside](#placing-from-outside), [Where a subtask may go](#where-a-subtask-may-go), [Ripple](#ripple) and [Benchmark](#benchmark).
 ##### `SubtaskAppearance`
@@ -9056,19 +8996,19 @@ type SubtaskAppearance = "provisional" | "fixed" | "muted" | "open";
 ##### `SubtasksProps`
-Its table stands on [Subtasks](#/subtasks/type-SubtasksProps).
+Its table stands on [Subtasks](#subtasks).
 ##### `Task`
-Its table stands on [Subtasks](#/subtasks/type-Task).
+Its table stands on [Subtasks](#subtasks).
-Used on [Scenarios](#/), [Installation](#/installation), [First schedule](#/schedule), [Lanes](#/lane), [Lane groups](#/lane-groups), [Subtasks](#/subtasks), [Bar labels](#/bar-labels), [Appearances](#/appearances), [Overlap](#/overlap), [Dependencies](#/dependencies), [Routes](#/routes), [Time axis and calendar](#/time-axis), [Blocked time](#/blocked-time), [Milestones](#/milestones), [Now line](#/now-line), [Pan and zoom](#/pan-and-zoom), [Selection](#/selection), [Interactions](#/interactions), [Tooltip](#/tooltip), [View](#/view), [Linked schedules](#/linked-schedules), [The handle](#/handle), [Findings as data](#/findings), [Move and lane](#/move-and-lane), [Stretch, lead-in, lead-out](#/stretch), [Snapping](#/snapping), [Placing from outside](#/placing), [Where a subtask may go](#/where-it-may-go), [Ripple](#/ripple) and [Benchmark](#/benchmark).
+Used on [Scenarios](#scenarios), [Installation](#installation), [First schedule](#first-schedule), [Lanes](#lanes), [Lane groups](#lane-groups), [Subtasks](#subtasks), [Bar labels](#bar-labels), [Appearances](#appearances), [Overlap](#overlap), [Dependencies](#dependencies), [Routes](#routes), [Time axis and calendar](#time-axis-and-calendar), [Blocked time](#blocked-time), [Milestones](#milestones), [Now line](#now-line), [Pan and zoom](#pan-and-zoom), [Selection](#selection), [Interactions](#interactions), [Tooltip](#tooltip), [View](#view), [Linked schedules](#linked-schedules), [The handle](#the-handle), [Findings as data](#findings-as-data), [Move and lane](#move-and-lane), [Stretch, lead-in, lead-out](#stretch-lead-in-lead-out), [Snapping](#snapping), [Placing from outside](#placing-from-outside), [Where a subtask may go](#where-a-subtask-may-go), [Ripple](#ripple) and [Benchmark](#benchmark).
 ##### `ViolatedDependency`
-Its table stands on [Findings as data](#/findings/type-ViolatedDependency).
+Its table stands on [Findings as data](#findings-as-data).
-Used on [Dependencies](#/dependencies).
+Used on [Dependencies](#dependencies).
 ##### `ZoomLimits`
@@ -9076,5 +9016,5 @@ 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) |
+| `min` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#pan-and-zoom) |
+| `max` *required* | `number` | — | <br>Shown in: [Move through the plan (Pan and zoom)](#pan-and-zoom) |