fix(capture): merge candidates/flows/steps/runs by key in flow-store blob hydration (9-kn-d)
Second live defect from the 9-apply re-runs: mergeFlowStoreJson merged tasks and task_loops by id but let a warm lambda's stale local candidates/flows/steps/runs arrays mask fresher blob records. Live evidence: approve of prop-1785526040570098296 on a warm lambda refused FLOW_CANDIDATE_NOT_PROMOTABLE while the identical CHA-C11 re-apply on a cold lambda promoted flow_cap_9d65aa57, and approve of prop-1785528026964024269 on a cold lambda auto-applied flow_cap_ca8f2945 through the CHA-C1 hook.
Union-merge by natural key (candidate_id; flow_id+version; flow_id+flow_version+ step_id; run_id), newest updated wins. Regression tiers added (warm-stale unit + e2e): suite 14/14, pre-fix merge fails 3/14. Capture/task/delegation/calendar blob suites 133/133. Also adds the durable live capture smoke driver scripts/verify-capture-flywheel-live-smoke.mjs.
Semantic Changes
47 symbols
0 comments
muse hub commit comment sha256:945c476057fe156d954b9330b270ae28b40cb804f998126cbcd1f68fba1f6e37 --body "your comment"
No comments yet. Be the first to start the discussion.