Prefer button-driven flows for Telegram test verdicts

skills/long-task-governor/SKILL.md

@@ -178,6 +178,7 @@ When this skill applies:
 5. before claiming progress, check for real evidence
 6. if no evidence and no concrete action, stop the clock
 7. if the run is clearly heading toward a user pass/fail or accept/reject judgement on Telegram, prepare a button-path before the final handoff
+8. if the entire test itself exists to validate Telegram decision closure, run it as a button-driven flow rather than a normal long plain-text report
 
 ---
 
@@ -198,6 +199,7 @@ When operating under long-task governance on Telegram:
 - if a choice is genuinely required, use Telegram inline buttons
 - if buttons are required, send them first via the `message` tool rather than first producing a normal text reply
 - if the workflow can already predict the final handoff is a user judgement, move to a button-path before the final closing paragraph
+- if the test's whole point is to validate button closure, prefer a button-driven flow from the outset
 - if no real choice is needed, execute the most reasonable next step directly
 - if the assistant accidentally emits a plain-text choice menu, or says buttons will be used without actually sending them first, treat that as a workflow violation and convert the lesson into a permanent rule