chore(upgrade-signal): read new ProtocolVersions schedule contract

[PelleKrab]

Summary

Adds support for reading dynamic upgrade activation schedules from the L1 ProtocolVersions contract.

This updates the upgrade-signal utility to:

• read the contract-backed upgrade schedule with getSchedule()
• read the global minimumProtocolVersion()
• map contract schedule entries onto known BaseUpgrade::CONTRACT_VARIANTS
• reject schedules requiring a newer node protocol version than the binary supports
• derive the node protocol version from the Cargo/GitHub release version
• allow unreleased 0.0.0 dev builds to bypass the minimum-version rejection with U256::MAX

The Solidity ABI in this crate intentionally includes only the read surface used by nodes, not the
full contract interface.

Notes

CONTRACT_VARIANTS remains explicit because it is not the same as all BaseUpgrade variants. It
represents the contract-backed upgrade set in L1 schedule order and intentionally excludes non-
contract-backed upgrades like Bedrock and Zombie.

Tests

cargo fmt --check -p base-upgrade-signal
cargo test -p base-upgrade-signal --all-features
cargo clippy -p base-upgrade-signal --all-targets --all-features -- -D warnings

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[jackchuma]

looks good - just one optional nit to address

[github-actions]

Review Summary

Reviewed the migration from per-upgrade getTimestamp/getProtocolVersion calls to the batch getSchedule() + minimumProtocolVersion() contract interface.

No new issues found. The implementation is clean:

• The positional mapping via CONTRACT_VARIANTS.iter().zip(timestamps.iter()) correctly aligns contract registration IDs with the hardfork ladder, and the doc comment accurately describes the semantics (positional by id, not a timestamp sort).
• The packed-semver encoding in packed_protocol_version correctly places major << 96 | minor << 64 | patch << 32 into the U256 limb layout, and protocol_version_to_f64 decodes using the matching inverse.
• The 0.0.0 → U256::MAX dev-build bypass is well-tested and documented.
• Error handling in read_schedule correctly records metrics for all upgrade IDs on failure (no partial-success paths remain after the batch migration).
• read_schedule_tolerant properly delegates to read_schedule without double-counting error metrics.
• The expect calls on env!("CARGO_PKG_VERSION_*").parse() are safe — Cargo guarantees these are numeric strings.
• Test coverage is thorough: partial schedules, full schedules, filtering, unknown entries, and hardforks without contract entries are all exercised.

Previous inline comments from an earlier review run addressed minor documentation points that appear to already be resolved in this version of the PR.

[github-actions]

❌ base-std fork tests did not run

The build or setup step failed before any tests could execute. Check the workflow logs for details.

Dependency	Ref	Commit
base-std	main	4658f1b7
base-anvil	f4370bc97756557d0ef1a6c325ad7d2532e71112	f4370bc9