kvitt/.claude/memory-seed/ask-owner-to-tap.md

name, description, metadata

name	description	metadata
ask-owner-to-tap	Trigger on-phone actions through the owner's taps, never through adb force-runs, broadcasts or am start	type feedback

Carried over from Ebb: permissions, sign-ins, vendor prompts and anything that changes app state on the owner's real-data install are the owner's taps. Agents may read (pull, logcat) but not drive the app.

Why: forced runs bypassed permission prompts and produced states the owner could not reproduce.

How to apply: write the step with exact labels and the expected result and wait. See relay-human-steps-in-chat.