@umriss-ui/schedule 0.42.0 → 0.44.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.42.0
+# @umriss-ui/schedule 0.44.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -133,7 +133,7 @@ export default function HandOver() {
       </Stack>
       <div data-callout="2">
         <Schedule
-          ariaLabel="On-call rota, 16 to 23 March"
+          aria-label="On-call rota, 16 to 23 March"
           height={420}
           now={NOW}
           intents={["lane"]}
@@ -418,7 +418,7 @@ export default function TourPlan() {
     <Stack gap={3}>
       <div data-callout="1">
         <Schedule
-          ariaLabel="Tours of Wednesday, 18 March"
+          aria-label="Tours of Wednesday, 18 March"
           height={470}
           intents={["move"]}
           onIntent={apply}
@@ -652,7 +652,7 @@ export default function SprintAroundLeave() {
       </Stack>
       <div data-callout="2">
         <Schedule
-          ariaLabel="Sprint 14, work per person"
+          aria-label="Sprint 14, work per person"
           calendar={WORKING_DAYS}
           height={570}
           now={NOW}
@@ -844,7 +844,7 @@ export default function ReplanTheDay() {
       </div>
       <div data-callout="2">
         <Schedule
-          ariaLabel="Plan of Tuesday, 17 March, in the planner's hands"
+          aria-label="Plan of Tuesday, 17 March, in the planner's hands"
           height={380}
           intents={["move", "lane", "stretch", "leadIn", "leadOut"]}
           onIntent={apply}
@@ -863,7 +863,7 @@ export default function ReplanTheDay() {
         onOpenChange={(open) => {
           if (!open) setMenu(null);
         }}
-        ariaLabel={target !== null ? `Actions for ${target.id}` : "Actions for the plan"}
+        aria-label={target !== null ? `Actions for ${target.id}` : "Actions for the plan"}
       >
         {target !== null ? (
           <>
@@ -944,7 +944,7 @@ const dependencies: Dependency[] = [{ id: "handover", from: "design", to: "build
 export default function SmallestSchedule() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(8), at(16)] } });
   return (
-    <Schedule ariaLabel="Tuesday, design and build" height={150}>
+    <Schedule aria-label="Tuesday, design and build" height={150}>
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="arjun" label="Arjun Mehta" />
       <Dependencies data={dependencies} />
@@ -964,14 +964,14 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -1101,7 +1101,7 @@ const HANDOVERS: readonly Dependency[] = [
 export default function FirstSchedule() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: DAY } });
   return (
-    <Schedule ariaLabel="Tours of Tuesday, 17 March" height={240}>
+    <Schedule aria-label="Tours of Tuesday, 17 March" height={240}>
       {VEHICLES.map((vehicle) => (
         <Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
       ))}
@@ -1134,7 +1134,7 @@ const PEOPLE = [
 export default function NoWorkYet() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(23, 8), at(27, 18)] } });
   return (
-    <Schedule ariaLabel="Sprint 15, nothing planned yet" height={170}>
+    <Schedule aria-label="Sprint 15, nothing planned yet" height={170}>
       {PEOPLE.map((person) => (
         <Lane key={person.id} id={person.id} label={person.label} />
       ))}
@@ -1229,7 +1229,7 @@ export default function MachinePlan() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: DAY_OF_PLAN } });
   return (
     <Schedule
-      ariaLabel="Machine shop, Tuesday 17 March"
+      aria-label="Machine shop, Tuesday 17 March"
       height={380}
       now={HALF_PAST_TEN}
       label={(step) => NAMES.get(step.task) ?? step.task}
@@ -1244,6 +1244,164 @@ export default function MachinePlan() {
 }
 ```
 
+##### Fill a pane of fixed height
+
+Without `height`, a schedule takes the height of its frame: this pane is 480 px, and the schedule is exactly that, bands included. Drag the pane's corner and the schedule follows.
+
+```tsx
+import { useSchedule } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const at = (hours: number) => new Date(2026, 2, 17, hours).getTime();
+
+const ORDERS: Task[] = [{ id: "a-2041", name: "A-2041 Housing", color: "light-dark(#2563eb, #6b9bff)" }];
+
+const STEPS: Subtask[] = [
+  { id: "a-2041-1", task: "a-2041", lane: "saw", from: at(6), to: at(7) },
+  { id: "a-2041-2", task: "a-2041", lane: "mill", from: at(8), to: at(10) },
+  { id: "a-2041-3", task: "a-2041", lane: "qa", from: at(11), to: at(12) },
+];
+
+export default function FillsItsPane() {
+  const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(5), at(13)] } });
+  return (
+    <div data-pane="" style={{ height: 480, resize: "vertical", overflow: "hidden" }}>
+      <Schedule aria-label="Plan of Tuesday in a pane">
+        <Lane id="saw" label="Saw" />
+        <Lane id="mill" label="Mill" />
+        <Lane id="qa" label="Inspection" />
+        <Subtasks data={STEPS} tasks={ORDERS} />
+      </Schedule>
+    </div>
+  );
+}
+```
+
+##### Thirty lanes, a floor of 400 px
+
+In a block with no height, a schedule is 400 px whatever its lanes. The lanes beyond the plot scroll inside it, and the page does not grow.
+
+```tsx
+import { useSchedule } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const at = (hours: number) => new Date(2026, 2, 17, hours).getTime();
+
+const ORDERS: Task[] = [{ id: "round", name: "Round", color: "light-dark(#0d9488, #3cc7b8)" }];
+
+const STATIONS = Array.from({ length: 30 }, (_, index) => ({ id: `s-${index + 1}`, label: `Station ${index + 1}` }));
+
+const STEPS: Subtask[] = STATIONS.map((station, index) => ({
+  id: `round-${index + 1}`,
+  task: "round",
+  lane: station.id,
+  from: at(6 + (index % 6)),
+  to: at(7 + (index % 6)),
+}));
+
+export default function ThirtyLanes() {
+  const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(5), at(14)] } });
+  return (
+    <Schedule aria-label="Round of thirty stations">
+      {STATIONS.map((station) => (
+        <Lane key={station.id} id={station.id} label={station.label} />
+      ))}
+      <Subtasks data={STEPS} tasks={ORDERS} />
+    </Schedule>
+  );
+}
+```
+
+##### Show that a plan is on its way
+
+`loading`, as the chart and the table have it: over a plan the plan stays, dims after a moment and starts no drag, tooltip or key intent until the answer is in; before the first lanes, placeholder lines stand in the lane column.
+
+```tsx
+import { useEffect, useRef, useState } from "react";
+import { Button, Text } from "@umriss-ui/core";
+import { useSchedule } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
+const DAY: readonly [number, number] = [at(6), at(16)];
+
+const TOURS: readonly Task[] = [
+  { id: "t-01", name: "T-01 Harbour", color: "light-dark(#2563eb, #6b9bff)" },
+  { id: "t-03", name: "T-03 Old Town", color: "light-dark(#c2410c, #f08a52)" },
+];
+
+/** Each answer shifts the second tour by a quarter of an hour. */
+function legs(answer: number): readonly Subtask[] {
+  const shift = (answer % 4) * 15;
+  return [
+    { id: "t-01-1", task: "t-01", lane: "van-1", from: at(7), to: at(9) },
+    { id: "t-03-1", task: "t-03", lane: "van-2", from: at(8, shift), to: at(10, shift) },
+    { id: "t-01-2", task: "t-01", lane: "e-van", from: at(11), to: at(13) },
+  ];
+}
+
+const LANES = [
+  { id: "van-1", label: "Van FP 214 K" },
+  { id: "van-2", label: "Van FP 402 R" },
+  { id: "e-van", label: "E-van FP 377 K" },
+];
+
+function Plan({ answer, loading }: { answer: number; loading: boolean }) {
+  const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: DAY } });
+  return (
+    <Schedule aria-label="Tours of the day" height={220} loading={loading} intents={["move", "lane"]}>
+      {LANES.map((lane) => (
+        <Lane key={lane.id} id={lane.id} label={lane.label} />
+      ))}
+      <Subtasks data={legs(answer)} tasks={TOURS} />
+    </Schedule>
+  );
+}
+
+function Waiting() {
+  const { Schedule } = useSchedule({ initialView: { domain: DAY } });
+  return <Schedule aria-label="Tours of the day, loading" height={220} loading />;
+}
+
+export default function Loading() {
+  const [answer, setAnswer] = useState(0);
+  const [loading, setLoading] = useState(false);
+  const pending = useRef<ReturnType<typeof setTimeout> | undefined>(undefined);
+  useEffect(() => () => clearTimeout(pending.current), []);
+
+  const reload = () => {
+    setLoading(true);
+    clearTimeout(pending.current);
+    pending.current = setTimeout(() => {
+      setAnswer((n) => n + 1);
+      setLoading(false);
+    }, 1500);
+  };
+
+  return (
+    <div className="pair">
+      <div>
+        <Text as="p" size="sm" tone="muted">
+          loading over a plan - the answer takes 1.5 s
+        </Text>
+        <Plan answer={answer} loading={loading} />
+        <div className="demo-actions">
+          <Button size="sm" onClick={reload} disabled={loading}>
+            Reload
+          </Button>
+        </div>
+      </div>
+      <div>
+        <Text as="p" size="sm" tone="muted">
+          loading, before the first lanes
+        </Text>
+        <Waiting />
+      </div>
+    </div>
+  );
+}
+```
+
 #### Keyboard
 
 | Key | Action |
@@ -1262,7 +1420,7 @@ export default function MachinePlan() {
 
 #### Accessibility
 
-The schedule is a figure named by `ariaLabel`, and its plot one tab stop with the role `application`, read as "schedule" (`aria-roledescription`), named alike and described by a summary: the lanes, the subtasks in view, the visible span, the findings by kind, then the keys. The canvas is hidden from a reader; the lane headers are text, and a group's fold button is named "Fold group" or "Unfold group" with the group's label. `ariaLabel` is required - name what the plan shows, "Plan of week 38".
+The schedule is a figure named by `aria-label`, 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. `aria-label` 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-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".
 
@@ -1274,14 +1432,14 @@ Under forced colours the plot paints itself in the system colours: the work in t
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `ref` | `Ref<HTMLDivElement> \| undefined` | — | Receives the root element. |
+| `height` | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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 80 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 |
+| `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: [Show that a plan is on its way](#first-schedule), [Read a folded group (Lane groups)](#lane-groups), [Cut the nights out of the axis (Time axis and calendar)](#time-axis-and-calendar) and 19 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) |
@@ -1292,7 +1450,8 @@ Under forced colours the plot paints itself in the system colours: the work in t
 | `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 |
+| `loading` | `boolean` | `false` | The plan is on its way, as the chart's `loading` says ([ADR-0042](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0042-a-rows-height-never-follows-what-it-shows.md)). A plan already drawn stays: it dims after a moment and takes no pointer - no new drag, no tooltip, no intent by key - until the answer is in; a drag begun before finishes and reports. The keys still walk it. With no lanes, placeholder lines stand in the lane column. The plot is `aria-busy` meanwhile.<br>Shown in: [Show that a plan is on its way](#first-schedule) |
+| `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 82 more |
 
 ###### Events
 
@@ -1305,28 +1464,12 @@ Under forced colours the plot paints itself in the system colours: the work in t
 
 | 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](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 78 more |
-
-###### Styling
+| `aria-label` *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 82 more |
 
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `className` | `string` | — | Goes to the root element. |
-| `style` | `CSSProperties` | — | Goes to the root element. |
+Also takes every attribute of `<div>` – without `aria-label`, `children`.
 
 ##### Types on this page
 
-###### `ScheduleHandle`
-
-What a schedule offers a caller imperatively: the arithmetic between a
-point on the screen and a time on a lane. Everything else is props.
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `positionAt` *required* | `(clientX: number, clientY: number) => { time: number; lane: string \| null } \| null` | — | The time and the lane at a client point, or null outside the plot.<br>Shown in: [Place a mark of your own (The handle)](#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`
 
 From `@umriss-ui/charts`.
@@ -1523,11 +1666,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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
+- 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.44.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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Plan
 
@@ -1568,7 +1711,7 @@ const LEGS: Subtask[] = [
 export default function LaneHeaders() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(12)] } });
   return (
-    <Schedule ariaLabel="Two vans of the North depot" height={150} headerWidth={210}>
+    <Schedule aria-label="Two vans of the North depot" height={150} headerWidth={210}>
       <Lane
         id="v1"
         label={
@@ -1632,7 +1775,7 @@ export default function ManyLanes() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(14)] } });
   return (
     <Schedule
-      ariaLabel="Twenty vans, Tuesday morning"
+      aria-label="Twenty vans, Tuesday morning"
       height={300}
       laneHeight={32}
       headerWidth={110}
@@ -1660,8 +1803,8 @@ The keys of [First schedule](#first-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](#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 |
+| `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 82 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 81 more |
 
 ### Lane groups
 
@@ -1708,7 +1851,7 @@ const WORK: Subtask[] = [
 export default function AGroup() {
   const { Schedule, Lane, LaneGroup, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(15)] } });
   return (
-    <Schedule ariaLabel="Two developers in a team, a designer and a tester outside it" height={240} headerWidth={200}>
+    <Schedule aria-label="Two developers in a team, a designer and a tester outside it" height={240} headerWidth={200}>
       <LaneGroup id="developers" label="Developers">
         <Lane id="arjun" label="Arjun Mehta" />
         <Lane id="chloe" label="Chloe Durand" />
@@ -1751,7 +1894,7 @@ const LEGS: Subtask[] = [
 export default function Nesting() {
   const { Schedule, Lane, LaneGroup, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(15)] } });
   return (
-    <Schedule ariaLabel="North depot with its vans and a truck, and a van from Riverside" height={330} headerWidth={200}>
+    <Schedule aria-label="North depot with its vans and a truck, and a van from Riverside" height={330} headerWidth={200}>
       <LaneGroup id="north" label="North depot">
         <LaneGroup id="vans" label="Vans">
           <Lane id="fp-214" label={`Van ${plate("FP 214 K")}`} />
@@ -1804,7 +1947,7 @@ export default function FoldFromOutside() {
           Unfold everything
         </Button>
       </Stack>
-      <Schedule ariaLabel="Two teams rolling out a release, folded from outside" height={280}>
+      <Schedule aria-label="Two teams rolling out a release, folded from outside" height={280}>
         <LaneGroup id="payments" label="Payments">
           <Lane id="priya" label="Priya Raman" />
           <Lane id="jonas" label="Jonas Keller" />
@@ -1876,7 +2019,7 @@ export default function TheMiniature() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="A depot that folds into one row"
+        aria-label="A depot that folds into one row"
         height={240}
         intents={["move", "lane"]}
         onIntent={(intent) => {
@@ -1931,7 +2074,7 @@ const WORK: Subtask[] = [
 export default function StartWithGroupsFolded() {
   const { Schedule, Lane, LaneGroup, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(15)], folded: ["discovery"] } });
   return (
-    <Schedule ariaLabel="Two teams rolling out a release, Discovery folded at the start" height={280}>
+    <Schedule aria-label="Two teams rolling out a release, Discovery folded at the start" height={280}>
       <LaneGroup id="payments" label="Payments">
         <Lane id="priya" label="Priya Raman" />
         <Lane id="jonas" label="Jonas Keller" />
@@ -1969,7 +2112,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Subtasks
 
@@ -2005,7 +2148,7 @@ const ROUNDS: Subtask[] = [
 export default function LeadInAndLeadOut() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6), at(14, 30)] } });
   return (
-    <Schedule ariaLabel="Three rounds of one van" height={110}>
+    <Schedule aria-label="Three rounds of one van" height={110}>
       <Lane id="van" label="Van FP 214 K" />
       <Subtasks data={ROUNDS} tasks={TOURS} />
     </Schedule>
@@ -2043,7 +2186,7 @@ const WORK: Subtask[] = [
 export default function TaskColours() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(16, 6), at(20, 20)] } });
   return (
-    <Schedule ariaLabel="Projects due this week among the rest" height={150}>
+    <Schedule aria-label="Projects due this week among the rest" height={150}>
       <Lane id="chloe" label="Chloe Durand" />
       <Lane id="eva" label="Eva Novak" />
       <Subtasks data={WORK} tasks={PROJECTS} />
@@ -2149,7 +2292,7 @@ const SPRINT_14: readonly [number, number] = [new Date(2026, 2, 9, 6).getTime(),
 export default function ASprint() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: SPRINT_14 } });
   return (
-    <Schedule ariaLabel="Sprint 14, 9 to 20 March" height={500} label={(s) => s.name ?? s.id}>
+    <Schedule aria-label="Sprint 14, 9 to 20 March" height={500} label={(s) => s.name ?? s.id}>
       {PEOPLE.map((person) => (
         <Lane key={person.id} id={person.id} label={person.name} />
       ))}
@@ -2169,18 +2312,18 @@ The keys of [First schedule](#first-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `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 82 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 82 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), [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 |
+| `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 79 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 75 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 75 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 75 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 75 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 |
@@ -2191,9 +2334,9 @@ The keys of [First schedule](#first-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `id` *required* | `string` | — | The caller's identity of the task.<br>Shown in: [Main time, lead-in and lead-out](#subtasks), [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 |
+| `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 74 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 74 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 74 more |
 
 ##### Types on this page
 
@@ -2256,7 +2399,7 @@ export default function BarLabels() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: DAY } });
   return (
     <Schedule
-      ariaLabel="Tuesday, 17 March, with the work items written in"
+      aria-label="Tuesday, 17 March, with the work items written in"
       height={196}
       label={(subtask) => subtask.name ?? subtask.id}
     >
@@ -2279,7 +2422,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -2287,7 +2430,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -2371,7 +2514,7 @@ const WORK: Subtask[] = [
 export default function Provisional() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
-    <Schedule ariaLabel="Agreed work above, provisional work below" height={144}>
+    <Schedule aria-label="Agreed work above, provisional work below" height={144}>
       <Lane id="released" label="Agreed, with lead-in" />
       <Lane id="draft" label="Provisional" />
       <Subtasks data={WORK} tasks={PROJECTS} />
@@ -2401,7 +2544,7 @@ export default function Fixed() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
     <Schedule
-      ariaLabel="A round that may move above, a booked slot below"
+      aria-label="A round that may move above, a booked slot below"
       height={144}
       label={(leg) => (leg.id === "nailed" ? "T-05 · booked slot" : "T-05")}
     >
@@ -2435,7 +2578,7 @@ export default function Muted() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
     <Schedule
-      ariaLabel="Our team's work above, another team's below"
+      aria-label="Our team's work above, another team's below"
       height={144}
       label={() => "Checkout migration"}
     >
@@ -2468,7 +2611,7 @@ const WORK: Subtask[] = [
 export default function Progress() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
-    <Schedule ariaLabel="Work claiming nothing above, work at 65 per cent below" height={144}>
+    <Schedule aria-label="Work claiming nothing above, work at 65 per cent below" height={144}>
       <Lane id="unclaimed" label="Says nothing" />
       <Lane id="started" label="65 per cent done" />
       <Subtasks data={WORK} tasks={PROJECTS} />
@@ -2501,7 +2644,7 @@ const WORK: Subtask[] = [
 export default function Open() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
-    <Schedule ariaLabel="Work running past the view at either edge" height={188}>
+    <Schedule aria-label="Work running past the view at either edge" height={188}>
       <Lane id="runs-on" label="Runs on" />
       <Lane id="whole" label="Wholly in view" />
       <Lane id="began" label="Began before" />
@@ -2567,7 +2710,7 @@ export default function Combinations() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
     <Schedule
-      ariaLabel="Bars carrying several appearances at once"
+      aria-label="Bars carrying several appearances at once"
       height={230}
       label={(leg) => NAMES[leg.id] ?? leg.id}
     >
@@ -2590,7 +2733,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -2598,7 +2741,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -2684,7 +2827,7 @@ const WORK: Subtask[] = [
 export default function DoubleBooking() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(8), at(16)] } });
   return (
-    <Schedule ariaLabel="Kofi booked on two projects at once" height={150}>
+    <Schedule aria-label="Kofi booked on two projects at once" height={150}>
       <Lane id="kofi" label="Kofi Mensah" />
       <Lane id="hana" label="Hana Sato" />
       <Subtasks data={WORK} tasks={PROJECTS} />
@@ -2717,7 +2860,7 @@ const LEGS: Subtask[] = [
 export default function LeadOutMeetsLeadIn() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(6, 30), at(11, 30)] } });
   return (
-    <Schedule ariaLabel="Two rounds of one van, touching at unloading and loading" height={110}>
+    <Schedule aria-label="Two rounds of one van, touching at unloading and loading" height={110}>
       <Lane id="fp-402" label="Van FP 402 R" />
       <Subtasks data={LEGS} tasks={TOURS} />
     </Schedule>
@@ -2751,7 +2894,7 @@ const WORK: Subtask[] = [
 export default function ThreeAtOnce() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(7), at(14)] } });
   return (
-    <Schedule ariaLabel="Priya on three incidents at once" height={150}>
+    <Schedule aria-label="Priya on three incidents at once" height={150}>
       <Lane id="priya" label="Priya Raman" />
       <Lane id="jonas" label="Jonas Keller" />
       <Subtasks data={WORK} tasks={INCIDENTS} />
@@ -2774,14 +2917,14 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -2833,7 +2976,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - 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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Dependencies
 
@@ -2882,7 +3025,7 @@ const DRIVES: Dependency[] = [
 export default function StopsOfATour() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(7), at(10)] } });
   return (
-    <Schedule ariaLabel="Two morning tours with their stops" height={150}>
+    <Schedule aria-label="Two morning tours with their stops" height={150}>
       <Lane id="fp-214" label="Van FP 214 K" />
       <Lane id="fp-377" label="E-van FP 377 K" />
       <Dependencies data={DRIVES} />
@@ -2926,7 +3069,7 @@ const HANDOVERS: Dependency[] = [
 export default function Anchors() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(16, 30)] } });
   return (
-    <Schedule ariaLabel="Two handovers with different anchors" height={150}>
+    <Schedule aria-label="Two handovers with different anchors" height={150}>
       <Lane id="truck" label="Truck FP 520 E" />
       <Lane id="van" label="Van FP 290 E" />
       <Dependencies data={HANDOVERS} />
@@ -2974,7 +3117,7 @@ function Variant({ attach }: { attach: DependencyAttachment }) {
       <Text size="xs" tone="muted" mono>
         attach=&quot;{attach}&quot;
       </Text>
-      <Schedule ariaLabel={`A release through three engineers, lines from the ${attach}`} height={188} attach={attach}>
+      <Schedule aria-label={`A release through three engineers, lines from the ${attach}`} height={188} attach={attach}>
         <Lane id="priya" label="Priya Raman" />
         <Lane id="ada" label="Ada Mwangi" />
         <Lane id="sam" label="Sam Okafor" />
@@ -3030,7 +3173,7 @@ function Variant({ ends }: { ends: DependencyEnds }) {
       <Text size="xs" tone="muted" mono>
         ends=&quot;{ends}&quot;
       </Text>
-      <Schedule ariaLabel={`Design, build and test, ends ${ends}`} height={188} attach="nearest" ends={ends}>
+      <Schedule aria-label={`Design, build and test, ends ${ends}`} height={188} attach="nearest" ends={ends}>
         <Lane id="noah" label="Noah Fischer" />
         <Lane id="arjun" label="Arjun Mehta" />
         <Lane id="eva" label="Eva Novak" />
@@ -3077,7 +3220,7 @@ const HANDOVERS: Dependency[] = [{ id: "transfer", from: "line-haul", to: "round
 export default function ViolatedDependency() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(11)] } });
   return (
-    <Schedule ariaLabel="A handover from the truck to the van that is too short" height={150}>
+    <Schedule aria-label="A handover from the truck to the van that is too short" height={150}>
       <Lane id="truck" label="Truck FP 118 R" />
       <Lane id="van" label="Van FP 214 K" />
       <Dependencies data={HANDOVERS} />
@@ -3120,7 +3263,7 @@ const HANDOVERS: Dependency[] = [
 export default function OneHandoverDrawnItsOwnWay() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(12, 30)] } });
   return (
-    <Schedule ariaLabel="Design, build, test and a sign-off drawn its own way" height={188} attach="nearest" ends="none">
+    <Schedule aria-label="Design, build, test and a sign-off drawn its own way" height={188} attach="nearest" ends="none">
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="arjun" label="Arjun Mehta" />
       <Lane id="eva" label="Eva Novak" />
@@ -3203,9 +3346,9 @@ type DependencyEnds = "dot" | "none";
 
 #### Known limits
 
-- 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)).
+- 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.44.0/docs/adr/0032-what-umriss-is-not.md)).
 
