ticket: delegate companion notify coder

.yoi/tickets/00001KTTW04W2/item.md

@@ -2,7 +2,7 @@
 title: 'Orchestrator進捗をAutoKickなしでCompanionへ通知する'
 state: 'inprogress'
 created_at: '2026-06-11T08:15:24Z'
-updated_at: '2026-06-12T14:51:31Z'
+updated_at: '2026-06-12T14:52:34Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-11T10:31:56Z'

.yoi/tickets/00001KTTW04W2/thread.md

@@ -155,3 +155,19 @@ Implementation worktree created for multi-agent handoff.
 - Next: spawn sibling coder with narrow write scope to the implementation worktree. Reviewer will be started after coder evidence is available.
 
 ---
+
+<!-- event: plan author: orchestrator at: 2026-06-12T14:52:34Z -->
+
+## Plan
+
+Coder delegated.
+
+- Coder Pod: `yoi-coder-companion-progress-notify`
+- Worktree: `/home/hare/Projects/yoi/.worktree/orchestrator-progress-companion-notify`
+- Branch: `ticket/orchestrator-progress-companion-notify`
+- Scope: write `/home/hare/Projects/yoi/.worktree/orchestrator-progress-companion-notify`; read child worktree plus minimal non-recursive runtime-root read required by spawn validation.
+- Task: implement `Notify { auto_run: false }` weak progress notification semantics, bounded Orchestrator progress summary delivery to live/reachable Companion, missing/stopped no spawn/restore behavior, Panel freshness/last-updated indication, focused tests, and required validation.
+- Concurrent work note: `00001KTVJFT6F` has active coder work in another worktree and may edit Panel UI; coder was instructed to keep Panel changes narrow and report overlap if it becomes a blocker.
+- Constraint: coder was instructed not to use root/original workspace for decision evidence or git/validation/cleanup, and not to create generated memory/local/runtime/log/lock/secret-like `.yoi` paths.
+
+---