Module cutover 

Legacy → new-protocol cutover machinery.

Two concerns live here:

• extract_pre_cutover_seed walks a live legacy SystemContextHandle and produces a PreCutoverSeed.
• forward_legacy_timeout_votes and forward_legacy_high_qc tail the legacy event stream and bridge those events into the coordinator’s client API so the new protocol can form TC2s and propose at the boundary.

Functions

cutover_decided 🔒

Bridged requests only matter at the NEW_PROTOCOL_VERSION cutover; forwarding earlier fills the bounded request queue the parked coordinator can’t drain.

extract_pre_cutover_seed

Walk legacy state to produce a PreCutoverSeed; None on a broken walk.

forward_legacy_high_qc

Forward the last legacy view’s QC into the coordinator, so the cutover-view leader can propose on it instead of waiting out a timeout when the cutover seed was snapshotted before the QC formed.

forward_legacy_timeout_votes

Forward legacy TimeoutVote2 events into the new-protocol timeout collectors so the first new leader can form TC2 at the boundary.