@camstack/ui-library 1.2.256 → 1.2.258

package/dist/composites/clips/ClipBandBar.d.ts

@@ -1,16 +1,46 @@
-import { DayWindow, DensityBucket } from '../cap-settings/recording-timeline-model.js';
+/**
+* The clips section's timebar — the recording section's own controls, driving
+* a clip list instead of a player (D564).
+*
+* *"Possiamo utilizzare lo stesso componente della sezione recording con la
+* timebar dove selezionare un periodo e mostrare le clip solo di quella banda
+* selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] — the operator, 2026-09-20. So this is not a
+* second timebar: it is `TimelineControls` and `EventHeatmap`, the two pieces
+* `RecordingTimeline` is itself built from, over the same
+* `recording-timeline-model` (`dayWindow`, `panWindow`,
+* `zoomWindowAnchoredRight`, `bucketMsForSpan`, `axisTicks`). One
+* implementation, one model, two surfaces.
+*
+* ## What it does NOT take from the recording timeline
+*
+* `CoverageTrack` stays behind. There it is the seek surface — a click drives
+* the hero player through the `camstack-control` channel or an HLS VOD
+* request. A copy here would either be a dead bar or a SECOND thing claiming
+* to move the playhead, and two components holding two ideas of the same
+* position is the defect this repo keeps paying for. The clips section plays a
+* clip through `ClipPanel`, which is its own, already-shipped path.
+*
+* ## This component is presentational
+*
+* It holds no state. The day, the visible window and the picked bucket all
+* live in `ClipsSection`, because that is where the band is turned into the
+* `listClips` argument — a bar that kept its own copy of the selection would
+* be the second authority again, one component down.
+*/
+import { type JSX } from "react";
+import { type DayWindow, type DensityBucket } from "../cap-settings/recording-timeline-model.js";
 export interface ClipBandBarProps {
-    /** The calendar day the window is inside. */
-    readonly day: Date;
-    readonly onDayChange: (day: Date) => void;
-    /** The visible window — the band, whenever no bucket is picked. */
-    readonly view: DayWindow;
-    /** The full day, the clamp for every zoom and pan. */
-    readonly dayBounds: DayWindow;
-    readonly onViewChange: (view: DayWindow) => void;
-    readonly buckets: readonly DensityBucket[];
-    readonly selectedBucketIndex: number | null;
-    readonly onSelectBucket: (index: number) => void;
-    readonly densityLoading: boolean;
+	/** The calendar day the window is inside. */
+	readonly day: Date;
+	readonly onDayChange: (day: Date) => void;
+	/** The visible window — the band, whenever no bucket is picked. */
+	readonly view: DayWindow;
+	/** The full day, the clamp for every zoom and pan. */
+	readonly dayBounds: DayWindow;
+	readonly onViewChange: (view: DayWindow) => void;
+	readonly buckets: readonly DensityBucket[];
+	readonly selectedBucketIndex: number | null;
+	readonly onSelectBucket: (index: number) => void;
+	readonly densityLoading: boolean;
 }
-export declare function ClipBandBar({ day, onDayChange, view, dayBounds, onViewChange, buckets, selectedBucketIndex, onSelectBucket, densityLoading, }: ClipBandBarProps): import("react").JSX.Element;
+export declare function ClipBandBar({ day, onDayChange, view, dayBounds, onViewChange, buckets, selectedBucketIndex, onSelectBucket, densityLoading }: ClipBandBarProps): JSX.Element;

package/dist/composites/clips/ClipPanel.d.ts

