//! Bridge backend trait for duplex execution boundaries.
//!
//! A bridge node splits the signal graph into left (recording) and right (playback)
//! sub-graphs. It maintains internal state across callbacks. Feedback is handled
//! externally via `feedback_read`/`feedback_write` annotations on graph nodes —
//! the bridge itself does not manage feedback.
use crateTranscendental;
use crateProcessResult;
/// A graph node that serves as a duplex boundary between recording and playback chains.
///
/// # Execution model
///
/// Each tick is split into five phases:
/// 1. ReadFeedback — mix feedback buffers into node inputs
/// 2. process_left — execute left sub-graph + bridge.process_left(inputs)
/// 3. process_right — bridge.process_right(outputs) + execute right sub-graph
/// 4. WriteFeedback — capture node outputs into feedback buffers
/// 5. Shadow copy — swap read/write feedback buffers