From 25e067b2b9da566be623eef1a7761e53a164e1c5 Mon Sep 17 00:00:00 2001
From: Eve <eve@local>
Date: Wed, 22 Apr 2026 11:57:51 +0800
Subject: [PATCH] Harden long-task governor Telegram interaction guard

---
 memory/2026-04-22.md               |  2 ++
 skills/long-task-governor/SKILL.md | 10 ++++++++++
 2 files changed, 12 insertions(+)

diff --git a/memory/2026-04-22.md b/memory/2026-04-22.md
index 0e91987..99b92d3 100644
--- a/memory/2026-04-22.md
+++ b/memory/2026-04-22.md
@@ -47,3 +47,5 @@
   - `_meta.json`
 - skill 目標：把 `general_chat vs long_task` 判準、狀態機、checkpoint 規格、no-fake-progress、stop-clock gate 收斂到外掛式 workflow layer。
 - 已同步更新 `WORKFLOW.md`，要求：只要不是 ordinary single-turn general chat，就必須套用 `long-task-governor`。
+- live test 期間實際抓到一個缺口：在 Telegram 上做 long-task checkpoint / next-step 收尾時，我仍可能退回純文字 `1 / 2 / 3` 選單。
+- 因此已再補一條 skill 規則：`Telegram interaction guard`，禁止 governed long-task flow 在 Telegram 上用純文字選單收尾；若需要選擇，必須改用 inline buttons，否則直接執行最合理下一步。
diff --git a/skills/long-task-governor/SKILL.md b/skills/long-task-governor/SKILL.md
index c8fa3a8..c33e48c 100644
--- a/skills/long-task-governor/SKILL.md
+++ b/skills/long-task-governor/SKILL.md
@@ -190,6 +190,16 @@ This skill should be paired with:
 
 But this skill itself is the governance layer and should remain independently maintainable.
 
+### Telegram interaction guard
+
+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 no real choice is needed, execute the most reasonable next step directly
+- if the assistant accidentally emits a plain-text choice menu, treat that as a workflow violation and convert the lesson into a permanent rule
+
+This prevents governed long-task flows from degrading back into ambiguous text-only decision gates.
+
 ---
 
 ## 9. Success criteria