@@ -1,8 +1,32 @@
-import { CamProfile, Clip } from '@camstack/types';
+/**
+* The selected clip — what it is, how it plays, and how it is saved.
+*
+* **No second player.** `getClipPlayback` answers `{ playbackUrl, format,
+* served }` and the panel hands it to the SAME hero the recordings timeline
+* drives: `vod.play({ url, format })` → `StreamPanel playbackUrl/playbackFormat`
+* → `HlsVideo`'s `mp4` branch (`video.src`, no hls.js). Building a clip player
+* here is the thing D549 decision 22 exists to refuse.
+*
+* **`format` travels.** An MP4 handed to hls.js is parsed as a manifest and
+* fails, so the format the provider named is forwarded verbatim and never
+* defaulted here.
+*
+* **`served` is shown.** A clip that holds only one twin answers with the one
+* it has, and the surface SAYS so — a missing main twin must never be served
+* silently as if it were the asked-for quality (D549 decision 15). Both ids
+* are already on the row, so changing quality re-asks the hub and never
+* re-searches the camera.
+*
+* **Nothing is appended to the URL.** The route is `access:'authenticated'`
+* and the session cookie authenticates it (D549 decision 22); the same URL is
+* the download.
+*/
+import { type JSX } from "react";
+import type { CamProfile, Clip } from "@camstack/types";
 export interface ClipPanelProps {
-    readonly deviceId: number;
-    readonly clip: Clip;
-    readonly profile: CamProfile;
-    readonly onProfileChange: (profile: CamProfile) => void;
+	readonly deviceId: number;
+	readonly clip: Clip;
+	readonly profile: CamProfile;
+	readonly onProfileChange: (profile: CamProfile) => void;
 }
-export declare function ClipPanel({ deviceId, clip, profile, onProfileChange }: ClipPanelProps): import("react").JSX.Element;
+export declare function ClipPanel({ deviceId, clip, profile, onProfileChange }: ClipPanelProps): JSX.Element;

package/dist/composites/clips/ClipTile.d.ts

@@ -1,7 +1,28 @@
-import { Clip } from '@camstack/types';
+/**
+* One clip, as a tile.
+*
+* The picture is resolved by `resolveTileMedia` — vouched JPEG, an offer, or
+* the reason there is none (D549 decision 5). An offer is fetched rather than
+* dropped into an `<img src>`, because the route's **204 + x-camstack-reason**
+* is invisible to an `<img>`: it fires `onerror` with nothing to say. The
+* refusal is LATCHED for the life of the tile and never retried behind the
+* operator's back.
+*
+* The row also carries what the camera itself said: its native types, the
+* behaviours beside the class, which storages hold it, and — for a row that
+* is an EVENT sitting inside no file — `playable: false` with its reason
+* (measured: 1 of 29 hub events on 3628). Such a row is SHOWN, never dropped
+* and never offered as playable-then-failing (D549 decision 19).
+*
+* The CHROME is the library's: a `Card` for the tile, `Badge` for every label
+* the camera gave it, `Skeleton` while a mint is in flight. Only the ladder
+* above is this file's own, because only it is a decision.
+*/
+import { type JSX } from "react";
+import type { Clip } from "@camstack/types";
 export interface ClipTileProps {
-    readonly clip: Clip;
-    readonly selected: boolean;
-    readonly onSelect: (clip: Clip) => void;
+	readonly clip: Clip;
+	readonly selected: boolean;
+	readonly onSelect: (clip: Clip) => void;
 }
-export declare function ClipTile({ clip, selected, onSelect }: ClipTileProps): import("react").JSX.Element;
+export declare function ClipTile({ clip, selected, onSelect }: ClipTileProps): JSX.Element;

package/dist/composites/clips/ClipsSection.d.ts

