Ship Validator v2 on MagicBlock Engine

@bmuddha is already working on this.

Since Sep 17, 2026.

### Goal

Ship the Engine-based validator as the production foundation, with materially better security, stability, and scalability.

### Why

V1 provides a baseline, but its architectural limits make growth and reliable operation harder. V2 moves the validator onto MagicBlock Engine and establishes durable recovery and replication foundations for later decentralization work.

### Scope

- Complete the validator integration with MagicBlock Engine.
- Replace temporary local work tracking with durable intent handling so scheduled work survives restarts and recovers cleanly.
- Establish the replication and recovery foundations needed by later releases.
- Fix reliability, correctness, and load-related issues found during qualification, and expand realistic black-box coverage through RedSuite for V2 and future releases.
- Complete production monitoring and incident reporting, and exercise migration and rollback procedures.

The release candidate must use the Engine architecture for release-critical flows, recover work durably, cover the agreed scenarios in RedSuite, and meet the agreed security, stability, and scalability bar.

Fraud proofs, challenge resolution, leader rotation, permissionless operation, and SDK V1 are outside this release.

Delivery depends on the V1 baseline, outstanding durable-intent work, and continued RedSuite development. Roadmap target: early November 2026.

Related planning: magicblock-labs/dev-kanban#201.