Boole

Tracks the remaining correctness, interoperability, and rollout work required for Anchor to activate and operate safely across the Boole SSV fork.

The original Boole implementation is tracked in #768. This milestone captures residual activation-readiness work discovered through current-code review, mixed-client testing, restart testing, and fork-boundary analysis.

Work in this milestone should:

• preserve slot-derived message routing and validation;
• align lifecycle-driven subscriptions, scoring, ENR, discovery, handshake, and peer state with scheduled fork boundaries;
• cover continuous transitions, restart-at-boundary behavior, clock anomalies, and mixed-version operation;
• include focused regression tests and activation canary evidence where appropriate.

The first issue aligns lifecycle transitions with exact slots and reconciles downstream scoring and ENR state.

Issues are directionally correct, not prescriptive; verify symbols at PR time.