ticket: accept profile launch policy scope

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

@@ -1,2 +1,3 @@
 {"id":"orch-plan-20260614-061023-1","ticket_id":"00001KV11DHGZ","kind":"conflicts_with","related_ticket":"00001KTZY8HK2","note":"This Ticket changes Profile concrete scope / launch policy surfaces and is likely to overlap with `00001KTZY8HK2` profile API/resource migration. Start `00001KTZY8HK2` first; re-evaluate after it merges or if explicit override is requested.","author":"orchestrator","at":"2026-06-14T06:10:23Z"}
 {"id":"orch-plan-20260614-061023-2","ticket_id":"00001KV11DHGZ","kind":"waiting_capacity_note","note":"Queued batch routing started independent Tickets `00001KTR81P9X`, `00001KTZY8HK2`, and `00001KV12W2RT`. This Ticket remains queued due to profile-surface conflict/migration ordering with `00001KTZY8HK2`, not because of missing requirements. Re-evaluate after profile extend removal branch is integrated.","author":"orchestrator","at":"2026-06-14T06:10:23Z"}
+{"id":"orch-plan-20260614-063525-3","ticket_id":"00001KV11DHGZ","kind":"accepted_plan","accepted_plan":{"summary":"Implement launch-policy-owned concrete scope/delegation authority: remove builtin Profile concrete scope dependency, construct fresh Orchestrator/Companion effective scopes in launch paths, preserve metadata snapshot restore, and ensure child delegation validation supports root read + worktree write only.","branch":"ticket-00001KV11DHGZ-profile-launch-policy-scope","worktree":"/home/hare/Projects/yoi/.worktree/profile-launch-policy-scope","role_plan":"Coder works on Profile schema/resource cleanup and launch policy scope construction in dedicated worktree; Reviewer focuses on authority boundaries, restore snapshot preservation, child delegation validation, and no regression of normal Companion launch scope."},"author":"orchestrator","at":"2026-06-14T06:35:25Z"}

.yoi/tickets/00001KV11DHGZ/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'Profile から concrete scope を外して launch policy で付与する'
-state: 'queued'
+state: 'inprogress'
 created_at: '2026-06-13T17:45:32Z'
-updated_at: '2026-06-14T06:10:23Z'
+updated_at: '2026-06-14T06:35:44Z'
 assignee: null
 readiness: 'implementation_ready'
 risk_flags: ['scope', 'delegation-scope', 'profiles', 'launch-policy', 'orchestrator', 'spawnpod', 'restore']

.yoi/tickets/00001KV11DHGZ/thread.md

@@ -44,3 +44,42 @@ Next action:
 - Re-evaluate after `00001KTZY8HK2` is merged/validated, or if human explicitly authorizes parallel work despite conflict risk.
 
 ---
+
+<!-- event: decision author: orchestrator at: 2026-06-14T06:35:25Z -->
+
+## Decision
+
+Routing decision: implementation_ready
+
+Reason:
+- The previous conflict/wait on `00001KTZY8HK2` is resolved: profile extend removal has been reviewed, merged, validated, and marked done.
+- Ticket remains queued, has implementation-ready requirements/acceptance criteria, and relation records are non-blocking `related` links only.
+- Risk flags are scope/delegation/profile/launch/restore, but binding invariants and acceptance tests are concrete.
+
+Evidence checked:
+- Ticket body/thread/relations/orchestration-plan records.
+- Completed `00001KTZY8HK2` status and validation.
+- Orchestrator worktree clean state.
+
+IntentPacket:
+- Move concrete filesystem `scope` / `delegation_scope` out of reusable Profiles and into launch policy/effective metadata construction. Preserve restore snapshot authority and explicit child delegation behavior.
+
+Binding decisions / invariants:
+- Profiles own reusable behavior/model/prompt/feature policy, not concrete runtime authority.
+- Fresh Orchestrator launch effective authority: direct read original workspace; delegation read original workspace + write original workspace `.worktree`; no root workspace write delegation.
+- Normal Companion/TUI launch still gets expected workspace write direct scope from launch policy.
+- SpawnPod child direct scope is explicit delegated child scope, not inherited/profile scope.
+- Restore preserves metadata snapshot and does not reapply current profile/default launch authority over saved scope.
+
+Validation:
+- focused scope/profile/client/pod/spawn/restore tests, `cargo build -p yoi`, `cargo fmt --check`, `git diff --check`; `nix build .#yoi` if packaging/resource changes warrant or feasible.
+
+---
+
+<!-- event: state_changed author: orchestrator at: 2026-06-14T06:35:44Z from: queued to: inprogress reason: orchestrator_acceptance_after_profile_conflict_resolved field: state -->
+
+## State changed
+
+Profile extend removal prerequisite/conflict has been resolved and merged. Ticket evidence, related records, orchestration plan, and clean workspace state were checked. No blockers remain; implementation can proceed in a dedicated child worktree.
+
+---