fix(hosted): strong-consistency calendar OAuth blob hydrate (INF-KN-3c)
Begin and Google callback hit different Netlify Lambdas within seconds. Eventual Blobs hydrate left oauth_pending invisible → state_invalid after consent. Hydrate calendar store (and token blobs) with consistency:strong and merge local pending connectors so warm disk is not wiped by a stale edge read.
sha256:53c6a39c765bea65cf82d9a717f82dc39839f98d6f018e501d9845b0d6562be3
sha
+14
~7
symbols
sha256:27776bd481bd52de1f1e15d6fbd75113922340221e142b44ae1d65f05a4f08ca
snapshot
+14
symbols added
~7
symbols modified
0
dead code introduced
Semantic Changes
21 symbols
+
listCalendarConnectorIdsForBlobSync
function
function listCalendarConnectorIdsForBlobSync L206–230
~
handler
Older
docs: KN-INF-3a gate flip complete — INF-3 smoke next
sha256:a96ec31dc776c4c8556d3d391676ef5b18be97bede15f79c0bea1ab5f74d7d34
All commits
Newer
mirror: GitHub Phase A durable MCP OAuth (#270)
sha256:b5f647cb9c409f563d4671fe3fc05ddea01fabfed9b41fc11cb923588e1c1baf
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:53c6a39c765bea65cf82d9a717f82dc39839f98d6f018e501d9845b0d6562be3 --body "your comment"
No comments yet. Be the first to start the discussion.