Add early button-path routing for Telegram decision flows

skills/long-task-governor/SKILL.md

@@ -177,6 +177,7 @@ When this skill applies:
 4. if reporting progress, use the 5-part checkpoint structure
 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
 
 ---
 
@@ -196,6 +197,7 @@ When operating under long-task governance on Telegram:
 - do not end checkpoints, test progress, or next-step decisions with plain-text menus like `1 / 2 / 3` or `A / B / C`
 - 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 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