236 lines
12 KiB
Markdown
236 lines
12 KiB
Markdown
<!-- event: create author: "yoi ticket" at: 2026-06-25T11:45:17Z -->
|
|
|
|
## 作成
|
|
|
|
LocalTicketBackend によって作成されました。
|
|
|
|
---
|
|
|
|
<!-- event: intake_summary author: hare at: 2026-06-25T16:34:16Z -->
|
|
|
|
## Intake summary
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: "yoi ticket" at: 2026-06-25T16:34:16Z from: planning to: ready reason: cli_state field: state -->
|
|
|
|
## State changed
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: workspace-panel at: 2026-06-25T16:44:45Z from: ready to: queued reason: queued field: state -->
|
|
|
|
## State changed
|
|
|
|
Ticket を `workspace-panel` が queued にしました。
|
|
|
|
|
|
---
|
|
|
|
<!-- event: decision author: yoi-orchestrator at: 2026-06-25T16:45:24Z -->
|
|
|
|
## Decision
|
|
|
|
Routing decision: blocked_by_dependency_or_missing_authority
|
|
|
|
Reason:
|
|
- Dashboard Queue による routing 許可を受けて Ticket / relations / orchestration plan / queue state を確認した。
|
|
- 本 Ticket は `00001KVZSGT0Q` (`Backend RuntimeRegistryにembedded worker-runtimeを接続する`) に `depends_on` relation を持つ。
|
|
- `00001KVZSGT0Q` は現在 `queued` で、さらに `00001KVZKSV6C` / `00001KVZBCQH4` の依存 chain により blocked と判断済み。
|
|
- Backend internal Companion Runtime / Web Console MVP は Backend RuntimeRegistry 上の embedded worker-runtime connection を前提にするため、基盤確定前に開始しない。
|
|
|
|
Evidence checked:
|
|
- Ticket body: Backend internal Companion runtime、conversation/transcript model、Web API、Web Console UI、Runtime/LLM integration、Safety/authority、Non-goals。
|
|
- Relations: outgoing `depends_on -> 00001KVZSGT0Q`。
|
|
- Orchestration plan: blocker record `orch-plan-20260625-164513-1` を追加。
|
|
- Queue state: queued は本 Ticket を含む6件。inprogress は worker-runtime core `00001KVZBCQH4` 1件。
|
|
- Workspace state: core implementation is under reviewer Worker; dependent Backend Registry work is not accepted yet。
|
|
|
|
Next action:
|
|
- 本 Ticket は queued のまま待機。
|
|
- `00001KVZSGT0Q` が accepted/completed して Backend embedded runtime connection が使えるようになった後、再 routing する。
|
|
|
|
Escalate if:
|
|
- Companion MVP を `00001KVZSGT0Q` 完了前に独立 spike する human decision がある。
|
|
- Backend internal Runtime foundation の scope が Companion MVP requirements を満たさない。
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-25T20:23:10Z from: queued to: planning reason: web_console_stream_transport_decision_missing field: state -->
|
|
|
|
## State changed
|
|
|
|
ユーザー指摘により queued から planning に戻す。
|
|
|
|
Missing decision / information:
|
|
- 本 Ticket は Web Console MVP の conversation/transcript model で「request/response 完了後に transcript を返す」または「SSE / streaming endpoint」を実装時に選んでよいとしており、実質的に WS/SSE/polling/streaming の transport 方針を固定し得る。
|
|
- これは `00001KVZKSTJT` で決定すべき WebSocket/event-stream transport 設計点であり、未決定のまま queued に置くのは不適切。
|
|
|
|
Context checked:
|
|
- Ticket body: Web Console UI、Companion message API、assistant response 取得または stream、conversation/transcript projection、Safety/authority。
|
|
- Existing relation: `00001KVZSGT0Q` への dependency。
|
|
- Added relation: `00001KVZKSTJT` への `depends_on` を追加し、WS/SSE/polling transport decision が解決するまで本 Ticket を blocker 付き planning として扱う。
|
|
- `00001KVZKSTE2` は REST command server であり、SSE/WebSocket event stream server は Non-goal と明記されているため、この差し戻し対象ではない。
|
|
|
|
Why implementation latitude is insufficient:
|
|
- Web Console の response delivery を request/response、SSE、WebSocket、polling のどれに寄せるかは後続 API/UI/Backend runtime integration の binding decision であり、Coder の local tactic として固定すべきではない。
|
|
|
|
Next planning question/action:
|
|
- `00001KVZKSTJT` で WebSocket/event-stream transport の採否、Backend-owned client / Browser-facing projection / cursor semantics / busy/error behavior を決める。
|
|
- その決定に基づいて、本 Ticket の conversation/transcript model と Web API acceptance criteria を再同期してから ready/queued に戻す。
|
|
|
|
---
|
|
|
|
<!-- event: intake_summary author: hare at: 2026-06-25T20:30:38Z -->
|
|
|
|
## Intake summary
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: "yoi ticket" at: 2026-06-25T20:30:38Z from: planning to: ready reason: cli_state field: state -->
|
|
|
|
## State changed
|
|
|
|
Marked ready by `yoi ticket state`.
|
|
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: workspace-panel at: 2026-06-25T20:34:27Z from: ready to: queued reason: queued field: state -->
|
|
|
|
## State changed
|
|
|
|
Ticket を `workspace-panel` が queued にしました。
|
|
|
|
|
|
---
|
|
|
|
<!-- event: decision author: yoi-orchestrator at: 2026-06-25T20:36:54Z -->
|
|
|
|
## Decision
|
|
|
|
Routing decision: blocked_by_dependency_or_missing_authority
|
|
|
|
Reason:
|
|
- Dashboard Queue 後に Ticket / relations / workspace state を確認した。
|
|
- 本 Ticket は Web Console MVP であり、WebSocket/event-stream transport/proxy `00001KVZKSTJT` と Backend embedded Runtime connection `00001KVZSGT0Q` を前提にする。
|
|
- `00001KVZKSTJT` は queued/blocked、`00001KVZSGT0Q` も Backend Registry foundation chain 待ち。Web Console を先に始めると response delivery / stream semantics を UI/API 側で先取りして固定するため開始しない。
|
|
|
|
Evidence checked:
|
|
- Ticket body: Companion Runtime/Web Console MVP、message API、transcript/stream response choice、Safety/authority。
|
|
- Relations: `depends_on -> 00001KVZKSTJT` と `depends_on -> 00001KVZSGT0Q`。
|
|
- Orchestration plan: blocker record `orch-plan-20260625-203613-1` を追加。
|
|
|
|
Next action:
|
|
- 本 Ticket は queued のまま待機。
|
|
- `00001KVZKSTJT` と `00001KVZSGT0Q` が done になった後、Web Console MVP の acceptance criteria を再確認して routing する。
|
|
|
|
---
|
|
|
|
<!-- event: decision author: yoi-orchestrator at: 2026-06-26T07:41:53Z -->
|
|
|
|
## Decision
|
|
|
|
Routing decision: implementation_ready
|
|
|
|
Reason:
|
|
- Dependencies are done: `00001KVZSGT0Q` embedded Runtime connection、`00001KVZKSTJT` WebSocket observation proxy、`00001KVZQHPNY` config bundle sync。
|
|
- Current `inprogress` is 0. Web Console MVP can now build on stable Backend internal Runtime / Worker create / transcript / WS/proxy foundations.
|
|
- Ticket body has concrete backend API, Web UI, safety/authority, Non-goals, and validation requirements.
|
|
|
|
Evidence checked:
|
|
- Ticket body: Backend internal Companion runtime, conversation/transcript model, Web API, Web Console UI, Runtime/LLM integration, Safety/authority, acceptance criteria。
|
|
- Relations: depends_on `00001KVZSGT0Q` and `00001KVZKSTJT`, both done.
|
|
- Orchestration plan: accepted plan `orch-plan-20260626-074131-5` recorded.
|
|
- Workspace state: orchestration worktree clean; no spawned child Workers currently active.
|
|
|
|
IntentPacket:
|
|
|
|
Intent:
|
|
- Backend internal Runtime 上に toolsなし Companion Worker を作成・保持し、Web frontend から status/transcript/message send/response display ができる Console MVP を実装する。
|
|
|
|
Binding decisions / invariants:
|
|
- Companion v0 は workspace filesystem / shell / git / Ticket mutation authority を持たない。
|
|
- Browser は raw provider credential、socket path、session path、runtime file path、Runtime direct endpoint/token を扱わない。
|
|
- Backend API / WS/projection を authority とし、local session file / Pod socket を直接読まない。
|
|
- Prompt prose は Rust 直書きではなく `resources/prompts` など prompt resource boundary に置く。
|
|
- v0 は full TUI parity / tool call UI / file viewer / diff viewer / thinking block grouping / multi Worker attach を実装しない。
|
|
- Long-running request 中の追加 message は single-flight / busy reject でよい。
|
|
|
|
Requirements / acceptance criteria:
|
|
- Backend internal runtime 上に Companion Worker が存在し、runtime/worker API から確認できる。
|
|
- Web frontend から Companion status / transcript projection を取得できる。
|
|
- Web Console UI から user message を送信できる。
|
|
- Companion が LLM response を生成し、Web UI に表示される、または v0実装上の provider-less/mock boundary が明確で reviewer が確認できる。
|
|
- v0 Companion は filesystem / shell / git / Ticket mutation tools を持たない。
|
|
- Provider busy/error/timeout/cancelled が typed error/UI state で扱われる。
|
|
- Focused backend/frontend tests or manual validation notes are present.
|
|
|
|
Implementation latitude:
|
|
- Request/response completion vs existing WS/projection usageの具体方式は Coder が既存 foundation に合わせて選べる。ただし `00001KVZKSTJT` の Backend-owned observation/proxy境界を壊さない。
|
|
- v0 LLM/provider integration が重すぎる場合は、Backend internal Runtimeの現在能力内で最小 toolsなし conversational round-trip を成立させ、未実装 provider execution boundaryを明確に報告すること。
|
|
- UI route/layout/component naming は existing `web/workspace` style に合わせる。
|
|
|
|
Escalate if:
|
|
- Filesystem/shell/git/Ticket mutation authority が必要になる。
|
|
- Browser に Runtime/provider credentials や raw path を渡す必要が出る。
|
|
- Full TUI console parity or tool-call UI が必要になる。
|
|
- Existing worker-runtime cannot generate a real LLM response without broad worker/engine integration and acceptance criteria cannot be satisfied honestly.
|
|
|
|
Validation:
|
|
- `cargo fmt --all`
|
|
- `cargo test -p yoi-workspace-server`
|
|
- `cargo check -p yoi`
|
|
- `cd web/workspace && deno task check`
|
|
- `cd web/workspace && deno task build`
|
|
- `git diff --check`
|
|
- 可能なら `nix build .#yoi --no-link`
|
|
|
|
Critical risks / reviewer focus:
|
|
- Authority leakage to Browser or Companion Worker。
|
|
- Hidden context injection instead of normal conversation history。
|
|
- Prompt prose embedded in Rust instead of prompt resource。
|
|
- UI claiming live LLM behavior if implementation is actually mock/provider-less。
|
|
- Over-scoping into full TUI parity/tool UI。
|
|
|
|
---
|
|
|
|
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-26T07:42:06Z from: queued to: inprogress reason: routing_accepted_after_backend_runtime_foundation_done field: state -->
|
|
|
|
## State changed
|
|
|
|
Routing decision: implementation_ready。
|
|
|
|
Embedded Runtime connection、WebSocket observation proxy、Profile/config bundle sync は done。Ticket body / relations / workspace state / accepted plan を確認し、Backend internal Companion Web Console MVP は unblocked と判断した。accepted plan と IntentPacket は thread / orchestration plan に記録済み。
|
|
|
|
これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
|
|
|
|
---
|
|
|
|
<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-26T07:43:09Z -->
|
|
|
|
## Implementation report
|
|
|
|
Implementation kickoff:
|
|
|
|
- Worktree created: `/home/hare/Projects/yoi/.worktree/00001KVZ9JGK0-web-console-mvp`
|
|
- Branch: `work/00001KVZ9JGK0-web-console-mvp`
|
|
- Coder Worker spawned: `yoi-coder-00001KVZ9JGK0-web-console`
|
|
|
|
Scope notes:
|
|
- Coder has read access to the implementation worktree and non-recursive workspace root identity path needed by runtime startup.
|
|
- Coder write scope is limited to `crates/workspace-server/**`, `web/workspace/**`, `resources/prompts/**`, root `Cargo.toml`, `Cargo.lock`, and `package.nix` if dependency/package changes are needed.
|
|
- Coder is instructed not to modify Ticket records and not to operate in root/orchestration worktrees.
|
|
|
|
Queued capacity note:
|
|
- `00001KW04A8K6` remains queued while Web Console MVP is inprogress because both are UI/control-surface consumers of the new Runtime APIs; TUI migration should start after this branch is reviewed/merged/done.
|
|
|
|
---
|