ticket: accept profile launch policy scope

2026-06-14 15:35:56 +09:00
parent 69fc3675f0
commit cdb12af997
3 changed files with 42 additions and 2 deletions
@@ -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.
+
+---