5.1 KiB
Created
Created by LocalTicketBackend create.
Plan
Preflight / implementation intent
Classification: implementation-ready with coordination risk.
Intent:
- Add a local, workspace-scoped role session registry and Ticket claim index for
yoi panelorchestration state. - Store registry data under the configured user data directory, not under git-tracked
.yoi/ticketsfiles and not under the runtime directory. - Model
Ticket -> at most one active local Pod claimwhile allowingPod/session -> 0..N related Tickets. - Represent pre-Ticket Intake sessions even before a Ticket exists.
- Join Ticket state, local registry data, and Pod metadata in panel state/actions where practical, without introducing automatic polling/spawn.
Requirements:
- Define a stable workspace key/path for registry storage under
manifest::paths::data_dir()or an equivalent existing user-data boundary. - Keep local Pod names, socket paths, runtime status, and local claim state out of git-tracked Ticket frontmatter/thread files.
- Make claim creation race-aware: when starting Intake for an existing Ticket, claim before spawn/restore; if a claim exists, do not start a second Pod silently.
- Treat stale claims explicitly with diagnostics/reclaim affordance rather than auto-replacing them.
- Intake is not 1:1 with Ticket: support no related Ticket and multiple related Tickets in the local model.
- Preserve the current interim access path where
ticket-*Pods are visible in the panel.
Code map:
crates/manifest/src/paths.rs: existing data/config/runtime directory boundary; registry should use durable user data, not runtime.crates/tui/src/multi_pod.rs: Intake launch path (prepare_intake_launch/finish_intake_launch), panel snapshot construction, selected actions.crates/tui/src/workspace_panel.rs: Ticket rows, related Pod display,workflow_state = intakerow behavior, Panel view model.crates/client/src/ticket_role.rs: Ticket role launch context and Pod naming; useful integration point but should not write git-tracked Ticket assignment.- Existing Pod list/status model is in
crates/tui/src/multi_pod.rs/workspace_panel.rs; use it for liveness/restorability rather than persisting live status as authority.
Boundaries / non-goals:
- Do not store local Pod assignment in Ticket metadata/thread.
- Do not assume Intake Pod and Ticket are 1:1.
- Do not add polling that auto-starts Intake for
workflow_state = intakeTickets. - Do not replace Orchestrator scheduling.
- Do not implement the real Companion Pod lifecycle here.
- Do not remove selected-Pod direct-send here;
workspace-panel-remove-direct-pod-sendowns that and is being implemented in parallel.
Coordination note:
workspace-panel-remove-direct-pod-sendis active in branchwork/workspace-panel-remove-direct-pod-sendand may touchmulti_pod.rs/workspace_panel.rs. Keep this registry implementation as additive/localized as possible and report any likely merge conflicts.
Validation:
- Add focused unit tests for registry serialization/path behavior, one-active-claim-per-Ticket invariant, and non-1:1 Intake/Ticket relation.
- Run focused
cargo test -p tui workspace_panel --liband relevant new registry tests; runcargo test -p tui multi_pod --libif integration touches panel runtime paths; run formatting/checks appropriate for the diff.
Intake summary
Implementation intent is clear: add a user-data workspace-scoped local role/session registry and Ticket claim index, enforce one active local Pod claim per Ticket, allow one Intake session to relate to multiple Tickets or none, and keep local Pod assignment out of git-tracked Ticket records.
State changed
Ticket intake complete; workflow_state intake -> ready.
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.