Prefer button-driven flows for Telegram test verdicts

WORKFLOW_GATES.md

@@ -31,6 +31,17 @@ This especially applies to:
 
 If the endpoint is predictably a user decision, the assistant should structure the run so that the final user-facing handoff is already prepared as a button interaction.
 
+### Button-driven test rule
+
+If a test or validation flow is known in advance to end in a Telegram pass/fail, accept/reject, or rerun/stop decision, do not start that test in the ordinary text-reply lane.
+
+Instead, the test must be treated as a **button-driven flow** from the beginning:
+1. use normal text only for internal progress while no user decision handoff is needed
+2. once the flow is designed around a final owner verdict, prepare the ending as a `message`-tool button handoff
+3. for short regression tests whose whole purpose is to verify button closure behavior, prefer opening and closing through the button path itself rather than narrating a long plain-text test body first
+
+This rule exists because repeatedly "planning to use buttons at the end" still leaks plain text first.
+
 ### Forbidden behavior
 
 These are violations when used as the closing interaction on Telegram: