docs: define remaining pluginization tasks / 定義剩餘插件化 task 與下一個 migration 目標
This commit is contained in:
36
reports/next-inline-migration-target.md
Normal file
36
reports/next-inline-migration-target.md
Normal file
@@ -0,0 +1,36 @@
|
||||
# Next Inline Migration Target
|
||||
|
||||
## Selected target
|
||||
|
||||
The next inline runtime behavior to migrate should be:
|
||||
|
||||
- **callback acknowledgement + resolved button rendering**
|
||||
|
||||
## Why this target first
|
||||
|
||||
- repo-side helper ownership already exists
|
||||
- runtime behavior is compact and visually testable
|
||||
- lower risk than changing stop-policy injection first
|
||||
- success is easy to verify through Telegram UI and callback acknowledgement messages
|
||||
|
||||
## Repo-side owners already available
|
||||
|
||||
- `src/runtime/openclaw-telegram-poc.ts`
|
||||
- `src/runtime/openclaw-telegram-bridge.ts`
|
||||
- `src/runtime/openclaw-telegram-callback-actions.ts`
|
||||
- `src/config.ts`
|
||||
- `config/reply-end-controls.json`
|
||||
|
||||
## Migration goal
|
||||
|
||||
Reduce the amount of hardcoded callback acknowledgement and resolved button logic that remains inline in the patched OpenClaw Telegram runtime.
|
||||
|
||||
## Acceptance for this target
|
||||
|
||||
After migration:
|
||||
|
||||
- continue button still updates UI correctly
|
||||
- stop button still updates UI correctly
|
||||
- continue acknowledgement still appears
|
||||
- stop acknowledgement still appears
|
||||
- no regression in state persistence
|
||||
Reference in New Issue
Block a user