ticket: route plugin request capabilities

.yoi/tickets/00001KVMGAEJN/artifacts/relations.json

@@ -0,0 +1,13 @@
+{
+  "version": 1,
+  "relations": [
+    {
+      "ticket_id": "00001KVMGAEJN",
+      "kind": "depends_on",
+      "target": "00001KVMG8FTW",
+      "note": "WebSocket capability design should reuse or deliberately diverge from the URL permission/request-target schema produced by `host_api.request`; current Ticket remains requirements_sync_needed until those design decisions are resolved.",
+      "author": "yoi-orchestrator",
+      "at": "2026-06-21T07:17:46Z"
+    }
+  ]
+}

.yoi/tickets/00001KVMGAEJN/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'Plugin: URL 権限ベースの別 capability として WebSocket support を設計する'
-state: 'queued'
+state: 'planning'
 created_at: '2026-06-21T07:11:34Z'
-updated_at: '2026-06-21T07:15:42Z'
+updated_at: '2026-06-21T07:17:52Z'
 assignee: null
 readiness: 'requirements_sync_needed'
 risk_flags: ['plugin', 'host-api', 'websocket', 'service', 'ingress', 'lifecycle', 'permissions', 'security', 'persistence']

.yoi/tickets/00001KVMGAEJN/thread.md

@@ -29,4 +29,43 @@ LocalTicketBackend によって作成されました。
 Ticket を `workspace-panel` が queued にしました。
 
 
+---
+
+<!-- event: decision author: yoi-orchestrator at: 2026-06-21T07:17:40Z -->
+
+## Decision
+
+Routing decision: `return_to_planning_requirements_sync`
+
+Reason:
+- Ticket frontmatter has `readiness: requirements_sync_needed`。
+- Intake summary explicitly says this should be handled as WebSocket capability design/spec sync, not implementation-direct routing。
+- Ticket body still lists concrete open questions that must be resolved before implementation or worktree side effects:
+  - WebSocket connection ownership: Yoi host-owned vs Plugin-instance-owned host API。
+  - Incoming message dispatch route: Ingress vs Service event/status stream vs other host routing。
+  - Reconnect / backoff / heartbeat / shutdown / cancellation / restore scope for first slice。
+  - Auth/headers/secrets model and grant/display split。
+  - Whether this work item closes as design/spec only or includes a minimal implementation slice。
+- Related Ticket `00001KVMG8FTW` is now routed for implementation of the `host_api.request` URL permission model. WebSocket design should reuse or intentionally diverge from that resulting URL permission schema after it stabilizes。
+
+Decision:
+- Do not create implementation worktree or spawn Coder/Reviewer for this Ticket now。
+- Return to `planning` with concrete missing requirements/design decisions。
+- Record relation to `00001KVMG8FTW` so WebSocket design can be resumed after request permission model lands。
+
+Required next planning output before queueing again:
+- Decide whether this is design/spec only or includes a minimal implementation slice。
+- Decide connection ownership and lifecycle boundary。
+- Decide incoming-message durable/visible dispatch path and no-hidden-context behavior。
+- Decide WebSocket URL permission/grant schema relative to `host_api.request` request-target schema。
+- Decide auth/secrets display/grant model and non-goals for reconnect/backoff/heartbeat in first slice。
+
+---
+
+<!-- event: state_changed author: yoi-orchestrator at: 2026-06-21T07:17:52Z from: queued to: planning reason: requirements_sync_needed_connection_lifecycle_and_scope_decisions field: state -->
+
+## State changed
+
+Ticket remains `requirements_sync_needed` and has unresolved design questions around connection ownership, incoming-message dispatch path, lifecycle bounds, auth/secrets handling, and design-vs-implementation scope. Returning to planning rather than starting implementation side effects.
+
 ---