ticket: use base32 project record ids

2026-06-09 22:10:47 +09:00
parent 0803bc3725
commit 4203988d74
798 changed files with 477 additions and 105 deletions
@@ -0,0 +1,36 @@
+---
+title: "Workspace panel orchestrator lifecycle"
+state: "closed"
+created_at: "2026-06-05T21:07:04Z"
+updated_at: "2026-06-06T04:23:48Z"
+---
+
+## Background
+
+The workspace orchestration panel needs a background Orchestrator Pod that is restored or spawned when the panel opens and remains alive after the panel closes.
+
+## Requirements
+
+- Derive Orchestrator Pod name from workspace directory, e.g. `<dir-name>-orchestrator`.
+- On panel open:
+  - restore if restorable;
+  - attach/observe if already live;
+  - spawn if missing and permitted.
+- Use `.yoi/ticket.config.toml` role profile for `orchestrator`.
+- Use the Ticket role launcher where practical.
+- Panel close must not stop the Orchestrator.
+- Surface lifecycle diagnostics in the panel.
+- Do not make Orchestrator the foreground composer target by default; Companion remains foreground management chat.
+
+## Non-goals
+
+- Full panel UI layout.
+- Intake handoff contract.
+- Scheduler/lease/queue.
+- Automatic coder/reviewer spawning.
+
+## Acceptance criteria
+
+- Workspace panel startup can ensure an Orchestrator Pod exists or report why it cannot.
+- Orchestrator lifecycle uses existing Pod restore/spawn semantics and does not duplicate registry logic.
+- Tests cover name derivation and restore/spawn decision logic where practical.