@mega-yfue/eufy-sdk 0.4.0-beta.19 → 0.4.0-beta.20

package/dist/model/capabilities/manifest.d.ts

@@ -61,8 +61,14 @@ export interface ActionDescriptor extends ActionSpec {
 /** What one capability exposes on a device — the join of its bound object and its own declaration. */
 export interface CapabilityDescriptor {
     capability: Capability;
-    /** The fluent accessor this capability is reached under: `dev[accessor]()`. */
-    accessor: string;
+    /**
+     * The fluent accessor this capability is reached under: `dev[accessor]()`.
+     *
+     * Absent for a capability with nothing to bind — one whose whole surface is inbound events, so it
+     * declares no members and no `actions()` and therefore has no object to reach. Such a capability is
+     * described for its {@link events} alone; every other field is empty.
+     */
+    accessor?: string;
     /** The reads INSTALLED on this device, never the theoretical set. */
     reads: readonly ReadDescriptor[];
     /** The installed actions that carry a description. */
@@ -102,6 +108,16 @@ export interface DeviceManifest {
  * Parameterised over the module list; the barrel binds it to the real one. A capability the device did
  * not bind — because it does not have it, or because nothing is bound yet — contributes no descriptor
  * at all.
+ *
+ * With ONE exception, and it is not a bound object: a capability whose whole surface is inbound events
+ * declares no members and no `actions()`, so `buildActions` builds nothing for it and there is no
+ * object here to walk. Its events are still device truth, and the resolved set in {@link
+ * AvailabilityContext.capabilities} is what says this device has it — so it is described from its own
+ * declaration, with no {@link CapabilityDescriptor.accessor} and every other field empty, and only on
+ * a device with at least one bound object.
+ *
+ * Claims resolve against an empty read set there, which is the truthful evidence — a module that binds
+ * nothing installs no getter, so a `reads` claim cannot hold. A topology claim still applies.
  * @internal
  */
 export declare function describeBound(modules: readonly CapabilityModule[], bound: Readonly<Record<string, unknown>>, ctx?: AvailabilityContext): CapabilityDescriptor[];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mega-yfue/eufy-sdk",
-  "version": "0.4.0-beta.19",
+  "version": "0.4.0-beta.20",
   "description": "One typed TypeScript client for the Anker eufy v6 cloud — capability-driven devices, realtime events over P2P/MQTT/push, and live media",
   "license": "Apache-2.0",
   "author": "mega-yfue",