@camstack/system 1.2.390 → 1.2.392

package/dist/builtins/sqlite-storage/retired-settings-keys.d.ts

@@ -1,226 +1,276 @@
-import { ISettingsBackend, SettingsCollection } from '@camstack/types';
+/**
+* Retired settings keys — the boot-time purge of DEAD configuration.
+*
+* ## Why this exists
+*
+* When a feature is removed, its persisted keys stay in the store. Nothing
+* reads them, so nothing breaks — and that is exactly the problem: a dead key
+* still LOOKS like live configuration. On 2026-08-07 an audit read
+* `object-detection: yolo26m-256` out of `detection-pipeline`'s `pipelineSteps`
+* blob — a global step seed removed months earlier, that no live per-camera
+* dispatch has ever consulted — and spent an hour investigating a package-zone
+* fault against a model the node was not running.
+*
+* The fix is not a hand `DELETE`. A hand delete cleans one machine once: the
+* next boot of that node, and every restore of a backup taken before it, brings
+* the keys back. This purge runs at every boot of the settings engine ON THE
+* HUB, so the store CONVERGES no matter how it got there.
+*
+* ## Where it runs: the hub, and only the hub
+*
+* The addon settings store is hub-central. `settings-store` is a `singleton`
+* cap that resolves to the hub, so every node's `ctx.settings` reads and writes
+* the HUB's rows — an agent's own SQLite file holds node-local collections only
+* (`platform-probe`, `metrics-native`, `hub-forwarder`). Measured 2026-08-07:
+* neither agent even has a `detection-pipeline:addon-settings` table.
+*
+* So there is exactly one copy of the data to clean, and running the machinery
+* on every node's boot would be work that can never find anything. The gate is
+* {@link settingsStoreIsAuthoritativeHere}, and an agent skips SILENTLY — a
+* "skipped" line on every agent boot forever is noise about work that has no
+* reason to happen there.
+*
+* ## Contract
+*
+* - **Idempotent.** A clean row plans nothing, writes nothing, logs nothing.
+* - **Loud exactly once**, and only when it actually deletes: one line naming
+*   the addon, the row and the keys.
+* - **Exact-match only.** A retired key never prefix- or substring-matches, so
+*   the live `videoPipelineSteps` survives the retirement of `pipelineSteps`.
+*   `perNodeKeys` additionally match the `<key>@<nodeId>` form the per-node
+*   store writes (`nodeScopedKey`), and nothing else.
+* - **A failed read never writes.** Same rule as `settings-read-guard.ts`: a
+*   read fault answering "empty" would rewrite the row to `{}` and destroy the
+*   live keys the purge exists to protect.
+*
+* ## Adding a key
+*
+* Only add a key you have TRACED to having no reader. The registry is a claim
+* that the key is dead; it is enforced by nothing else.
+*/
+import type { ISettingsBackend, SettingsCollection } from "@camstack/types";
 /** One retired-key declaration, scoped to a single store row. */
 export interface RetiredKeySpec {
-    /** Addon id owning the store (the settings-store namespace). */
-    readonly namespace: string;
-    /** Collection inside that namespace, e.g. `addon-settings`. */
-    readonly collection: SettingsCollection;
-    /** Row id inside the collection, e.g. `root`. */
-    readonly row: string;
-    /** Keys retired verbatim. Matched exactly. */
-    readonly keys: readonly string[];
-    /**
-     * Keys retired in both their bare form and their per-node form
-     * (`<key>@<nodeId>`), which is how `nodeScopedKey` persists a
-     * `perNode: true` schema field.
-     */
-    readonly perNodeKeys: readonly string[];
-    /**
-     * Keys retired one level DOWN, inside each object value of a map-shaped row.
-     *
-     * `device-manager`'s `deviceMeta` row is `{ [deviceId]: PersistedDeviceMeta }`:
-     * the dead key is not a key of the row, it is a key of each device's meta.
-     * Absent ⇒ the row is treated as flat and nothing nested is touched.
-     */
-    readonly mapValueKeys?: readonly string[];
-    /** Why they are dead — cited in the record, not re-derived at the call site. */
-    readonly reason: string;
+	/** Addon id owning the store (the settings-store namespace). */
+	readonly namespace: string;
+	/** Collection inside that namespace, e.g. `addon-settings`. */
+	readonly collection: SettingsCollection;
+	/** Row id inside the collection, e.g. `root`. */
+	readonly row: string;
+	/** Keys retired verbatim. Matched exactly. */
+	readonly keys: readonly string[];
+	/**
+	* Keys retired in both their bare form and their per-node form
+	* (`<key>@<nodeId>`), which is how `nodeScopedKey` persists a
+	* `perNode: true` schema field.
+	*/
+	readonly perNodeKeys: readonly string[];
+	/**
+	* Keys retired one level DOWN, inside each object value of a map-shaped row.
+	*
+	* `device-manager`'s `deviceMeta` row is `{ [deviceId]: PersistedDeviceMeta }`:
+	* the dead key is not a key of the row, it is a key of each device's meta.
+	* Absent ⇒ the row is treated as flat and nothing nested is touched.
+	*/
+	readonly mapValueKeys?: readonly string[];
+	/** Why they are dead — cited in the record, not re-derived at the call site. */
+	readonly reason: string;
 }
 /** What a purge pass deleted from one row. */
 export interface RetiredKeyPurgeResult {
-    readonly addon: string;
-    readonly collection: string;
-    readonly row: string;
-    readonly keys: readonly string[];
-    /** `<mapKey>.<retiredKey>` for every nested deletion. Empty for a flat row. */
-    readonly nested: readonly string[];
+	readonly addon: string;
+	readonly collection: string;
+	readonly row: string;
+	readonly keys: readonly string[];
+	/** `<mapKey>.<retiredKey>` for every nested deletion. Empty for a flat row. */
+	readonly nested: readonly string[];
 }
 /** The store access the purge needs. Narrow on purpose — trivially fakeable. */
 export interface RetiredKeyStore {
-    /** Current row value, or `null` when the row does not exist. Throws on fault. */
-    read(spec: RetiredKeySpec): Promise<Record<string, unknown> | null>;
-    /** Replace the row with `value`. */
-    write(spec: RetiredKeySpec, value: Record<string, unknown>): Promise<void>;
+	/** Current row value, or `null` when the row does not exist. Throws on fault. */
+	read(spec: RetiredKeySpec): Promise<Record<string, unknown> | null>;
+	/** Replace the row with `value`. */
+	write(spec: RetiredKeySpec, value: Record<string, unknown>): Promise<void>;
 }
 /**
- * The store access the ROW purge needs. Separate from {@link RetiredKeyStore}
- * because it has a different owner: a retired row is purged by the ADDON that
- * stopped writing it, right after it has declared the successor collection —
- * not by the settings engine at its own boot, which runs before any addon has
- * declared anything and would find every successor unreadable, forever.
- */
+* The store access the ROW purge needs. Separate from {@link RetiredKeyStore}
+* because it has a different owner: a retired row is purged by the ADDON that
+* stopped writing it, right after it has declared the successor collection —
+* not by the settings engine at its own boot, which runs before any addon has
+* declared anything and would find every successor unreadable, forever.
+*/
 export interface RetiredRowStore {
-    /** Does the row exist at all? Throws on fault. */
-    hasRow(spec: RetiredRowSpec): Promise<boolean>;
-    /** Delete the row outright. Idempotent. */
-    deleteRow(spec: RetiredRowSpec): Promise<void>;
-    /** How many rows the evidence collection holds. Throws on fault. */
-    countRows(collection: SettingsCollection): Promise<number>;
+	/** Does the row exist at all? Throws on fault. */
+	hasRow(spec: RetiredRowSpec): Promise<boolean>;
+	/** Delete the row outright. Idempotent. */
+	deleteRow(spec: RetiredRowSpec): Promise<void>;
+	/** How many rows the evidence collection holds. Throws on fault. */
+	countRows(collection: SettingsCollection): Promise<number>;
 }
 /** What a row purge deleted. */
 export interface RetiredRowPurgeResult {
-    readonly owner: string;
-    readonly collection: string;
-    readonly row: string;
+	readonly owner: string;
+	readonly collection: string;
+	readonly row: string;
 }
 /**
- * Is THIS node the one whose settings store is the cluster's authority?
- *
- * Mirrors `resolveNodeRole` (server/backend `node-role.ts`) — unset or `'hub'`
- * means hub, which is the launcher's own default. It is duplicated rather than
- * imported because `@camstack/system` is a dependency OF the backend, not the
- * other way round; the parse is four lines and the env var is the contract.
- *
- * Anything else answers `false`. Skipping where the purge should have run is a
- * missed cleanup the next hub boot fixes; running where it should not have is a
- * write to a store this node does not own. Only one of those is recoverable.
- */
+* Is THIS node the one whose settings store is the cluster's authority?
+*
+* Mirrors `resolveNodeRole` (server/backend `node-role.ts`) — unset or `'hub'`
+* means hub, which is the launcher's own default. It is duplicated rather than
+* imported because `@camstack/system` is a dependency OF the backend, not the
+* other way round; the parse is four lines and the env var is the contract.
+*
+* Anything else answers `false`. Skipping where the purge should have run is a
+* missed cleanup the next hub boot fixes; running where it should not have is a
+* write to a store this node does not own. Only one of those is recoverable.
+*/
 export declare function settingsStoreIsAuthoritativeHere(env: NodeJS.ProcessEnv): boolean;
 /** The logging surface the purge uses — a structural subset of `IScopedLogger`. */
 export interface RetiredKeyLogger {
-    info(message: string, context?: {
-        readonly meta?: Record<string, unknown>;
-    }): void;
-    warn(message: string, context?: {
-        readonly meta?: Record<string, unknown>;
-    }): void;
+	info(message: string, context?: {
+		readonly meta?: Record<string, unknown>;
+	}): void;
+	warn(message: string, context?: {
+		readonly meta?: Record<string, unknown>;
+	}): void;
 }
 /**
- * The dead keys, per row.
- *
- * ## Addressing these rows
- *
- * Every namespace below is a FORKED addon, whose `ctx.settings` comes from
- * `addon-context-factory` and writes `<addonId>:addon-settings` row `root`. The
- * scoped table is therefore the right target — unlike the hub builtin whose
- * mis-addressed spec is dissected at {@link RetiredRowSpec}. Confirmed per
- * namespace against `packages/<pkg>/package.json`'s manifest `id`.
- *
- * ## `keys` vs `perNodeKeys` is a data-loss decision, not a style choice
- *
- * `perNodeKeys` matches `<key>` AND `<key>@<nodeId>`. That is right for a key
- * whose per-node copies are all dead (the engine cascade, the decoder
- * `backend`). It is WRONG for `probedBestHwaccel` / `probedBestAudioBackend`,
- * where the bare key is unreachable residue but every `@<nodeId>` copy is the
- * node's live probe result — those go under `keys`, which is exact-match.
- *
- * `detection-pipeline` / `addon-settings` / `root` — every key in this row is
- * dead; the row itself is kept because the addon writes a live key into it
- * (`videoPipelineSteps`). `pipelineTemplates` is no longer read or written
- * (templates were removed, D759) and is deliberately NOT listed here: stored
- * template rows are left exactly as they are.
- *
- *  - `pipelineSteps` / `pipelineEngine`: the persisted GLOBAL step + engine
- *    seed. Removed with `getGlobalSteps` becoming pure — dispatch builds steps
- *    from the orchestrator's `agentSettings` plus per-camera overrides, and
- *    never consulted the seed. See `addon-pipeline/src/detection-pipeline/provider.ts`.
- *  - `engineRuntime` / `engineBackend` / `engineDevice` / `probedBestEngine`:
- *    the per-node engine CASCADE, removed with the operator-facing engine
- *    election. Each node now runs a device-array of inference pools balanced
- *    per session, and the node-default pool derives live from the node's own
- *    hardware (`resolveAutoEngine`). See
- *    `addon-pipeline/src/detection-pipeline/engine-store-keys.ts`.
- */
+* The dead keys, per row.
+*
+* ## Addressing these rows
+*
+* Every namespace below is a FORKED addon, whose `ctx.settings` comes from
+* `addon-context-factory` and writes `<addonId>:addon-settings` row `root`. The
+* scoped table is therefore the right target — unlike the hub builtin whose
+* mis-addressed spec is dissected at {@link RetiredRowSpec}. Confirmed per
+* namespace against `packages/<pkg>/package.json`'s manifest `id`.
+*
+* ## `keys` vs `perNodeKeys` is a data-loss decision, not a style choice
+*
+* `perNodeKeys` matches `<key>` AND `<key>@<nodeId>`. That is right for a key
+* whose per-node copies are all dead (the engine cascade, the decoder
+* `backend`). It is WRONG for `probedBestHwaccel` / `probedBestAudioBackend`,
+* where the bare key is unreachable residue but every `@<nodeId>` copy is the
+* node's live probe result — those go under `keys`, which is exact-match.
+*
+* `detection-pipeline` / `addon-settings` / `root` — every key in this row is
+* dead; the row itself is kept because the addon writes a live key into it
+* (`videoPipelineSteps`). `pipelineTemplates` is no longer read or written
+* (templates were removed, D759) and is deliberately NOT listed here: stored
+* template rows are left exactly as they are.
+*
+*  - `pipelineSteps` / `pipelineEngine`: the persisted GLOBAL step + engine
+*    seed. Removed with `getGlobalSteps` becoming pure — dispatch builds steps
+*    from the orchestrator's `agentSettings` plus per-camera overrides, and
+*    never consulted the seed. See `addon-pipeline/src/detection-pipeline/provider.ts`.
+*  - `engineRuntime` / `engineBackend` / `engineDevice` / `probedBestEngine`:
+*    the per-node engine CASCADE, removed with the operator-facing engine
+*    election. Each node now runs a device-array of inference pools balanced
+*    per session, and the node-default pool derives live from the node's own
+*    hardware (`resolveAutoEngine`). See
+*    `addon-pipeline/src/detection-pipeline/engine-store-keys.ts`.
+*/
 export declare const RETIRED_SETTINGS_KEYS: readonly RetiredKeySpec[];
 /**
- * Whole ROWS whose owner stopped writing them.
- *
- * A key purge cannot express this. It reads a row, drops keys, writes the rest
- * back — so retiring everything in a row leaves an empty row behind, and
- * retiring a row that IS a map of devices would mean listing 974 keys. What is
- * dead here is the row itself.
- *
- * ### Addressing: these rows are NOT namespaced
- *
- * `namespace` on a {@link RetiredKeySpec} is the settings-store namespace, and
- * it resolves to the table `<namespace>:<collection>`. That is right for an
- * addon whose `ctx.settings` came from `addon-context-factory` (a forked
- * runner), which writes `<addonId>:addon-settings` row `root`. A HUB BUILTIN
- * does not: its `ctx.settings` comes from `ConfigManager.createSettingsView`,
- * which is `getAllAddon` / `setAllAddon` — one row per key in the UNSCOPED
- * `addon-settings` table, keyed `<addonId>.<key>`.
- *
- * The device-manager is a hub builtin, so its rows are
- * `addon-settings` / `device-manager.deviceMeta` and never lived in
- * `device-manager:addon-settings`. The previous key-spec pointed at the scoped
- * table and was therefore a no-op on every hub that ever ran it — measured on
- * the 2026-08-19 evidence copy: `device-manager:addon-settings` has zero rows,
- * while `addon-settings` holds all six device-manager keys.
- *
- * ### Ordering: the guard is not optional
- *
- * These rows are the ONLY copy of the fleet until
- * `scripts/migrate-device-manager-blobs.mjs` has written
- * `device-manager:devices`. Purging them on a hub that has not been migrated
- * destroys every device. {@link purgeRetiredSettingsRows} therefore refuses
- * unless `evidence` — a collection that must be non-empty — actually is.
- */
+* Whole ROWS whose owner stopped writing them.
+*
+* A key purge cannot express this. It reads a row, drops keys, writes the rest
+* back — so retiring everything in a row leaves an empty row behind, and
+* retiring a row that IS a map of devices would mean listing 974 keys. What is
+* dead here is the row itself.
+*
+* ### Addressing: these rows are NOT namespaced
+*
+* `namespace` on a {@link RetiredKeySpec} is the settings-store namespace, and
+* it resolves to the table `<namespace>:<collection>`. That is right for an
+* addon whose `ctx.settings` came from `addon-context-factory` (a forked
+* runner), which writes `<addonId>:addon-settings` row `root`. A HUB BUILTIN
+* does not: its `ctx.settings` comes from `ConfigManager.createSettingsView`,
+* which is `getAllAddon` / `setAllAddon` — one row per key in the UNSCOPED
+* `addon-settings` table, keyed `<addonId>.<key>`.
+*
+* The device-manager is a hub builtin, so its rows are
+* `addon-settings` / `device-manager.deviceMeta` and never lived in
+* `device-manager:addon-settings`. The previous key-spec pointed at the scoped
+* table and was therefore a no-op on every hub that ever ran it — measured on
+* the 2026-08-19 evidence copy: `device-manager:addon-settings` has zero rows,
+* while `addon-settings` holds all six device-manager keys.
+*
+* ### Ordering: the guard is not optional
+*
+* These rows are the ONLY copy of the fleet until
+* `scripts/migrate-device-manager-blobs.mjs` has written
+* `device-manager:devices`. Purging them on a hub that has not been migrated
+* destroys every device. {@link purgeRetiredSettingsRows} therefore refuses
+* unless `evidence` — a collection that must be non-empty — actually is.
+*/
 export interface RetiredRowSpec {
-    /** Settings-store namespace, or absent for an unscoped collection. */
-    readonly namespace?: string;
-    readonly collection: SettingsCollection;
-    /** Row id inside that collection. */
-    readonly row: string;
-    /** Addon that owned the row — reported, never used to address it. */
-    readonly owner: string;
-    /**
-     * A collection that must hold at least one row before this one may go.
-     * The successor of the retired data: if it is empty, the migration has not
-     * run here and deleting is data loss, not cleanup.
-     */
-    readonly evidence: {
-        readonly collection: SettingsCollection;
-    };
-    readonly reason: string;
+	/** Settings-store namespace, or absent for an unscoped collection. */
+	readonly namespace?: string;
+	readonly collection: SettingsCollection;
+	/** Row id inside that collection. */
+	readonly row: string;
+	/** Addon that owned the row — reported, never used to address it. */
+	readonly owner: string;
+	/**
+	* A collection that must hold at least one row before this one may go.
+	* The successor of the retired data: if it is empty, the migration has not
+	* run here and deleting is data loss, not cleanup.
+	*/
+	readonly evidence: {
+		readonly collection: SettingsCollection;
+	};
+	readonly reason: string;
 }
 /**
- * The device-manager's three fleet blobs, replaced by one row per device in
- * `device-manager:devices` (`device-row-store.ts`).
- *
- * 625 KB of the `addon-settings` table's 627 KB, re-read and re-parsed on every
- * projection and rewritten in full on every rename. `deviceIndex` is listed
- * here like the other two even though it was never migrated: `addonId` and
- * `stableId` are columns of every row, so an addon's device list is a query,
- * and the one bit that was not derivable — "has `registerDevice` run?" — is the
- * `registered` column.
- */
+* The device-manager's three fleet blobs, replaced by one row per device in
+* `device-manager:devices` (`device-row-store.ts`).
+*
+* 625 KB of the `addon-settings` table's 627 KB, re-read and re-parsed on every
+* projection and rewritten in full on every rename. `deviceIndex` is listed
+* here like the other two even though it was never migrated: `addonId` and
+* `stableId` are columns of every row, so an addon's device list is a query,
+* and the one bit that was not derivable — "has `registerDevice` run?" — is the
+* `registered` column.
+*/
 export declare const RETIRED_SETTINGS_ROWS: readonly RetiredRowSpec[];
 /**
- * Adapt the settings backend to {@link RetiredKeyStore}.
- *
- * `get` answering a non-object (missing row) is a MISS, not a fault: it maps to
- * `null` and the purge skips the row. A backend throw propagates, which is what
- * routes it to the "read failed, row left untouched" branch.
- */
+* Adapt the settings backend to {@link RetiredKeyStore}.
+*
+* `get` answering a non-object (missing row) is a MISS, not a fault: it maps to
+* `null` and the purge skips the row. A backend throw propagates, which is what
+* routes it to the "read failed, row left untouched" branch.
+*/
 export declare function retiredKeyStoreOf(backend: ISettingsBackend): RetiredKeyStore;
 /**
- * Nested `<mapKey>.<retiredKey>` paths that `spec` retires inside a map-shaped
- * row. Pure. Values that are not plain objects are skipped, never rewritten.
- */
+* Nested `<mapKey>.<retiredKey>` paths that `spec` retires inside a map-shaped
+* row. Pure. Values that are not plain objects are skipped, never rewritten.
+*/
 export declare function planNestedRetiredKeyPurge(blob: Readonly<Record<string, unknown>>, spec: RetiredKeySpec): readonly string[];
 /** Keys of `blob` that `spec` retires. Pure. */
 export declare function planRetiredKeyPurge(blob: Readonly<Record<string, unknown>>, spec: RetiredKeySpec): readonly string[];
 /**
- * Delete every retired key present in the declared rows — on the hub.
- *
- * Off the authoritative node this is a no-op that touches nothing and says
- * nothing (see the module header). Returns one entry per row that actually
- * changed — empty when the store is already clean, which is the steady state
- * after the first boot that ran it.
- */
+* Delete every retired key present in the declared rows — on the hub.
+*
+* Off the authoritative node this is a no-op that touches nothing and says
+* nothing (see the module header). Returns one entry per row that actually
+* changed — empty when the store is already clean, which is the steady state
+* after the first boot that ran it.
+*/
 export declare function purgeRetiredSettingsKeys(store: RetiredKeyStore, logger: RetiredKeyLogger, specs?: readonly RetiredKeySpec[], env?: NodeJS.ProcessEnv): Promise<readonly RetiredKeyPurgeResult[]>;
 /**
- * Delete every retired ROW whose successor is populated — on the hub.
- *
- * Off the authoritative node this is a no-op that touches nothing and says
- * nothing, same gate as {@link purgeRetiredSettingsKeys}.
- *
- * **The evidence check is the whole safety of this function.** A retired row is
- * the only copy of its data until the migration has written the successor
- * collection, and the migration is an OFFLINE step an operator runs — it is not
- * part of boot. So a hub that boots the new code before being migrated must
- * find its blobs intact, not deleted: the purge SKIPS, loudly, and the next
- * boot after the migration cleans up. An evidence read that FAILS is treated
- * exactly like an empty one — a fault is never permission to delete.
- */
+* Delete every retired ROW whose successor is populated — on the hub.
+*
+* Off the authoritative node this is a no-op that touches nothing and says
+* nothing, same gate as {@link purgeRetiredSettingsKeys}.
+*
+* **The evidence check is the whole safety of this function.** A retired row is
+* the only copy of its data until the migration has written the successor
+* collection, and the migration is an OFFLINE step an operator runs — it is not
+* part of boot. So a hub that boots the new code before being migrated must
+* find its blobs intact, not deleted: the purge SKIPS, loudly, and the next
+* boot after the migration cleans up. An evidence read that FAILS is treated
+* exactly like an empty one — a fault is never permission to delete.
+*/
 export declare function purgeRetiredSettingsRows(store: RetiredRowStore, logger: RetiredKeyLogger, specs?: readonly RetiredRowSpec[], env?: NodeJS.ProcessEnv): Promise<readonly RetiredRowPurgeResult[]>;

