Skip to content

fix(telegram): preserve plan progress history#1105

Open
artemgetmann wants to merge 1 commit into
codex/telegram-work-log-v11-20260706from
codex/telegram-progress-format-20260707
Open

fix(telegram): preserve plan progress history#1105
artemgetmann wants to merge 1 commit into
codex/telegram-work-log-v11-20260706from
codex/telegram-progress-format-20260707

Conversation

@artemgetmann

@artemgetmann artemgetmann commented Jul 7, 2026

Copy link
Copy Markdown
Owner

Summary

  • append plan/checklist progress updates instead of replacing earlier natural progress text
  • keep the retained Work Log as chronological user-facing history
  • stack on fix(telegram): retain work log before final answer #1096 so Work Log retention and progress-history behavior are reviewed together

Validation

  • pnpm exec vitest run extensions/telegram/src/work-log.test.ts extensions/telegram/src/progress-controller.test.ts extensions/telegram/src/bot-message-dispatch.test.ts
  • GitHub checks: green on head 88746ac70559671cd14fa7c4b9984fde9a5107cf
  • Live isolated tester-bot proof:
    • runtime branch codex/telegram-progress-format-20260707
    • runtime commit 88746ac70559671cd14fa7c4b9984fde9a5107cf
    • bot @Artem_jarvis_email_bot, runtime PID 41349, port 20271
    • baseline pass artifact .artifacts/telegram-smoke/20260707T063002Z-baseline-975ae95d.json
    • /tts on sent as 54902; TTS ack/voice 54904
    • proof prompt 54905
    • retained Work Log 54906 with text Work log
    • separate final answer 54908
    • separate TTS voice 54909
    • transcript artifact .artifacts/telegram-work-log-review-20260707/live-transcript-after-proof.json
    • screenshot artifact .artifacts/telegram-work-log-review-20260707/live-final-state.png

Proof Gaps

  • openclaw screen record --app Telegram --duration 180s failed with gateway 1006, so no video artifact was produced.
  • Inline Show/Hide was visible and unit-covered, but not live-clicked because Telegram Desktop did not expose message-level controls through GUI-control and the Telegram-as-me CLI has no callback-click command.

- What: append plan/checklist progress without erasing earlier natural status updates.

- Why: Telegram progress is visible work history, so plan snapshots should not replace prior progress.

- Risk: medium-low; changes progress accumulation semantics and is covered by focused dispatch/controller tests.
@artemgetmann artemgetmann force-pushed the codex/telegram-progress-format-20260707 branch from 2262576 to 88746ac Compare July 7, 2026 06:18
@artemgetmann artemgetmann changed the title fix: preserve Telegram plan progress history fix(telegram): preserve plan progress history Jul 7, 2026
@artemgetmann artemgetmann changed the base branch from main to codex/telegram-work-log-v11-20260706 July 7, 2026 06:18
@artemgetmann artemgetmann marked this pull request as ready for review July 7, 2026 06:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant