ticket: close return planning policy

.yoi/tickets/closed/20260608-071722-orchestrator-return-to-planning-context-policy/item.md

@@ -2,13 +2,13 @@
 id: '20260608-071722-orchestrator-return-to-planning-context-policy'
 slug: 'orchestrator-return-to-planning-context-policy'
 title: 'Require project context before Orchestrator returns Tickets to planning'
-status: 'open'
+status: 'closed'
 kind: 'task'
 priority: 'P1'
 labels: ['ticket', 'orchestrator', 'planning', 'workflow', 'prompt']
-workflow_state: 'inprogress'
+workflow_state: 'done'
 created_at: '2026-06-08T07:17:22Z'
-updated_at: '2026-06-09T00:24:31Z'
+updated_at: '2026-06-09T01:18:52Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-09T00:04:21Z'

.yoi/tickets/closed/20260608-071722-orchestrator-return-to-planning-context-policy/resolution.md

@@ -0,0 +1,21 @@
+Implemented, reviewed, merged, and validated.
+
+Summary:
+- Strengthened Orchestrator routing guidance so `ready` / `queued` Tickets are returned to `planning` only when a concrete missing decision/information remains after bounded project-context checks.
+- Clarified risk flags, risky domains, and authority-adjacent work as context lookup / reviewer-focus / escalation signals rather than automatic stop gates.
+- Added risky-but-specified guidance and an `allow-spawnpod-child-workspace-cwd`-style example for proceeding with reviewer focus when work is specified.
+- Aligned `ticket-preflight-workflow`, `multi-agent-workflow`, and work-item docs with the same policy.
+- Preserved workflow_state semantics and did not reintroduce preflight/readiness as a separate state or lane.
+
+Implementation:
+- Coder commit: `8576615 workflow: tighten orchestrator planning return policy`
+- Reviewer approved with no blocking findings.
+- Merge commit: `5af58b5 merge: tighten orchestrator planning return policy`
+
+Validation after merge:
+- `cargo fmt --check`
+- `git diff --check`
+- `cargo run -q -p yoi -- ticket doctor`
+- `nix build .#yoi`
+
+`cargo check --workspace` was intentionally omitted because the merged implementation is workflow/docs text only and no Rust code/tests changed; Nix build covered resource/package integrity.

.yoi/tickets/closed/20260608-071722-orchestrator-return-to-planning-context-policy/thread.md

@@ -256,3 +256,40 @@ Residual risks / notes:
 - Final merge/close/cleanup is intentionally not performed here without explicit merge approval.
 
 ---
+
+<!-- event: state_changed author: hare at: 2026-06-09T01:18:52Z from: inprogress to: done reason: closed field: workflow_state -->
+
+## State changed
+
+Ticket closed; workflow_state を done に設定しました。
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-09T01:18:52Z status: closed -->
+
+## 完了
+
+Implemented, reviewed, merged, and validated.
+
+Summary:
+- Strengthened Orchestrator routing guidance so `ready` / `queued` Tickets are returned to `planning` only when a concrete missing decision/information remains after bounded project-context checks.
+- Clarified risk flags, risky domains, and authority-adjacent work as context lookup / reviewer-focus / escalation signals rather than automatic stop gates.
+- Added risky-but-specified guidance and an `allow-spawnpod-child-workspace-cwd`-style example for proceeding with reviewer focus when work is specified.
+- Aligned `ticket-preflight-workflow`, `multi-agent-workflow`, and work-item docs with the same policy.
+- Preserved workflow_state semantics and did not reintroduce preflight/readiness as a separate state or lane.
+
+Implementation:
+- Coder commit: `8576615 workflow: tighten orchestrator planning return policy`
+- Reviewer approved with no blocking findings.
+- Merge commit: `5af58b5 merge: tighten orchestrator planning return policy`
+
+Validation after merge:
+- `cargo fmt --check`
+- `git diff --check`
+- `cargo run -q -p yoi -- ticket doctor`
+- `nix build .#yoi`
+
+`cargo check --workspace` was intentionally omitted because the merged implementation is workflow/docs text only and no Rust code/tests changed; Nix build covered resource/package integrity.
+
+---