When a Loom meeting notes page (auto-created from Google Calendar sync) is edited and published by a user during the meeting, the post-meeting write-back of the AI summary, recording embed, action items, and transcript fails silently. The placeholder text ("After your meeting, Loom AI will add a meeting summary...") remains permanently on the page with no error notification to the user.

Root cause:
Loom's write-back service caches the page version number from page creation. When a user edits and publishes the page during the meeting, the version advances. The write-back then submits a stale version number → Confluence API returns 409 conflict → write-back fails with no retry and no user notification.

Steps to reproduce:

1. Have a Google Calendar meeting with Loom meeting notes enabled (Confluence page auto-created)

1. During the meeting, edit and publish the Confluence meeting notes page (e.g., add notes, action items)

1. Wait for meeting to end and AI processing to complete (~2-5 min)

1. Observe: placeholder text remains, no summary/transcript/recording embed is written back

Expected behavior:
Write-back should fetch the current page version before writing, retry on 409 conflict, and notify the user if it ultimately fails.

Actual behavior:
Write-back submits stale version, receives 409, fails silently. No retry, no notification.

Impact:
Any meeting where someone takes notes on the Loom-created Confluence page risks losing the AI summary entirely. Fails silently with no indication anything went wrong.