docs: address radar specification review #485

Issue: #485
User-Visible: no

docs/SCOPE.md

@@ -95,7 +95,23 @@ the file — and if a future version wants to reclaim that space, it asks.
 - Automations, scenes, scripts, notifications → HA core.
 - Device/entity administration (rename, reassign area, disable) → HA registry
   UIs. We *read* the registry, we never manage it.
+  A narrow owner-approved exception for
+  [#485](https://github.com/Matysh/houseplan-card/issues/485) allows explicit
+  HA-admin-confirmed creation/removal of House Plan's own derived room presence
+  and estimated-count entities only; it does not create automations or rename,
+  reassign or disable source entities. Ordinary radar setup has no implicit
+  provisioning side effect.
 - History, graphs, statistics → recorder/history cards. We show now, not then.
+  A narrow exception approved for
+  [#485](https://github.com/Matysh/houseplan-card/issues/485), with defaults
+  confirmed on 2026-09-08, permits local spatial radar setup/occupancy analysis:
+  explicitly started observation runs of at most 24 hours with raw points
+  expiring after 24 hours, and a separately enabled day/week heatmap containing
+  coarse aggregate cells for at most seven days. Each aggregate collection run
+  also lasts at most 24 hours. History/collection controls require House Plan
+  editing permission; no automatic start, renewal or restart, continuous
+  multi-day collection, cloud upload or personal identity tracking. Ordinary
+  View remains current-only. This does not authorize a general history dashboard.
 - Camera streams, media controls → their own cards; our more-info opens HA's.
 - Energy monitoring/analytics → HA Energy.
 - Photorealistic rendering, a free 3D camera, a separate 3D model and 3D

docs/specs/485-radar-presence-stage1.md

@@ -225,6 +225,26 @@ conversion, non-origin mount and 1/5 cm spaces representing the same room.
 
 ### 5.2 Wizard, no premature persistence
 
+**Touch editor: best effort / intentionally degraded.** The calibration wizard,
+including mount/reference placement, uses the desktop Device editor as its
+reference environment. This is deliberate, not a missing mobile implementation
+promise: mark the reference on the computer first, start the 10-second countdown,
+walk to the marked physical position without carrying the computer, remain still
+during capture, then return to inspect the result. The existing countdown makes
+that single-person desktop workflow possible; a phone/second controller is not
+required. If the user cannot complete the timed exercise comfortably, Retry or
+manual direction/mirror setup remains available rather than accepting a bad fit.
+
+A phone/tablet may run the same wizard best-effort, but precise point placement
+and full mobile parity are not promised. Show the desktop recommendation before
+setup and describe the limitation in both guides and release notes. Cancel/Back,
+lost permission, page hide, pinch, a second pointer or `pointercancel` must never
+commit a reference, complete a capture or save configuration accidentally. Page
+hide interrupts capture and clears transient samples; returning offers Retry,
+not a fabricated successful measurement. Essential safe exit/confirmation
+controls remain reachable. View/kiosk retain full touch support; S1-10/S1-18
+and touch safety smoke cover this floor, not unsupported precision parity.
+
 **Step 1: Installation.** Select the existing room; place the real sensor mount
 on the plan and drag its direction arrow. If decorative marker placement is
 available, offer it as a starting suggestion only, with text distinguishing it
@@ -509,6 +529,11 @@ field registry, reviewed full-scene screenshots light/dark/2D/isometry/mobile,
 permission and mutation evidence. Current docs-only work runs no implementation
 gates and claims no shipped changes.
 
+`docs/SCOPE.md` already records the owner-approved narrow #485 exception as part
+of this spec revision. Verify the implementation/release against that boundary;
+do not silently broaden it. The guides and release notes explicitly carry the
+desktop-first/best-effort-touch calibration limitation from §5.2.
+
 Rollback: hide live to remove visuals; disable radar to detach sources; restore
 saved config if needed. No Stage1 external write or raw store to reverse. Older
 frontend editing is discouraged; unsupported fields remain inert. Risks include

docs/specs/485-radar-presence-stage2.md

@@ -668,6 +668,9 @@ Implementation release must include both `docs/CHANGELOG.md` and
 recommendation, permissions, hardware warnings, retention/backups), English
 user-facing documentation, `docs/ARCHITECTURE.md`, `docs/CONFIG-COMPATIBILITY.md`,
 field registry and `docs/DEVELOPMENT.md` for HA harness/device proof caveats.
+`docs/SCOPE.md` records the narrow #485 exception in this specification revision;
+verify at implementation/release that local recording and its limits stay within
+that approved boundary, without silently broadening it.
 Golden/screenshots: selected local/device zones, rotated LD2450 rectangle,
 FP2 mapping, cloud/score, partial/unverified outcome, ordinary unchanged
 View/kiosk in light/dark en/ru. Capture/accept only through the repository's

docs/specs/485-radar-presence-stage3.md

@@ -764,7 +764,10 @@ Release artifacts for actual implementation: `docs/CHANGELOG.md` and
 `docs/CHANGELOG.ru.md`; `docs/USER-GUIDE.md` and `docs/USER-GUIDE.ru.md`;
 update `docs/ARCHITECTURE.md`,
 `docs/CONFIG-COMPATIBILITY.md`, field registry and privacy/support projection
-documentation. Capture representative actual coverage, ambiguous overlap,
+documentation. `docs/SCOPE.md` records the narrow #485 exception in this spec
+revision; verify that aggregates and owned HA outputs stay within that approved
+boundary at implementation/release, without silently broadening it.
+Capture representative actual coverage, ambiguous overlap,
 unknown native output and incomplete heatmap, light/dark
 and narrow/touch View. Use approved complete Linux CI documentation/golden
 artifacts and reviewed acceptance, not the conceptual UX sketch as a screenshot.