@mega-yfue/eufy-sdk 0.1.1-beta.0 → 0.1.1

package/README.md

@@ -23,10 +23,6 @@
 
 ---
 
-> [!NOTE]
-> Pre-1.0, so a minor bump may break: old shapes are removed rather than kept beside their
-> replacements. Each release's notes state what changed — see [Releases][releases].
-
 ## What it is
 
 A TypeScript SDK for the Anker eufy cloud that the current eufy app speaks. It logs in (captcha and 2FA
@@ -44,9 +40,9 @@ await dev.light?.()?.setBrightness(60);
 eufy.on("motion", (e) => console.log(e.deviceSn, "saw something"));
 ```
 
-Every accessor and every method is optional because both are **evidence-gated**: a device advertises
-exactly what it reported, so `?.` is not defensive style here — it is the type telling you the feature
-may not be there.
+Accessors and methods are optional because both are **evidence-gated**: a device exposes exactly the
+features it reported, so the optionality states that one may be absent. An **unverified write path
+throws** rather than send a frame it cannot stand behind.
 
 Realtime arrives over **P2P** (cameras and HomeBases), **secure MQTT** (appliances) and **push**
 (events), all surfaced as typed semantic events. Live **video streaming** works, with one shared pull
@@ -59,12 +55,10 @@ code path and an unlisted or future device resolves the same way as a known one.
 ## Install
 
 ```bash
-npm install @mega-yfue/eufy-sdk
+npm install @mega-yfue/eufy-sdk         # latest stable
+npm install @mega-yfue/eufy-sdk@beta    # the prerelease of the version in review
 ```
 
-Releases go to **npmjs**, published from CI with provenance. Prereleases ship on the `beta` channel
-(`npm install @mega-yfue/eufy-sdk@beta`) while a version is still under review.
-
 **Node.js ≥ 24.5.0** is required, not just recommended (see [`.nvmrc`](./.nvmrc)). `ffmpeg` is
 optional — only the live JPEG snapshot and one-shot mp4 record paths use it,
 and a host that ships its own build names it with `new EufyMega({ ffmpegPath })` rather than needing
@@ -72,34 +66,13 @@ one on `PATH`.
 
 ## Documentation
 
-The guides at **<https://mega-yfue.github.io/>** are the source of truth; this README stays a thin
-landing page. They cover installing and logging in, devices and capabilities, events and realtime
-transports, consuming live media, and the generated API reference. Runnable, typechecked samples live
-in [`examples/`](./examples/).
-
-## Design
-
-Four layers, one dependency direction — `core` → `transport` → `model` → `client`:
-
-```
-src/
-  core/         shared floor: crypto, cross-layer contracts, value types, session store
-  transport/    every byte-on-a-wire module: http, mqtt, p2p, push, tuya
-  model/        Device + one self-contained module per capability
-  client/       the facade: login, device registry, event fan-out
-  index.ts      public surface — one `export *` per layer barrel
-```
-
-**Capability ↔ transport decorrelation is a hard, CI-enforced rule:** `model/` never imports
-`transport/` and vice versa. A capability describes what a value MEANS; a transport moves bytes and
-never names a feature. Anything genuinely shared is a contract in `core/`. That rule and the rest of
-the code practice are in [AGENTS.md](./AGENTS.md).
+The guides at **<https://mega-yfue.github.io/>** cover installing and logging in, devices and
+capabilities, events and realtime transports, consuming live media, and the generated API reference.
+Runnable, typechecked samples live in [`examples/`](./examples/).
 
-Three runtime dependencies — `mqtt`, `protobufjs`, `jpeg-js` — and that is deliberate. HTTP is native
-`fetch`, hashing and ciphers are `node:crypto`, 64-bit integers are `BigInt`.
-
-**Unverified write paths throw rather than guess.** Some writes are fire-and-forget, so a guessed
-frame looks exactly like success; the SDK refuses instead of pretending.
+The architecture — four layers with one dependency direction, and the CI-enforced rule that keeps
+capabilities and transports from importing each other — is in [AGENTS.md](./AGENTS.md), with the rest of
+the code practice.
 
 ## Develop
 
@@ -135,5 +108,3 @@ temporary cooldown.
 The vendor now brands the line **Anker eufy**; "eufy" alone is the short form and still the name on
 the wire (`eufy_security`, `eufy_life`, `eufy_mega`) and in every product name (eufyCam, eufy Clean,
 eufy Life). Protocol vocabulary follows the device, not the marketing, so those are not renamed here.
-
-[releases]: https://github.com/mega-yfue/eufy-sdk/releases

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mega-yfue/eufy-sdk",
-  "version": "0.1.1-beta.0",
+  "version": "0.1.1",
   "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",