fix: include pre-answer callback debug in patch flow / 將 pre-answer callback debug 納入 patch 流程
This commit is contained in:
@@ -45,6 +45,8 @@ Observed patch points:
|
||||
|
||||
- raw callback debug file path:
|
||||
- `reply-end-debug.log`
|
||||
- pre-answer callback debug write:
|
||||
- `[pre-answer] ... data=...`
|
||||
- persisted state file path:
|
||||
- `reply-end-controls.json`
|
||||
- callback click handling:
|
||||
|
||||
@@ -74,6 +74,8 @@ The project now has:
|
||||
|
||||
The apply/rollback flow has been validated against a pristine extracted `openclaw@2026.5.7` package.
|
||||
|
||||
The live acceptance loop has also shown why observability matters: a pre-answer callback debug write was needed to separate Telegram callback ingress from later acknowledgement failures. That instrumentation is now part of the current PoC patch flow.
|
||||
|
||||
## What is still not pluginized enough
|
||||
|
||||
### 1. Live OpenClaw runtime still uses inline patch behavior
|
||||
|
||||
Reference in New Issue
Block a user