ticket: record routing progress

.yoi/tickets/00001KSKBPSJG/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"id":"orch-plan-20260610-090202-1","ticket_id":"00001KSKBPSJG","kind":"accepted_plan","accepted_plan":{"summary":"Implement the model setup wizard as an explicit one-shot CLI path, not normal Pod startup: add `yoi setup-model` that launches a setup TUI. The wizard should select a bundled model/provider entry, optionally accept an auth hint/reference when the provider requires one, and persist a user default Profile by updating the user Profile registry under the normal config root (`profiles.toml` plus a generated user Profile Lua file such as `profiles/default.lua`). It must not write workspace `.yoi`, session history, Ticket files, runtime/local/secret-like files, or start/attach a Pod during setup. Existing normal launch semantics remain unchanged except that subsequent default startup can use the persisted user default Profile.","branch":"tui-model-setup-wizard","worktree":"/home/hare/Projects/yoi/.worktree/tui-model-setup-wizard","role_plan":"Coder implements in `.worktree/tui-model-setup-wizard` with write scope limited to the child worktree. Orchestrator keeps Ticket/progress records in the main workspace. Reviewer will be delegated after coder report."},"author":"orchestrator","at":"2026-06-10T09:02:02Z"}

.yoi/tickets/00001KSKBPSJG/item.md

@@ -2,7 +2,7 @@
 title: "TUI: ユーザーマニフェストのモデル設定 wizard"
 state: 'inprogress'
 created_at: "2026-05-27T00:00:18Z"
-updated_at: '2026-06-10T07:59:32Z'
+updated_at: '2026-06-10T09:02:02Z'
 queued_by: 'yoi ticket'
 queued_at: '2026-06-10T07:59:32Z'
 ---

.yoi/tickets/00001KSKBPSJG/thread.md

@@ -104,4 +104,46 @@ State changed to `inprogress`.
 Accepting implementation after workspace inspection. Expected overlap with prompt-resource cleanup is low, so route in parallel in a dedicated worktree.
 
 
+---
+
+<!-- event: plan author: orchestrator at: 2026-06-10T09:02:02Z -->
+
+## Plan
+
+Routing decision: implementation_ready
+
+Reason:
+- Ticket is already `inprogress`; relation query and orchestration-plan query show no blockers.
+- Existing thread marked this as needing a small preflight. Bounded code/context check resolved the implementation-shaping decisions without needing another planning round.
+
+Evidence checked:
+- Ticket body/thread/artifacts for `00001KSKBPSJG`.
+- Relation records: none.
+- Orchestration plan records: none before this routing pass.
+- Current worktree/branch state: `.worktree/tui-model-setup-wizard` exists and has no implementation commit yet.
+- Current CLI surface in `crates/yoi/src/main.rs` includes top-level `panel`, `keys`, `pod`, `ticket`, `objective`, `session`, `memory lint`; setup is not yet present.
+- Profile/config surface in `crates/manifest/src/paths.rs` and `crates/manifest/src/profile.rs`; active reusable Profiles are Lua-first with user registry/config under the normal config root.
+- Provider/model catalog resources under `resources/providers` and `resources/models`.
+
+Binding decisions / invariants:
+- Add an explicit one-shot setup entry point `yoi setup-model`; it must not run normal Pod startup, create sessions, attach sockets, or spawn Pods while configuring.
+- Persist the result as a user default Profile through normal Profile mechanisms: user `profiles.toml` plus a generated user Profile Lua file (for example `profiles/default.lua`) under the normal config root. Do not write workspace `.yoi`, Ticket records, session history, runtime/local/secret-like files, or project records from the setup wizard.
+- Do not introduce legacy manifest authority or new environment-variable configuration surfaces.
+- Keep existing startup/profile semantics intact; the setup wizard only creates/updates config that normal startup already knows how to consume.
+- If provider credential handling needs more than selecting/recording an existing auth hint/ref, escalate rather than inventing a new secret store flow.
+
+Implementation latitude:
+- Exact TUI layout and internal state machine organization are up to coder, bounded by the one-shot setup and persistence invariants.
+- Coder may choose the generated profile name/path if it is deterministic, user-config scoped, and unambiguous from the default selector.
+- Coder may keep the catalog/model choice set modest and testable for the first implementation.
+
+Validation:
+- Focused CLI/parser and setup persistence tests.
+- Focused TUI/setup module tests where practical.
+- `cargo fmt --check` or `cargo fmt`, `git diff --check`, focused cargo tests, and broader `cargo check`/`nix build .#yoi` before merge because this touches CLI/TUI/config/package source surfaces.
+
+Escalate if:
+- The implementation requires changing Profile registry semantics, secret-store behavior, normal Pod launch behavior, or workspace `.yoi` authority.
+- Credential entry/storage cannot be limited to an existing explicit auth reference/hint.
+
 ---

.yoi/tickets/00001KTR6D3C5/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"id":"orch-plan-20260610-083728-1","ticket_id":"00001KTR6D3C5","kind":"waiting_capacity_note","note":"Panel launch did not specify a target Ticket and instructed Orchestrator to wait for explicit follow-up before spawning role Pods. Queue acceptance was not recorded yet. Bounded check: Ticket body/thread show implementation_ready, relation query has no blockers, orchestration plan has no existing records, main workspace is clean, and active worktrees are prompt-resource-centralization plus tui-model-setup-wizard. Waiting reason: human gate/explicit target authorization.","author":"orchestrator","at":"2026-06-10T08:37:28Z"}

