testsAndMisc/docs/superpowers/evidence/workout-flow-reach-home-2026-11-16.json
Krzysztof kuhy Rudnicki 40becf498d
Some checks are pending
dependency freshness / dependencies on newest stable (push) Waiting to run
md-naming / markdown naming convention (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (mypy, mypy) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (pylint, pylint) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (rest, ) (push) Waiting to run
Pre-commit checks / pre-commit (${{ matrix.group }}) (shellcheck, shellcheck) (push) Waiting to run
Python tests / test (push) Waiting to run
repo-contract / repo contract (push) Waiting to run
Shell tests / shell-tests (push) Waiting to run
Shell tests / lib-tests (push) Waiting to run
Shell tests / arch-tests (push) Waiting to run
Back out to Home before the workout flow taps Settings
The slot app reopened into an in-progress workout, which has no gear,
so the Firebase flow failed on its first tap. AndroidUi.back() plus a
bounded _reach_home step fix it; verified live on the Pixel slot on the
current and the reordered settings layout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-16 12:00:16 +01:00

49 lines
2.5 KiB
JSON

{
"intent": "workout_firebase_flow passes on the Pixel slot even when workout_app reopens into an in-progress workout instead of Home.",
"scope": [
"python_pkg/android_ui/driver.py (new AndroidUi.back)",
"python_pkg/android_ui/workout_firebase_flow.py (bounded _reach_home before tapping Settings)",
"No screen-locker source change; the SYNC/OFFLINE BACKUP reorder was a throwaway worktree edit, reverted and rebuilt"
],
"changes": [
"Root cause: the slot app resumed into the workout screen, which has no Settings gear, so tap('Settings') failed after 15 s",
"AndroidUi.back() sends KEYCODE_BACK (4) to the driver's own display",
"run_flow first presses BACK up to MAX_BACKS=3 times until Home's 'Settings' gear is on screen; if it never appears, tap('Settings') still fails naming the query"
],
"verification": [
{
"command": "pytest python_pkg/android_ui/tests --cov=python_pkg.android_ui --cov-branch",
"result": "pass",
"evidence": "143 passed, 100.00% branch coverage; 3 new tests were red first (no back(), no MAX_BACKS)"
},
{
"command": "workout_firebase_flow --serial 23181JEGR08034 --display self --account <linked account> (slot com.kuhy.slot1 v37, current layout, app reopened mid-workout)",
"result": "pass",
"evidence": "workout-firebase-flow: connected, exit 0 (the other account was rejected by the app as the wrong uid, flow timed out exit 1 as designed)"
},
{
"command": "same flow on slot v38 with SYNC and OFFLINE BACKUP swapped in settings_screen.dart",
"result": "pass",
"evidence": "dump shows OFFLINE BACKUP at y=1452 above SYNC at y=2178; flow: already connected, exit 0"
},
{
"command": "workout_firebase_flow --serial 23181JEGR08034 --display self --negative",
"result": "pass",
"evidence": "exit 1, stderr: waited 3.0s for 'No Such Button': no element matches 'No Such Button'"
},
{
"command": "git checkout settings_screen.dart, rebuild slot v39, rerun flow",
"result": "pass",
"evidence": "already connected, exit 0; screen-locker worktree removed, slot released, com.kuhy.workout_app untouched"
}
],
"risks": [
"BACK on an in-progress workout leaves that screen; workout_screen.dart allows the pop outside lock mode and the state persists (the slot reopened into it)",
"An unexpected route deeper than 3 levels still fails, naming 'Settings'"
],
"rollback": [
"git revert this commit",
"Rerun pytest python_pkg/android_ui/tests"
]
}