Skip to content

feat(runtime-host): expose peer Mesh transit controls - #4147

Merged
M4n5ter merged 4 commits into
feat/runtime-host-peer-transit-reconciliationfrom
feat/desktop-peer-mesh-transit
Aug 29, 2026
Merged

feat(runtime-host): expose peer Mesh transit controls#4147
M4n5ter merged 4 commits into
feat/runtime-host-peer-transit-reconciliationfrom
feat/desktop-peer-mesh-transit

Conversation

@M4n5ter

@M4n5ter M4n5ter commented Aug 29, 2026

Copy link
Copy Markdown
Member
English

Summary

Expose the Host-owned Peer Mesh transit switch through the CLI and Desktop, with bounded live reservation/circuit status and fixed resource limits sourced from the native endpoint.

Refs #3842

Verification

  • Runtime Host, CLI, and Desktop typechecks passed
  • 17 focused Runtime Host tests, 6 CLI operator tests, and 23 Desktop management tests passed
  • Rust tests (10) and Clippy passed
  • Astryx inventory and ASF header checks passed
  • Real Desktop flow verified: create Mesh, enable transit, reload, and observe the persisted state

Before:

After:

AI use

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

Tool(s) and scope: OpenAI Codex implemented and verified the change under the contributor's direction

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
中文

摘要

将 Runtime Host 所有的 Peer Mesh 成员转发开关接入 CLI 和 Desktop,并显示由 native endpoint 提供的有界 reservation/circuit 状态及固定资源上限

关联 #3842

验证

  • Runtime Host、CLI、Desktop typecheck 通过
  • 17 个 Runtime Host 聚焦测试、6 个 CLI operator 测试、23 个 Desktop 管理测试通过
  • Rust 10 个测试及 Clippy 通过
  • Astryx inventory 与 ASF header 检查通过
  • 已在真实 Desktop 中验证创建 Mesh、开启转发、刷新并恢复持久状态的完整流程

变更前:

变更后:

AI 使用

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

工具与范围:OpenAI Codex 在贡献者指导下实现并验证了本次变更

检查清单

  • 测试覆盖本次变更,且缺少变更时会失败
  • lint、格式化、typecheck 与受影响测试均在本地通过

本 PR 是否改变行为?

  • 是——已在摘要中说明

@github-actions github-actions Bot added the effort/L Under 1000 readable lines label Aug 29, 2026
@M4n5ter
M4n5ter force-pushed the feat/desktop-peer-mesh-transit branch from a8b73f9 to 32caeb2 Compare August 29, 2026 11:00
@M4n5ter
M4n5ter marked this pull request as ready for review August 29, 2026 11:37
@M4n5ter
M4n5ter force-pushed the feat/desktop-peer-mesh-transit branch from 32caeb2 to 4bc7abd Compare August 29, 2026 11:40

@jackwener jackwener left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed exact head 4bc7abdf2aee32cfa0a43708da87ecce0341690c against its stacked base a4e24ccb4b014474ff0daf1b1e5e5a74c04ec69e.

The CLI and Desktop both use the Host-owned peer.mesh.transit.set operation; neither surface creates a second policy authority. The protocol keeps the desired Mesh selection bounded while live reservation/circuit counts and fixed native limits come from the endpoint snapshot. Enable, switch, disable, local, SSH, and framed operator paths preserve explicit string | null semantics, and compatibility epoch 65 correctly fences the closed query/result change.

Runtime Host, CLI, and all Desktop TypeScript surfaces built or typechecked successfully. The 47 focused Runtime Host, CLI, and Desktop tests passed, as did Biome, Rust formatting, and git diff --check. 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.

@M4n5ter
M4n5ter force-pushed the feat/desktop-peer-mesh-transit branch from 4bc7abd to d3ebf9f Compare August 29, 2026 13:44
Add one Host-owned transit switch with bounded status projection across the CLI and Desktop management surfaces.

Generated-by: OpenAI Codex
Carry the canonical nullable Mesh selection through Host projections, Desktop, SSH, and CLI. Remove the duplicate per-Mesh boolean and transit-off side channel.
Remove the obsolete trusted-relay counter from the final transit metrics fixtures after the lower-layer contract was simplified.
Keep main's active-membership filtering while projecting the canonical top-level transit selection after rebasing the stack.

Generated-by: OpenAI Codex
@M4n5ter
M4n5ter force-pushed the feat/desktop-peer-mesh-transit branch from d3ebf9f to a6807b3 Compare August 29, 2026 13:54
@M4n5ter
M4n5ter merged commit f25b5d2 into main Aug 29, 2026
15 of 17 checks passed
@M4n5ter
M4n5ter deleted the feat/desktop-peer-mesh-transit branch August 29, 2026 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

effort/L Under 1000 readable lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants