1.4 KiB
1.4 KiB
Cancel from the actual run detail
The loaded detail's native action row reuses CancelRunAction alongside Rename. No new confirmation or protocol implementation: Keep sends nothing, only Confirm sends the exact run_id, and no canceled state appears before server acceptance. The accepted run detail now folds lifecycle fields into the held list row as well as the detail (the previous title-only update was insufficient for Cancel). Detail-only payloads are not duplicated into the summary list; pending old detail refreshes are invalidated after acceptance. Foreign run replies cannot replace the open detail. Native controls still own sizing and appearance.
Actual checks
- New normal-screen Material/Cupertino tests failed before registration, then passed: Keep/no request, Confirm exact id, delayed accepted canceled state, action disappears, Back shows canceled list row.
- 601 integrated tests pass; analyzer and normal web build pass.
- Normal-app real Chrome fixture probe passes23 captures, including Cupertino confirm/Keep, Material confirm and accepted detail/list. The fixture records exactly one cancel_run for its own synthetic run4. No real run was canceled.
- Fresh Cupertino-confirm and Material-accepted PNGs inspected in approved temp/cancel-wired-browser. Existing history/reconnect/Settings checks pass too.
- Mobile and authenticated production mutations remain unverified.