@camstack/system 1.2.304 → 1.2.306

package/dist/builtins/doorbell/doorbell-extension-slot.d.ts

@@ -0,0 +1,66 @@
+import { ExtensionSlotActivation, IDeviceExtensionProvider, IScopedLogger } from '@camstack/types';
+import { DoorbellBindingState, DurableBindingVerdict, RingVerdict } from './binding-mirror.js';
+import { DoorbellSource } from './doorbell-settings.js';
+/** The routing prefix of this owner's `slotRef`s. */
+export declare const VIRTUAL_DOORBELL_EXTENSION_SOURCE = "virtual-doorbell";
+/** The store the slot reads and writes, named (D62). */
+export declare const DOORBELL_SOURCES_AUTHORITY = "virtual-doorbell:doorbellSources";
+/** The authority that decides whether the wrapper serves a camera at all. */
+export declare const WRAPPER_ACTIVATION_AUTHORITY = "device-manager:setWrapperActive";
+/** The compact device row this slot needs from the device manager. */
+export interface DoorbellSlotDevice {
+    readonly id: number;
+    readonly name: string;
+    readonly type: string;
+    readonly location: string | null;
+    readonly parentDeviceId: number | null;
+}
+/** What the slot needs from the addon — its store, its mirror, and the fleet's reads. */
+export interface DoorbellSlotDeps {
+    readonly ownAddonId: string;
+    readonly logger: IScopedLogger;
+    readonly readSources: (deviceId: number) => Promise<readonly DoorbellSource[]>;
+    /** The addon's own settings-save path (normalise, store, invalidate). */
+    readonly persistSources: (deviceId: number, deviceIds: readonly number[]) => Promise<void>;
+    /** The host's own row — ONE read, for its type. */
+    readonly getDevice: (deviceId: number) => Promise<DoorbellSlotDevice | null>;
+    /** Several devices in ONE read. Ids no device has are simply absent. */
+    readonly listDevices: (deviceIds: readonly number[]) => Promise<readonly DoorbellSlotDevice[]>;
+    /** The D49 mirror's verdict for this camera, or undefined when it has none. */
+    readonly readBindingMirror: (deviceId: number) => DoorbellBindingState | undefined;
+    /**
+     * The DURABLE authority, read-only — the same read the ring gate makes
+     * before it drops a press. Never throws: a store that cannot answer is
+     * `unreadable`, which carries no information.
+     */
+    readonly readDurableBinding: (deviceId: number) => Promise<DurableBindingVerdict>;
+    readonly sourceCapableDeviceIds: () => Promise<readonly number[]>;
+    readonly listFleet: () => Promise<readonly DoorbellSlotDevice[]>;
+}
+/** How the card SAYS a verdict. The verdict itself is `ringVerdict`'s, never the card's. */
+export declare function activationFromVerdict(verdict: RingVerdict): ExtensionSlotActivation;
+/**
+ * The card's activation — READ-ONLY (D648 fix round 3).
+ *
+ * The verdict is `ringVerdict`, the function the ring gate decides with, fed
+ * the addon's mirror as it stands. The card never refreshes the mirror and
+ * never writes it: the mirror gates the ring, and a view that could move it
+ * would let a page refetch during a store blip silence a doorbell. The only
+ * read the card may make is the durable authority, and only where the ring
+ * gate would make it too (`needsDurableRead`: an `unbound` mirror). A camera
+ * the mirror has never seen costs nothing — the ring path errs open there and
+ * so does the card.
+ */
+/** The card's durable read for one camera, shared by every view asking at once. */
+type DurableReader = (deviceId: number) => Promise<DurableBindingVerdict>;
+/**
+ * Concurrent card views of the same `unbound` camera share ONE durable read,
+ * per camera, for as long as it is in flight — a page with several viewers
+ * (or a refetch storm) must not multiply the store round trip. Only the
+ * CARD's reads are shared: the ring gate calls the addon's
+ * `readDurableAuthority` on its own path and never waits behind a card.
+ */
+export declare function shareDurableReads(read: DurableReader): DurableReader;
+/** Build the `device-extension` provider the virtual doorbell registers. */
+export declare function createDoorbellExtensionProvider(deps: DoorbellSlotDeps): IDeviceExtensionProvider;
+export {};

package/dist/builtins/doorbell/virtual-doorbell.addon.d.ts

