TL;DR

Modify the rendering logic for each delivery surface to consume AgentPlanEventData and display a native checklist, updating the specified files to achieve this functionality.

Guidance

• Review the AgentPlanEventData structure to understand the available data for rendering the checklist on each surface.
• Update the rendering logic for each surface (e.g., CLI, Control UI, Telegram, Discord, Slack, etc.) to consume AgentPlanEventData and display the checklist with the required status markers (e.g., ✅, ⏳, ❌, ⬚).
• Ensure that the checklist rendering handles different step statuses (cancelled, in_progress, completed, pending) correctly, using strikethrough for cancelled steps and activeForm text when available for in_progress steps.

Example

No specific code example can be provided without more context, but the updates should involve modifying the rendering functions in files like src/cli/render/plan-checklist.ts and extensions/telegram/* to use the AgentPlanEventData and display the checklist accordingly.

Notes

The solution requires updating multiple files across different surfaces, and the estimated size of the changes is approximately 700 lines of code across 15 files. Verification of the changes involves scraping the channel transcript and asserting the presence of the expected checklist.

Recommendation

Apply the workaround by modifying the rendering logic for each delivery surface to consume AgentPlanEventData and display a native checklist, as this is the most direct approach to addressing the user-visible issue.