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

ticket: defer repository pages behind sidebar

Browse Source
This commit is contained in:
Hare
2026-06-22 01:41:16 +09:00
parent 520209f38c
commit a607a1f20d
3 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.yoi/tickets/00001KVNGJPRG/thread.md
+22
View File
@@ -30,4 +30,26 @@ Marked ready by `yoi ticket state`.
Ticket を `workspace-panel` が queued にしました。
---
<!-- event: decision author: yoi-orchestrator at: 2026-06-21T16:41:09Z -->
## Decision
Routing decision: `wait_do_not_parallelize_with_sidebar`
Reason:
- Ticket body is implementation-ready in isolation, but it is directly coupled to the currently active sidebar navigation work `00001KVNG9B9Z`。
- Relations show this Ticket is related to `00001KVNG9B9Z` with note: “Sidebar navigation should link to repository and objective pages”。
- `00001KVNG9B9Z` is already `inprogress`, has a live Coder Pod, and is expected to change `web/workspace/src/routes/+page.svelte` / sidebar component structure。
- Starting this Ticket in parallel now would likely produce overlapping route/layout/sidebar changes and non-trivial semantic merge work, rather than independent implementation。
- Host/Worker API work `00001KVNEKH9Q` just landed, further increasing the need to base the page/navigation work on current SPA state。
Decision:
- Do not create a worktree or spawn Coder for `00001KVNGJPRG` yet。
- Leave Ticket `queued` and record an orchestration `do_not_parallelize` note with `00001KVNG9B9Z`。
- Re-route this Ticket after sidebar work lands, or if sidebar implementation report shows a stable component boundary that makes repository/objective pages non-conflicting。
No implementation side effects were performed for this Ticket。
---