@@ -5,7 +5,7 @@ interface VirtualDoorbellAddonConfig {
     /**
      * Reload the camera→source assignment map (and the binding mirror) at
      * most this often — lazily, on trigger traffic. Covers devices/settings
-     * appearing after boot without a settings save, and is the cadence on
+     * appearing after boot without a save, and is the cadence on
      * which an unbind gets corroborated.
      */
     readonly assignmentsTtlMs: number;
@@ -19,9 +19,9 @@ interface VirtualDoorbellAddonConfig {
  *
  *   1. The operator binds the wrapper to a camera in the bindings UI
  *      (`defaultActive: false` — never auto-bound).
- *   2. In the camera's GENERAL settings (next to "Linked devices") the
- *      operator picks one or more SOURCE devices from a searchable list —
- *      that is the ONLY choice. The reaction is derived automatically per
+ *   2. In the camera's Extensions section (the `doorbell-source` slot,
+ *      D648/D655) the operator picks one or more SOURCE devices — that is
+ *      the ONLY choice. The reaction is derived automatically per
  *      device type: a binary sensor rings when it goes active, a switch
  *      rings when it turns on (see `trigger-engine.ts`). The persisted
  *      shape (`doorbellSources: [{deviceId}]`) stays extensible for a
@@ -53,6 +53,11 @@ export declare class VirtualDoorbellAddon extends BaseAddon<VirtualDoorbellAddon
     private readonly bindingMirror;
     constructor();
     protected onInitialize(): Promise<ProviderRegistration[]>;
+    /**
+     * The `device-extension` provider: the only editor of a camera's trigger
+     * devices since D655 (see `doorbell-extension-slot.ts`).
+     */
+    private buildExtensionProvider;
     private handleStateChanged;
     /**
      * Say out loud every case where a rise did NOT become a ring. Silence
@@ -136,18 +141,11 @@ export declare class VirtualDoorbellAddon extends BaseAddon<VirtualDoorbellAddon
      * Returns `true` when the ring must proceed.
      */
     private ringsDespiteUnboundMirror;
-    /**
-     * Record a binding we observed FIRST-HAND. Both callers are cap methods
-     * the router only reaches by resolving this wrapper for this device —
-     * which it can only do through the binding — so a call is direct evidence
-     * and outranks anything the store says.
-     */
-    private confirmBindingFromCapCall;
     /**
      * Lazily (re)build the camera→source assignment set from every
      * camera's device store. TTL-bounded so devices/settings appearing
-     * after boot are picked up without a settings save; invalidated
-     * eagerly by `applyDeviceSettingsPatch`.
+     * after boot are picked up without a save; invalidated eagerly by
+     * `persistDoorbellSources`.
      */
     private ensureAssignments;
     private loadAssignments;
@@ -164,29 +162,12 @@ export declare class VirtualDoorbellAddon extends BaseAddon<VirtualDoorbellAddon
      */
     private readDeviceSources;
     /**
-     * Single-trip, non-throwing device lookup (mirrors snapshot's
-     * `lookupDeviceMeta`). Null on any failure — callers fall back to
-     * rendering the section (better a spurious section than a thrown
-     * aggregator entry).
-     */
-    private lookupDevice;
-    /**
-     * Settings section for the device-detail page — contributed into the
-     * GENERAL settings surface (no `tab`, so it lands in the same tab as
-     * "Linked devices", ordered just after it). Camera-only: the doorbell
-     * cap also applies to Button accessories (native providers) where a
-     * virtual-source picker is meaningless.
-     *
-     * A SINGLE `device-multiselect` field carries only a declarative
-     * `deviceFilter` — the admin-ui renders the SHARED searchable device
-     * picker (same idiom as "Linked devices") whose options come from
-     * `deviceManager.listAll` filtered CLIENT-SIDE. The addon NO LONGER
-     * computes the option list server-side: the old path enumerated
-     * `deviceManager.getAllBindings`, which returns an empty set on the live
-     * cluster and left the picker blank. The reaction is still derived
-     * automatically per device type — no trigger/eventType controls.
+     * THE write path for a camera's trigger sources — the `doorbell-source`
+     * extension slot lands here (D648; its only caller since D655): normalise
+     * to `doorbellSources: [{deviceId}]`, strip the legacy keys, and invalidate
+     * the assignment cache so the next rise (and the binding mirror's next
+     * refresh, off the ring path) sees the new wiring.
      */
-    private buildDeviceSettingsContribution;
-    private saveDeviceSettingsPatch;
+    private persistDoorbellSources;
 }
 export default VirtualDoorbellAddon;