fix
patch
capture
fix/capture-store-blob-persist
#1 / 1
fix(capture): persist flow store through Netlify Blobs on all bridge capture routes (9-kn-c)
Root cause of the 9-apply live failure (409 FLOW_CANDIDATE_NOT_PROMOTABLE on prop-1785500300353491755): observe/candidates/propose/dismiss wrote only to the lambda's ephemeral DATA_DIR, so candidates evaporated before approve-time apply. Wrap the three mutating routes in withExternalProtocolBlobSync and hydrate before the candidates read — same pattern the CHA apply/list routes already use.
Seven-tier regression suite test/capture-store-blob-persist.test.mjs simulates separate lambda instances as separate DATA_DIRs sharing one blob store: 11/11 with the fix, 7/11 fail against pre-fix routes.
sha256:856bcb5bb3439932f417d8280b6f283fa2237f03d9d8562550226ab450d09e13
sha
+9
~33
−3
symbols
sha256:5e6e03a39d385f7877134728809a30cbf49d1657a90b186028c453512acc28b3
snapshot
+9
symbols added
~33
symbols modified
−3
symbols removed
0
dead code introduced
Semantic Changes
45 symbols
−
NEXT SESSION — 9-apply re-run (RELAY → scooling)
section NEXT SESSION — 9-apply re-run (RELAY → scooling) L21–307
−
THE ONE NEXT STEP — 9-apply re-run — Model: Operator + Auto (Scooling PRIMARY)
section THE ONE NEXT STEP — 9-apply re-run — Model: Operator + Auto (Scooling PRIMARY) L33–62
+
NEXT SESSION — 9-kn-c land + fresh capture re-run (RELAY → scooling)
section NEXT SESSION — 9-kn-c land + fresh capture re-run (RELAY → scooling) L21–310
+
THE ONE NEXT STEP — land 9-kn-c, then fresh capture re-run — Model: Operator + Auto
section THE ONE NEXT STEP — land 9-kn-c, then fresh capture re-run — Model: Operator + Auto L37–65
← Older
Oldest on fix/capture-store-blob-persist
All commits
Newer →
Latest on fix/capture-store-blob-persist
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:856bcb5bb3439932f417d8280b6f283fa2237f03d9d8562550226ab450d09e13 --body "your comment"
No comments yet. Be the first to start the discussion.