reply-end-controls/HANDOFF.md

HANDOFF

What this project is

reply-end-controls is a Telegram-only interaction-control feature.

Its purpose is to add reply-end buttons to assistant replies:

• A. 繼續
• B. 就這樣吧，不需要額外處理

The buttons are meant to:

• capture user intent about whether a conversation should continue
• persist that choice
• influence later assistant behavior

What already works

In openclawtest, the Telegram + OpenClaw PoC has already proven:

• buttons can be attached to assistant replies
• button clicks can be received as callback queries
• callback state can be persisted
• button UI can update
• acknowledgement replies can be sent
• stop/continue can influence later behavior

What environment this currently targets

• Telegram only
• OpenClaw runtime in openclawtest

This is not yet a clean cross-agent installable package. It is a successful PoC being pushed toward a cleaner reusable path.

Where to start reading

Read these files first:

1. README.md
2. telegram-v1-design.md
3. telegram-openclaw-poc-plan.md
4. reports/telegram-openclaw-poc-success.md
5. reports/openclaw-patch-inventory.md
6. reports/openclaw-patch-mapping-matrix.md
7. reports/next-phase-implementation-plan.md
8. reports/agent-consumable-minimum.md

Fastest operational entrypoints

For another engineering agent, the most useful command entrypoints are now:

• bash scripts/install-openclawtest-poc.sh
• npm run apply:openclawtest
• npm run verify:openclawtest
• npm run test

Repo structure

• src/core/ - reusable state/policy/callback logic
• src/telegram/ - Telegram-specific helper logic
• src/adapters/ - OpenClaw-facing state bridge code
• src/runtime/ - runtime helper layer for current PoC behavior
• scripts/ - apply / rollback and helper scripts
• tests/ - current unit tests
• reports/ - design notes, PoC success, pluginization reports

What is still fragile

• the live OpenClaw integration still uses runtime patching
• the feature is not yet a clean installable plugin package
• acceptance still includes human verification steps on Telegram UI

If you are the next agent

Your likely next step is not to rediscover the idea.

Your likely next step is to make the current PoC easier to consume by:

• reducing runtime patching
• tightening the apply/verify/rollback path
• making the adapter seam cleaner

Important constraint

Do not mix this project with the governance project.

They are separate workstreams.