@umriss-ui/schedule 0.7.0 → 0.34.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.7.0
+# @umriss-ui/schedule 0.34.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -1028,7 +1028,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -1358,9 +1358,9 @@ type IntentKind = Intent["kind"];
 
 ###### `PlacingItem`
 
-What the application says it is dragging in, while it drags it
-(schedule-refinement 07): the browser hands over the dragged data only on
-the drop, so the ghost before the drop can only come from the caller.
+What the application says it is dragging in, while it drags it: the
+browser hands over the dragged data only on the drop, so the ghost before
+the drop can only come from the caller.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -1498,7 +1498,7 @@ Put the subtask on another lane.
 ###### `PlaceIntent`
 
 Put work on the plan that was not on it: the answer to a drag from outside
-the schedule (schedule-refinement 07). It carries no subtask id - there is
+the schedule. It carries no subtask id - there is
 no subtask yet; the caller creates one, with its own identity, from
 `subtaskFromPlace`.
 
@@ -1671,7 +1671,7 @@ A group is structure, never a lane: nothing sits on it, no finding is reported f
 
 Folded, a group shows a miniature: every lane in it as a thin strip with its work in the tasks' colours. Dependencies still arrive at the right strip, findings are marked on the row, and a strip can be hovered and selected. Labels, appearances and grips need room and wait for the group to open.
 
-Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold - see [View](#/view).
+Folding is part of the schedule's view and never an intent: `folded` in `initialView` starts with groups folded, `toggleGroup`, `foldAll` and `unfoldAll` fold from outside, and `onViewChange` reports every fold the planner makes - see [View](#/view).
 
 #### Examples
 
@@ -1765,7 +1765,7 @@ export default function Nesting() {
 
 ##### Fold groups from outside
 
-`foldAll`, `unfoldAll` and `toggleGroup` fold from outside, and `view.folded` says what is folded - start from `initialView`, keep what `onViewChange` reports.
+`foldAll`, `unfoldAll` and `toggleGroup` fold from outside, and `view.folded` says what is folded - start from `initialView`, go to a whole view with `setView`, keep what `onViewChange` reports.
 
 ```tsx
 import { Button, Stack, Text } from "@umriss-ui/core";
@@ -1910,8 +1910,8 @@ import { useSchedule } from "@umriss-ui/schedule";
 import type { Subtask, Task } from "@umriss-ui/schedule";
 
 /* The schedule keeps the fold from here on. To store it, keep what
-   `onViewChange` reports; to steer it, use the setters `useSchedule` hands
-   back. */
+   `onViewChange` reports; to steer it, use `setView` and the setters
+   `useSchedule` hands back. `initialView` is read once. */
 
 const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
 
@@ -2328,7 +2328,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -2642,7 +2642,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -2825,7 +2825,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -3460,7 +3460,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -3803,7 +3803,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4545,7 +4545,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4681,7 +4681,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -4916,7 +4916,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -5556,9 +5556,9 @@ import { useSchedule } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/view/
 
-The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#/api/useSchedule) hands back holds it, and `onViewChange` reports every change of it - a pan or zoom at most once per frame; keep it where the application keeps things and hand it back through `initialView`.
+The schedule keeps its view itself and puts it nowhere, not in the address and not in any storage. `view` on what [`useSchedule`](#/api/useSchedule) hands back holds it, and `onViewChange` reports every change the planner makes to it - a pan or zoom at most once per frame; keep it where the application keeps things and go back to it with `setView`.
 
-A view that differs in content from the last one handed in applies at once, and what it leaves out goes back to its default; the same one again changes nothing. Without a span the schedule shows the extent of its subtasks, within `zoomLimits`. A group no `LaneGroup` declares falls out.
+`initialView` is the start, read once: a different value on a later render is ignored. `setView(view)` goes to a whole view at once, and what it leaves out goes back to its default; the same view again changes nothing, and `onViewChange` does not hear it. Without a span the schedule shows the extent of its subtasks, within `zoomLimits`. A group no `LaneGroup` declares falls out.
 
 `setDomain`, `toggleGroup`, `foldAll` and `unfoldAll` change the view from outside - a button of the application's own that shows the whole plan or folds every team. The selection is not part of the view (`selectedTask`).
 
@@ -5566,7 +5566,7 @@ A view that differs in content from the last one handed in applies at once, and
 
 ##### Keep and restore a view
 
-`onViewChange` reports the span and the folded groups as one view; keep it - here in the browser's storage, so it outlives a reload - and hand it back through `initialView`. Pan, zoom, fold, keep, reload, restore.
+`onViewChange` reports the span and the folded groups as one view; keep it - here in the browser's storage, so it outlives a reload - and go back to it with `setView`. Pan, zoom, fold, keep, reload, restore.
 
 ```tsx
 import { useState } from "react";
@@ -5612,11 +5612,10 @@ const WORK: Subtask[] = [
 ];
 
 export default function KeepAndRestore() {
-  /* The application holds the view the schedule reports; handing it another
-     one is all it takes to restore. */
-  const [view, setView] = useState<ScheduleView>(START);
+  /* The schedule holds its view; `view` is what it shows now, and `setView`
+     restores a kept one. */
   const [kept, setKept] = useState<ScheduleView | null>(readKept);
-  const { Schedule, Lane, LaneGroup, Subtasks, setDomain } = useSchedule({ initialView: view, onViewChange: setView });
+  const { Schedule, Lane, LaneGroup, Subtasks, view, setView, setDomain } = useSchedule({ initialView: START });
 
   return (
     <Stack gap={3}>
@@ -5677,19 +5676,19 @@ The keys of [First schedule](#/schedule/keyboard-schedule) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `initialView` | [`ScheduleView`](#type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 77 more |
+| `initialView` | [`ScheduleView`](#type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 77 more |
 
 ###### Events
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `onViewChange` | `(view: `[`ScheduleView`](#type-ScheduleView)`) => void` | — | Every change of the view, once, always the whole view - the one to keep, or to hand another schedule as its `initialView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
+| `onViewChange` | `(view: `[`ScheduleView`](#type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies.<br>Shown in: [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
 
 ##### `ScheduleView`
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `domain` | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 77 more |
+| `domain` | `readonly [number, number]` | — | The span in view, as two wall-clock instants. Absent, the schedule shows the extent of its subtasks, within `zoomLimits`.<br>Shown in: [Keep and restore a view](#/view/keep-and-restore), [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule) and 76 more |
 | `folded` | `readonly string[]` | — | The **Lane group**s that are folded, by id. An id no group carries falls out. A folded outer group hides the inner ones without their ids leaving the list, so unfolding it gives back the view that was there.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Read a folded group (Lane groups)](#/lane-groups/the-miniature), [Start with groups folded (Lane groups)](#/lane-groups/start-with-groups-folded) |
 
 ### Linked schedules
@@ -5702,7 +5701,7 @@ import { useSchedule } from "@umriss-ui/schedule";
 
 Demo page: https://romanhaendler.github.io/umriss-ui/schedule/linked-schedules/
 
-Each schedule has its own [`useSchedule`](#/api/useSchedule). Hand both the view one of them reports, through `initialView`: a view that differs from the last one handed in applies at once, without a remount, and the same one again changes nothing, so the two never feed each other.
+Each schedule has its own [`useSchedule`](#/api/useSchedule). Send what one reports to the other's `setView`, in both directions: the other goes there at once, without a remount, and `setView` is not reported, so the two never answer each other.
 
 While a drag is in flight the two can stand a frame apart; they settle as soon as it ends.
 
@@ -5710,13 +5709,12 @@ While a drag is in flight the two can stand a frame apart; they settle as soon a
 
 ##### Keep two schedules in step
 
-Hand the view `onViewChange` reports to both schedules' `initialView`: pan or zoom either one and the other follows - no `key`, no remount.
+Send what `onViewChange` reports to the other schedule's `setView`: pan or zoom either one and the other follows - no `key`, no remount.
 
 ```tsx
-import { useState } from "react";
 import { Stack, Text } from "@umriss-ui/core";
 import { useSchedule } from "@umriss-ui/schedule";
-import type { ScheduleView, Subtask, Task } from "@umriss-ui/schedule";
+import type { ScheduleParts, Subtask, Task } from "@umriss-ui/schedule";
 
 const at = (hours: number, minutes = 0) => new Date(2026, 2, 17, hours, minutes).getTime();
 const min = (n: number) => n * 60_000;
@@ -5757,12 +5755,12 @@ const ELECTRIC_LEGS = on(ELECTRIC);
 const time = (instant: number) => new Date(instant).toLocaleTimeString("en-GB", { hour: "2-digit", minute: "2-digit" });
 
 export default function InStep() {
-  /* One view for both: each schedule reports its own, and goes to the other's
-     because it differs from the last one handed in. */
-  const [view, setView] = useState<ScheduleView>({ domain: [at(5, 30), at(18)] });
-  const diesel = useSchedule({ initialView: view, onViewChange: setView });
-  const electric = useSchedule({ initialView: view, onViewChange: setView });
-  const span = view.domain ?? [at(5, 30), at(18)];
+  /* Both start on the same span; each reports what the reader does to it and
+     the other goes there by `setView`, which is not reported in turn. */
+  const start = { domain: [at(5, 30), at(18)] } as const;
+  const diesel: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => electric.setView(v) });
+  const electric: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => diesel.setView(v) });
+  const span = diesel.view.domain ?? start.domain;
   return (
     <Stack gap={2}>
       <diesel.Schedule ariaLabel="Diesel vehicles on Tuesday, 17 March" height={240}>
@@ -5790,10 +5788,9 @@ export default function InStep() {
 Two schedules with different lanes over one span: who was on call, above the incidents they were paged for.
 
 ```tsx
-import { useState } from "react";
 import { Stack } from "@umriss-ui/core";
 import { useSchedule } from "@umriss-ui/schedule";
-import type { ScheduleView, Subtask, Task } from "@umriss-ui/schedule";
+import type { ScheduleParts, Subtask, Task } from "@umriss-ui/schedule";
 
 /* Data from the operations world, written out here so the example runs on its own. */
 
@@ -5920,9 +5917,9 @@ const PAGED: readonly Subtask[] = INCIDENTS.map((incident) => ({
 const HIT = SERVICES.filter((service) => PAGED.some((incident) => incident.lane === service.id));
 
 export default function RotaBesideIncidents() {
-  const [view, setView] = useState<ScheduleView>({ domain: [day(16, 6), day(17, 14)] });
-  const rota = useSchedule({ initialView: view, onViewChange: setView });
-  const incidents = useSchedule({ initialView: view, onViewChange: setView });
+  const start = { domain: [day(16, 6), day(17, 14)] } as const;
+  const rota: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => incidents.setView(v) });
+  const incidents: ScheduleParts = useSchedule({ initialView: start, onViewChange: (v) => rota.setView(v) });
   return (
     <Stack gap={2}>
       <rota.Schedule ariaLabel="Who was on call" height={140}>
@@ -6003,13 +6000,13 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 ###### Events
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`onViewChange`](#/view/ScheduleOptions-onViewChange) | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Every change of the view, once, always the whole view - the one to keep, or to hand another schedule as its `initialView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with. |
+| [`onViewChange`](#/view/ScheduleOptions-onViewChange) | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Every change the planner makes, once, always the whole view - the one to keep, or to hand another schedule's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the schedule starts with, nor for one `setView` applies. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6196,7 +6193,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6779,7 +6776,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -6962,7 +6959,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7196,7 +7193,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7406,7 +7403,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -7827,7 +7824,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -8116,7 +8113,7 @@ From `ScheduleOptions` — the full table stands on [View](#/view/type-ScheduleO
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, and to go to whenever one differing in content from the last is handed in - the same view again changes nothing, and what it leaves out is reset; one the schedule reported itself, handed back late, is its own state coming back and not gone to. The schedule remembers none: where a view is kept is the application's decision. |
+| [`initialView`](#/view/ScheduleOptions-initialView) | [`ScheduleView`](#/view/type-ScheduleView) | — | The view to start from, read once when the hook first runs; a different value on a later render is ignored, as React ignores a changed `defaultValue`. To go to a view later, call `setView`. The schedule remembers none: where a view is kept is the application's decision. |
 
 From `ScheduleView` — the full table stands on [View](#/view/type-ScheduleView).
 
@@ -8147,7 +8144,7 @@ Demo page: https://romanhaendler.github.io/umriss-ui/schedule/api/
 
 Declares a schedule: hands back `Schedule` and the parts declared inside it
 - `Lane`, `LaneGroup`, `Subtasks`, `Dependencies`, `BlockedTimes`, `Milestones` -, its
-`view` and the setters `setDomain`, `toggleGroup`, `foldAll` and
+`view` and the setters `setView`, `setDomain`, `toggleGroup`, `foldAll` and
 `unfoldAll`. A ref on `Schedule` still gives the `ScheduleHandle`.
 
 ```ts
@@ -8475,7 +8472,7 @@ Its table stands on [Findings as data](#/findings/type-Overlap).
 ##### `PlaceIntent`
 
 Put work on the plan that was not on it: the answer to a drag from outside
-the schedule (schedule-refinement 07). It carries no subtask id - there is
+the schedule. It carries no subtask id - there is
 no subtask yet; the caller creates one, with its own identity, from
 `subtaskFromPlace`.
 
@@ -8492,9 +8489,9 @@ no subtask yet; the caller creates one, with its own identity, from
 
 ##### `PlacingItem`
 
-What the application says it is dragging in, while it drags it
-(schedule-refinement 07): the browser hands over the dragged data only on
-the drop, so the ghost before the drop can only come from the caller.
+What the application says it is dragging in, while it drags it: the
+browser hands over the dragged data only on the drop, so the ghost before
+the drop can only come from the caller.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
@@ -8510,15 +8507,13 @@ Used on [Placing from outside](#/placing) and [Where a subtask may go](#/where-i
 
 What the drawing needs to know, with the contradiction already settled.
 
-The four names are the ones this module was born with, and they are kept so
-that a caller's code does not change because a picture did. Two of them are
-now named after a drawing they no longer use, and the channel each one
-really owns stands beside it.
+Two of the field names (`dashed`, `hatched`) are older than the drawing;
+the channel each one owns stands beside it.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `dashed` *required* | `boolean` | — | `provisional`: the FILL - none at all, so the surface shows through, with a dashed outline in the task colour. Planned, not released. |
-| `hatched` *required* | `boolean` | — | `fixed`: the ENDS - a cap at each end of the main time. Not a hatch any more; a hatch now says "not available" of a refused lane, and the name is kept only so that this type did not change with the picture. |
+| `hatched` *required* | `boolean` | — | `fixed`: the ENDS - a cap at each end of the main time. Not a hatch: a hatch says "not available" of a refused lane. The field keeps the name `hatched`. |
 | `muted` *required* | `boolean` | — | `muted`: the SATURATION - the task colour mixed half into the surface, opaque and at full height. Another team's, another crew's. |
 | `open` *required* | `boolean` | — | `open`: the FADE, where the bar passes the edge of the view. It goes on past what is drawn. |
 
@@ -8572,12 +8567,15 @@ it, its view and the setters that change it.
 | `Dependencies` *required* | `typeof Dependencies` | — | <br>Shown in: [The smallest schedule (Installation)](#/installation/smallest-schedule), [A day of tours (First schedule)](#/schedule/first-schedule), [Plan a day in the machine shop (First schedule)](#/schedule/machine-plan) and 27 more |
 | `BlockedTimes` *required* | `typeof BlockedTimes` | — | <br>Shown in: [Block out leave and maintenance (Blocked time)](#/blocked-time/leave), [Plan work around someone's leave (Blocked time)](#/blocked-time/drag-around), [Check a sprint against the leave calendar (Blocked time)](#/blocked-time/team-leave) and 5 more |
 | `Milestones` *required* | `typeof Milestones` | — | <br>Shown in: [Mark a handover and a release (Milestones)](#/milestones/handovers-and-releases), [Say what a milestone is in your own tooltip (Milestones)](#/milestones/say-what-a-milestone-is) |
-| `view` *required* | [`ScheduleView`](#/view/type-ScheduleView) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Place a mark of your own (The handle)](#/handle/place-a-mark) |
+| `view` *required* | [`ScheduleView`](#/view/type-ScheduleView) | — | How the planner is looking at the plan: the span and the folded groups.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside), [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step) and 1 more |
+| `setView` *required* | `(view: `[`ScheduleView`](#/view/type-ScheduleView)`) => void` | — | Goes to a whole view; what it leaves out is shown whole again. Not reported through `onViewChange`: two schedules kept in step by `onViewChange: (v) => other.setView(v)` in both directions do not answer each other. A view with the content already shown changes nothing.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore), [Keep two schedules in step (Linked schedules)](#/linked-schedules/in-step), [Read a rota beside the incidents (Linked schedules)](#/linked-schedules/rota-beside-incidents) |
 | `setDomain` *required* | `(span: readonly [number, number] \| null) => void` | — | Puts a span of two wall-clock instants in view; `null` shows the subtasks' extent.<br>Shown in: [Keep and restore a view (View)](#/view/keep-and-restore) |
 | `toggleGroup` *required* | `(id: string) => void` | — | Folds or unfolds one **Lane group**. |
 | `foldAll` *required* | `() => void` | — | Folds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
 | `unfoldAll` *required* | `() => void` | — | Unfolds every group.<br>Shown in: [Fold groups from outside (Lane groups)](#/lane-groups/fold-from-outside) |
 
+Used on [Linked schedules](#/linked-schedules).
+
 ##### `ScheduleProps`
 
 Its table stands on [First schedule](#/schedule/type-ScheduleProps).
@@ -8592,7 +8590,7 @@ Used on [Milestones](#/milestones) and [Tooltip](#/tooltip).
 
 Its table stands on [View](#/view/type-ScheduleView).
 
-Used on [View](#/view) and [Linked schedules](#/linked-schedules).
+Used on [View](#/view).
 
 ##### `SnapRaster`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.7.0",
+  "version": "0.34.0",
   "description": "React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
   "license": "MIT",
   "author": "Roman Händler",
@@ -50,8 +50,8 @@
   "peerDependencies": {
     "react": ">=18",
     "react-dom": ">=18",
-    "@umriss-ui/charts": "^0.15.0",
-    "@umriss-ui/core": "^0.32.0"
+    "@umriss-ui/charts": "^0.34.0",
+    "@umriss-ui/core": "^0.34.0"
   },
   "devDependencies": {
     "@fontsource/geist-mono": "^5.3.0",
@@ -65,9 +65,9 @@
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/core": "0.32.0",
-    "@umriss-ui/demo": "0.0.0",
-    "@umriss-ui/charts": "0.15.0"
+    "@umriss-ui/charts": "0.34.0",
+    "@umriss-ui/core": "0.34.0",
+    "@umriss-ui/demo": "0.0.0"
   },
   "scripts": {
     "props": "node --disable-warning=ExperimentalWarning --experimental-strip-types demo/props.ts",
@@ -76,8 +76,9 @@
     "build": "vite build",
     "prebuild:demo": "pnpm run props",
     "build:demo": "vite build --config vite.demo.config.ts",
-    "pretypecheck": "pnpm run props",
     "typecheck": "tsc --noEmit",
+    "typecheck:demo": "pnpm run props && tsc --noEmit -p tsconfig.demo.json",
+    "check:site": "pnpm run props -- --check",
     "preview:demo": "vite preview --config vite.demo.config.ts --port 4176 --strictPort",
     "test:unit": "vitest run",
     "check:dist": "node --disable-warning=ExperimentalWarning --experimental-strip-types ../../scripts/check-dist.ts schedule.js schedule.css"