[P2-E8.1] Synchronizer bootstrapping

**Context.** How a dedicated synchronizer comes into existence: sequencer/mediator
bring-up, initial topology, dynamic parameters (incl. base rate 0), operator participant
dual-homing. Decide the app/console split: what the Sync Operator Node automates vs what
runs once through the Canton console.

**Deliverable.** Scripted, documented bring-up producing a synchronizer ready for
registration; consumed by the LocalNet topology (P2-E9.1) so tests and docs cannot drift.

**Acceptance.** One command (or documented short sequence) yields a functioning dedicated
sync on LocalNet; re-running is idempotent or fails cleanly.

**Depends on.** Nothing; feeds P2-E5.4, P2-E9.1.

—
Epic: #71 · Plan: [P2-E8-deployment-ops.md](https://github.com/ChainSafe/canton-extending-mainnet/blob/main/docs/planning/phase-2-epics/P2-E8-deployment-ops.md)