chore(edr_op): remove the unsupported OpHardfork::OSAKA variant

[anaPerezGhiglia]

#1601 was meant to be behavior-preserving with respect to the currently pinned revm/op-revm versions, so OpHardfork mirrored every OpSpecId variant, including OSAKA. EDR currently does not support Osaka-equivalent execution in OP.

op-revm replaced the Osaka variant with Karst (the actual OP hardfork) in 20.0.0, published to crates.io through ethereum-optimism/optimism#20068.

This PR removes the variant, since we don't support Karst in OP. It is dormant, unreachable from the napi API (which stops at Isthmus) and never constructed (activations end at Jovian), so the removal is behavior-preserving. Whenever Karst is supported, the variant should be incorporated again under the right name.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7244794

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Removes the OSAKA hardfork variant from the local OpHardfork model and related conversions, aligning supported hardforks with current OP needs and updating tests accordingly.

Changes:

• Removed OSAKA from OpHardfork, including string identifiers and op_revm::OpSpecId conversion.
• Updated FromStr / &'static str conversions to no longer accept/emit "Osaka".
• Adjusted test variant list and updated revm parity module documentation.

Suppressed comments (1)

crates/edr_op/src/hardfork.rs:124

• Removing support for parsing \"Osaka\" is an externally-observable behavior change: inputs that previously parsed will now return UnknownHardfork. If this string can appear in persisted configs/fixtures, consider keeping \"Osaka\" as a deprecated alias (either mapping to a chosen replacement or returning a more actionable error) or documenting/migrating callers accordingly.

impl FromStr for OpHardfork {
    type Err = UnknownHardfork;

    fn from_str(s: &str) -> Result<Self, Self::Err> {
        match s {
            name::BEDROCK => Ok(Self::BEDROCK),
            name::REGOLITH => Ok(Self::REGOLITH),
            name::CANYON => Ok(Self::CANYON),
            name::ECOTONE => Ok(Self::ECOTONE),
            name::FJORD => Ok(Self::FJORD),
            name::GRANITE => Ok(Self::GRANITE),
            name::HOLOCENE => Ok(Self::HOLOCENE),
            name::ISTHMUS => Ok(Self::ISTHMUS),
            name::JOVIAN => Ok(Self::JOVIAN),
            name::INTEROP => Ok(Self::INTEROP),
            _ => Err(UnknownHardfork),
        }
    }
}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[anaPerezGhiglia]

I don't think this is necessary

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.99%. Comparing base (0611870) to head (7244794).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1603      +/-   ##
==========================================
- Coverage   80.00%   79.99%   -0.01%     
==========================================
  Files         453      453              
  Lines       79293    79292       -1     
  Branches    79293    79292       -1     
==========================================
- Hits        63440    63432       -8     
- Misses      13673    13677       +4     
- Partials     2180     2183       +3     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.