fix(telegram): post stale/missed as new messages instead of editing bubble

[robster7674]

Root cause

TelegramStaleCheckWork used editMessageText to overwrite the glucose bubble with "⚠️ Stale" or "⚪ Missed reading" text. Once the bubble showed stale text, the suppress-delta logic (suppressDeltaBelowMgdl = 1) would suppress flat-glucose readings from re-editing it back to a glucose value — leaving the bubble stuck at "⚠️ Stale" indefinitely. Users saw this as "no telegram message".

Fix

Replace postEdit (editMessageText) with postSend (sendMessage). Stale/missed alerts now appear as new messages rather than overwriting the glucose bubble. The original bubble retains the last valid reading at all times.

Changes:

• Rename postEdit → postSend; drop editMessageText URL rewriting and message_id body field
• Rename messageId guard to hasActiveBubble to reflect that the ID is used only as a sentinel, not passed to the API
• Keep STALE_THROTTLE_MS = 70s, TRANSIENT_RETRY_DELAY_MS = 60s and retry scheduling from the previous PR

Test plan

• CGM reading sends glucose bubble to Telegram
• After stale threshold (~10 min), a new "⚠️ Stale" message appears; bubble still shows glucose value
• Next CGM reading edits the bubble back to the new glucose value (within refresh window)
• After missed threshold, a new "⚪ Missed reading." message appears
• Transient network error retries after 60s; throttle prevents double-posting to already-notified recipients

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR fixes a "stuck at stale" bug where the suppress-delta logic prevented re-editing the Telegram glucose bubble back to a glucose value after editMessageText had overwritten it with a stale/missed alert. Stale and missed alerts now post as new messages, leaving the original bubble intact.

• Replaces postEdit (editMessageText) with postSend (sendMessage): drops URL rewriting and the message_id request body field so only chat_id and text are sent.
• Renames the messageId guard to hasActiveBubble to clarify that the stored message ID is now used only as a sentinel (to confirm at least one successful send has occurred) and is no longer forwarded to the API.

Confidence Score: 5/5

Safe to merge — the change is narrow, addresses a clearly reproducible user-visible defect, and preserves all existing retry and throttle logic.

The diff touches exactly one method: postEdit is replaced by postSend with the URL rewriting and message_id body field removed. The hasActiveBubble rename is cosmetic only and carries no behavioral change. Throttle constants, retry scheduling, and error-handling branches are unchanged. The root-cause explanation in the PR description matches what the code was doing, and the fix directly removes the problematic edit path.

No files require special attention.

Important Files Changed

Filename	Overview
Common/src/main/java/tk/glucodata/TelegramStaleCheckWork.kt	Minimal, well-scoped change: postEdit → postSend, URL rewriting removed, message_id body field dropped, messageId guard renamed to hasActiveBubble. Throttle, retry, and scheduling logic are preserved and correct.

Sequence Diagram

sequenceDiagram
    participant CGM as CGM Reading
    participant OA as OutboundApi
    participant TG as Telegram API
    participant SW as TelegramStaleCheckWork

    CGM->>OA: sendTelegram(reading)
    OA->>TG: sendMessage or editMessageText (bubble)
    TG-->>OA: ok + message_id
    OA->>SW: schedule(destinationId, staleDelayMs)

    Note over SW: stale threshold elapsed
    SW->>SW: hasActiveBubble check
    SW->>TG: sendMessage(Stale) - NEW message
    TG-->>SW: 2xx
    SW->>SW: recordStaleAt, reschedule for missed threshold

    Note over SW: missed threshold elapsed
    SW->>TG: sendMessage(Missed reading) - NEW message
    TG-->>SW: 2xx
    SW->>SW: recordStaleAt, no further reschedule

    Note over OA: next CGM reading arrives
    CGM->>OA: sendTelegram(reading)
    OA->>TG: editMessageText(bubble) - bubble still intact
    TG-->>OA: ok

Loading

_{Reviews (1): Last reviewed commit: "fix(telegram): post stale/missed as new ..." | Re-trigger Greptile}