-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).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Routes
 
@@ -3246,7 +3389,7 @@ const HANDOVERS: Dependency[] = [
 export default function Curve() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(13, 30)] } });
   return (
-    <Schedule ariaLabel="Search results, from layout to polish, curved lines" height={188}>
+    <Schedule aria-label="Search results, from layout to polish, curved lines" height={188}>
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="chloe" label="Chloe Durand" />
       <Lane id="eva" label="Eva Novak" />
@@ -3286,7 +3429,7 @@ const HANDOVERS: Dependency[] = [
 export default function Straight() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(13, 30)] } });
   return (
-    <Schedule ariaLabel="Search results, from layout to polish, straight lines" height={188} route="straight" attach="nearest">
+    <Schedule aria-label="Search results, from layout to polish, straight lines" height={188} route="straight" attach="nearest">
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="chloe" label="Chloe Durand" />
       <Lane id="eva" label="Eva Novak" />
@@ -3326,7 +3469,7 @@ const HANDOVERS: Dependency[] = [
 export default function Orthogonal() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(13, 30)] } });
   return (
-    <Schedule ariaLabel="Search results, from layout to polish, orthogonal lines" height={188} route="orthogonal" attach="nearest">
+    <Schedule aria-label="Search results, from layout to polish, orthogonal lines" height={188} route="orthogonal" attach="nearest">
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="chloe" label="Chloe Durand" />
       <Lane id="eva" label="Eva Novak" />
@@ -3367,7 +3510,7 @@ const HANDOVERS: Dependency[] = [
 export default function PerDependency() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(6, 30), at(13, 30)] } });
   return (
-    <Schedule ariaLabel="Search results, from layout to polish, straight lines but one" height={188} route="straight" attach="nearest">
+    <Schedule aria-label="Search results, from layout to polish, straight lines but one" height={188} route="straight" attach="nearest">
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="chloe" label="Chloe Durand" />
       <Lane id="eva" label="Eva Novak" />
@@ -3388,7 +3531,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -3397,7 +3540,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -3538,7 +3681,7 @@ const WEEK: readonly [number, number] = [new Date(2026, 2, 16).getTime(), new Da
 export default function AWeek() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: WEEK } });
   return (
-    <Schedule ariaLabel="On-call rota, 16 to 23 March" height={420}>
+    <Schedule aria-label="On-call rota, 16 to 23 March" height={420}>
       {ENGINEERS.map((engineer) => (
         <Lane key={engineer.id} id={engineer.id} label={engineer.name} />
       ))}
@@ -3582,7 +3725,7 @@ export default function WorkingCalendar() {
   const [legs, setLegs] = useState<readonly Subtask[]>(LEGS);
   return (
     <Schedule
-      ariaLabel="Three days at East Gate depot, nights removed"
+      aria-label="Three days at East Gate depot, nights removed"
       calendar={OPENING_HOURS}
       height={220}
       intents={["move"]}
@@ -3693,7 +3836,7 @@ export default function OfficeHours() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(9, 9), at(20, 17)] } });
   return (
     <Schedule
-      ariaLabel="Sprint 14 of the web team, office hours only"
+      aria-label="Sprint 14 of the web team, office hours only"
       calendar={OFFICE_HOURS}
       height={280}
       label={(item) => item.name ?? item.id}
@@ -3721,7 +3864,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -3737,7 +3880,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -3870,7 +4013,7 @@ export default function Leave() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Team plan, week of 16 March" height={240}>
+      <Schedule aria-label="Team plan, week of 16 March" height={240}>
         {PEOPLE.map((person) => (
           <Lane key={person.id} id={person.id} label={person.label} />
         ))}
@@ -3936,7 +4079,7 @@ export default function DragAround() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Two people, one on leave"
+        aria-label="Two people, one on leave"
         height={150}
         intents={["move", "lane"]}
         onIntent={onIntent}
@@ -4071,7 +4214,7 @@ export default function TeamLeave() {
   const clashes = findings(WORK, [], BLOCKED).inBlockedTime;
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Sprint 14 with the team's leave" height={500}>
+      <Schedule aria-label="Sprint 14 with the team's leave" height={500}>
         {PEOPLE.map((person) => (
           <Lane key={person.id} id={person.id} label={person.name} />
         ))}
@@ -4171,7 +4314,7 @@ export default function HandoversAndReleases() {
   const { Schedule, Lane, Subtasks, Milestones } = useSchedule({ initialView: { domain: [day(0, 6), day(5, 0)] } });
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Portal and billing plan, week of 16 March" height={188}>
+      <Schedule aria-label="Portal and billing plan, week of 16 March" height={188}>
         <Lane id="anna" label="Anna Berg" />
         <Lane id="ben" label="Ben Ortiz" />
         <Lane id="chloe" label="Chloe Lind" />
@@ -4223,7 +4366,7 @@ function Own({ target }: { target: ScheduleTooltipTarget }) {
 export default function SayWhatAMilestoneIs() {
   const { Schedule, Lane, Subtasks, Milestones } = useSchedule({ initialView: { domain: [at(6, 30), at(15, 30)] } });
   return (
-    <Schedule ariaLabel="Build and test around the code freeze" height={150} tooltip={(target) => <Own target={target} />}>
+    <Schedule aria-label="Build and test around the code freeze" height={150} tooltip={(target) => <Own target={target} />}>
       <Lane id="arjun" label="Arjun Mehta" />
       <Lane id="eva" label="Eva Novak" />
       <Subtasks data={WORK} tasks={PROJECTS} />
@@ -4422,7 +4565,7 @@ const ROUNDS: Subtask[] = TOURS.map((tour) => ({
 export default function NowLine() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
   return (
-    <Schedule ariaLabel="Today's tours, with the present" height={420} now={NOW}>
+    <Schedule aria-label="Today's tours, with the present" height={420} now={NOW}>
       {VEHICLES.map((vehicle) => (
         <Lane key={vehicle.id} id={vehicle.id} label={vehicle.plate} />
       ))}
@@ -4462,7 +4605,7 @@ const DUTIES: Subtask[] = [
 export default function FollowTheClock() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [current - 6 * HOUR, current + 6 * HOUR] } });
   return (
-    <Schedule ariaLabel="Today's on-call rota, with the present" height={188} now>
+    <Schedule aria-label="Today's on-call rota, with the present" height={188} now>
       <Lane id="ada" label="Ada Mwangi" />
       <Lane id="tomasz" label="Tomasz Nowak" />
       <Lane id="leila" label="Leila Haddad" />
@@ -4482,7 +4625,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -4490,7 +4633,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -4587,7 +4730,7 @@ export default function PanAndZoom() {
   const { Schedule, Lane, Subtasks } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
   return (
     <Schedule
-      ariaLabel="A plan to pan and zoom"
+      aria-label="A plan to pan and zoom"
       height={196}
       zoomLimits={{ min: 2 * HOUR, max: 48 * HOUR }}
     >
@@ -4615,7 +4758,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -4623,7 +4766,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -4723,7 +4866,7 @@ const TRANSFERS: readonly Dependency[] = [
 export default function SelectATask() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(5, 30), at(13, 30)] } });
   return (
-    <Schedule ariaLabel="Two consignments at North depot" height={140}>
+    <Schedule aria-label="Two consignments at North depot" height={140}>
       <Lane id="truck-118" label="Truck FP 118 R" />
       <Lane id="van-214" label="Van FP 214 K" />
       <Dependencies data={TRANSFERS} />
@@ -4787,7 +4930,7 @@ export default function ControlTheSelection() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Legs at North depot on Tuesday, 17 March"
+        aria-label="Legs at North depot on Tuesday, 17 March"
         height={284}
         selectedTask={selected}
         onSelectedTaskChange={(task, subtask) => {
@@ -4832,7 +4975,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -4841,7 +4984,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -4908,7 +5051,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - One task at a time: there is no multiple selection.
 
-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).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Interactions
 
@@ -4970,7 +5113,7 @@ export default function ReportThePointer() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="One consignment on a truck and a van"
+        aria-label="One consignment on a truck and a van"
         height={152}
         onInteraction={(interaction) => setLast(describe(interaction))}
       >
@@ -5070,7 +5213,7 @@ export default function OpenAContextMenu() {
   return (
     <>
       <Schedule
-        ariaLabel="On-call rota, 16 to 23 March"
+        aria-label="On-call rota, 16 to 23 March"
         height={420}
         onInteraction={onInteraction}
       >
@@ -5085,7 +5228,7 @@ export default function OpenAContextMenu() {
         onOpenChange={(open) => {
           if (!open) setMenu(null);
         }}
-        ariaLabel={menu !== null ? `Hand over ${menu.duty.id}` : "Hand over"}
+        aria-label={menu !== null ? `Hand over ${menu.duty.id}` : "Hand over"}
       >
         {menu !== null &&
           ENGINEERS.filter((engineer) => engineer.id !== menu.duty.lane).map((engineer) => (
@@ -5108,7 +5251,7 @@ export default function OpenAContextMenu() {
 #### When to use something else
 
 - You only need to know which task was picked → Selection
-- You need the time at a point outside an interaction → The handle
+- You need the time at a point outside an interaction → Functions on the hook
 
 #### Keyboard
 
@@ -5122,8 +5265,8 @@ The keys of [First schedule](#first-schedule) apply here.
 |---|---|---|---|
 | `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) |
+| `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 (Functions on the hook)](#functions-on-the-hook), [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 (Functions on the hook)](#functions-on-the-hook), [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) |
 
@@ -5195,7 +5338,7 @@ const TRANSFERS: readonly Dependency[] = [
 export default function DefaultTooltip() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
   return (
-    <Schedule ariaLabel="Three vehicles with the default tooltip" height={196}>
+    <Schedule aria-label="Three vehicles with the default tooltip" height={196}>
       {VEHICLES.map((vehicle) => (
         <Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
       ))}
@@ -5268,7 +5411,7 @@ export default function OwnTooltip() {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
   return (
     <Schedule
-      ariaLabel="Three vehicles with the load in the tooltip"
+      aria-label="Three vehicles with the load in the tooltip"
       height={196}
       tooltip={(target) => <LoadTooltip target={target} />}
     >
@@ -5388,7 +5531,7 @@ export default function DetailPanelInstead() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Sprint 14 of the web team"
+        aria-label="Sprint 14 of the web team"
         height={260}
         tooltip={false}
         onInteraction={onInteraction}
@@ -5488,7 +5631,7 @@ function Covers({ target }: { target: ScheduleTooltipTarget }) {
 export default function SayWhatABarCoversAndALineJoins() {
   const { Schedule, Lane, Subtasks, Dependencies, BlockedTimes } = useSchedule({ initialView: { domain: [at(6, 30), at(15, 30)] } });
   return (
-    <Schedule ariaLabel="Design, build and test, with leave under the build" height={188} tooltip={(target) => <Covers target={target} />}>
+    <Schedule aria-label="Design, build and test, with leave under the build" height={188} tooltip={(target) => <Covers target={target} />}>
       <Lane id="noah" label="Noah Fischer" />
       <Lane id="arjun" label="Arjun Mehta" />
       <Lane id="eva" label="Eva Novak" />
@@ -5593,7 +5736,7 @@ export default function KeepAndRestore() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Two teams on Tuesday, 17 March" height={290}>
+      <Schedule aria-label="Two teams on Tuesday, 17 March" height={290}>
         <LaneGroup id="product" label="Product">
           <Lane id="noah" label="Noah Fischer" />
           <Lane id="arjun" label="Arjun Mehta" />
@@ -5650,7 +5793,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `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 82 more |
 
 ###### Events
 
@@ -5662,7 +5805,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 | 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), [The smallest schedule (Installation)](#installation), [A day of tours (First schedule)](#first-schedule) and 77 more |
+| `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 81 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
@@ -5735,13 +5878,13 @@ export default function InStep() {
   const span = diesel.view.domain ?? start.domain;
   return (
     <Stack gap={2}>
-      <diesel.Schedule ariaLabel="Diesel vehicles on Tuesday, 17 March" height={240}>
+      <diesel.Schedule aria-label="Diesel vehicles on Tuesday, 17 March" height={240}>
         {DIESEL.map((vehicle) => (
           <diesel.Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
         ))}
         <diesel.Subtasks data={DIESEL_LEGS} tasks={CONSIGNMENTS} />
       </diesel.Schedule>
-      <electric.Schedule ariaLabel="Electric vans, the same hours" height={152}>
+      <electric.Schedule aria-label="Electric vans, the same hours" height={152}>
         {ELECTRIC.map((vehicle) => (
           <electric.Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
         ))}
@@ -5894,12 +6037,12 @@ export default function RotaBesideIncidents() {
   const incidents: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => rota.setView(v) });
   return (
     <Stack gap={2}>
-      <rota.Schedule ariaLabel="Who was on call" height={140}>
+      <rota.Schedule aria-label="Who was on call" height={140}>
         <rota.Lane id="primary" label="Primary" />
         <rota.Lane id="secondary" label="Secondary" />
         <rota.Subtasks data={DUTIES} tasks={PEOPLE} />
       </rota.Schedule>
-      <incidents.Schedule ariaLabel="Incidents, the same hours" height={290}>
+      <incidents.Schedule aria-label="Incidents, the same hours" height={290}>
         {HIT.map((service) => (
           <incidents.Lane key={service.id} id={service.id} label={service.name} />
         ))}
@@ -5924,14 +6067,14 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -5990,9 +6133,9 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - 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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
-### The handle
+### Functions on the hook
 
 Converts between a point on the screen and a time on a lane, so marks of your own - a cut-off, a delivery window, a pin - stand at the right place beside the plan.
 
@@ -6000,10 +6143,12 @@ Converts between a point on the screen and a time on a lane, so marks of your ow
 import { useSchedule } from "@umriss-ui/schedule";
 ```
 
-The handle holds three functions and nothing else: `clientPointOf(time, lane?)`, `positionAt(clientX, clientY)` and `visibleDomain()`. Everything else the schedule does is props.
+[`useSchedule`](#api-index-1) hands back three functions for what is on the screen: `clientPointOf(time, lane?)`, `positionAt(clientX, clientY)` and `visibleDomain()`. Before a schedule is mounted the first two answer `null`. The `ref` of `Schedule` is its root element.
 
 Place your marks again whenever `view.domain` changes.
 
+`scrollToLane(lane)`, `scrollToSubtask(id)` and `focusSubtask(id)` show a lane or a subtask picked from a list of your own, a findings list or a search. `scrollToSubtask` brings the lane and the time into view and leaves the focus where it is; `focusSubtask` also makes the subtask the active one and focuses the plot. All three answer `false`, and change nothing, for an unknown lane or subtask, a lane inside a folded group (none is unfolded) and a schedule that is not mounted.
+
 #### Examples
 
 ##### Place a mark of your own
@@ -6014,7 +6159,7 @@ Place your marks again whenever `view.domain` changes.
 import { useEffect, useRef, useState } from "react";
 import { Stack, Text } from "@umriss-ui/core";
 import { useSchedule } from "@umriss-ui/schedule";
-import type { ScheduleHandle, Subtask, Task } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
 
 const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
 const min = (n: number) => n * 60_000;
@@ -6043,18 +6188,17 @@ const CUT_OFF = at(14);
 const clock = (time: number) => new Date(time).toLocaleTimeString("en-GB", { hour: "2-digit", minute: "2-digit" });
 
 export default function PlaceAMark() {
-  const { Schedule, Lane, Subtasks, view } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
-  const plan = useRef<ScheduleHandle>(null);
+  const { Schedule, Lane, Subtasks, view, clientPointOf, positionAt } = useSchedule({ initialView: { domain: [at(5, 30), at(18)] } });
   const host = useRef<HTMLDivElement>(null);
   const [pin, setPin] = useState<number | null>(null);
   const [under, setUnder] = useState("Move the pointer over the plan");
 
   /* The client point, turned into one inside this example - anew whenever the span moves. */
   useEffect(() => {
-    const point = plan.current?.clientPointOf(CUT_OFF);
+    const point = clientPointOf(CUT_OFF);
     const left = host.current?.getBoundingClientRect().left;
     setPin(point == null || left === undefined ? null : point.x - left);
-  }, [view.domain]);
+  }, [view.domain, clientPointOf]);
 
   return (
     <Stack gap={2}>
@@ -6066,13 +6210,12 @@ export default function PlaceAMark() {
         )}
       </div>
       <Schedule
-        ref={plan}
-        ariaLabel="Three vehicles with a cut-off of the application's own"
+        aria-label="Three vehicles with a cut-off of the application's own"
         height={196}
         onInteraction={(interaction) => {
           /* The interaction carries time and lane already; `positionAt` is for
              listeners of your own, which have only a point. */
-          const there = plan.current?.positionAt(interaction.clientX, interaction.clientY);
+          const there = positionAt(interaction.clientX, interaction.clientY);
           setUnder(there == null ? "off the plan" : `${clock(there.time)} on ${there.lane ?? "no lane"}`);
         }}
       >
@@ -6089,6 +6232,69 @@ export default function PlaceAMark() {
 }
 ```
 
+##### Show a finding
+
+`scrollToSubtask` brings a subtask's lane and time into view and leaves the focus; `focusSubtask` also makes it the active subtask. Pick a finding, or press Enter on it.
+
+```tsx
+import { Button, Stack, Text } from "@umriss-ui/core";
+import { useSchedule } from "@umriss-ui/schedule";
+import type { Subtask, Task } from "@umriss-ui/schedule";
+
+const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
+
+const STATIONS = Array.from({ length: 60 }, (_, i) => ({ id: `station-${i + 1}`, label: `Station ${String(i + 1).padStart(2, "0")}` }));
+
+const ORDERS: readonly Task[] = [{ id: "order", name: "Order O-7731", color: "light-dark(#2563eb, #6b9bff)" }];
+
+const STEPS: readonly Subtask[] = STATIONS.map((station, i) => ({
+  id: `step-${i + 1}`,
+  task: "order",
+  lane: station.id,
+  from: at(6 + (i % 10)),
+  to: at(7 + (i % 10)),
+}));
+
+const FINDINGS = [
+  { subtask: "step-4", text: "Station 04 starts before its material arrives" },
+  { subtask: "step-37", text: "Station 37 overlaps a shift break" },
+  { subtask: "step-58", text: "Station 58 ends after the cut-off" },
+];
+
+export default function ShowAFinding() {
+  const { Schedule, Lane, Subtasks, scrollToSubtask, focusSubtask } = useSchedule({ initialView: { domain: [at(5, 30), at(10)] } });
+  return (
+    <Stack gap={2}>
+      <Stack gap={1} data-findings>
+        {FINDINGS.map((finding) => (
+          <Button
+            key={finding.subtask}
+            data-finding={finding.subtask}
+            onClick={() => scrollToSubtask(finding.subtask)}
+            onKeyDown={(event) => {
+              if (event.key !== "Enter") return;
+              event.preventDefault();
+              focusSubtask(finding.subtask);
+            }}
+          >
+            {finding.text}
+          </Button>
+        ))}
+      </Stack>
+      <Schedule aria-label="Sixty stations of one order" height={240}>
+        {STATIONS.map((station) => (
+          <Lane key={station.id} id={station.id} label={station.label} />
+        ))}
+        <Subtasks data={STEPS} tasks={ORDERS} />
+      </Schedule>
+      <Text size="sm" tone="muted">
+        A click shows the subtask; Enter also moves the focus to the plot.
+      </Text>
+    </Stack>
+  );
+}
+```
+
 #### When to use something else
 
 - You need the time under the pointer during a hover or a click → Interactions
@@ -6103,8 +6309,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`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. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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
@@ -6117,7 +6322,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -6223,7 +6428,7 @@ export default function ListTheFindings() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Three people's week with its findings" height={184}>
+      <Schedule aria-label="Three people's week with its findings" height={184}>
         <Lane id="noah" label="Noah Fischer" />
         <Lane id="chloe" label="Chloe Durand" />
         <Lane id="arjun" label="Arjun Mehta" />
@@ -6278,7 +6483,7 @@ export default function NothingToFix() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Two developers' week, without findings" height={140}>
+      <Schedule aria-label="Two developers' week, without findings" height={140}>
         <Lane id="hana" label="Hana Sato" />
         <Lane id="kofi" label="Kofi Mensah" />
         <Subtasks data={WORK} tasks={PROJECTS} />
@@ -6335,7 +6540,7 @@ export default function CountPerKind() {
         <Badge tone={doubleBooked > 0 ? "warning" : "success"}>{doubleBooked} double-booked</Badge>
         <Badge tone={late > 0 ? "warning" : "success"}>{late} transfers too short</Badge>
       </Stack>
-      <Schedule ariaLabel="The day's legs with their findings counted" height={196}>
+      <Schedule aria-label="The day's legs with their findings counted" height={196}>
         {VEHICLES.map((vehicle) => (
           <Lane key={vehicle.id} id={vehicle.id} label={vehicle.label} />
         ))}
@@ -6386,7 +6591,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - 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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Editing
 
@@ -6431,7 +6636,7 @@ export default function MoveInTime() {
   const [work, setWork] = useState(START);
   return (
     <Schedule
-      ariaLabel="Two people's work this week"
+      aria-label="Two people's work this week"
       height={140}
       intents={["move"]}
       onIntent={(intent) => setWork((current) => current.map((item) => applyIntent(item, intent)))}
@@ -6494,7 +6699,7 @@ export default function MoveToAnotherLane() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Five vehicles on Tuesday, 17 March, editable"
+        aria-label="Five vehicles on Tuesday, 17 March, editable"
         height={284}
         intents={["move", "lane"]}
         onIntent={(intent) => {
@@ -6634,7 +6839,7 @@ export default function RefuseADoubleBooking() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Sprint 14 of the web team, editable"
+        aria-label="Sprint 14 of the web team, editable"
         height={240}
         intents={["move", "lane"]}
         onIntent={onIntent}
@@ -6673,7 +6878,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -6687,7 +6892,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -6761,10 +6966,10 @@ From `Overlap` — the full table stands on [Findings as data](#findings-as-data
 
 #### Known limits
 
-- 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)).
+- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Stretch, lead-in, lead-out
 
@@ -6803,7 +7008,7 @@ export default function StretchTheMainTime() {
   const [work, setWork] = useState(START);
   return (
     <Schedule
-      ariaLabel="Two estimates to adjust"
+      aria-label="Two estimates to adjust"
       height={140}
       intents={["stretch"]}
       onIntent={(intent) => setWork((current) => current.map((item) => applyIntent(item, intent)))}
@@ -6842,7 +7047,7 @@ export default function ChangeLeadInAndLeadOut() {
 
   return (
     <Schedule
-      ariaLabel="Two tours from North depot"
+      aria-label="Two tours from North depot"
       height={150}
       intents={["stretch", "leadIn", "leadOut"]}
       onIntent={(intent) => setTours((current) => current.map((tour) => applyIntent(tour, intent)))}
@@ -6869,7 +7074,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -6883,7 +7088,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -6936,7 +7141,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A main time never becomes shorter than one raster step, or a minute without a raster.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Snapping
 
@@ -6972,7 +7177,7 @@ export default function SnapToTheTicks() {
   const [tours, setTours] = useState(START);
   return (
     <Schedule
-      ariaLabel="A tour on the default raster"
+      aria-label="A tour on the default raster"
       height={100}
       intents={["move"]}
       onIntent={(intent) => setTours((current) => current.map((tour) => applyIntent(tour, intent)))}
@@ -7008,7 +7213,7 @@ export default function SnapToADuration() {
   const [work, setWork] = useState(START);
   return (
     <Schedule
-      ariaLabel="Work planned in half days"
+      aria-label="Work planned in half days"
       height={140}
       snap={HALF_DAY}
       intents={["move", "stretch"]}
@@ -7046,7 +7251,7 @@ export default function SnapToHandovers() {
   const [watches, setWatches] = useState(START);
   return (
     <Schedule
-      ariaLabel="An on-call watch on the handover raster"
+      aria-label="An on-call watch on the handover raster"
       height={110}
       snap={HANDOVERS}
       intents={["move"]}
@@ -7079,7 +7284,7 @@ export default function NoSnapping() {
   const [windows, setWindows] = useState(START);
   return (
     <Schedule
-      ariaLabel="A maintenance window placed freely"
+      aria-label="A maintenance window placed freely"
       height={100}
       snap={false}
       intents={["move"]}
@@ -7102,7 +7307,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -7117,7 +7322,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -7261,7 +7466,7 @@ export default function DragFromTheBacklog() {
         ))}
       </Stack>
       <Schedule
-        ariaLabel="Today's plan of three people, with the backlog beside it"
+        aria-label="Today's plan of three people, with the backlog beside it"
         height={196}
         intents={["place", "move", "lane"]}
         placing={placing}
@@ -7295,7 +7500,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -7310,7 +7515,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -7436,7 +7641,7 @@ export default function LanesThatFit() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="Two cooled vans and a dry van"
+        aria-label="Two cooled vans and a dry van"
         height={190}
         intents={["move", "lane"]}
         canMoveTo={mayGo}
@@ -7522,7 +7727,7 @@ export default function DraggedIn() {
         </div>
       </Card>
       <Schedule
-        ariaLabel="A chilled delivery waiting beside two cooled vans and a dry van"
+        aria-label="A chilled delivery waiting beside two cooled vans and a dry van"
         height={190}
         intents={["place"]}
         placing={placing}
@@ -7679,7 +7884,7 @@ export default function AroundLeave() {
   return (
     <Stack gap={3}>
       <Schedule
-        ariaLabel="The apps team this week, with leave"
+        aria-label="The apps team this week, with leave"
         height={236}
         intents={["move", "lane"]}
         canMoveTo={mayGo}
@@ -7713,7 +7918,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
@@ -7729,7 +7934,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -7795,7 +8000,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A rule that changes while a drag runs is noticed at the drop, not before.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Ripple
 
@@ -7852,7 +8057,7 @@ export default function PushTheLaterStops() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Tour T-01 on van FP 214 K" height={100}>
+      <Schedule aria-label="Tour T-01 on van FP 214 K" height={100}>
         <Lane id="van-214" label="Van FP 214 K" />
         <Dependencies data={DRIVES} />
         <Subtasks data={stops} tasks={TOURS} />
@@ -7921,7 +8126,7 @@ export default function MoveAWholeTour() {
 
   return (
     <Stack gap={3}>
-      <Schedule ariaLabel="Two tours from North depot" height={140}>
+      <Schedule aria-label="Two tours from North depot" height={140}>
         <Lane id="van-214" label="Van FP 214 K" />
         <Lane id="van-377" label="E-van FP 377 K" />
         <Dependencies data={DRIVES} />
@@ -7977,7 +8182,7 @@ export default function RippleOnEveryDrag() {
 
   return (
     <Schedule
-      ariaLabel="Design, build and test of the shop search, rippling"
+      aria-label="Design, build and test of the shop search, rippling"
       height={184}
       intents={["move", "stretch"]}
       onIntent={onIntent}
@@ -8002,7 +8207,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -8016,7 +8221,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -8080,10 +8285,10 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 #### Known limits
 
-- 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)).
+- 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.44.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://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://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Measuring
 
@@ -8298,7 +8503,7 @@ const RUNS = [
 function Plot({ data, onInteraction }: { data: Plan; onInteraction: (e: ScheduleInteraction) => void }) {
   const { Schedule, Lane, Subtasks, Dependencies } = useSchedule({ initialView: { domain: VIEW } });
   return (
-    <Schedule ariaLabel="Benchmark plan" height={HEIGHT} laneHeight={LANE_HEIGHT} onInteraction={onInteraction}>
+    <Schedule aria-label="Benchmark plan" height={HEIGHT} laneHeight={LANE_HEIGHT} onInteraction={onInteraction}>
         {data.lanes.map((id) => (
           <Lane key={id} id={id} />
         ))}
@@ -8415,7 +8620,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`height`](#first-schedule) | `number` | `400` | Height in CSS pixels, both bands included. The width is the host's. |
+| [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). 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. |
 
@@ -8429,7 +8634,7 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`ariaLabel`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
 
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
@@ -8511,13 +8716,14 @@ Everything `@umriss-ui/schedule` exports, with its signature. A component's prop
 Declares a schedule: hands back `Schedule` and the parts declared inside it
 - `Lane`, `LaneGroup`, `Subtasks`, `Dependencies`, `BlockedTimes`, `Milestones` -, its
 `view` and the setters `setView`, `setDomain`, `toggleGroup`, `foldAll` and
-`unfoldAll`. A ref on `Schedule` still gives the `ScheduleHandle`.
+`unfoldAll`, `positionAt`, `clientPointOf` and `visibleDomain`, and `scrollToLane`, `scrollToSubtask` and
+`focusSubtask`.
 
 ```ts
 function useSchedule(options?: ScheduleOptions): ScheduleParts;
 ```
 
-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).
+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), [Functions on the hook](#functions-on-the-hook), [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
 
@@ -8560,7 +8766,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](#scenarios), [First schedule](#first-schedule), [Lane groups](#lane-groups), [Blocked time](#blocked-time), [Tooltip](#tooltip) and [Findings as data](#findings-as-data).
+Used on [Scenarios](#scenarios), [First schedule](#first-schedule), [Lane groups](#lane-groups), [Blocked time](#blocked-time), [Tooltip](#tooltip), [Functions on the hook](#functions-on-the-hook) and [Findings as data](#findings-as-data).
 
 ##### `inBlockedTime`
 
@@ -8595,7 +8801,7 @@ nothing.
 function overlaps(subtasks: readonly Subtask[]): Overlap[];
 ```
 
-Used on [Scenarios](#scenarios), [Lane groups](#lane-groups), [Findings as data](#findings-as-data) and [Move and lane](#move-and-lane).
+Used on [Scenarios](#scenarios), [Lane groups](#lane-groups), [Functions on the hook](#functions-on-the-hook), [Findings as data](#findings-as-data) and [Move and lane](#move-and-lane).
 
 ##### `resolveAppearance`
 
@@ -8883,19 +9089,6 @@ the channel each one owns stands beside it.
 | `muted` *required* | `boolean` | — | `muted`: the SATURATION - the task colour mixed half into the surface, opaque and at full height. Another team's, another crew's. |
 | `open` *required* | `boolean` | — | `open`: the FADE, where the bar passes the edge of the view. It goes on past what is drawn. |
 
-##### `ScheduleHandle`
-
-What a schedule offers a caller imperatively: the arithmetic between a
-point on the screen and a time on a lane. Everything else is props.
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `positionAt` *required* | `(clientX: number, clientY: number) => { time: number; lane: string \| null } \| null` | — | The time and the lane at a client point, or null outside the plot.<br>Shown in: [Place a mark of your own (The handle)](#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](#the-handle).
-
 ##### `ScheduleHit`
 
 What a pointer is on.
@@ -8926,10 +9119,10 @@ it, its view and the setters that change it.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `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 |
+| `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 82 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 82 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 |
+| `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 82 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) |
@@ -8937,6 +9130,12 @@ it, its view and the setters that change it.
 | `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**. |
+| `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 - and null while no schedule is mounted.<br>Shown in: [Place a mark of your own (Functions on the hook)](#functions-on-the-hook) |
+| `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 (Functions on the hook)](#functions-on-the-hook) |
+| `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
+| `scrollToLane` *required* | `(lane: string) => boolean` | — | Scrolls the lanes until the lane's row is in view, and returns `true`; `false` and nothing changed for an unknown lane, one inside a folded **Lane group** (none is unfolded), or while no schedule is mounted. |
+| `scrollToSubtask` *required* | `(id: string) => boolean` | — | Brings the subtask's lane and time into view, the span moving to it and keeping its width as `setDomain` would, and leaves the focus where it is; `false` and nothing changed in the cases of `scrollToLane`.<br>Shown in: [Show a finding (Functions on the hook)](#functions-on-the-hook) |
+| `focusSubtask` *required* | `(id: string) => boolean` | — | Does what `scrollToSubtask` does, then makes the subtask the **Active subtask** and moves the focus to the plot, where the live region reads it out as the arrow keys do; `false` and nothing changed in the cases of `scrollToLane`.<br>Shown in: [Show a finding (Functions on the hook)](#functions-on-the-hook) |
 | `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) |
 
@@ -8984,7 +9183,7 @@ Stretch the main time at one or both of its edges.
 
 Its table stands on [Subtasks](#subtasks).
 
-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).
+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), [Functions on the hook](#functions-on-the-hook), [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`
 
@@ -9002,7 +9201,7 @@ Its table stands on [Subtasks](#subtasks).
 
 Its table stands on [Subtasks](#subtasks).
 
-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).
+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), [Functions on the hook](#functions-on-the-hook), [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`