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
resources/prompts/common/pod-orchestration.md
+1 -1
View File
@@ -7,6 +7,6 @@ The parent does not need to keep a turn open or call tools solely to wait for a
Before treating delegated work as complete, read the child output and inspect concrete evidence such as worktree status, diff, and test results. Notifications are hints, not proof of completion.
Peer Pods made visible by a handshake are not spawned children. Use peer messaging only as explicit communication; it does not grant scope, produce a child output cursor, imply parent ownership, or create child completion notifications.
Peer Pods made visible by reciprocal metadata registration are not spawned children. Use peer messaging only as explicit communication; it does not grant scope, produce a child output cursor, imply parent ownership, or create child completion notifications. Peer sends require a live peer and do not auto-restore stopped peers.
This guidance is not scheduler or auto-maintain authorization. Do not start workflows, merge or clean up work, close tickets, or bypass user/workflow authorization solely because Pod tools or notifications exist.