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

ticket: delegate panel role session registry

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 10:42:57 +09:00
parent 5db02079d0
commit 176e50450b
No known key found for this signature in database
2 changed files with 21 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-012131-workspace-panel-local-role-session-registry/item.md
View File

@ -8,7 +8,7 @@ priority: P1
labels: [tui, panel, ticket, pod, orchestration]
workflow_state: ready
created_at: 2026-06-07T01:21:31Z
updated_at: 2026-06-07T01:42:13Z
updated_at: 2026-06-07T01:42:51Z
assignee: null
legacy_ticket: null
---

20
.yoi/tickets/open/20260607-012131-workspace-panel-local-role-session-registry/thread.md
View File

@ -68,4 +68,24 @@ Implementation intent is clear: add a user-data workspace-scoped local role/sess
Ticket intake complete; workflow_state intake -> ready.
---
<!-- event: implementation_report author: hare at: 2026-06-07T01:42:51Z -->
## Implementation report
## Delegation
Implementation delegated to child Pod `panel-role-session-registry-coder-20260607` in worktree `.worktree/workspace-panel-local-role-session-registry` on branch `work/workspace-panel-local-role-session-registry`.
Scope:
- Add a durable user-data workspace-scoped local role session registry and Ticket claim index.
- Enforce one active local Pod claim per Ticket while allowing a role session/Intake Pod to relate to zero or more Tickets.
- Keep local Pod assignment out of git-tracked Ticket metadata/thread.
- Preserve no-polling semantics and the interim `ticket-*` Pod visibility path.
Coordination note: `workspace-panel-remove-direct-pod-send` is active in parallel and may touch `multi_pod.rs` / `workspace_panel.rs`; the child was instructed to keep the registry implementation additive/localized and report likely conflicts.
The child should commit implementation work in the child worktree and report diff/tests. Merge, review, Ticket closure, and cleanup remain with the parent/human workflow.
---