jaredandClaude Opus 5
c921f11521
CI / Build & Quality Checks (push) Canceled after 0s
CI / Trigger Desktop Build (push) Canceled after 0s
CI / Secret scan (gitleaks) (push) Canceled after 0s
CI / Docker image build & smoke test (push) Canceled after 0s
CI / Playwright smoke (e2e) (push) Canceled after 0s
The ring event (m.rtc.notification) now renders — only once the ring is over (its lifetime lapsed or the caller hung up) and only if we did not join between the ring and the hang-up — as a red 'Missed call from bob' line with the ring's time, in the same style as the call-membership summaries. Derived entirely from events already in the timeline; nothing is sent; a call we answered shows nothing extra, and a later separate call cannot retro-actively 'answer' an earlier missed one. Verified headless in a DM: ring ignored → line appears once bob hangs up; a second call that alice answers adds no line and leaves the first one in place. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA