chore(main): release ejector 0.7.1

[taiko-kitty]

🤖 I have created a release beep boop

0.7.1 (2026-08-15)

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)
• taiko-client-rs,ejector: bump event-scanner to v1.1.1 (#21737) (729a43e)

Documentation

• ejector: add package README (#21872) (f18da26)

Code Refactoring

• ejector: remove router and wrapper dependencies (#21962) (43847ec)

---

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: 444a352ce8

ℹ️ 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]

Update the lockfile version with the crate bump

This release bumps the crate to 0.7.1, but the tracked packages/ejector/Cargo.lock still records the local ejector package as 0.7.0 (checked at packages/ejector/Cargo.lock:1848-1849). The release config explicitly lists that lockfile package version as an extra-files target for packages/ejector, so the release commit leaves the repository's published release metadata inconsistent and the next release-please run will have to repair this instead of starting from the released state.

Useful? React with 👍 / 👎.