docs: rename integration name from matrix_e2ee to matrix_e2e

- Rename runbook: matrix-e2ee-update.md -> matrix-e2e-update.md
- Update all references in AGENTS.md, hass.windy.lan.md,
  home-assistant-matrix.md to use the short name matrix_e2e
- The code domain stays matrix_e2ee (E2EE) in source; all
  doc prose and command references now use matrix_e2e

hosts/hass.windy.lan.md

@@ -111,6 +111,7 @@ getent hosts hass.windy.lan
 
 ## Local patches (custom components)
 
+
 ### Manual custom-component install (this host)
 
 Home Assistant loads custom integrations from
@@ -246,6 +247,47 @@ The `_unrecorded_attributes` mechanism exists in Core 2026.8.1
 (`Entity.__init_subclass__` → `state_info["unrecorded_attributes"]`, consumed
 by recorder `shared_attrs_bytes_from_event`).
 
+
+### `matrix_e2e` live tree (E2E Matrix bot, verified 2026-08-16, W1N-175)
+
+**v0.2.7** (W1N-176: SAS cancel code/reason logging for diagnosis):
+source copy from `/home/windy/project/ha-matrix-e2e` (development clone) deployed
+2026-08-16 via SSH rsync from workstation (upgraded from v0.2.6). Custom **`matrix_e2e`** integration — **Config Flow**
+(UI). See [docs/home-assistant-matrix.md](../docs/home-assistant-matrix.md).
+**Update runbook:** [runbooks/matrix-e2e-update.md](../runbooks/matrix-e2e-update.md).
+
+- Bot `@hass:chans.xyz` reused (E2EE device `rO1R915ncu`). v0.2.0 YAML import
+  migrated existing config into a **Config Entry** (`source: import`), then the
+  YAML block was removed from `configuration.yaml`. All settings now managed via
+  **Settings → Devices & Services → Matrix E2EE → Configure**.
+- Config Entry options: `allowed_rooms` `["!gidvAzpDzwtzfEDrqu:chans.xyz", "!boxfylDSzOvrWkcsyY:chans.xyz"]`,
+  `allowed_users` `["@zhiqiang:chans.xyz"]`, `command_prefix` `"!"`.
+- Storage (persistent volume, in HA backups as of upgrade): `/config/.storage/matrix_e2e_session.json`
+  + `/config/.storage/matrix_e2e_store/`. Config backups:
+  `/homeassistant/.matrix-e2ee-backups/` (`matrix_e2e.bak-20260816`,
+  `matrix_e2e.bak-20260816-v0.2.3`, `matrix_e2e.bak-20260816-v0.2.4`);
+  full HA backup slugs `3d9d36db` (pre-v0.1.4) + `9f223f35` (pre-v0.2.0).
+- v0.2.6 changes: `_log_verification_state()` tracks SAS state transitions
+  with `async_write_ha_state` for diagnosis (W1N-174); `_bridge_verification_request()`
+  handles inbound `m.key.verification.request` → `m.key.verification.ready` since
+  nio lacks a `request` framework (W1N-173).
+- v0.2.5 changes: bridge `m.key.verification.request` → `ready` (nio lacks
+  request framework, W1N-173).
+- v0.2.4 changes: `_patch_nio_sas_timeout()` workaround for nio 0.26.0
+  `_last_event_time` stale-timestamp bug (SAS timed out at 60s regardless of
+  activity); `_repair_dropped_start()` recovers SAS `start` events nio dropped
+  when the peer device was unknown; `_query_device_keys()` generalized beyond
+  own device keys; `VERIFICATION_TIMEOUT_SECONDS` 600→240 (fires before nio's
+  5 min `_max_age`). Earlier undocumented deploys: v0.2.3 (W1N-168 sync loop
+  background task, W1N-169 SAS double-send fix), v0.2.1 (W1N-167 storage I/O
+  `asyncio.to_thread`, W1N-166 own-keys query).
+- Automation `1761188403590`「Matrix 聊天关卫生间灯」unchanged: trigger
+  `matrix_e2e_command` (command `关卫生间灯`), actions `light.turn_off` +
+  `matrix_e2e.send_message` (room `!gidvAzpDzwtzfEDrqu`).
+- **SAS not yet completed:** every device requires explicit `confirm_verification`.
+  Encrypted-room commands stay fail-closed until `@zhiqiang`'s device is verified.
+  Two paths available: SAS manual confirm or fingerprint, see
+  [docs/home-assistant-matrix.md § Device verification](../docs/home-assistant-matrix.md).
 ## Known issues
 
 **Bluetooth hci0 instability — RTL8821CS (verified 2026-08-13, W1N-74):**