.yoi/tickets/00001KTR6D3C5/item.md

@@ -2,7 +2,7 @@
 title: 'Lua Profileに組み込みyoi APIとimport/extendを追加する'
 state: 'queued'
 created_at: '2026-06-10T07:19:31Z'
-updated_at: '2026-06-10T08:04:05Z'
+updated_at: '2026-06-10T08:37:28Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-10T08:04:05Z'

.yoi/tickets/00001KTR6YVDB/item.md

@@ -2,7 +2,7 @@
 title: 'LLM向けプロンプト直書きを廃止してresources/promptsへ集約する'
 state: 'inprogress'
 created_at: '2026-06-10T07:29:13Z'
-updated_at: '2026-06-10T08:11:58Z'
+updated_at: '2026-06-10T09:06:45Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-10T07:49:23Z'

.yoi/tickets/00001KTR6YVDB/thread.md

@@ -56,4 +56,51 @@ Accepting implementation after workspace inspection. Expected overlap with TUI m
 Implemented directly in worktree .worktree/prompt-resource-centralization because Pod-management tools are not available in this API session.\n\nBranch/commit:\n- prompt-resource-centralization / 342d5cf refactor: move ticket role prompts to resources\n\nSummary:\n- Moved Ticket role launch guidance strings from crates/client/src/ticket_role.rs into resources/prompts/ticket_role/*.md.\n- Added workspace/user override lookup for ticket_role prompt fragments before falling back to embedded resources.\n- Kept Rust code responsible for runtime composition, bounded dynamic fields, and segment assembly.\n- Added regression coverage for workspace prompt override behavior.\n\nValidation:\n- cargo fmt\n- cargo test -p client ticket_role --lib\n- git diff --check\n- cargo check -p client\n\nPending:\n- External review/merge validation not yet performed.\n- TUI model setup wizard worktree exists but implementation has not started.
 
 
+---
+
+<!-- event: plan author: orchestrator at: 2026-06-10T09:00:04Z -->
+
+## Plan
+
+Routing update: review_needed
+
+Reason:
+- Implementation report exists for branch `prompt-resource-centralization` / commit `342d5cf8`, but independent review and merge validation are not yet recorded.
+
+Evidence checked:
+- Ticket body/thread/artifacts and relation/orchestration-plan records.
+- Worktree status for `.worktree/prompt-resource-centralization` is clean and branch has commit `342d5cf8` over `develop`.
+- Visible Pods showed no existing child reviewer.
+
+Next action:
+- Spawned branch-local reviewer Pod `reviewer-prompt-resource-centralization` with read-only scope over the worktree and this Ticket. Reviewer is asked for approve/request_changes, blockers, notes, and focused validation evidence.
+
+Boundary:
+- This is branch-local review evidence only; no main-branch Ticket approval, merge, close, or cleanup is recorded by this routing step.
+
+---
+
+<!-- event: review author: reviewer-prompt-resource-centralization at: 2026-06-10T09:06:45Z status: approve -->
+
+## Review: approve
+
+Branch-local review verdict: approve
+
+Evidence:
+- Reviewed branch diff from merge-base `76165b47d664cb02a79c16272fbb5f8377a693bb` against `develop`.
+- Verified production `crates/client/src/ticket_role.rs` no longer hardcodes the large LLM-facing Ticket role launch / intake handoff / orchestrator / coder / reviewer prompt prose; prompt fragments now live under `resources/prompts/ticket_role/*.md`.
+- Verified runtime values remain sectioned/bounded and resource lookup order is workspace `.yoi/prompts/ticket_role/*.md` -> user prompts dir -> builtin embedded resource.
+- Verified existing semantics and tests cover representative builtin prompt generation and workspace override behavior.
+
+Validation run by reviewer:
+- `cargo test -p client ticket_role --lib` passed.
+- `git diff --check $(git merge-base HEAD develop)..HEAD` passed.
+- `nix build .#yoi` passed.
+
+Non-blocking notes:
+- Dedicated user-level prompt override test could be added later, but workspace override exercises the same loader path sufficiently for this change.
+- Prompt text fragments remain in test assertions only; this is not production prompt hardcoding.
+
+This is branch-local review evidence; final main-branch approval/close still belongs to merge-completion.
+
 ---

.yoi/tickets/00001KTR83D6E/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"id":"orch-plan-20260610-083728-1","ticket_id":"00001KTR83D6E","kind":"waiting_capacity_note","note":"Panel launch did not specify a target Ticket and instructed Orchestrator to wait for explicit follow-up before spawning role Pods. Queue acceptance was not recorded yet. Bounded check: Ticket body/thread show implementation_ready, relation query has no blockers, orchestration plan has no existing records, main workspace is clean, and active worktrees are prompt-resource-centralization plus tui-model-setup-wizard. Waiting reason: human gate/explicit target authorization.","author":"orchestrator","at":"2026-06-10T08:37:28Z"}

.yoi/tickets/00001KTR83D6E/item.md

@@ -2,7 +2,7 @@
 title: 'Edit/Writeの同一ファイル変更をToolExecutionContextで直列化する'
 state: 'queued'
 created_at: '2026-06-10T07:49:10Z'
-updated_at: '2026-06-10T08:10:58Z'
+updated_at: '2026-06-10T08:37:28Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-10T08:10:58Z'