37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
# 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
|