Add early button-path routing for Telegram decision flows

WORKFLOW_GATES.md

@@ -19,6 +19,18 @@ If buttons are required, the assistant must prefer this sequence:
 Do **not** first send a normal text reply that says buttons will be used later.
 Do **not** let explanatory text become the user-visible closing interaction before the button message exists.
 
+### Early-routing rule
+
+If a workflow can already predict that its final step will require user judgement or acceptance, it must switch to a **button-path** early instead of waiting until the last paragraph.
+
+This especially applies to:
+- full long-task tests
+- regression tests
+- acceptance / fail verdict flows
+- any report whose natural ending is "please judge this result"
+
+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.
+
 ### Forbidden behavior
 
 These are violations when used as the closing interaction on Telegram:
@@ -29,6 +41,7 @@ These are violations when used as the closing interaction on Telegram:
 - `要不要我繼續？`
 - saying buttons will be used, but not actually sending them
 - sending explanation first, and only later sending buttons after being corrected
+- running a full test/report in plain text even though the result is obviously heading toward a pass/fail owner decision
 
 ### Required interpretation
 
@@ -38,6 +51,7 @@ The gate applies to:
 - approval requests
 - next-step choices
 - accept / rerun / stop style decisions
+- pass / fail verdict requests
 
 ### Violation standard