46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
# Remaining Pluginization Task List
|
|
|
|
## Goal
|
|
|
|
Track the remaining major work needed to move `reply-end-controls` from a successful Telegram/OpenClaw PoC toward a cleaner agent-consumable integration.
|
|
|
|
## Remaining major tasks
|
|
|
|
### Task A - Reduce live runtime inline patching
|
|
|
|
Current runtime patching still directly owns some logic that should eventually live behind repo-side helpers/bridges.
|
|
|
|
Subtasks:
|
|
|
|
1. identify remaining inline logic not yet cleanly represented in repo modules
|
|
2. pick one small inline runtime behavior to migrate next
|
|
3. verify that migration does not break Telegram acceptance
|
|
|
|
### Task B - Tighten apply / verify / rollback into a clearer consumer workflow
|
|
|
|
Current scripts exist, but they still feel like engineering tools rather than a polished integration workflow.
|
|
|
|
Subtasks:
|
|
|
|
1. make script expectations explicit
|
|
2. ensure output is concise and user-facing enough for another agent to follow
|
|
3. document an end-to-end happy path
|
|
|
|
### Task C - Final maturity judgment
|
|
|
|
The project still needs a final written judgment on whether it is:
|
|
|
|
- only suitable for further development handoff
|
|
- suitable for direct reuse by another agent in controlled conditions
|
|
- or ready for broader adoption
|
|
|
|
Subtasks:
|
|
|
|
1. define maturity criteria
|
|
2. compare current state against those criteria
|
|
3. write final readiness report
|
|
|
|
## Immediate next move
|
|
|
|
Continue Task A first.
|