@@ -1,4 +1,109 @@
+/**
+* `host/clips-browser` — a camera's clips, from EVERY source it has, as the
+* LAST SECTION of the Recording tab.
+*
+* Mounted by the framework, not by hand: `videoclips.cap.ts` declares
+* `deviceConfig.ui = { kind:'widget', widgetId:'host/clips-browser',
+* tab:'recording', topTab:true, order:100 }` and
+* `deriveDeviceConfigContribution` emits the section (D14). `DeviceDetail.tsx`
+* is not edited — placement is data. Because the admin Recordings page renders
+* every `location:'top-tab'` + `tab:'recording'` section behind its camera
+* picker (`CameraRecordingSettingsSection`), the same declaration puts this on
+* both surfaces with no second wiring.
+*
+* ## Built from the library, not from scratch
+*
+* It shipped as its own top tab made of five bespoke components, and the
+* operator rejected both: *"La UI è orribile, non segue la nostra UI affatto …
+* Io in realtà utilizzerei la stessa tab recordings, lì abbiamo già tutto il
+* necessario, una nuova sezione alla fine per le clips dove possiamo
+* selezionare le source con un multiselect common, non componenti nuovi
+* anonimi."* [The UI is horrible, it does not follow our UI at all … I would actually use the same recordings tab, we already have everything necessary there, a new section at the end for the clips where we can select the sources with a common multiselect, no new anonymous components.] So every piece of chrome here is a component this repo already
+* has: `Select`, `DataTable`, `EmptyState`, `ErrorBox`, `Pagination`, `Card`,
+* `Badge`, `Button`, `Skeleton`. What the chrome CARRIES is unchanged, and it
+* is the feature:
+*
+*  - **The source list is complete, always.** Every source the camera has,
+*    with its availability and the age of its catalog, whichever provider is
+*    being asked. A source never leaves the table.
+*  - **Nothing is deduped.** A clip held in two storages appears twice, once
+*    per source, and every tile says which (D549).
+*  - **Four states are tellable apart**: loading, empty-with-a-cause,
+*    degraded-per-source, and each silent source in its own words. Every one
+*    of them used to render as "no clips", which is the defect this whole line
+*    of work is about — a camera with no SD card (640) is not quiet, and a
+*    camera whose own index disagrees with its own calendar (618, 6–20
+*    September) is not quiet either.
+*
+* ## The period comes from the recording section's timebar, not a day picker
+*
+* It shipped with its own `‹ day ›` pair and the operator replaced it the same
+* way he replaced the chrome: *"Possiamo utilizzare lo stesso componente della
+* sezione recording con la timebar dove selezionare un periodo e mostrare le
+* clip solo di quella banda selezionata, espandibile."* [We can use the same component as the recording section with the timebar where a period can be selected and show the clips of that selected band only, expandable.] So the list follows a
+* BAND (D564) — `TimelineControls` for the day, the zoom and the pan,
+* `EventHeatmap` for picking a narrower window out of it, both of them the
+* pieces `RecordingTimeline` is itself built from, over the same
+* `recording-timeline-model`. Three things that are decisions, not details:
+*
+*  - **The band lives HERE, once.** `ClipBandBar` is presentational. Two
+*    components holding two ideas of the selected period is the defect this
+*    repo keeps paying for, and the period is what the query is made of.
+*  - **`CoverageTrack` stayed behind**, because there it is the seek surface
+*    that moves the hero player's playhead. A copy here would be a dead bar or
+*    a second claimant on that position.
+*  - **A band is asked for only if it is affordable.** `clip-band.ts` counts
+*    the LOCAL days it touches — the camera's own search is clamped to one per
+*    call, and a day listing is 4.3–6.0 s on 592 — and refuses past the bound
+*    by name rather than asking and rendering whichever days answered.
+*
+* ## The picker WRITES nothing, and there is nothing for it to write
+*
+* A clip source is not enabled or disabled — it EXISTS, because of a
+* configuration that lives somewhere else. The operator put it exactly:
+* *"non è affatto necessario lo stato di abilitato o meno delle sources. Loro
+* vivono lì, ad esempio hksv c'è se la camera è esportata su homekit, reolink
+* la dà di suo così come il camstack."* [the enabled-or-not state of the sources is not necessary at all. They live there, for example hksv is there if the camera is exported to homekit, reolink provides it on its own, as does camstack.] HKSV is there if the camera is
+* exported to HomeKit; the Reolink source is there because Reolink is that
+* camera's provider; CamStack's is always there. None of that is a decision to
+* make in a clips list, so this surface offers no switch and writes no
+* authority (D557, amended). A directory-wide guard in
+* `clips-section-sources.test.tsx` keeps it that way.
+*
+* ## Why the picker is a SELECT and not a multiselect
+*
+* The operator asked for *"un multiselect common"* while `listClips` still
+* took `sources?: string[]`. It now takes ONE `provider` —
+* *"l'utilizzatore è uno solo"* [there is only one user] — and a multi-pick control over a
+* one-at-a-time argument offers a sum the hub cannot answer. So the control is
+* the shared single-choice one, `Select`: the same component the Recordings
+* page's own camera picker uses, which is what *"segue la nostra UI"* means
+* here.
+*
+* ## The control's value is ALWAYS what the query carries
+*
+* There is no "default" option and no empty value. This section used to send
+* no `provider` at all until the operator chose, because the cap documented
+* absence as "the device's bound provider, which is CamStack on every camera".
+* No code implemented that: measured on device 592 (2026-09-20, bound to
+* `recorder` AND `provider-reolink`) a bare `listClips` with `limit: 3`
+* answered SIX rows — three per source, merged — while the default option read
+* "CamStack recordings". The label named one thing and the query asked two.
+*
+* Naming a provider is now required (D554 amended), and the default is this surface's
+* to make: the FIRST source the camera lists, shown selected in the control, so
+* what is on screen and what was asked are the same fact. A camera that lists
+* no source is asked NOTHING — the query never fires and the body says nobody
+* answered, rather than spinning against a question with no addressee.
+*
+* ## One provider is a fleet STATE
+*
+* `listSources` derives from `deviceManager.getBindings`. A camera bound to one
+* provider makes the selector inert, and it SAYS why: an empty or silently
+* single-entry control would read as a defect.
+*/
+import { type JSX } from "react";
 export interface ClipsSectionProps {
-    readonly deviceId: number;
+	readonly deviceId: number;
 }
