Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: harden peer pod registration

Browse Source
This commit is contained in:
Hare
2026-06-02 22:23:13 +09:00
parent 093a84fc83
commit 057c2eff5f
9 changed files with 202 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/design/pod-session-state.md
+2 -2
View File
@@ -34,9 +34,9 @@ Delegated write scope is a capability loan. Stopping, shutting down, or pruning
## Peer Pods
Peer visibility is also Pod metadata, but it is distinct from spawned-child delegation. A TUI user can run `:peer <pod-name>` while attached to an idle Pod to register a reciprocal peer handshake with another existing Pod.
Peer visibility is also Pod metadata, but it is distinct from spawned-child delegation. A TUI user can run `:peer <pod-name>` while attached to an idle Pod to register reciprocal peer metadata with another existing Pod. This is a metadata-level registration, not live target-controller consent.
A peer relationship only makes the Pods mutually visible through `ListPods` with visibility source `peer`. It does not grant filesystem scope, create a child output cursor, make either Pod the other's parent, or imply child completion notifications. Peer messages use `SendToPeerPod`, which delivers a labeled notification into the target Pod's normal durable notification/history path.
A peer relationship only makes the Pods mutually visible through `ListPods` with visibility source `peer`. It does not grant filesystem scope, create a child output cursor, make either Pod the other's parent, or imply child completion notifications. Peer messages use `SendToPeerPod`, which delivers a labeled notification into the target Pod's normal durable notification/history path. `SendToPeerPod` requires the peer to be live and fails clearly for non-live peers rather than auto-restoring them.
## Notifications are not authority