feat(runtime-host): reconcile peer Mesh transit

[M4n5ter]

English

Summary

Persist one selected Peer Mesh as the local transit desired state and reconcile it into the native Relay v2 policy. Signed route records scope transit capability to that Mesh, while membership removal or Mesh closure withdraws access and reservations automatically.

This PR is stacked on #4142.

Refs #3842

Verification

• cargo test --manifest-path native/runtime-host-peer/Cargo.toml --locked --all-targets --all-features
• cargo clippy --manifest-path native/runtime-host-peer/Cargo.toml --locked --all-targets --all-features -- -D warnings
• npm --workspace @maka/runtime-host run typecheck
• npm --workspace @maka/runtime-host run build
• focused Runtime Host peer native, listener, and Mesh suites: 17 passed

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex assisted with implementation, tests, and validation.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

中文

概要

将一个选定的 Peer Mesh 持久化为本机 transit desired state，并将其协调为 native Relay v2 策略。签名路由记录将 transit 能力限定在该 Mesh 内；成员被移除或 Mesh 关闭时，访问权限与 reservation 会自动撤销。

本 PR stack 在 #4142 之上。

Refs #3842

验证

• cargo test --manifest-path native/runtime-host-peer/Cargo.toml --locked --all-targets --all-features
• cargo clippy --manifest-path native/runtime-host-peer/Cargo.toml --locked --all-targets --all-features -- -D warnings
• npm --workspace @maka/runtime-host run typecheck
• npm --workspace @maka/runtime-host run build
• Runtime Host peer native、listener 与 Mesh 聚焦测试：17 项通过

AI 使用

• 没有生成式工具作出实质贡献
• 生成式工具作出了实质贡献

工具与范围：OpenAI Codex 协助实现、测试与验证。

检查清单

• 测试覆盖本次变更，且在没有修复时会失败
• lint、format、typecheck 与受影响测试均在本地通过

本 PR 是否改变行为？

• 是——已在概要中说明
• 否

[jackwener]

I reviewed exact head a4e24ccb4b014474ff0daf1b1e5e5a74c04ec69e against its stacked base 99fc779aedf69035dcad1e5170c78df6a549e07b.

The selected Mesh remains durable desired state, signed route records scope transit capability to active shared membership, native relay admission stays closed to the configured roster, and membership removal or Mesh closure withdraws routes, reservations, active connections, and pending transit attempts. Native retries resolve current relay addresses rather than persisting stale endpoints.

The Runtime Host build passed; its compiled test suite passed 1,357 tests with 9 platform/environment skips, the 18 focused peer tests passed, and Biome, Rust formatting, and git diff --check passed. Exact-head hosted CI, admission quality, Windows recovery, package validation, and native platform builds are green.

This approval is scoped to the stacked base. Current main has an independent Mesh-status change that conflicts in peer-mesh/node.ts; the stack must preserve that active-membership filter when it is rebased before landing.

---

Automated review notice: This comment was posted by an automated review agent operated by WAWQAQ. It is not an independent human review and does not replace one.