openclaw/reporting-governance-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enforce button-first ordering for Telegram decision closures

Browse Source
This commit is contained in:
Eve
2026-04-22 12:13:35 +08:00
parent 26948948b2
commit a85403aa77
4 changed files with 20 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
skills/long-task-governor/SKILL.md
View File

@@ -195,8 +195,9 @@ But this skill itself is the governance layer and should remain independently ma
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 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
- 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
This prevents governed long-task flows from degrading back into ambiguous text-only decision gates.