@camstack/ui-library 1.2.291 → 1.2.292

package/dist/composites/addon-global-settings-form.d.ts

@@ -1,15 +1,3 @@
-/**
-* `AddonGlobalSettingsForm` — mounts an addon's global-settings schema
-* via `api.addonSettings.getGlobalSettings` + `updateGlobalSettings`
-* and renders it with `ConfigFormBuilder`. Single source of truth for
-* the addon's settings — no hardcoded option lists anywhere in the UI.
-*
-* Used wherever an addon's settings need to be edited inline (e.g.
-* benchmark tabs, per-node pipeline editor). The caller passes the
-* tRPC client + (addonId, nodeId); the component handles the fetch
-* + patch loop. `onAfterChange` fires once the patch is applied so
-* consumers can re-read any derived state.
-*/
 import { type JSX } from "react";
 import type { ConfigUISchemaWithValues } from "@camstack/types";
 interface AddonGlobalSettingsFormTrpc {

package/dist/composites/cap-settings/AutotrackSection.d.ts

@@ -1,19 +1,3 @@
-/**
-* Autotrack settings card — rendered inside the PTZ panel when the
-* device has `DeviceFeature.PtzAutotrack`. Three knobs (cross-vendor
-* schema): target type, stop delay, disappear delay, plus an enable /
-* disable toggle that drives the `ptz-autotrack` cap directly.
-*
-* Save semantics:
-*   - Toggle (enable/disable) calls `setEnabled` immediately.
-*   - Form fields debounce-save on blur — no explicit Save button.
-*
-* Vendor capability hints:
-*   - The cap's status carries `currentSettings` from the camera's
-*     own GET; rendered on every poll so the operator sees what's
-*     really applied vs what they typed.
-*   - When the firmware ignored a setting, the field stays editable.
-*/
 import { type JSX } from "react";
 interface AutotrackSectionProps {
 	readonly deviceId: number;

package/dist/composites/cap-settings/CameraGridLayoutEditor.d.ts

@@ -1,24 +1,3 @@
-/**
-* The camera-grid layout editor.
-*
-* A grid's geometry is the one thing a DERIVED settings form cannot express: a
-* generated form renders "cell 1 source = 592, cell 1 crop x = 0.25, cell 1 crop
-* width = 0.5…" and nobody can hold a picture in their head from that. So the
-* geometry gets a widget — the canvas, drawn at the grid's own aspect ratio,
-* with the cells on it — while the knobs that ARE ordinary fields (the name,
-* the canvas size, the frame rate) sit beside it in the same panel.
-*
-* Every rectangle in here is NORMALIZED [0,1], on both sides: the crop taken
-* out of a source, and the cell it lands in. That is how the addon stores them
-* (a source camera can change resolution, and a stored pixel rectangle would
-* quietly start cutting the wrong region), so the editor speaks the same
-* language rather than converting at the boundary.
-*
-* The preview is the source cameras' own snapshots, positioned by CSS from the
-* SAME normalized numbers that will become the ffmpeg `crop`/`overlay`. It costs
-* the server nothing and it is wrong in exactly the ways the real composition
-* would be wrong.
-*/
 import { type JSX } from "react";
 export interface CameraGridLayoutEditorProps {
 	readonly deviceId: number;

package/dist/composites/cap-settings/ConsumablesPanel.d.ts

@@ -1,21 +1,3 @@
-/**
-* ConsumablesPanel — maintenance-items surface for the generic
-* `consumables` capability. A cap-settings component (ui-library),
-* mounted as a cap-contributed top-level device-detail tab via the
-* cap-UI contribution mechanism (the `consumables` cap declares
-* `ui: { kind:'widget', widgetId:'host/consumables-panel', tab:'consumables', topTab:true, ... }`).
-*
-* Reads the cap's pushed runtime-state slice via `useDeviceCapability`
-* and renders one row per item: a fill bar + percentage when `level` is
-* known, else an `ok`/`replace` status pill when `status` is known, else
-* a muted em-dash. When a provider also reports `remaining` (a count in
-* days/hours/cycles), its value is shown alongside — `null` renders a
-* muted em-dash, never a fake `0` (D393); absent `remaining` renders
-* nothing, exactly as before this field existed. A per-item "Replaced"
-* button calls `cap.reset` when the item is `resettable`. The cap is
-* inert until a provider sets items — an empty list renders a muted
-* placeholder.
-*/
 import { type JSX } from "react";
 import type { CapSettingsComponentProps } from "./index";
 export declare function ConsumablesPanel({ deviceId }: CapSettingsComponentProps): JSX.Element;

package/dist/composites/cap-settings/MaskShapeCanvas.d.ts

@@ -1,105 +1,3 @@
-/**
-* MaskShapeCanvas — ONE shared, Konva-based on-frame "drawing plane" editor
-* that handles ALL four `MaskShape` kinds: `rect`, `polygon`, `grid`, `line`.
-*
-* It is a generalization of the detection `ZoneCanvas` (orchestrator) so that
-* privacy-mask (rect/polygon), motion-zones (grid), and the
-* pipeline-orchestrator zones/lines editor can eventually all share a single
-* editor instead of three bespoke ones. Every coordinate is normalized 0..1 of
-* the camera frame (top-left origin), like every existing on-frame editor.
-*
-* ─────────────────────────────────────────────────────────────────────────────
-* Behaviours ported (the references are NOT edited — this generalizes them):
-*
-*   - From `ZoneCanvas` (orchestrator zone-editor):
-*       • ResizeObserver-sized `<Stage>`, `transparent` absolute-fill overlay
-*         mode for layering over a stream player, optional `backdrop` slot,
-*         pointer-events pass-through while not editing.
-*       • polygon draw / vertex-drag / body-drag with optimistic local override
-*         + the `useEffect` that drops the override once the controlled prop
-*         echoes the commit back, the rAF-throttled cursor ghost-line preview,
-*         the `Arrow` tripwire, and the memoised export.
-*   - From `PrivacyMaskCanvas`:
-*       • rect move + bottom-right-handle resize with 0..1 clamp, polygon
-*         vertex add (edge midpoint) / remove (✕, gated by min/max), and the
-*         `polygonVertices` {min,max} gate (e.g. Hikvision {min:4,max:4}).
-*   - From `MotionGridCanvas`:
-*       • grid cell-paint gesture (press-drag paints every touched cell to the
-*         value the first-touched cell flipped to), row-major `cells`.
-*
-* ─────────────────────────────────────────────────────────────────────────────
-* Usage — each consumer maps its own model onto `MaskShapeItem[]` and gates the
-* editor with `supportedShapes`:
-*
-* @example privacy-mask (rect + polygon)
-* ```tsx
-* const items: MaskShapeItem[] = regions.map((r) => ({ id: r.id, shape: r.shape }))
-* <MaskShapeCanvas
-*   transparent
-*   items={items}
-*   supportedShapes={['rect', 'polygon']}
-*   polygonVertices={options.polygonVertices}        // Hikvision {min:4,max:4}
-*   selectedId={selectedId}
-*   onSelect={setSelectedId}
-*   onShapeChange={(id, shape) =>
-*     onRegionsChange(regions.map((r) => (r.id === id ? { ...r, shape } : r)))}
-*   onDrawComplete={(shape) => onRegionsChange([...regions, { id: nextId(), shape }])}
-*   drawingKind={drawing ? 'rect' : null}
-* />
-* ```
-*
-* @example motion-zones (grid)
-* ```tsx
-* const items: MaskShapeItem[] = [{
-*   id: 'motion',
-*   shape: { kind: 'grid', gridWidth: w, gridHeight: h, cells },
-* }]
-* <MaskShapeCanvas
-*   transparent
-*   items={items}
-*   supportedShapes={['grid']}
-*   grid={{ width: w, height: h }}
-*   selectedId="motion"
-*   onSelect={() => {}}
-*   onShapeChange={(_id, shape) => {
-*     if (shape.kind === 'grid') onCellsChange(shape.cells)
-*   }}
-*   onDrawComplete={() => {}}
-*   drawingKind={null}
-* />
-* ```
-*
-* @example orchestrator (polygon + line/tripwire)
-* ```tsx
-* const items: MaskShapeItem[] = zones.map((z) => ({
-*   id: z.id,
-*   label: z.name,
-*   color: z.color,
-*   shape: z.kind === 'tripwire'
-*     ? { kind: 'line', points: z.points }
-*     : { kind: 'polygon', points: z.points },
-* }))
-* <MaskShapeCanvas
-*   transparent
-*   items={items}
-*   supportedShapes={['polygon', 'line']}
-*   selectedId={selectedZoneId}
-*   onSelect={onSelectZone}
-*   onShapeChange={(id, shape) => {
-*     if (shape.kind === 'polygon' || shape.kind === 'line')
-*       onZonePointsChange(id, shape.points)
-*   }}
-*   onDrawComplete={(shape) => onZoneComplete(shape)}
-*   drawingKind={drawingKind === 'tripwire' ? 'line' : drawingKind}
-*   backdrop={<CameraStreamPlayer ... />}
-* />
-* ```
-*
-* Purely controlled — the parent owns the truth. Every edit fires
-* `onShapeChange(id, shape)` (or `onDrawComplete(shape)` for a freshly-drawn
-* shape) with a brand-new immutable shape object; points and cells are never
-* mutated in place.
-*/
 import { type JSX, type MemoExoticComponent, type ReactNode } from "react";
 import type { MaskShape, MaskShapeKind } from "@camstack/types";
 /** One editable item on the drawing plane. */

package/dist/composites/cap-settings/MotionZonesSettings.d.ts

@@ -1,41 +1,3 @@
-/**
-* MotionZonesSettings — management surface for the on-camera
-* `motion-zones` capability. A cap-settings component (ui-library),
-* mounted into the device-detail Config tab via the cap-UI
-* contribution mechanism (the `motion-zones` cap declares a `ui` block).
-*
-* The on-camera motion mask is a SINGLE `grid` region in the shared
-* MaskShape vocabulary (a row-major boolean cell lattice). This component
-* owns its own control panel (Edit toggle, All on / All off / Invert,
-* count, Revert, Save) and paints the editable lattice over the live frame
-* with the shared `MaskShapeCanvas` drawing-plane — registered as a
-* player-overlay layer ONLY while "Edit grid" is toggled on (OFF by
-* default — nothing draws on mount).
-*
-* Detection enable + sensitivity are NOT edited here — they are the
-* camera's on-board motion master switch, owned by the driver's
-* "On-camera motion" settings section. Saving sends a `cells`-only patch
-* (one grid region); enable / sensitivity are left untouched camera-side.
-*
-* ── Resizable input grid (resampled to the camera grid on save) ──────────────
-* The camera's native motion grid (`getOptions().grid`, e.g. 22×18) is the
-* FINEST resolution that round-trips — painting finer than it can't be stored
-* (not reconstructible). So the camera grid is the FLOOR (×1) and the operator
-* picks BIGGER cells: an integer cell-size multiplier (×1/×2/×3) where a UI cell
-* spans an m×m block of camera cells (×2 → quarter as many, ×3 → ninth). The
-* CAMERA grid stays authoritative:
-*   - LOAD: the camera grid is COARSENED into the chosen UI resolution (a UI
-*     cell is `true` if ANY camera cell in its block is painted) so existing
-*     masks display on the bigger-celled surface.
-*   - SAVE: the UI grid is EXPANDED back to camera gridWidth×gridHeight — every
-*     camera cell takes the value of the UI cell whose block covers it.
-* At ×1 both transforms are the identity, so the camera-grid round-trip is
-* exact; at higher multipliers `coarsen(expand(uiCells)) === uiCells`, so an
-* edit made at the chosen resolution survives the round-trip exactly. The
-* component's draft (`uiCells`) lives at the UI resolution; the last-saved truth
-* (`committedCamera`) and every comparison stay anchored to the camera-native
-* grid so `dirty`/Save/Revert math is resolution-independent.
-*/
 import { type JSX } from "react";
 import type { CapSettingsComponentProps } from "./index";
 export declare function MotionZonesSettings({ deviceId }: CapSettingsComponentProps): JSX.Element | null;

package/dist/composites/cap-settings/SceneReferenceGallery.d.ts

@@ -1,41 +1,3 @@
-/**
-* SceneReferenceGallery — the photographs a scene is actually judging against,
-* grouped by lighting variant, each individually deletable.
-*
-* ## Why it has to exist
-*
-* A scene's whole answer is "does this region still look like the photograph".
-* Until now the operator could see a COUNT of references and never the
-* references themselves, which makes the two failure modes indistinguishable
-* from the outside: a blurry capture taken while a van was in the way poisons a
-* condition forever, and from a cosine score there is no way to tell which one
-* it was. `deleteReference` shipped with the cap for exactly this and had no
-* caller.
-*
-* ## The image
-*
-* A bare `<img>` against the `event-media` data plane
-* (`/addon/pipeline-analytics/event-media/m/<mediaId>` — D482), which is
-* `access: 'authenticated'` — that accepts the `camstack_session` cookie, and a
-* cookie is the only credential an `<img>` can send. Same mechanism, and the
-* same reasoning, as `use-device-snapshot`; no bearer-token blob fetch is
-* needed and no second copy of the auth plumbing is introduced here.
-*
-* `SceneReference.thumbnailMediaId` finally IS a media row id (D482). It was
-* named `…MediaId` while holding a composite MediaStore key
-* (`scene:<ownerId>:thumbnailSmall:<ts>`), which this component read
-* POSITIONALLY for its owner id — a name that described the right design
-* beside a value that did not, which is the shape of leftover this repo has
-* been bitten by three times. The tile now addresses the row.
-*
-* **A missing blob is normal, not exceptional.** Reference thumbnails written
-* before the `ownerKind: 'scene'` fix carried an `ownerId` no event row backs,
-* which made them eligible for the orphan sweep — so on an existing install
-* some of these ids resolve to nothing. That must degrade to a dated
-* placeholder: the reference is still real, still being scored against, and
-* still deletable. A gallery that blanks or throws over a missing picture would
-* take the delete button away exactly when it is needed.
-*/
 import type { SceneMonitor, SceneReference } from "@camstack/types";
 import { type JSX } from "react";
 /** The hub-proxied prefix for the pipeline-analytics event-media data plane. */

package/dist/composites/cap-settings/scene-monitor-copy.d.ts

@@ -8,6 +8,7 @@
 * lighting the scene has never been captured in.
 */
 import type { SceneMonitor } from "@camstack/types";
+import { type UiTextFn } from "../../contexts/ui-text";
 /** The lighting variants an operator is OFFERED. The resolver can also report
 *  `night`, `dawn` and `dusk`; those are shown when present but never demanded,
 *  because most installs only ever see day and IR. */
@@ -24,8 +25,12 @@ export type SceneCaptureVariant = (typeof SCENE_CAPTURE_VARIANTS)[number];
 * `onUncoveredCondition: 'skip'` the night checks are simply not made.
 */
 export declare const SCENE_OPTIONAL_VARIANT: SceneCaptureVariant;
-export declare const VARIANT_LABEL: Readonly<Record<string, string>>;
-export declare function variantLabel(condition: string): string;
+interface VariantLabelEntry {
+	readonly labelKey: string;
+	readonly labelFallback: string;
+}
+export declare const VARIANT_LABEL: Readonly<Record<string, VariantLabelEntry>>;
+export declare function variantLabel(condition: string, t?: UiTextFn): string;
 /**
 * "Daylight ✓ · Night (IR) ✗ — optional; checks in night (ir) are skipped."
 *
@@ -39,7 +44,7 @@ export declare function variantLabel(condition: string): string;
 * is — the part you do not have to do — and the sentence says what actually
 * happens instead, which differs by the scene's own policy.
 */
-export declare function coverageLine(monitor: SceneMonitor): string;
+export declare function coverageLine(monitor: SceneMonitor, t?: UiTextFn): string;
 /**
 * The calm sentence for a scene that is sitting the current light out — `null`
 * whenever it is checking normally.
@@ -49,12 +54,12 @@ export declare function coverageLine(monitor: SceneMonitor): string;
 * needs nothing from the operator; the only thing worth saying is which light
 * it is waiting out and that it will pick itself back up.
 */
-export declare function suspensionLine(monitor: SceneMonitor): string | null;
+export declare function suspensionLine(monitor: SceneMonitor, t?: UiTextFn): string | null;
 /**
 * The one line under a scene's name. It answers, in order: can it judge, what
 * does it say, and how long has it said it.
 */
-export declare function statusLine(monitor: SceneMonitor, now: number): string;
+export declare function statusLine(monitor: SceneMonitor, now: number, t?: UiTextFn): string;
 /** The badge word. `latched` wins over `verdict`, because the latch is the
 *  thing the operator asked to be told and it outlives the live state.
 *
@@ -62,7 +67,7 @@ export declare function statusLine(monitor: SceneMonitor, now: number): string;
 *  never `alarm`, and never the `danger` variant the page maps that to. A
 *  missing IR reference must not be able to paint a red badge on a scene that
 *  is doing exactly what it was configured to do. */
-export declare function badgeFor(monitor: SceneMonitor): {
+export declare function badgeFor(monitor: SceneMonitor, t?: UiTextFn): {
 	text: string;
 	tone: "alarm" | "ok" | "unknown";
 };
@@ -76,3 +81,4 @@ export declare function roiTooLarge(roi: {
 	height: number;
 }): boolean;
 export declare function humanDuration(ms: number): string;
+export {};

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

@@ -28,6 +28,7 @@
 * an operator whether to look at the card, the network or the firmware.
 */
 import type { ClipSource } from "@camstack/types";
+import { type UiTextFn } from "../../contexts/ui-text.js";
 /** How loudly a source's state should read. Never the whole message. */
 export type ClipSourceTone = "ok" | "warn" | "error";
 /** A source's state, rendered. */
@@ -52,7 +53,7 @@ export interface ClipSourceNotice {
 	readonly answered: boolean;
 }
 /** Turn one source row into the line the picker and the list show. */
-export declare function describeSource(source: ClipSource): ClipSourceNotice;
+export declare function describeSource(source: ClipSource, t?: UiTextFn): ClipSourceNotice;
 /**
 * How old a source's catalog is, or null when it did not say.
 *
@@ -60,4 +61,4 @@ export declare function describeSource(source: ClipSource): ClipSourceNotice;
 * 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;
+export declare function formatCatalogAge(catalogAsOf: number | undefined, now: number, t?: UiTextFn): string | null;

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

@@ -1,3 +1,4 @@
+import { type UiTextFn } from "../../contexts/ui-text.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>;
@@ -13,4 +14,4 @@ export type MintedThumbnail = {
 * 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>;
+export declare function fetchMintedThumbnail(url: string, fetcher: ThumbnailFetcher, t?: UiTextFn): Promise<MintedThumbnail>;

package/dist/composites/clips/clip-tile-media.d.ts

@@ -34,6 +34,7 @@
 * tested against that build.
 */
 import type { Clip } from "@camstack/types";
+import { type UiTextFn } from "../../contexts/ui-text.js";
 /** The five things a tile can be. */
 export type ClipTileMedia = {
 	readonly kind: "vouched";
@@ -64,7 +65,7 @@ export interface MintRefusalHeaders {
 	readonly retryAfterMs?: number | null;
 }
 /** What to draw for one clip's tile. */
-export declare function resolveTileMedia(clip: Clip): ClipTileMedia;
+export declare function resolveTileMedia(clip: Clip, t?: UiTextFn): ClipTileMedia;
 /**
 * A 204, as something the tile can draw.
 *
@@ -74,4 +75,4 @@ export declare function resolveTileMedia(clip: Clip): ClipTileMedia;
 * vocabulary that moves is a tile that stops early, never one that asks for
 * ever.
 */
-export declare function describeRefusal(headers: MintRefusalHeaders): ClipTileMedia;
+export declare function describeRefusal(headers: MintRefusalHeaders, t?: UiTextFn): ClipTileMedia;

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

@@ -30,6 +30,7 @@
 */
 import type { Clip, ClipSource } from "@camstack/types";
 import type { ClipBand, ClipBandPlan } from "./clip-band.js";
+import { type UiTextFn } from "../../contexts/ui-text.js";
 import { type ClipSourceNotice } from "./clip-source-state.js";
 /** React Query's settled-ness, narrowed to what this decision needs. */
 export type ClipQueryStatus = "pending" | "error" | "success";
@@ -83,4 +84,4 @@ export type ClipsViewState = {
 	readonly answered: readonly ClipSourceNotice[];
 	readonly silent: readonly ClipSourceNotice[];
 };
-export declare function resolveClipsView(input: ClipsViewInput): ClipsViewState;
+export declare function resolveClipsView(input: ClipsViewInput, t?: UiTextFn): ClipsViewState;

package/dist/composites/confirm-dialog.d.ts

@@ -1,65 +1,3 @@
-/**
-* The ONE modal dialog of the product — confirm, alert and prompt.
-*
-* ## Why all three live here
-*
-* The admin UI used to reach for `window.confirm` / `window.alert` /
-* `window.prompt` wherever a `useConfirm()` call was inconvenient. A native
-* dialog is wrong on three counts, and the operator hit the worst one on
-* Identity → Users: resetting a password opened `window.prompt`, which
-* **cannot mask its input**. A new password was typed in clear text, into a
-* box the browser may offer to remember. On top of that a native dialog
-* matches none of the product's visual language and the host can neither style
-* nor test it.
-*
-* So the fix is not "a password modal" — a second dialog component is the
-* defect, not the cure. The provider that already served every confirm in the
-* admin UI (and in the viewer, which documents its own copy as "deliberately
-* the same one `@camstack/ui-library` exposes to the admin UI") grew two more
-* intents. One provider, one backdrop, one visual language, one set of
-* keyboard rules.
-*
-* ## The three intents are NOT one control
-*
-* - `confirm` — a destructive yes/no. It names what is destroyed, and for the
-*   `danger` variant the destructive button is the NON-default: opening focus
-*   lands on Cancel, so a reflexive Enter cancels.
-* - `alert` — an error/notice with a single acknowledge.
-* - `prompt` — one text input with OK/Cancel. `inputType: 'password'` masks it
-*   (and opts out of autofill/remember); `readOnly` turns it into a readable,
-*   select-all-on-open field, which is the shape the copy-to-clipboard
-*   fallback needs — a password box would be actively wrong there.
-*
-* ## Why the surface is a native `<dialog>`
-*
-* These dialogs open OVER surfaces that are themselves native `<dialog>`s
-* opened with `showModal()` — the event detail panel, the similar-groups
-* modal. A `showModal()` dialog is promoted to the TOP LAYER and everything
-* outside it is inert, so a plain `fixed inset-0` overlay rendered at the app
-* root would be drawn behind that backdrop and could not be clicked at all.
-* Confirming a track delete from the detail panel would have been impossible.
-* So this surface is a `<dialog>` of its own: the top layer stacks, the newest
-* `showModal()` wins, and the confirm sits above the panel that asked for it.
-*
-* jsdom implements `<dialog>` but not `showModal()`, so the open falls back to
-* the `open` attribute there. Everything this component does — focus, keys,
-* resolution — is identical on both paths; only the top-layer promotion, which
-* jsdom cannot model at all, is missing. The fallback is asserted below.
-*
-* ## Focus, and why there is NO focus trap
-*
-* A `showModal()` dialog already scopes the tab ring to itself, and the
-* surfaces underneath (`SlideOverPanel`) implement no trap of their own. A
-* second, hand-rolled focus trap on top of that is how a page becomes
-* unescapable, so this component deliberately does not trap. What it does do:
-*
-* - focuses the input (prompt) or the DEFAULT button on open,
-* - restores focus to the previously focused element on close,
-* - handles Escape/Enter from a `keydown` on the dialog itself and calls
-*   `stopPropagation()`. React attaches its listeners at the root container, so
-*   stopping there keeps the event from reaching the `window` Escape listener
-*   of whatever modal is underneath: one Escape closes ONE dialog.
-*/
 import { type JSX, type ReactNode } from "react";
 export type DialogVariant = "danger" | "warning" | "default";
 export interface ConfirmOptions {

package/dist/composites/data-table.d.ts

@@ -33,9 +33,7 @@
 * The table stays a table. The wrapper is `overflow-x-auto`, so a phone
 * scrolls the columns sideways INSIDE the table — the page body never moves
 * sideways, and the cells stay one line (`whitespace-nowrap`). That is the
-* default (`mobileMode="scroll"`). Cards are opt-in via `mobileMode="cards"`;
-* `auto` still applies the old column-count rule for a surface that wants it.
-* See `resolveTableLayout`.
+* only rendering — there is no card list and no per-table switch.
 *
 * ── Scrolling the BODY, not the page ──────────────────────────────────────
 * `maxBodyHeight` caps the table and scrolls its rows INSIDE the container
@@ -48,7 +46,6 @@
 * the operator moves through the rows.
 */
 import { type ReactNode, type JSX } from "react";
-import { type TableMobileMode } from "./data-table-layout";
 import { type DataTablePaginationLabels } from "./data-table-pagination";
 import { type DataTableSelection } from "./data-table-selection";
 import { type TableSortState, type TableSortValue } from "./table-sort";
@@ -111,12 +108,6 @@ export interface DataTableProps<T> {
 	/** Per-row className resolver (e.g. status-coloured backgrounds). */
 	readonly rowClassName?: (row: T, rowIndex: number) => string | undefined;
 	/**
-	* Narrow-viewport rendering. Default `scroll` — the table stays a table and
-	* the wrapper scrolls sideways. Pass `cards` to force the card list,
-	* `auto` for the old column-count rule (`CARD_MODE_MIN_COLUMNS`).
-	*/
-	readonly mobileMode?: TableMobileMode;
-	/**
 	* Tailwind `max-h-*` class capping the table. The rows then scroll INSIDE
 	* this container and the column header is pinned to its top; the page around
 	* it does not move. Absent (default) = the table is as tall as its rows and
@@ -176,4 +167,4 @@ export interface DataTableProps<T> {
 * does not need a breakpoint of its own.
 */
 export declare const TABLE_SCROLL_MAX_H: "max-h-[60vh]";
-export declare function DataTable<T>({ columns, rows, rowKey, onRowClick, minWidthPx, emptyMessage, className, bordered, rowClassName, mobileMode, maxBodyHeight, fill, defaultSort, sort: sortProp, onSortChange, pageSize, page: pageProp, onPageChange, paginationLabels, selection }: DataTableProps<T>): JSX.Element | null;
+export declare function DataTable<T>({ columns, rows, rowKey, onRowClick, minWidthPx, emptyMessage, className, bordered, rowClassName, maxBodyHeight, fill, defaultSort, sort: sortProp, onSortChange, pageSize, page: pageProp, onPageChange, paginationLabels, selection }: DataTableProps<T>): JSX.Element | null;

package/dist/composites/detection-canvas.d.ts

@@ -1,12 +1,3 @@
-/**
-* DetectionCanvas — renders an image with overlaid bounding boxes.
-*
-* Adapted to the Phase 6 detection output rework: consumes the new
-* `ObjectDetection` shape (flat at root, `bbox: {x,y,width,height}`,
-* `labels: ScoredLabel[]`, `parentId` for details). Details (face,
-* plate) are drawn as inner boxes correlated with their parent via
-* `parentId`.
-*/
 import { type JSX, type ReactNode } from "react";
 export type { ObjectDetection, ScoredLabel, DetectionBoundingBox } from "@camstack/types";
 import type { ObjectDetection } from "@camstack/types";

package/dist/composites/detection-result-tree.d.ts

@@ -1,15 +1,3 @@
-/**
-* DetectionResultTree — displays detection results as a hierarchical tree.
-*
-* Adapted to the Phase 6 output rework: the tree consumes flat
-* `ObjectDetection[]` and correlates details (face / plate) with
-* their parents via `parentId`. First-level entries are top-level
-* nodes; their details render as indented children. Each node shows:
-*   - bbox (rectangle)
-*   - macroClass + score badge
-*   - `labels[]` (ScoredLabel — own + inherited)
-*   - `debug.alternateLabels` (top-N per source) when present
-*/
 import { type JSX } from "react";
 import type { ObjectDetection } from "@camstack/types";
 export interface DetectionResultTreeProps {

package/dist/composites/device-controls/container-primary-hero.d.ts

@@ -1,20 +1,3 @@
-/**
-* <ContainerPrimaryHero> — renders a CONTAINER device's detail hero AS its
-* primary child.
-*
-* The container has no surface of its own: it resolves a primary child
-* (priority default, or the operator's durable primary-child pick) and renders
-* THAT child's `HeroCard` from the shared control registry, bound to the child's
-* numeric id — identical to opening the child device directly.
-*
-* The override is persisted as the chosen child's re-sync/rename-stable
-* `entityId` (`primaryChildEntityId`); resolution matches on it directly — see
-* `container-primary.ts`. A legacy numeric `linkDeviceId` is still honored as a
-* fallback. Other children remain as detail tabs (owned by the device-detail
-* page); this component only owns the hero surface. The "primary child" picker
-* that overrides the resolution lives in the device's primary config block (see
-* admin-ui `PrimaryChildRow`), wired to `deviceManager.setPrimaryChildEntityId`.
-*/
 import type { ReactNode } from "react";
 import type { UseDeviceProxyTrpc } from "../../hooks/use-device-proxy";
 import { type ContainerChild } from "./container-primary";

package/dist/composites/device-controls/humidifier-control.d.ts

@@ -1,20 +1,3 @@
-/**
-* Humidifier controls for a `DeviceType.Humidifier` device.
-*
-* Reads the `humidifier` cap status slice (on / current / target /
-* mode / action / bounds) and renders:
-*   - HumidifierInlineControl (device-list row): a compact on/off
-*     tap-toggle + a small `current%→target%` readout. Row-narrow.
-*   - HumidifierHeroCard (device-detail hero): a bespoke state-tinted
-*     droplet + rising-mist SVG in the framed-box language, an on/off
-*     toggle, a target-humidity range slider with a `%` readout, a
-*     current-humidity readout, and a mode `<select>` (only when modes
-*     are available).
-*
-* Mirrors the climate / valve controls' `useDeviceCapability` +
-* `useOptimisticSlice` pattern so the row and hero never diverge.
-* Controls are gated on `available`. The decorative SVG is aria-hidden.
-*/
 import { type ReactNode } from "react";
 import type { DeviceControlProps } from "./control-registry";
 /** The `action` HA attribute drives the droplet / mist tint. */

package/dist/composites/device-controls/lawn-mower-control.d.ts

@@ -14,6 +14,7 @@
 */
 import type { ReactNode } from "react";
 import type { LawnMowerActivity } from "@camstack/types";
+import { type UiTextFn } from "../../contexts/ui-text";
 import type { DeviceControlProps } from "./control-registry";
 export interface LawnMowerActivityMeta {
 	readonly label: string;
@@ -25,7 +26,7 @@ export interface LawnMowerActivityMeta {
 * yet) to a human label + colour tone. Exhaustive switch: a new enum
 * member fails the build.
 */
-export declare function lawnMowerActivityMeta(activity: LawnMowerActivity | undefined): LawnMowerActivityMeta;
+export declare function lawnMowerActivityMeta(activity: LawnMowerActivity | undefined, t?: UiTextFn): LawnMowerActivityMeta;
 /**
 * LawnMowerInlineControl — compact, activity-aware mower controls for a
 * device-list row. Mow / Pause / Dock + battery badge.

package/dist/composites/device-controls/pet-feeder-panel.d.ts

@@ -1,21 +1,3 @@
-/**
-* Pet-feeder controls for a `DeviceType.PetFeeder` device.
-*
-* Reads the `pet-feeder` cap status slice (foodLevel / food1 / food2 /
-* lowFood / batteryPower / desiccantLeftDays / feeding / status / error /
-* errorCode / isDualHopper + the four persisted settings) and renders:
-*   - PetFeederInlineControl (device-list row): a compact food-level +
-*     battery readout with a one-tap Feed button (default portion).
-*   - PetFeederHeroCard (device-detail hero): the food-bowl fill gauge
-*     signature, battery + desiccant readouts, a manual-feed portion
-*     stepper honouring the 4-200 g hardware range (per-hopper on
-*     dual-hopper models), a maintenance action row (Call pet / Reset
-*     desiccant / Mark refilled) and the child-lock / indicator-light /
-*     feed-sound / volume settings.
-*
-* Mirrors the AC card's `useDeviceCapability` + inferred-cap pattern so
-* the row and hero never diverge. Actions are gated on `available`.
-*/
 import { type ReactNode } from "react";
 import type { ControlPanelProps } from "./types.js";
 export declare function PetFeederPanel({ trpc, deviceId, layout, optimistic }: ControlPanelProps): ReactNode;

package/dist/composites/device-controls/script-automation-controls.d.ts

@@ -1,4 +1,5 @@
 import type { ReactNode } from "react";
+import { type UiTextFn } from "../../contexts/ui-text";
 import type { DeviceControlProps } from "./control-registry";
 /**
 * "3 min ago", or nothing at all.
@@ -7,7 +8,7 @@ import type { DeviceControlProps } from "./control-registry";
 * epoch. "1 Jan 1970" next to a script is the kind of detail that sends an
 * operator looking for a clock problem that does not exist.
 */
-export declare function lastRunLabel(atMs: number, nowMs: number): string | null;
+export declare function lastRunLabel(atMs: number, nowMs: number, t?: UiTextFn): string | null;
 export declare function ScriptInlineControl({ trpc, deviceId, optimistic }: DeviceControlProps): ReactNode;
 export declare function ScriptHeroCard({ trpc, deviceId, optimistic }: DeviceControlProps): ReactNode;
 export declare function AutomationInlineControl({ trpc, deviceId, optimistic }: DeviceControlProps): ReactNode;