UP: #160 Telegram completion and Refining failover notifications

[fujiwaranosai850]

Local upstream-publication tracking issue for the notification family currently centered on local issue #160, with #87 as the broader/root tracker.

This promotion issue owns the full local-to-upstream release prep for the Telegram operator-visible notification bug family.

Family scope

Primary local implementation lane:

• Patch devclaw-local-current completion and Refining notifications for Telegram failover compliance #160 Patch devclaw-local-current completion and Refining notifications for Telegram failover compliance

Broader root tracker / diagnostic context:

• Investigate missing completion announcements after work_finish #87 Investigate missing completion announcements after work_finish

Promotion goal

Prepare a clean upstreamable package for the bug family where operator-facing Telegram announcements for Refining and done/completion do not reliably appear, even when related GitHub issue comments do.

Promotion constraints

• local truth branch is devclaw-local-current
• keep local-only docs and runbook material under /dev
• this issue is local release/publication tracking, not an upstream issue
• upstream PR opening remains human-controlled

Required promotion record

This issue should track:

• the exact local issue(s) being promoted: Patch devclaw-local-current completion and Refining notifications for Telegram failover compliance #160, with Investigate missing completion announcements after work_finish #87 as root context
• source branch(es) and exact commits once the patch lane is confirmed
• target review/* branch for local review into devclaw-local-current
• target pr/* branch for later upstream export
• local fork PR URL into devclaw-local-current
• upstream issue linkage once confirmed or created
• compare URL and final proposed upstream PR title/body after operator testing is complete
• any remaining human-only steps

Current status

As of now, this is only the release-prep tracker. It does not assert that #160 is accepted, validated live, or ready for upstream PR yet.

Notes

Use this issue as the canonical local promotion tracker for this family so release/publication steps do not get scattered across #87, #160, and chat history.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Local review package is now prepared for this promotion family.

Review package

• review branch: review/168-telegram-completion-refining-notifications
• base: devclaw-local-current
• head commit: 50427f0fadeda15308aa60959c099782df7d2d08
• packaged commits:
  • d21ee17 fix: harden telegram completion notification fallback
  • 50427f0 fix: await completion notification delivery

Local review PR

• PR fix: Telegram completion and Refining failover notifications (#168) #170
• fix: Telegram completion and Refining failover notifications (#168) #170

Current runbook state

This completes the local review package creation/open step for the promotion tracker.
The next phase is local-truth review, merge, and testing on devclaw-local-current before any later pr/* upstream export step.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Local review PR #170 has now been merged into devclaw-local-current.

Merged local-truth state

• local review PR: fix: Telegram completion and Refining failover notifications (#168) #170
• PR URL: fix: Telegram completion and Refining failover notifications (#168) #170
• merge commit: 59ecd44a8d1caabc3953de0b9b111ac44f87bbd9

I am refreshing the local-truth checkout so the exact resulting branch head can be recorded next. At this point the runbook has advanced through local review PR creation and merge; the active next phase is local-truth validation/testing before any pr/* upstream export step.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Local truth has been rebuilt and the live plugin source has been switched to the devclaw-local-current worktree as a linked install.

Build provenance embedded in the rebuilt artifact:

• commit: 59ecd44a8d1caabc3953de0b9b111ac44f87bbd9
• branch: devclaw-local-current
• built at: 2026-05-01T02:57:13.796Z

I am now at the runbook step where the gateway restart and post-restart live-source verification are being performed.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Removed the stale duplicate plugin load path for issue-160-telegram-failover-compliance from ~/.openclaw/openclaw.json so only devclaw-local-current remains in plugins.load.paths.

Gateway restart and live-source verification are now being repeated to confirm the runtime actually loads the merged local-truth notification lane.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Correction in progress: PR #170 was merged into devclaw-local-current too early for this workflow.

I have created a rollback branch to revert that premature merge:

• rollback branch: review/168-rollback-premature-merge
• rollback head: 07a3af324a09b0cf39d1d4f1c13a8a70f5f93b87

Next I am opening the rollback PR into devclaw-local-current, then I will switch the live environment to the original review branch so the branch itself can be tested in the live environment before continuing the release process.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Correction status:

• rollback PR revert: undo premature merge of #168 notification package #172 has been merged, so devclaw-local-current is back to the pre-package state
• current local-truth head is now 562d2fdb8207b53df71edd063f3df510a56f9fb8

I am now finishing the branch-first test setup by switching the live environment to review/168-telegram-completion-refining-notifications instead of devclaw-local-current.
A build-dependency issue in that review worktree is the only remaining setup snag right now.