From 40de48092fd1558d65215dd5cb70d9955a41d302 Mon Sep 17 00:00:00 2001
From: Noah <noah@it.bluefla.re>
Date: Tue, 8 Sep 2026 17:18:43 -0600
Subject: [PATCH] qemu: regression script for home leaving fullscreen

tests/scripts/home-leaves-fullscreen.txt taps the dashboard into
fullscreen, proves the rail gear's pixel now resolves to the 720x720 canvas,
sends `home` and proves the gear's own box is back; then the same from
another page. The `home` verb used to reach Dashboard/Dashboard without
leaving fullscreen, which is the state a hardware wake tap leaves behind
(flare-edge #176). Runs green on the rig: 20 ok, 0 failed.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N3G6m9Aw5RyVY4ZowtKzEj
---
 qemu/README.md                                |  2 +-
 qemu/tests/scripts/home-leaves-fullscreen.txt | 35 +++++++++++++++++++
 2 files changed, 36 insertions(+), 1 deletion(-)
 create mode 100644 qemu/tests/scripts/home-leaves-fullscreen.txt

diff --git a/qemu/README.md b/qemu/README.md
index ea253c4..a3cd524 100644
--- a/qemu/README.md
+++ b/qemu/README.md
@@ -92,7 +92,7 @@ All take the virt-fragment `<zImage>`; `FLARE_EDGE=<checkout>` where noted.
 | `portal-scenario.sh` | `FLARE_EDGE` | real flared against the desk mock portal: authenticated check-in, desired-state pull, signed tier-1 `.wfw` download; verify/stage/APPLYING as a dry run (no `WARDEN_FW_ALLOW_APPLY`) |
 | `ota-apply.sh` | `FLARE_EDGE` | the FULL apply: the `.wfw`'s bootable rootfs payload is written to rootfs_b (`run.sh --allow-apply` gates it per boot), the AvbABData in `misc` flips, and slot `_b` boots the applied version |
 | `ui-shot.sh` | - | display+touch, headless: QMP-screendumps the 720x720 UI, taps the Metrics tab via `input-send-event`, asserts the frame changed (`qmp.py` is the QMP client) |
-| `ui-drive.sh <script>` | - | the same rig for a SEQUENCE: boots once, runs a `qmp.py drive` script of taps/swipes/screenshots in panel pixels, and FAILS if warden-ui died on the way (stage-2 init announces the exit on the console). `tests/scripts/nav-stress.txt` is the navigation regression: it reproduces the s_row_left overflow that segfaulted the UI on returning to Settings > Apps |
+| `ui-drive.sh <script>` | - | the same rig for a SEQUENCE: boots once, runs a `qmp.py drive` script of taps/swipes/screenshots in panel pixels, and FAILS if warden-ui died on the way (stage-2 init announces the exit on the console). `tests/scripts/nav-stress.txt` is the navigation regression: it reproduces the s_row_left overflow that segfaulted the UI on returning to Settings > Apps; `tests/scripts/home-leaves-fullscreen.txt` proves the `home` verb clears dashboard fullscreen, the state a hardware wake tap leaves behind (flare-edge #176) |
 | `real-image-boot.sh` | matched `rootfs.img` + `oem.img` | an ACTUAL flare-edge build (placed by `mkimage.sh --rootfs-image/--oem-image`) boots its own init chain to getty; binaries predating known fixes reproduce their bugs faithfully, a time machine for field issues |
 | watchdog (`run.sh --watchdog`) | - | arm `/dev/watchdog`, don't pet: the VM resets ~30 s later (verified) |
 
diff --git a/qemu/tests/scripts/home-leaves-fullscreen.txt b/qemu/tests/scripts/home-leaves-fullscreen.txt
new file mode 100644
index 0000000..dff61d3
--- /dev/null
+++ b/qemu/tests/scripts/home-leaves-fullscreen.txt
@@ -0,0 +1,35 @@
+# `home` must leave dashboard fullscreen, not only reach Dashboard/Dashboard.
+#
+# On the dashboard a tap anywhere toggles fullscreen (screen_overview.c's
+# tap-catcher). On a panel a flow's `wake` is a real finger on the glass, so
+# a flow that woke the panel on the dashboard left the next flow a 720x720
+# canvas over the chrome: the rail gear at (47,676) resolved to
+# `widget box=0,0,720x720` instead of `obj box=12,640,72x72`, and every
+# hit against chrome failed from there (bench sample 2026-09-08, flare-edge
+# #176). The runner's `home` preamble now clears fullscreen last, after the
+# dashboard is the page again, so this is the regression guard for it.
+#
+# `wake` first, as every compiled flow does: by the time the control bridge is
+# up the rig may already sit dimmed, and sleep.c swallows the touch that wakes
+# a dimmed panel (flare-edge #148) -- the tap below must reach the tap-catcher.
+wake
+sleep 1
+assert_page Dashboard/Dashboard
+assert_hit 47 676 obj box=12,640,72x72
+tap 360 360
+sleep 1
+assert_hit 47 676 widget box=0,0,720x720
+home
+sleep 1
+assert_page Dashboard/Dashboard
+assert_hit 47 676 obj box=12,640,72x72
+# The same from another page: fullscreen on, leave, come home.
+tap 360 360
+sleep 1
+assert_hit 47 676 widget box=0,0,720x720
+nav Mining Devices/ASICs
+sleep 1
+home
+sleep 1
+assert_page Dashboard/Dashboard
+assert_hit 47 676 obj box=12,640,72x72