-export declare function ClipsSection({ deviceId }: ClipsSectionProps): import("react").JSX.Element;
+export declare function ClipsSection({ deviceId }: ClipsSectionProps): JSX.Element | null;

package/dist/composites/clips/clip-band.d.ts

@@ -1,58 +1,92 @@
-import { DayWindow } from '../cap-settings/recording-timeline-model.js';
+/**
+* The BAND — the period the clip list is asked for, and what it costs.
+*
+* The clips section used to own a day picker. It now follows a period selected
+* on the recording timebar (D564), so the window it asks `listClips` for is no
+* longer a calendar day: it is whatever the operator has zoomed, panned or
+* bucket-clicked down to. Everything in this module exists because a period is
+* a different KIND of thing from a day in exactly two ways.
+*
+* ## The cost is counted in LOCAL days, because the camera's own search is
+*
+* A Reolink search is clamped to one camera-local day per call — measured
+* 2026-09-20 on hub child 3628: a two-day ask answered 39 windows all dated
+* the START day, silently, and `nodelink-js` now clamps and trace-logs it. The
+* provider therefore LOOPS local days
+* (`reolink-videoclips-provider.ts`), and a day listing is 4.3–6.0 s on 592
+* (209 clips in 6.0 s; 546 in 4.3 s). A band's width in ms says nothing about
+* what it costs; the number of local days it touches says everything. That is
+* the unit here, and the walk goes through `Date`'s own day arithmetic so a
+* DST week is seven days and not 6.96 (`clip-day-window.ts`).
+*
+* ## A band wider than the bound is REFUSED, never asked and partly shown
+*
+* The recording timebar cannot itself express more than a local day — its
+* widest zoom level is 24 h and `zoomWindowAnchoredRight` clamps to the day's
+* bounds — so {@link MAX_BAND_LOCAL_DAYS} is set at the one place a reachable
+* band can still exceed one day: a window that straddles local midnight. The
+* bound is enforced HERE rather than trusted to the control, because a control
+* that later grows a wider zoom must not silently hand the list a
+* recording-sized ask. Above it the query is not fired at all and the surface
+* says which band it refused and why. Trimming the band to the days it could
+* afford and rendering those is the defect this refusal exists to prevent — it
+* is an empty list reading as "no clips" with extra steps.
+*/
+import type { DayWindow } from "../cap-settings/recording-timeline-model.js";
 /** The half-open instant range `listClips` is asked for. */
 export interface ClipBand {
-    readonly fromMs: number;
-    readonly toMs: number;
+	readonly fromMs: number;
+	readonly toMs: number;
 }
 /**
- * How many local days a band may touch and still be asked for.
- *
- * Two, which is every band the timebar can produce: its view window never
- * spans more than one calendar day, and the only way to reach a second is to
- * sit across local midnight. A third is not a gesture this control has, so it
- * is a bug or a future widening — either way the list refuses rather than
- * guesses.
- */
+* How many local days a band may touch and still be asked for.
+*
+* Two, which is every band the timebar can produce: its view window never
+* spans more than one calendar day, and the only way to reach a second is to
+* sit across local midnight. A third is not a gesture this control has, so it
+* is a bug or a future widening — either way the list refuses rather than
+* guesses.
+*/
 export declare const MAX_BAND_LOCAL_DAYS = 2;
 /** What the surface may do with a band, decided once. */
 export type ClipBandPlan = {
-    readonly kind: 'askable';
-    readonly band: ClipBand;
-    readonly localDays: number;
+	readonly kind: "askable";
+	readonly band: ClipBand;
+	readonly localDays: number;
 } | {
-    readonly kind: 'too-wide';
-    readonly band: ClipBand;
-    readonly localDays: number;
-    readonly maxLocalDays: number;
+	readonly kind: "too-wide";
+	readonly band: ClipBand;
+	readonly localDays: number;
+	readonly maxLocalDays: number;
 };
 /**
- * How many LOCAL calendar days the half-open band touches.
- *
- * The end instant is exclusive, so a band that ends exactly at the next local
- * midnight is one day, not two — otherwise every whole-day band would report
- * double what it costs.
- */
+* How many LOCAL calendar days the half-open band touches.
+*
+* The end instant is exclusive, so a band that ends exactly at the next local
+* midnight is one day, not two — otherwise every whole-day band would report
+* double what it costs.
+*/
 export declare function localDaysInBand(band: ClipBand): number;
 /** Whether this band may be asked for, and what it costs, in one value. */
 export declare function planClipBand(band: ClipBand): ClipBandPlan;
 /** A density bucket's own window, as `EventHeatmap` hands it back. */
 export interface ClipBandBucket {
-    readonly startMs: number;
-    readonly endMs: number;
+	readonly startMs: number;
+	readonly endMs: number;
 }
 /**
- * The band for the current selection: the picked bucket, or — when nothing is
- * picked — the whole visible window.
- *
- * "Nothing picked means everything visible" is safe here and only here,
- * because the visible window is itself bounded by the timebar. It is never
- * "everything the camera holds" (D382's unstated ask).
- */
+* The band for the current selection: the picked bucket, or — when nothing is
+* picked — the whole visible window.
+*
+* "Nothing picked means everything visible" is safe here and only here,
+* because the visible window is itself bounded by the timebar. It is never
+* "everything the camera holds" (D382's unstated ask).
+*/
 export declare function bandForSelection(view: DayWindow, bucket: ClipBandBucket | null): ClipBand;
 /**
- * The band, spelled out.
- *
- * Every state renders it — an empty list has to say WHICH period it is empty
- * for, the same rule the day label carried before the band replaced it.
- */
+* The band, spelled out.
+*
+* Every state renders it — an empty list has to say WHICH period it is empty
+* for, the same rule the day label carried before the band replaced it.
+*/
 export declare function formatBandLabel(band: ClipBand): string;

package/dist/composites/clips/clip-day-window.d.ts

@@ -1,36 +1,13 @@
-/**
- * LOCAL calendar-day arithmetic for the clips browser.
- *
- * The browser no longer NAVIGATES days — it follows a band selected on the
- * recording timebar (D564) — but the local day survived the move as the unit
- * the COST is counted in: a Reolink search is clamped to one camera-local day
- * per call, so `clip-band.ts` counts a band's local days to decide whether it
- * may be asked for. The window builder this file used to own went with the day
- * picker; `recording-timeline-model.ts`'s `dayWindow(date, nowMs)` is the one
- * that builds windows now, and one directory holding two functions of that
- * name was the confusion worth deleting.
- *
- * Two properties are pinned by spec because both are invisible until they are
- * wrong:
- *
- *  - Deriving the day in UTC shifts every band by the browser's offset, and an
- *    operator in Berlin would see a 22:00 clip filed under the next day.
- *  - Walking days by adding 86 400 000 ms repeats or skips a calendar day
- *    across a DST change. The walk goes through `Date`'s own day arithmetic.
- *
- * A day id is `YYYY-MM-DD` — it orders lexicographically, which is what lets
- * the band's day walk terminate on a comparison rather than on a count.
- */
 /** The LOCAL calendar day an instant falls in, as `YYYY-MM-DD`. */
 export declare function toDayId(instant: Date): string;
 /** Walk `days` calendar days from `dayId` — DST-safe, because `Date` does it. */
 export declare function shiftDay(dayId: string, days: number): string;
 /**
- * The day, spelled out — the calendar half of a band's label.
- *
- * An empty list has to say WHICH period it is empty for; "no clips" with no
- * date beside it is the ambiguity this surface exists to remove. `formatBandLabel`
- * puts the times around it, and every state renders the result, not only the
- * populated one.
- */
+* The day, spelled out — the calendar half of a band's label.
+*
+* An empty list has to say WHICH period it is empty for; "no clips" with no
+* date beside it is the ambiguity this surface exists to remove. `formatBandLabel`
+* puts the times around it, and every state renders the result, not only the
+* populated one.
+*/
 export declare function formatDayLabel(dayId: string): string;

package/dist/composites/clips/clip-source-state.d.ts

@@ -1,34 +1,63 @@
-import { ClipSource } from '@camstack/types';
+/**
+* What a clip SOURCE is saying right now, in words an operator can act on.
+*
+* `ClipSourceAvailability.state` has five values and four of them used to
+* render identically — as an empty list, which reads "this camera has no
+* recordings". That is the defect the whole external-videoclips line exists to
+* fix ([D549](../../../../../docs/decisions/adr-0549-an-external-clip-catalog-is-another-videoclips-provider-served-by-the-devices-owner-and-listed-beside-the-others.md)
+* § 7b), measured on real cameras:
+*
+*  - 640 has **no SD card** (`HddInfo mount 0`). It is not quiet; it stores
+*    nothing.
+*  - 618's own calendar marks 6–20 September present and its own index then
+*    lists **zero files** for those days, with 177 GB free. That is a defect
+*    ON THE CAMERA, and the only honest thing to say is which days were asked
+*    for and came back empty.
+*  - A standalone battery camera is **asleep**; a read would be a wake, so
+*    what you are looking at is a CACHE with an age.
+*  - `native:reolink:hub` is **unreachable** today because the library parser
+*    for the events view has not landed — so the degraded case is not
+*    hypothetical, it is what every hub child looks like right now.
+*
+* This module is the one place those five become words, kept pure so the
+* distinctness can be pinned without a React tree (a rendering test that only
+* checked colour would pass with all five saying "no clips").
+*
+* The provider's own `reason` travels VERBATIM. It is the camera's refusal in
+* the camera's words; re-writing it here would lose the only detail that tells
+* an operator whether to look at the card, the network or the firmware.
+*/
+import type { ClipSource } from "@camstack/types";
 /** How loudly a source's state should read. Never the whole message. */
-export type ClipSourceTone = 'ok' | 'warn' | 'error';
+export type ClipSourceTone = "ok" | "warn" | "error";
 /** A source's state, rendered. */
 export interface ClipSourceNotice {
-    /** The source's own id (`analytics`, `native:reolink:hub`, …). */
-    readonly source: string;
-    /** The operator-facing source name the provider gave it. */
-    readonly label: string;
-    /** One line, unique per state. Never "no clips". */
-    readonly headline: string;
-    /** The provider's reason, verbatim, or null when it gave none. */
-    readonly detail: string | null;
-    readonly tone: ClipSourceTone;
-    /**
-     * Did this source contribute rows to the list on screen?
-     *
-     * `sleeping` answers TRUE: a sleeping camera serves its persisted catalog
-     * (D549 decision 4), so its clips ARE in the list — only their age is
-     * different. The other three contribute nothing, and an empty day must name
-     * them as the reason rather than claim the camera was quiet.
-     */
-    readonly answered: boolean;
+	/** The source's own id (`analytics`, `native:reolink:hub`, …). */
+	readonly source: string;
+	/** The operator-facing source name the provider gave it. */
+	readonly label: string;
+	/** One line, unique per state. Never "no clips". */
+	readonly headline: string;
+	/** The provider's reason, verbatim, or null when it gave none. */
+	readonly detail: string | null;
+	readonly tone: ClipSourceTone;
+	/**
+	* Did this source contribute rows to the list on screen?
+	*
+	* `sleeping` answers TRUE: a sleeping camera serves its persisted catalog
+	* (D549 decision 4), so its clips ARE in the list — only their age is
+	* different. The other three contribute nothing, and an empty day must name
+	* them as the reason rather than claim the camera was quiet.
+	*/
+	readonly answered: boolean;
 }
 /** Turn one source row into the line the picker and the list show. */
 export declare function describeSource(source: ClipSource): ClipSourceNotice;
 /**
- * How old a source's catalog is, or null when it did not say.
- *
- * Null is NOT "now". A source that omits `catalogAsOf` was read live and has
- * no age to show; inventing "just now" for a source that never told us would
- * be the same lie as drawing a cached list as current (D549 decision 13).
- */
+* How old a source's catalog is, or null when it did not say.
+*
+* Null is NOT "now". A source that omits `catalogAsOf` was read live and has
+* no age to show; inventing "just now" for a source that never told us would
+* be the same lie as drawing a cached list as current (D549 decision 13).
+*/
 export declare function formatCatalogAge(catalogAsOf: number | undefined, now: number): string | null;

package/dist/composites/clips/clip-still-retry.d.ts

@@ -1,50 +1,50 @@
 /**
- * When a tile comes back for a still the server said was queued — and when it
- * gives up (D563).
- *
- * ## Why a retry, and not a queue or a push
- *
- * A deferred refusal is FREE. The provider's lane rejects past its capacity
- * without touching the camera, so asking again costs one cheap HTTP round trip
- * to the addon and zero Baichuan commands. That is what rules out the
- * alternatives: a push would need a channel, a subscription and server-side
- * fan-out of 60 tile identities to save requests that cost nothing, and a
- * client-side queue would be a second copy of the authority that already lives
- * where the camera's real constraint is. Scroll-into-view alone does not help
- * either — the 43 tiles measured refusing on 592 are already on screen.
- *
- * ## The shape
- *
- * Exponential, jittered, bounded. Exponential because a fixed interval either
- * hammers or dawdles; JITTERED because 43 tiles refused in the same paint
- * would otherwise come back in the same instant and refuse together again;
- * BOUNDED because a tile that asks for ever is the other way to show the
- * operator nothing.
- *
- * The server's `retry-after` is taken only when it is LONGER than the curve.
- * The curve is the floor, so a provider answering `retry-after: 1` for a whole
- * page cannot turn this into 43 requests a second.
- *
- * Sized against the measurement: one page is 60 tiles and the provider serves
- * one mint in flight per host, so the last tile is ~60 mints away. The budget
- * below outlasts that; a shorter one would be theatre.
- */
+* When a tile comes back for a still the server said was queued — and when it
+* gives up (D563).
+*
+* ## Why a retry, and not a queue or a push
+*
+* A deferred refusal is FREE. The provider's lane rejects past its capacity
+* without touching the camera, so asking again costs one cheap HTTP round trip
+* to the addon and zero Baichuan commands. That is what rules out the
+* alternatives: a push would need a channel, a subscription and server-side
+* fan-out of 60 tile identities to save requests that cost nothing, and a
+* client-side queue would be a second copy of the authority that already lives
+* where the camera's real constraint is. Scroll-into-view alone does not help
+* either — the 43 tiles measured refusing on 592 are already on screen.
+*
+* ## The shape
+*
+* Exponential, jittered, bounded. Exponential because a fixed interval either
+* hammers or dawdles; JITTERED because 43 tiles refused in the same paint
+* would otherwise come back in the same instant and refuse together again;
+* BOUNDED because a tile that asks for ever is the other way to show the
+* operator nothing.
+*
+* The server's `retry-after` is taken only when it is LONGER than the curve.
+* The curve is the floor, so a provider answering `retry-after: 1` for a whole
+* page cannot turn this into 43 requests a second.
+*
+* Sized against the measurement: one page is 60 tiles and the provider serves
+* one mint in flight per host, so the last tile is ~60 mints away. The budget
+* below outlasts that; a shorter one would be theatre.
+*/
 /** How many times a tile comes back before it says so and stops. */
 export declare const STILL_RETRY_ATTEMPTS = 4;
 /** First wait, doubling from there. */
-export declare const STILL_RETRY_BASE_MS = 4000;
+export declare const STILL_RETRY_BASE_MS = 4e3;
 /** No single wait is longer than this, whatever the server hints. */
-export declare const STILL_RETRY_MAX_WAIT_MS = 30000;
+export declare const STILL_RETRY_MAX_WAIT_MS = 3e4;
 export interface StillRetryInput {
-    /** 0 for the first retry, 1 for the second, … */
-    readonly attempt: number;
-    /** The server's `retry-after`, in ms, or `null` when it sent none. */
-    readonly serverHintMs: number | null;
-    /** Injected so the schedule is assertable; `Math.random` in production. */
-    readonly random: () => number;
+	/** 0 for the first retry, 1 for the second, … */
+	readonly attempt: number;
+	/** The server's `retry-after`, in ms, or `null` when it sent none. */
+	readonly serverHintMs: number | null;
+	/** Injected so the schedule is assertable; `Math.random` in production. */
+	readonly random: () => number;
 }
 export interface StillRetryPlan {
-    readonly waitMs: number;
+	readonly waitMs: number;
 }
 /** The next wait, or `null` when the budget is spent. */
 export declare function planStillRetry(input: StillRetryInput): StillRetryPlan | null;

package/dist/composites/clips/clip-thumbnail-fetch.d.ts

@@ -1,16 +1,16 @@
-import { ClipTileMedia } from './clip-tile-media.js';
+import { type ClipTileMedia } from "./clip-tile-media.js";
 /** The `fetch` this module uses — injected so the contract is testable. */
 export type ThumbnailFetcher = (url: string, init: RequestInit) => Promise<Response>;
 /** A minted still, or the reason there is none. */
 export type MintedThumbnail = {
-    readonly kind: 'image';
-    readonly blob: Blob;
+	readonly kind: "image";
+	readonly blob: Blob;
 } | ClipTileMedia;
 /**
- * Ask a mint route for one still.
- *
- * Never rejects: a thrown fetch is a refusal like any other, because a tile
- * that throws is a tile that renders nothing and says nothing — the exact
- * failure this module exists to prevent.
- */
+* Ask a mint route for one still.
+*
+* Never rejects: a thrown fetch is a refusal like any other, because a tile
+* that throws is a tile that renders nothing and says nothing — the exact
+* failure this module exists to prevent.
+*/
 export declare function fetchMintedThumbnail(url: string, fetcher: ThumbnailFetcher): Promise<MintedThumbnail>;