traces

docs/pt2-copy-state-machine.md

@@ -10,6 +10,7 @@ Frame:
 
 ```text
 05 00 6D 00 00 32
+00 00 6D 00 00 37  ; family-00 set/queue form to test
 ```
 
 ROM path:
@@ -40,6 +41,7 @@ Frame:
 
 ```text
 05 00 6C 00 00 33
+00 00 6C 00 00 36  ; family-00 set/queue form observed during active report drain
 ```
 
 ROM path:
@@ -110,10 +112,27 @@ Observed on the real panel:
 006D repeated without 006C      -> COPY IN PROGRESS -> CONNECT NOT ACT
 ```
 
+Family-00 comparison run on 2026-05-27:
+
+```text
+00 00 6D 00 00 37 -> 00 00 6C 00 00 36
+  -> immediate 04 00 6D / 04 00 6C table readbacks
+  -> no command-5-like 01 00 02 / 02 00 04 response rhythm
+
+05 00 6D 00 00 32 -> 05 00 6C 00 00 33
+  -> 01 00 02 responses after 006D
+  -> 02 00 04 responses after 006C
+```
+
+This suggests the family-00 forms update/read back selector values but should not
+be treated as equivalent to the command-5 COPY side-effect selectors unless an
+LCD observation proves otherwise.
+
 Current interpretation:
 
 - `0x006D` is a copy-start/progress-window refresh selector.
 - `0x006C` is a completion/exit selector that only behaves cleanly while the copy window is live.
+- The observed `00 00 6C 00 00 36` frame is copy-related, but should not be read as "COPY COMPLETED" by itself.
 - The copy window is transient and timer-controlled.
 - The panel does not treat `0x006C` as a stateless "show completed" command.