package/dist/builtins/sqlite-storage/shm-lock-canary.d.ts

@@ -1,60 +1,60 @@
-import { IScopedLogger } from '@camstack/types';
+import type { IScopedLogger } from "@camstack/types";
 /** `UNIX_SHM_DMS`: the byte of the `-shm` a live connection holds shared. */
 export declare const SQLITE_SHM_DMS_BYTE = 128;
 /** How often the canary looks, in ms. One small procfs read. */
 export declare const SHM_LOCK_CANARY_INTERVAL_MS: number;
 /** One HELD lock from `/proc/locks`. Waiters (`->` lines) are not locks. */
 export interface ProcLock {
-    readonly pid: number;
-    /** The inode, as the decimal string procfs prints — never rounded through a double. */
-    readonly inode: string;
-    readonly start: number;
-    /** `null` = to end of file (`EOF`). */
-    readonly end: number | null;
+	readonly pid: number;
+	/** The inode, as the decimal string procfs prints — never rounded through a double. */
+	readonly inode: string;
+	readonly start: number;
+	/** `null` = to end of file (`EOF`). */
+	readonly end: number | null;
 }
 /**
- * Parse `/proc/locks`. Line shape:
- * `1: POSIX  ADVISORY  READ 3490531 08:31:3769403373 128 128`
- * (`id: TYPE MODE ACCESS PID MAJ:MIN:INODE START END`). A blocked waiter is
- * printed as `1: -> POSIX …` and holds nothing, so it is skipped; a line that
- * does not parse is skipped rather than guessed at.
- */
+* Parse `/proc/locks`. Line shape:
+* `1: POSIX  ADVISORY  READ 3490531 08:31:3769403373 128 128`
+* (`id: TYPE MODE ACCESS PID MAJ:MIN:INODE START END`). A blocked waiter is
+* printed as `1: -> POSIX …` and holds nothing, so it is skipped; a line that
+* does not parse is skipped rather than guessed at.
+*/
 export declare function parseProcLocks(text: string): readonly ProcLock[];
 /** Does a lock owned by `pid` on `inode` cover the DMS byte? */
 export declare function holdsDmsLock(locks: readonly ProcLock[], pid: number, inode: string): boolean;
 /**
- * `unavailable` = this platform has no `/proc/locks` (said once, then the
- * canary stops). `unreadable` = Linux, but this look failed (the `-shm` absent,
- * procfs unreadable) — a different fact, and on the hub a worrying one.
- */
-export type ShmLockState = 'held' | 'missing' | 'unavailable' | 'unreadable';
+* `unavailable` = this platform has no `/proc/locks` (said once, then the
+* canary stops). `unreadable` = Linux, but this look failed (the `-shm` absent,
+* procfs unreadable) — a different fact, and on the hub a worrying one.
+*/
+export type ShmLockState = "held" | "missing" | "unavailable" | "unreadable";
 /** The canary's impure edges, injectable so a spec drives them. */
 export interface ShmLockCanaryDeps {
-    readonly platform: NodeJS.Platform;
-    readonly pid: number;
-    /** The `-shm` inode as a decimal string; throws when the file is absent. */
-    readonly shmInode: (shmPath: string) => string;
-    readonly readProcLocks: () => string;
+	readonly platform: NodeJS.Platform;
+	readonly pid: number;
+	/** The `-shm` inode as a decimal string; throws when the file is absent. */
+	readonly shmInode: (shmPath: string) => string;
+	readonly readProcLocks: () => string;
 }
 export interface ShmLockCanaryOptions {
-    readonly dbPath: string;
-    readonly logger: IScopedLogger;
-    readonly intervalMs?: number;
-    readonly deps?: Partial<ShmLockCanaryDeps>;
+	readonly dbPath: string;
+	readonly logger: IScopedLogger;
+	readonly intervalMs?: number;
+	readonly deps?: Partial<ShmLockCanaryDeps>;
 }
 export declare class ShmLockCanary {
-    private readonly shmPath;
-    private readonly logger;
-    private readonly intervalMs;
-    private readonly deps;
-    private timer;
-    private last;
-    private lastError;
-    constructor(options: ShmLockCanaryOptions);
-    start(): void;
-    stop(): void;
-    /** One look. Logs only a change of state. Public for the spec. */
-    check(): ShmLockState;
-    private observe;
-    private report;
+	private readonly shmPath;
+	private readonly logger;
+	private readonly intervalMs;
+	private readonly deps;
+	private timer;
+	private last;
+	private lastError;
+	constructor(options: ShmLockCanaryOptions);
+	start(): void;
+	stop(): void;
+	/** One look. Logs only a change of state. Public for the spec. */
+	check(): ShmLockState;
+	private observe;
+	private report;
 }