run 33

docs/pt2-protocol-summary.md

@@ -356,6 +356,33 @@ Current caution:
 - The protocol surface now looks parameterized rather than flat:
   command bytes pick broad regions, and `state/value` bytes appear to choose
   page, subtype, or class within those regions.
+- Sustained "camera-info-like" fan-out streams have now also been tested:
+  repeated discovery carousels, selector carousels, direct host-shaped family
+  feeds, hybrid select-then-feed streams, and heartbeat-family base-status
+  feeds.
+- None of those sustained streams visibly activated the panel or cleared the
+  broader inactive state.
+- Two of those host-fed fan-out branches still produced new structured
+  responses:
+  host `00 00 7A 50 26 56` produced `07 80 2F 95 C9 AE`, and host
+  `00 00 40 40 30 6A` produced `07 80 D0 50 26 7B`.
+- Those are best treated as meaningful one-shot host-stimulated branches, not
+  yet as proof of a stable live camera-info or session stream.
+- Follow-up HE30 tests strengthened that further:
+  these do not look like isolated one-off branches, but like two small
+  parameterized family surfaces:
+  - host `7A ...` -> RCP `2F ...`
+  - host `40/50 ...` -> RCP `50 ...` / `D4 ...`
+- Examples observed so far include:
+  - `7A 50 26` -> `2F 95 C9`
+  - `7A 58 26` -> `2F 65 F2`
+  - `7A 50 3A` -> `2F 95 52`
+  - `40 40 30` -> `50 78 26` or `50 50 26`
+  - `50 40 30` -> `D4 50 26`
+  - `40 60 30` -> `50 58 26`
+- Exact and host-shaped answers to these second-stage families still did not
+  produce a stable next turn, and cold-start direct tests fell back toward
+  `40`/`C0` transient families instead.
 
 ## What We Do Not Know