feat(runtime-host): project peer Host reachability - #4275
Merged
M4n5ter merged 1 commit intoAug 31, 2026
Conversation
6 tasks
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 00:08
3137fe6 to
29930d3
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
2 times, most recently
from
August 31, 2026 00:44
d9a1d0d to
a17fc28
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 00:51
a17fc28 to
969c416
Compare
jackwener
approved these changes
Aug 31, 2026
jackwener
left a comment
Member
There was a problem hiding this comment.
Approved at the explicit direction of M4n5ter. No technical review was performed as part of this action; M4n5ter requested the approval and accepts responsibility for subsequent handling.
Review notice: This approval was submitted by an automated review agent operated by jackwener and is published at the direction of M4n5ter, who is the human accountable for it.
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 01:59
969c416 to
ff16bdf
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 02:37
ff16bdf to
cf68a3b
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 03:26
cf68a3b to
bf7affb
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 04:09
bf7affb to
246b3eb
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 05:03
246b3eb to
585ec2f
Compare
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 05:50
585ec2f to
ba1bb9b
Compare
Generated-by: OpenAI Codex
M4n5ter
force-pushed
the
feat/peer-mesh-host-reachability
branch
from
August 31, 2026 06:02
ba1bb9b to
dce1c53
Compare
M4n5ter
marked this pull request as ready for review
August 31, 2026 06:11
saltand
pushed a commit
to saltand/maka-agent
that referenced
this pull request
Aug 31, 2026
Generated-by: OpenAI Codex
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
English
Project demanded Runtime Host connectivity as explicit ephemeral phases: discovery, connection, authentication, handshake, and ready waiting. Shared-Session targets remain sparse and become ready only after the authenticated Host handshake; membership or cached route knowledge alone never reports a usable Host.
Cancellation and target-generation fencing prevent a late connection attempt from publishing readiness after removal. This PR is stacked on #4274.
中文
将按需 Runtime Host 连接投影为明确的临时阶段:发现、连接、认证、握手和等待就绪。共享 Session target 保持稀疏,只有完成经过认证的 Host 握手后才会 ready;仅有 membership 或缓存路由绝不会被显示成可用 Host。
取消传播与 target generation fence 会阻止已移除连接的迟到结果发布 readiness。本 PR stack 在 #4274 之上。
Refs #3842
Refs #3843
Verification
English
中文
Review focus
Connection phases are ephemeral observations, not durable Mesh or mount state. Membership must not create all-to-all application streams.
AI use
Tool(s) and scope: OpenAI Codex — architecture planning, implementation, focused tests, and review.
Checklist
Does this PR entail a change in behavior?