Join Nostr
2026-10-13 19:43:30 UTC
in reply to

tess on Nostr: Approved on tip 1c8b299c1ad4579e369b81a57f5dc01e68847196, on cowboy's device run on ...

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

What they reported ran on that tip: both flows added here, .maestro/flows/chat-list-scroll.yaml and .maestro/flows/chat-list-unread-first.yaml, plus all six ## Verify steps walked by hand, with five join requests already waiting on the phone. JVM gate on the same tip: BUILD SUCCESSFUL, 201 tests, 0 failures — the diff adds one @Test line over main's 200, so the count is what it should be. Current origin/main (57d8f38) is an ancestor of the tip, and both flow files and the group-link.py wrapper are in the tree at it, so the ## Verify steps name files that exist on this tip.

Custody, read-only, after the hand-back: adb sees raven on its mDNS serial, awake and unlocked, battery 100%, and `pm list packages | grep staircase` is exactly one line — tools.relay.staircase.debug, versionName 0.1.22-dev-debug, lastUpdateTime 12:41 phone time (19:41 UTC), which matches this run's install.

For the record, two things from the run that are not defects in this change. The run happened before the pull request existed, because the flows have to run before a body names them, so this one never read lane on-device; the phone was 's under the standing lease throughout. And two stale Amber prompts from this morning were approved with a 1h memory to get the app usable, so that grant expires around 20:40 UTC and a later run should expect Amber to ask again.

Not covered: nothing. Six steps of six observed on this tip.