merge: sync orchestration before queue 00001KVNKD56W

This commit is contained in:
2026-06-22 17:48:39 +09:00
17 changed files with 2648 additions and 238 deletions
+2 -2
View File
@@ -1,8 +1,8 @@
---
title: 'Workspace web UI: add sidebar navigation panel'
state: 'inprogress'
state: 'closed'
created_at: '2026-06-21T16:30:12Z'
updated_at: '2026-06-21T16:37:34Z'
updated_at: '2026-06-21T17:01:46Z'
assignee: null
queued_by: 'workspace-panel'
queued_at: '2026-06-21T16:35:06Z'
+26
View File
@@ -0,0 +1,26 @@
Workspace web UI に sidebar navigation panel を追加し、Orchestrator worktree の `orchestration` branch に統合した。
主な成果:
- `web/workspace/src/lib/workspace-sidebar/` に sidebar components を追加:
- `WorkspaceSidebar.svelte`
- `RepositoriesNavSection.svelte`
- `ObjectivesNavSection.svelte`
- `WorkersNavSection.svelte`
- `types.ts`
- `web/workspace/src/routes/+page.svelte` を sidebar + main content の responsive two-column layout に更新。
- Sidebar header に workspace label/name と disabled settings placeholder を表示。
- `repositories`, `objectives`, `workers` sections を追加。
- Objectives section は `/api/objectives` を読み、title/state と empty/error states を section-local に表示。
- Workers section は `/api/workers` を読み、Worker label/state/status/role を表示し、Pod を primary UI naming として露出しない。
- Repository section は future Repository API に繋げやすい placeholder seam として実装。
- Host/Worker API/UI merge 後の `+page.svelte` conflict を解消し、main Host/Worker content と sidebar skeleton を両方維持。
- Backend/API authority, SSR, mutation/business logic は追加していない。
統合・検証:
- Merge commit: `613f4126 merge: workspace sidebar navigation`
- Implementation commits: `d3b8bdfd`, `4ab696b4`
- Reviewer final verdict: approve
- Validation passed: `git diff --check HEAD^1..HEAD`, `deno task check`, `deno task build`, `cargo test -p yoi-workspace-server`, `cargo run -p yoi -- ticket doctor`, and `nix build .#yoi --no-link`
範囲外:
- Settings page, Repository CRUD/API, Objective edit/detail UI, Worker start/stop/attach controls, drag/drop/collapsible tree, auth, multi-workspace switcher は実装していない。
+251
View File
@@ -135,3 +135,254 @@ Next action:
- Wait for Coder implementation report, then spawn Reviewer read-only for the implementation diff。
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T16:54:08Z -->
## Implementation report
Coder conflict-resolution report received from `yoi-coder-00001KVNG9B9Z`.
Final implementation HEAD:
- `4ab696b4` merge commit from current `orchestration` into `impl/00001KVNG9B9Z-workspace-sidebar`
Relevant commits:
- `d3b8bdfd feat: add workspace sidebar skeleton`
- `4ab696b4` merge/conflict-resolution commit
Conflict resolution summary:
- Resolved `web/workspace/src/routes/+page.svelte` conflict after Host/Worker API/UI from `00001KVNEKH9Q` landed。
- Preserved merged Host/Worker main content/cards/table。
- Preserved sidebar navigation skeleton。
- Updated sidebar Workers section to consume available `/api/workers` response through typed `ListResponse<Worker>`
- Kept Pod naming out of sidebar, presenting workers by label/state/status/role。
- Changes remain scoped to Workspace frontend。
Coder validation reported:
- `cd web/workspace && deno task check`: passed
- `cd web/workspace && deno task build`: passed
- `git diff --check`: passed
- `git diff --check orchestration..HEAD`: passed
- `cargo run -p yoi -- ticket doctor`: passed
- `nix build .#yoi --no-link`: passed
- `cargo test -p yoi-workspace-server`: not run because backend code was not changed during conflict resolution
Generated artifact cleanup:
- Coder removed generated/ignored frontend artifacts after validation:
- `web/workspace/.svelte-kit`
- `web/workspace/build`
- `web/workspace/node_modules`
Orchestrator evidence checked:
- Worktree clean on `impl/00001KVNG9B9Z-workspace-sidebar` at `4ab696b4`
- Diff `orchestration..HEAD` touches expected frontend files only: new `web/workspace/src/lib/workspace-sidebar/*` components and `web/workspace/src/routes/+page.svelte`
- `git diff --check orchestration..HEAD`: passed。
- Merge-tree conflict scan vs current `orchestration`: no conflict markers / no changed-in-both diagnostics。
Next action:
- Route to read-only Reviewer Pod for acceptance review。
---
<!-- event: comment author: yoi-orchestrator at: 2026-06-21T16:54:49Z -->
## Comment
Review routing:
Spawned read-only Reviewer Pod:
- `yoi-reviewer-00001KVNG9B9Z-r1`
Review target:
- Worktree: `/home/hare/Projects/yoi/.worktree/00001KVNG9B9Z-workspace-sidebar`
- Branch: `impl/00001KVNG9B9Z-workspace-sidebar`
- Current implementation HEAD: `4ab696b4`
- Implementation commits:
- `d3b8bdfd feat: add workspace sidebar skeleton`
- `4ab696b4` merge/conflict-resolution commit from current `orchestration`
- Primary review diff: `orchestration..HEAD` inside implementation worktree, so review sees final sidebar changes on top of current Host/Worker API/UI state。
Reviewer scope:
- read-only `/home/hare/Projects/yoi`
Reviewer focus:
- Sidebar visibility/layout/responsive behavior。
- Workspace header/settings placeholder。
- Repositories/objectives/workers sections。
- Objective and worker section bounded loading/empty/error handling。
- Worker naming avoids Pod-primary UI。
- Main Host/Worker content from `00001KVNEKH9Q` remains preserved after conflict resolution。
- No backend authority/SSR/business logic changes。
Orchestrator will wait for reviewer verdict before integration。
---
<!-- event: review author: yoi-reviewer-00001KVNG9B9Z-r1 at: 2026-06-21T17:00:16Z status: approve -->
## Review: approve
Verdict: `approve`
確認範囲:
- Ticket authority:
- `.yoi/tickets/00001KVNG9B9Z/item.md`
- `.yoi/tickets/00001KVNG9B9Z/thread.md`
- Implementation diff:
- `git diff --name-status orchestration..HEAD`
- implementation-only diff against merge-base `a607a1f20d0622b1f556c36cca155da68109fe25..HEAD`
- Frontend files:
- `web/workspace/src/routes/+page.svelte`
- `web/workspace/src/lib/workspace-sidebar/WorkspaceSidebar.svelte`
- `web/workspace/src/lib/workspace-sidebar/RepositoriesNavSection.svelte`
- `web/workspace/src/lib/workspace-sidebar/ObjectivesNavSection.svelte`
- `web/workspace/src/lib/workspace-sidebar/WorkersNavSection.svelte`
- `web/workspace/src/lib/workspace-sidebar/types.ts`
- API shape spot-check:
- `crates/workspace-server/src/server.rs`
- `crates/workspace-server/src/hosts.rs`
- `crates/workspace-server/src/records.rs`
Blocking issues:
- None。
Acceptance verification:
- Left sidebar is wired into `+page.svelte` and layout is separated from main content。
- Sidebar header shows workspace label/name and disabled settings placeholder。
- `repositories`, `objectives`, and `workers` sections are present。
- Objectives section fetches `/api/objectives` and handles loading/error/empty locally。
- Workers section fetches `/api/workers`, uses Worker naming in visible UI, and handles 404/empty/error locally。
- Main Host/Worker content from current orchestration branch is preserved。
- No backend/API authority changes were introduced by the implementation-only diff。
- Responsive CSS uses a two-column layout on wide viewports and single-column layout below 760px, with `min-width: 0`, wrapping, and table overflow containment。
Non-blocking concerns:
- `orchestration..HEAD` currently shows apparent `.yoi/tickets/00001KVNG9B9Z/item.md` / `thread.md` reversions because `orchestration` has newer review-routing/report commits after the implementation branchs merge-base. The implementation-only diff against the merge-base is frontend-only, and `git merge-tree --write-tree orchestration HEAD` reports a clean merge. This should not block a normal merge, but avoid applying the literal `orchestration..HEAD` patch/squash in a way that drops newer ticket thread entries。
Reviewer validation:
- `git diff --check`: passed
- `git diff --check orchestration..HEAD`: passed
- `git diff --check $(git merge-base orchestration HEAD)..HEAD`: passed
- `cd web/workspace && deno task check`: passed (`svelte-check found 0 errors and 0 warnings`)
- `cd web/workspace && deno task build`: passed; static adapter wrote site to `build`
- `cargo run -p yoi -- ticket doctor`: passed (`doctor: ok`)
- `nix build .#yoi --no-link`: passed
- `cargo test -p yoi-workspace-server`: passed (`6 passed; 0 failed`)
- `git merge-tree --write-tree orchestration HEAD`: passed with status 0; produced merged tree `24e0e026264333fc63d60c0e2d649839445acb64`
Generated artifacts:
- Reviewer did not clean generated ignored artifacts after validation:
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
- `web/workspace/node_modules/`
- They are ignored and not tracked; `git ls-files --others --exclude-standard` reports `0`
Worktree status:
- Clean tracked state on `impl/00001KVNG9B9Z-workspace-sidebar` at `4ab696b4`
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:00:46Z -->
## Implementation report
Reviewer r1 approvalを受けて、実装ブランチを Orchestrator worktree の `orchestration` branch に統合した。
統合:
- Merge commit: `613f4126 merge: workspace sidebar navigation`
- Merged branch: `impl/00001KVNG9B9Z-workspace-sidebar`
- Implementation commits:
- `d3b8bdfd feat: add workspace sidebar skeleton`
- `4ab696b4` merge/conflict-resolution commit from current `orchestration`
Orchestrator worktree validation:
- `git diff --check HEAD^1..HEAD`: passed
- `cd web/workspace && rm -rf node_modules .svelte-kit build && deno task check`: passed (`svelte-check found 0 errors and 0 warnings`)
- `cd web/workspace && deno task build`: passed
- `cargo test -p yoi-workspace-server`: passed (`6 passed`)
- `cargo run -p yoi -- ticket doctor`: passed (`doctor: ok`)
- `nix build .#yoi --no-link`: passed
Validation generated ignored frontend artifacts in Orchestrator worktree:
- `web/workspace/node_modules/`
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
These were removed after validation. Final Orchestrator worktree status after validation cleanup is clean on `orchestration` at `613f4126`
---
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-21T17:00:59Z from: inprogress to: done reason: implementation_merged_and_validated field: state -->
## State changed
Reviewer approval、Orchestrator worktree への統合、Deno check/build、workspace-server tests、Ticket doctor、Nix build が完了したため `done` に遷移する。
---
<!-- event: state_changed author: hare at: 2026-06-21T17:01:13Z from: done to: closed reason: closed field: state -->
## State changed
Ticket を closed にしました。
---
<!-- event: close author: hare at: 2026-06-21T17:01:13Z status: closed -->
## 完了
Workspace web UI に sidebar navigation panel を追加し、Orchestrator worktree の `orchestration` branch に統合した。
主な成果:
- `web/workspace/src/lib/workspace-sidebar/` に sidebar components を追加:
- `WorkspaceSidebar.svelte`
- `RepositoriesNavSection.svelte`
- `ObjectivesNavSection.svelte`
- `WorkersNavSection.svelte`
- `types.ts`
- `web/workspace/src/routes/+page.svelte` を sidebar + main content の responsive two-column layout に更新。
- Sidebar header に workspace label/name と disabled settings placeholder を表示。
- `repositories`, `objectives`, `workers` sections を追加。
- Objectives section は `/api/objectives` を読み、title/state と empty/error states を section-local に表示。
- Workers section は `/api/workers` を読み、Worker label/state/status/role を表示し、Pod を primary UI naming として露出しない。
- Repository section は future Repository API に繋げやすい placeholder seam として実装。
- Host/Worker API/UI merge 後の `+page.svelte` conflict を解消し、main Host/Worker content と sidebar skeleton を両方維持。
- Backend/API authority, SSR, mutation/business logic は追加していない。
統合・検証:
- Merge commit: `613f4126 merge: workspace sidebar navigation`
- Implementation commits: `d3b8bdfd`, `4ab696b4`
- Reviewer final verdict: approve
- Validation passed: `git diff --check HEAD^1..HEAD`, `deno task check`, `deno task build`, `cargo test -p yoi-workspace-server`, `cargo run -p yoi -- ticket doctor`, and `nix build .#yoi --no-link`
範囲外:
- Settings page, Repository CRUD/API, Objective edit/detail UI, Worker start/stop/attach controls, drag/drop/collapsible tree, auth, multi-workspace switcher は実装していない。
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:01:46Z -->
## Implementation report
Post-close cleanup completed。
- Stopped child Pods and reclaimed scope:
- `yoi-coder-00001KVNG9B9Z`
- `yoi-reviewer-00001KVNG9B9Z-r1`
- Removed ignored frontend validation artifacts from child worktree before worktree removal:
- `web/workspace/node_modules/`
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
- Removed implementation worktree:
- `/home/hare/Projects/yoi/.worktree/00001KVNG9B9Z-workspace-sidebar`
- Deleted implementation branch:
- `impl/00001KVNG9B9Z-workspace-sidebar`
- Orchestrator worktree remains clean on `orchestration` at `c29eba0c`
Root/original workspace was not used for merge/validation/cleanup operations。
Follow-up note:
- `00001KVNGJPRG` had been left queued behind this sidebar work due `do_not_parallelize`; this blocker is now cleared for re-routing on top of the settled sidebar/navigation structure。
---
@@ -0,0 +1,2 @@
{"id":"orch-plan-20260621-164056-1","ticket_id":"00001KVNGJPRG","kind":"do_not_parallelize","related_ticket":"00001KVNG9B9Z","note":"Repository/objective pages and sidebar navigation both modify the Workspace SPA navigation/layout surface, especially `web/workspace/src/routes/+page.svelte` and route/component structure. Start this Ticket after `00001KVNG9B9Z` lands or after its implementation diff is known enough to route a non-conflicting continuation.","author":"yoi-orchestrator","at":"2026-06-21T16:40:56Z"}
{"id":"orch-plan-20260621-170253-2","ticket_id":"00001KVNGJPRG","kind":"accepted_plan","accepted_plan":{"summary":"Add read-only current-workspace Repository APIs/pages with bounded Git summary/log and Ticket Kanban, plus Objective list page and sidebar links, preserving filesystem Ticket/Objective authority and static SPA boundaries.","branch":"impl/00001KVNGJPRG-repository-objective-pages","worktree":"/home/hare/Projects/yoi/.worktree/00001KVNGJPRG-repository-objective-pages","role_plan":"Orchestrator creates a dedicated child worktree from current sidebar-integrated `orchestration` and spawns a narrow-scope Coder. Reviewer will be spawned read-only after Coder reports implementation commit(s). After approval, Orchestrator integrates into `orchestration`, validates workspace-server/frontend/Nix, records closure, and cleans only the child worktree/branch."},"author":"yoi-orchestrator","at":"2026-06-21T17:02:53Z"}
+2 -2
View File
@@ -1,8 +1,8 @@
---
title: 'Workspace web: repository and objective pages'
state: 'queued'
state: 'closed'
created_at: '2026-06-21T16:35:19Z'
updated_at: '2026-06-21T16:40:35Z'
updated_at: '2026-06-21T17:31:43Z'
assignee: null
queued_by: 'workspace-panel'
queued_at: '2026-06-21T16:40:35Z'
+30
View File
@@ -0,0 +1,30 @@
Workspace web に Repository / Objective pages を追加し、Orchestrator worktree の `orchestration` branch に統合した。
主な成果:
- Read-only Repository backend APIs を追加:
- `/api/repositories`
- `/api/repositories/local`
- `/api/repositories/local/log`
- `/api/repositories/local/tickets`
- Current workspace root を local Repository として扱う bounded repository summary を追加。
- Git repository では bounded branch/head/root/dirty/remote/recent log summary を返す。
- Non-Git workspace では `git.status = unavailable` と bounded diagnostics に degrade。
- Git log summary は recent commit hash/subject/author/timestamp に限定し、diff/patch/file content/blame/config は読まない。
- Remote URL summary は URL-scheme userinfo を redact。
- Read-only Ticket Kanban を Ticket state ごとに grouping し、workspace-local Ticket fallback diagnostic を含めた。
- Objective list summaries を filesystem Objective records から追加。
- Static SPA に hash-navigation Repository / Objectives pages を追加。
- Sidebar Repository/Objectives links を新 pages に接続。
- Repository page に summary, Git summary/log, diagnostics, read-only Ticket Kanban を表示。
- Objective page に title/state/updated_at/summary と detail placeholder links を表示。
- Ticket / Objective canonical authority remains filesystem read-through records; mutation API / DB canonical migration は追加していない。
統合・検証:
- Merge commit: `7ee702b1 merge: repository objective pages`
- Implementation commit: `ceb1ee3b feat: add repository objective pages`
- Reviewer final verdict: approve
- Validation passed: `cargo fmt --check`, `git diff --check HEAD^1..HEAD`, `cargo test -p yoi-workspace-server`, `cargo check -p yoi-workspace-server`, `deno task check`, `deno task build`, `cargo run -p yoi -- ticket doctor`, and `nix build .#yoi --no-link`
範囲外 / follow-up notes:
- Repository CRUD/API, Objective edit/detail mutation, full Git browser/diff/file views, drag/drop Kanban, and write APIs were not implemented。
- Reviewer noted possible follow-ups: keep `#/objectives` sidebar link visible even on objective empty/error states, and further tighten remote URL sanitization for query-param or SCP-like token forms if needed。
+381
View File
@@ -30,4 +30,385 @@ 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。
---
<!-- event: decision author: yoi-orchestrator at: 2026-06-21T17:02:35Z -->
## Decision
Routing decision: `implementation_ready_after_sidebar_landed`
Reason:
- This Ticket was previously left queued due `do_not_parallelize` with `00001KVNG9B9Z` because repository/objective pages and sidebar navigation both touched the Workspace SPA navigation/layout surface。
- `00001KVNG9B9Z` is now `closed` and integrated (`613f4126 merge: workspace sidebar navigation`), so the sequencing blocker is cleared。
- Related bootstrap Ticket `00001KVMFFYVX` is also closed/integrated。
- Ticket body has concrete backend/API/frontend requirements, acceptance criteria, and validation requirements。
- Relations are `related` only; no blocking relation remains。
- Orchestrator worktree is clean on `orchestration` at `eb2e5907`; target worktree / branch is not present。
IntentPacket:
Intent:
- Add Repository and Objective pages reachable from the Workspace sidebar, using filesystem read-through Ticket/Objective authority and bounded read-only Repository/Git summaries。
Binding decisions / invariants:
- Ticket / Objective canonical authority remains existing filesystem records; do not migrate canonical writes to SQLite or add mutation APIs。
- Repository page is read-only initial slice for current workspace root as local Repository。
- Git info and log summaries must be bounded; do not expose full diffs, file contents, blame, or secret-like config。
- Repository Ticket Kanban is read-only and grouped by Ticket state; no drag/drop or state mutation。
- Objective list uses existing filesystem read-through `/api/objectives` data, with detail links/placeholders as practical。
- Frontend remains static SPA; no SSR/business authority。
- Sidebar links should use the now-landed navigation/component structure。
- API failures, non-Git repo, and empty state must be section-local。
Requirements / acceptance criteria:
- Add read-only Repository list/detail/summary API or minimal workspace repository summary。
- For Git repository: bounded branch/head/root/dirty/remote/recent log summary。
- For non-Git repository: safe `kind = local` / git unavailable diagnostic。
- Add bounded Git log summary API returning recent N commit hash/subject/author/timestamp only。
- Add Repository Ticket Kanban read model grouped by Ticket state, with safe fallback to workspace-local tickets when target metadata is absent。
- Add Repository page showing summary, Git summary/log, and Ticket Kanban。
- Add Objective list page showing objective title/state/updated_at/summary and detail link/placeholder if feasible。
- Sidebar repositories/objectives links navigate to these pages。
- Deno check/build and backend validation pass。
Implementation latitude:
- Use SvelteKit static SPA client-side routing/hash/router approach or simple stateful navigation if current skeleton lacks route generation; keep static output compatible。
- Backend API names may be pragmatic, e.g. `/api/repositories`, `/api/repositories/{id}`, `/api/repositories/{id}/log`, `/api/repositories/{id}/tickets`
- Current workspace root can be the only repository for this slice。
- Ticket Kanban fallback can group all workspace tickets by state with diagnostic that target metadata is not yet available。
- Keep UI simple and avoid broad design-system churn。
Escalate if:
- Implementing repository APIs would require reading file contents/diffs or unsafe Git config/secrets。
- Objective detail requires mutation or schema changes。
- Static SPA route approach conflicts with SvelteKit adapter/static constraints。
- Sidebar/navigation architecture from `00001KVNG9B9Z` cannot support pages without broad rewrite。
Validation plan:
- `cargo fmt --check`
- `cargo test -p yoi-workspace-server`
- `cargo check -p yoi-workspace-server`
- `cd web/workspace && deno task check && deno task build`
- `git diff --check`
- `cargo run -p yoi -- ticket doctor`
- `nix build .#yoi --no-link`
---
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-21T17:02:42Z from: queued to: inprogress reason: sidebar_dependency_landed_unblocked_implementation field: state -->
## State changed
Previously recorded `do_not_parallelize` sequencing reason is cleared because sidebar navigation Ticket `00001KVNG9B9Z` is closed and integrated. Human queue authorization remains applicable, and the Ticket has concrete implementation requirements, so Orchestrator accepts implementation.
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:03:39Z -->
## Implementation report
Implementation start report:
- Created child implementation worktree:
- `/home/hare/Projects/yoi/.worktree/00001KVNGJPRG-repository-objective-pages`
- Created branch:
- `impl/00001KVNGJPRG-repository-objective-pages`
- Base commit:
- `0f7e78c1 ticket: accept repository objective pages`
- Confirmed tracked Ticket project records are visible in the child worktree。
- Confirmed `.yoi/memory` has no tracked/untracked entries in the child worktree check。
- Spawned sibling Coder Pod:
- `yoi-coder-00001KVNGJPRG`
- Coder scope:
- read: `/home/hare/Projects/yoi`
- write: `/home/hare/Projects/yoi/.worktree/00001KVNGJPRG-repository-objective-pages`
Next action:
- Wait for Coder implementation report, then spawn Reviewer read-only for the implementation diff。
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:23:16Z -->
## Implementation report
Coder implementation report received from `yoi-coder-00001KVNGJPRG`.
Implementation commit:
- `ceb1ee3b feat: add repository objective pages`
Changed areas:
- Backend repository read APIs:
- Added `crates/workspace-server/src/repositories.rs`
- Added bounded local repository/Git summary and log reader。
- Added endpoints:
- `/api/repositories`
- `/api/repositories/local`
- `/api/repositories/local/log`
- `/api/repositories/local/tickets`
- Added read-only Ticket Kanban grouping by Ticket state with workspace-local fallback diagnostic。
- Added Objective list summaries from existing filesystem Objective records。
- Frontend Workspace SPA:
- Added hash-navigation pages for Repository and Objectives。
- Wired sidebar Repository/Objectives links to the new pages。
- Added Repository summary, Git summary/log, diagnostics, and read-only Ticket Kanban UI。
- Added Objective list with title/state/updated_at/summary and detail placeholder links。
- Tests:
- Extended workspace-server API tests for repository endpoints and Objective summary。
- Added Git URL sanitization/log parsing unit tests。
Coder validation reported:
- `cargo fmt --all`: passed
- `cargo fmt --check`: passed
- `cargo test -p yoi-workspace-server`: passed
- `cargo check -p yoi-workspace-server`: passed
- `cd web/workspace && deno task check`: passed
- `cd web/workspace && deno task build`: passed
- `git diff --check`: passed
- `cargo run -p yoi -- ticket doctor`: passed
- `nix build .#yoi --no-link`: passed after staging newly added `repositories.rs` so Git-backed flake source filtering included it。
Generated artifact cleanup:
- Coder removed `web/workspace/build` and `web/workspace/.svelte-kit`
- Orchestrator additionally removed ignored `web/workspace/node_modules/` before Reviewer routing。
Orchestrator evidence checked:
- Worktree clean on `impl/00001KVNGJPRG-repository-objective-pages` at `ceb1ee3b`
- Diff `0f7e78c1..HEAD` touches 8 expected backend/frontend files, about 1228 insertions / 142 deletions。
- `git diff --check 0f7e78c1..HEAD`: passed。
- No generated frontend artifacts remain in child worktree status。
Next action:
- Route to read-only Reviewer Pod for acceptance review。
---
<!-- event: comment author: yoi-orchestrator at: 2026-06-21T17:23:58Z -->
## Comment
Review routing:
Spawned read-only Reviewer Pod:
- `yoi-reviewer-00001KVNGJPRG-r1`
Review target:
- Worktree: `/home/hare/Projects/yoi/.worktree/00001KVNGJPRG-repository-objective-pages`
- Branch: `impl/00001KVNGJPRG-repository-objective-pages`
- Baseline: `0f7e78c1`
- Implementation commit: `ceb1ee3b feat: add repository objective pages`
- Diff: `0f7e78c1..ceb1ee3b`
Reviewer scope:
- read-only `/home/hare/Projects/yoi`
Reviewer focus:
- Read-only bounded Repository APIs and Git summaries。
- No diffs/file contents/blame/secret-like config exposure。
- Sanitized remote URL summary。
- Non-Git degradation。
- Read-only Ticket Kanban grouped by state。
- Objective list uses filesystem read-through records。
- Static SPA navigation/pages and section-local error handling。
- Generated artifact / Nix source filtering hygiene。
Orchestrator will wait for reviewer verdict before integration。
---
<!-- event: review author: yoi-reviewer-00001KVNGJPRG-r1 at: 2026-06-21T17:30:09Z status: approve -->
## Review: approve
Verdict: `approve`
確認範囲:
- Ticket authority:
- `.yoi/tickets/00001KVNGJPRG/item.md`
- `.yoi/tickets/00001KVNGJPRG/thread.md`
- Diff `0f7e78c1..ceb1ee3b`:
- `crates/workspace-server/src/lib.rs`
- `crates/workspace-server/src/records.rs`
- `crates/workspace-server/src/repositories.rs`
- `crates/workspace-server/src/server.rs`
- `web/workspace/src/lib/workspace-sidebar/ObjectivesNavSection.svelte`
- `web/workspace/src/lib/workspace-sidebar/RepositoriesNavSection.svelte`
- `web/workspace/src/lib/workspace-sidebar/types.ts`
- `web/workspace/src/routes/+page.svelte`
Blocking issues:
- None found。
Acceptance verification:
- Repository APIs are read-only `GET` routes only。
- Git commands use fixed argument vectors through `Command::new("git").arg("-C").arg(workspace_root).args(args)`; no shell interpolation。
- Git summary/log is bounded:
- log limit clamps to `1..=50`
- command output capped at `4096`
- fields capped at `240`, hash at `40`
- no diff/patch/file content/blame/config commands are used。
- Remote URL summary strips URL-scheme userinfo and marks `redacted`
- Non-Git workspaces return `git.status = "unavailable"` plus diagnostics rather than failing the Repository page model。
- Ticket Kanban reads filesystem Ticket summaries and groups by state; no Ticket mutation route/UI was added。
- Objective list continues to use filesystem read-through `/api/objectives`; no Objective mutation/API authority added。
- Frontend remains static SPA/hash navigation; no SSR/business authority introduced。
- Nix build succeeds with the new Rust source file。
Non-blocking concerns:
- `ObjectivesNavSection.svelte` only shows the “All objectives” sidebar link when objectives are successfully loaded and non-empty. In an empty/error state, the page is still reachable from hero links, but the sidebar itself does not provide a stable top-level Objectives link. Consider keeping `#/objectives` visible in all non-loading states in a follow-up。
- Remote sanitization removes URL-scheme userinfo, but does not attempt query-param or SCP-like token redaction. Acceptable for the initial bounded summary, but worth tightening if remote URLs may include local secret-bearing config。
Reviewer validation:
- `cargo fmt --check`: passed
- `git diff --check 0f7e78c1..HEAD`: passed
- `cargo test -p yoi-workspace-server`: passed (`8 passed`)
- `cargo check -p yoi-workspace-server`: passed
- `cd web/workspace && deno task check`: passed (`svelte-check found 0 errors and 0 warnings`)
- `cd web/workspace && deno task build`: passed
- `cargo run -p yoi -- ticket doctor`: passed (`doctor: ok`)
- `nix build .#yoi --no-link`: passed
Generated artifacts:
- Reviewer did not clean generated ignored artifacts after validation。
- Ignored generated artifacts present:
- `target/`
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
- `web/workspace/node_modules/`
- No untracked non-ignored files。
Worktree status:
- Clean tracked/non-ignored state on `impl/00001KVNGJPRG-repository-objective-pages` at `ceb1ee3b`
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:30:51Z -->
## Implementation report
Reviewer r1 approvalを受けて、実装ブランチを Orchestrator worktree の `orchestration` branch に統合した。
統合:
- Merge commit: `7ee702b1 merge: repository objective pages`
- Merged branch: `impl/00001KVNGJPRG-repository-objective-pages`
- Implementation commit:
- `ceb1ee3b feat: add repository objective pages`
Orchestrator worktree validation:
- `cargo fmt --check`: passed
- `git diff --check HEAD^1..HEAD`: passed
- `cargo test -p yoi-workspace-server`: passed (`8 passed`)
- `cargo check -p yoi-workspace-server`: passed
- `cd web/workspace && rm -rf node_modules .svelte-kit build && deno task check`: passed (`svelte-check found 0 errors and 0 warnings`)
- `cd web/workspace && deno task build`: passed
- `cargo run -p yoi -- ticket doctor`: passed (`doctor: ok`)
- `nix build .#yoi --no-link`: passed
Validation generated ignored frontend artifacts in Orchestrator worktree:
- `web/workspace/node_modules/`
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
These were removed after validation. Final Orchestrator worktree status after validation cleanup is clean on `orchestration` at `7ee702b1`
---
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-21T17:30:58Z from: inprogress to: done reason: implementation_merged_and_validated field: state -->
## State changed
Reviewer approval、Orchestrator worktree への統合、workspace-server tests/check、Deno check/build、Ticket doctor、Nix build が完了したため `done` に遷移する。
---
<!-- event: state_changed author: hare at: 2026-06-21T17:31:14Z from: done to: closed reason: closed field: state -->
## State changed
Ticket を closed にしました。
---
<!-- event: close author: hare at: 2026-06-21T17:31:14Z status: closed -->
## 完了
Workspace web に Repository / Objective pages を追加し、Orchestrator worktree の `orchestration` branch に統合した。
主な成果:
- Read-only Repository backend APIs を追加:
- `/api/repositories`
- `/api/repositories/local`
- `/api/repositories/local/log`
- `/api/repositories/local/tickets`
- Current workspace root を local Repository として扱う bounded repository summary を追加。
- Git repository では bounded branch/head/root/dirty/remote/recent log summary を返す。
- Non-Git workspace では `git.status = unavailable` と bounded diagnostics に degrade。
- Git log summary は recent commit hash/subject/author/timestamp に限定し、diff/patch/file content/blame/config は読まない。
- Remote URL summary は URL-scheme userinfo を redact。
- Read-only Ticket Kanban を Ticket state ごとに grouping し、workspace-local Ticket fallback diagnostic を含めた。
- Objective list summaries を filesystem Objective records から追加。
- Static SPA に hash-navigation Repository / Objectives pages を追加。
- Sidebar Repository/Objectives links を新 pages に接続。
- Repository page に summary, Git summary/log, diagnostics, read-only Ticket Kanban を表示。
- Objective page に title/state/updated_at/summary と detail placeholder links を表示。
- Ticket / Objective canonical authority remains filesystem read-through records; mutation API / DB canonical migration は追加していない。
統合・検証:
- Merge commit: `7ee702b1 merge: repository objective pages`
- Implementation commit: `ceb1ee3b feat: add repository objective pages`
- Reviewer final verdict: approve
- Validation passed: `cargo fmt --check`, `git diff --check HEAD^1..HEAD`, `cargo test -p yoi-workspace-server`, `cargo check -p yoi-workspace-server`, `deno task check`, `deno task build`, `cargo run -p yoi -- ticket doctor`, and `nix build .#yoi --no-link`
範囲外 / follow-up notes:
- Repository CRUD/API, Objective edit/detail mutation, full Git browser/diff/file views, drag/drop Kanban, and write APIs were not implemented。
- Reviewer noted possible follow-ups: keep `#/objectives` sidebar link visible even on objective empty/error states, and further tighten remote URL sanitization for query-param or SCP-like token forms if needed。
---
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-21T17:31:43Z -->
## Implementation report
Post-close cleanup completed。
- Stopped child Pods and reclaimed scope:
- `yoi-coder-00001KVNGJPRG`
- `yoi-reviewer-00001KVNGJPRG-r1`
- Removed ignored frontend validation artifacts from child worktree before worktree removal:
- `web/workspace/node_modules/`
- `web/workspace/.svelte-kit/`
- `web/workspace/build/`
- Removed implementation worktree:
- `/home/hare/Projects/yoi/.worktree/00001KVNGJPRG-repository-objective-pages`
- Deleted implementation branch:
- `impl/00001KVNGJPRG-repository-objective-pages`
- Orchestrator worktree remains clean on `orchestration` at `4b1f1e59`
Root/original workspace was not used for merge/validation/cleanup operations。
---