openclaw - 💡(How to fix) Fix bug(signal): heartbeat/session final replies can stay internal instead of reaching Signal [1 participants]

Problem

In live Signal DM use, some assistant follow-up/final messages are visible in the internal session transcript (agent:main:signal:direct:+1...) but do not actually arrive to the human in Signal.

Observed symptoms:

• the human receives the early "starting..." receipt but not the final report
• the internal session shows the assistant produced the missing final text
• cron job state can still show lastDeliveryStatus: delivered
• raw leakage like terminated has also appeared in the same general heartbeat/session-delivery area

Why this matters

This creates false confidence that follow-through happened when the actual user-facing channel only got half the story.

For heartbeat-driven work, that is especially bad because the whole point is trustworthy proactive follow-through.

Desired outcome

When a heartbeat/session/cron run produces user-facing output for a Signal DM:

• the final report should reliably egress to Signal, not just remain in the internal session transcript
• delivery status should reflect real user-visible delivery, not only internal completion bookkeeping
• internal runtime strings like terminated should never leak into the user-visible channel

Acceptance shape

• no more cases where the internal session shows a final assistant reply that never appears in Signal
• cron/session delivery status matches the actual user-visible result
• heartbeat follow-ups reliably land end-to-end in Signal
• if delivery fails, surface it as an explicit delivery failure instead of a silent transcript-only success

Notes

This surfaced in the main Signal DM while running heartbeat-driven repo housekeeping and damage-report follow-through. A concrete example was a 10 AM damage report where the start note arrived but the final red/yellow/green report did not.