Ship Validator v3 with permissionless validation and network integrity

@bmuddha is already working on this.

Since Sep 17, 2026.

### Goal

Ship Validator V3's network-integrity system as one release, allowing any sufficiently staked operator to participate as a validator or verifier.

### Why

Permissionless operation requires a complete response to faults: detection, proof, challenge resolution, leadership rotation, and economic consequences. Shipping only part of that lifecycle would not provide a safe operating model.

### Scope

- Detect conflicting or invalid validator behavior, and produce and verify fraud proofs.
- Resolve challenges through committees and rotate leadership as part of the same safety flow.
- Apply stake-based incentives and slashing deterrence.
- Support registration and operation of sufficiently staked third-party validators and verifiers, limiting MagicBlock's role to arbitration during disputed challenge resolution.
- Validate the full lifecycle under normal operation, faults, restarts, and adversarial scenarios.
- Exercise operational rollout and rollback for permissionless participation.

Detection, fraud proofs, committee challenge resolution, leader rotation, and permissionless operation must ship together, not as independently releasable roadmap outcomes. Completion requires the full lifecycle to work end to end and a qualified third party to be able to run both validator and verifier roles.

Delivery depends on Validator V2 and DLP V2's registration, discovery, and challenge primitives. Fully automated dispute resolution is deferred to the following half-year. Roadmap target: early February 2027.

Related planning: magicblock-labs/dev-kanban#194, magicblock-labs/dev-kanban#196, and magicblock-labs/dev-kanban#198.