chore(main): release fork-diff 0.7.3

[taiko-kitty]

🤖 I have created a release beep boop

0.7.3 (2026-08-26)

Chores

• protocol: merge taiko-alethia-protocol-v3.0.0 (v3.1.0 + hardening) back to main (f837160)
• protocol: record the v3.0.0 merge ancestry (take 2) (9646f55)
• protocol: record the v3.0.0 merge ancestry (take 2) (bc35381)
• protocol: record the v3.0.0 merge ancestry lost by squashing #21922 (#21930) (ca16fba)

---

This PR was generated with Release Please. See documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c1b1358a92

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid tagging fork-diff from an unrelated protocol chore

This fork-diff release only contains the protocol chore from ca16fba, and I checked that commit with git diff-tree and it has no tree diff or packages/fork-diff changes. When this bump is published, .github/workflows/fork-diff--production.yml runs on any fork-diff-* tag and deploys the current taiko-geth branch to production, so merging this would redeploy geth.taiko.xyz from an unrelated empty/protocol-only change without the normal fork-diff preview path. Drop this release or wait until there is an actual fork-diff change to publish.

Useful? React with 👍 / 👎.