docs: document KAV, Lone Pine, Lazy B and Sweet Grass configure context

2026-10-21 16:53:13 +00:00
parent 2b1c36cd91
commit ddba519c3c
10 changed files with 494 additions and 25 deletions
@@ -72,3 +72,17 @@ Updated October 20, 2026 after owner feedback:
 Navigation editor caution: after deleting an entry, reload before another mutation. Its table can display new rows while event handlers still refer to prior row positions. A removed Ventilation entry was corrected during verification; final navigation has Compressor, Well, Washer, Ventilation, Coop, Water Usage and Device Status, with no Temperature/Hot Tub.

 Page roots matter: Copy on the first root does not capture additional roots. Read the DOM-backed root list before replacements; preserve unrelated site-information roots. A pasted replacement appends at the bottom; use the root Up arrow to restore desired order.
+
+## Read-only context inspection, verified October 21, 2026
+
+Use the relevant KAV-GUIDE.md, LONE-PINE-GUIDE.md, LAZY-B-GUIDE.md or SWEET-GRASS-GUIDE.md first; then inspect only the current target page/subtree. The full baseline survey need not be repeated for every task.
+
+Native Copy succeeded in production on all four site families. Exported JSON has id, name, type, data and nested elements. Validate the copied root's identity against the current tree before interpreting the clipboard; an empty/stale clipboard is not evidence that Copy uses an internal-only format. The older SITE-STUDY.md inference has been corrected.
+
+For a large page, enumerate top-level editor roots from the visible DOM and copy each required root separately. Resolve the direct Copy button under that root's header, rather than searching all descendant buttons. This allowed Sweet Grass Motors (1,435 elements) and old Motors (1,246) to be inspected. Do not infer a complete page from the first copied root.
+
+Reload clean Configure Pages between previews, particularly after large charts/motor pages. On timeout, inspect current UI and clipboard identity before retrying. Keep survey batches small and record verified findings immediately; a browser-tool session reset can discard in-memory analysis.
+
+For bindings, record display value, editable flag, updateRegister, writeValue/updateValue, limits flag and units independently. A read-only field can retain a stale write target. Legacy (Dont Use) components can have both register and updateRegister keys; behavior is not established by an internal name alone. Limit values do not enforce anything when limits=false.
+
+This survey used Copy only and discarded editors. No production paste, Save, register command, device action or alarm test was performed. Earlier Mandel development tests remain separate evidence with separate authorization.