ticket: add panel role session registry task

2026-06-07 10:22:18 +09:00
parent 7f386f749e
commit 1b7de88a59
9 changed files with 130 additions and 3 deletions
@@ -8,7 +8,7 @@ priority: P1
 labels: [tui, panel, companion, orchestration]
 workflow_state: intake
 created_at: 2026-06-07T00:16:51Z
-updated_at: 2026-06-07T00:18:58Z
+updated_at: 2026-06-07T01:21:43Z
 assignee: null
 legacy_ticket: null
 ---
@@ -46,6 +46,9 @@ Redesign the workspace panel composer around a real workspace Companion Pod and
 3. `companion-status-context-tool-policy`
   - Define Companion prompt/profile/tool policy: status-awareness and human assistance, no direct repository writes or Ticket mutations.

+4. `workspace-panel-local-role-session-registry`
+   - Define the local user-data overlay for role sessions and Ticket claims; keep local Pod assignment out of git-tracked Ticket metadata.
+
 ## Non-goals

 - Removing Pod attach/open.
@@ -26,4 +26,23 @@ Target model:
 Split child tickets were created for direct-send removal, Companion lifecycle, and Companion prompt/tool policy.


+---
+
+<!-- event: decision author: hare at: 2026-06-07T01:21:43Z -->
+
+## Decision
+
+## Local role/session overlay split
+
+The Companion/panel redesign should not store Ticket↔local Pod assignment in git-tracked Ticket metadata. Local Pod names, runtime/session identity, socket/restorable state, and current claims are per-machine runtime concerns.
+
+A new child ticket `workspace-panel-local-role-session-registry` covers the local overlay model:
+
+- Ticket project records keep workflow state and auditable summaries only.
+- A Ticket may have at most one active local Pod claim at a time.
+- A Pod/session may relate to zero or more Tickets.
+- Intake is not 1:1 with Ticket: pre-Ticket Intake may have no Ticket yet, and one Intake session may materialize/split into multiple Tickets.
+- Existing `ticket-*` Pod visibility in the panel is acceptable as an interim access path until the registry UI/model exists.
+- The panel should not poll and automatically start Intake for newly-created `workflow_state = intake` Tickets; starting/claiming remains an explicit action.
+
 ---