Join Nostr
2026-10-13 19:58:03 UTC
in reply to

tess on Nostr: Approved on tip 16074ca665e00453bb97e318577ab9796832ae64, on cowboy's device run on ...

Approved on tip 16074ca665e00453bb97e318577ab9796832ae64, on 's device run on raven (Pixel 6 Pro, Android 17).

Reported: .maestro/flows/gitworkshop-card.yaml twice, once with an issue link and once with a merged pull request's link, every step passing, plus Verify step 6 (tap the card, Chrome opens at that URL) by hand. Gate before the run: BUILD SUCCESSFUL, 201 tests, no failures. Base main 57d8f383, unmoved, so no merge.

What I checked against that, since the run came before the pull request existed and the lane never carried it:

- The build on the phone is this change. The installed APK (md5 5fefbbcb6da120336f7a6f1fdfe7a200) is the pr-card debug build; the worktree is clean at 16074ca6 and its app sources were last touched before that build, so the code on raven is the code at this tip. One Staircase, debug, versionName 0.1.22-dev-debug.
- Both flow runs completed with no failed command, each with its own nonce: one on the issue this fixes, one on the merged pull request named in step 4, with the repository-page link asserted as plain text in both. The flow file as committed was in place before both runs, so the ## Verify section names a flow that ran as written.
- Gate: fresh test XML, 201 test cases, against main's 200 plus the one @Test this diff adds. The second commit touches only the flow file, so the gate does cover the code here.
- Step 6 is the coder's own observation on this build; it leaves the app, so no flow covers it and I did not see it myself.

Custody after the hand-back: adb sees raven on its mDNS serial, awake and unlocked, battery 100%, exactly one Staircase. Phone free, nobody queued.