From 33467911ca18dfd2c6d74943b43d260395d33f87 Mon Sep 17 00:00:00 2001
From: Hare <kei.hiracchi.0928@gmail.com>
Date: Mon, 8 Jun 2026 22:15:44 +0900
Subject: [PATCH] ticket: record composer history readiness

---
 .../item.md                                      |  4 ++--
 .../thread.md                                    | 16 ++++++++++++++++
 2 files changed, 18 insertions(+), 2 deletions(-)

diff --git a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md
index a4d91f77..888fdabf 100644
--- a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md
+++ b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/item.md
@@ -6,9 +6,9 @@ status: open
 kind: task
 priority: P2
 labels: [tui, composer, history, persistence]
-workflow_state: planning
+workflow_state: 'ready'
 created_at: 2026-06-01T02:11:04Z
-updated_at: 2026-06-05T23:01:38Z
+updated_at: '2026-06-08T13:14:53Z'
 assignee: null
 ---
 
diff --git a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md
index 50f8e3f0..689f0731 100644
--- a/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md
+++ b/.yoi/tickets/open/20260601-021104-tui-composer-history-persistence/thread.md
@@ -19,4 +19,20 @@ Updated based on user direction:
 - keep typed `Segment` storage, non-destructive recall semantics, and no Pod/session transcript mutation.
 
 
+---
+
+<!-- event: intake_summary author: intake at: 2026-06-08T13:14:53Z -->
+
+## Intake summary
+
+既存 Ticket を確認し、同目的の open Ticket は他にないことを確認した。要件は、TUI composer の Up/Down recall 履歴を user data dir 配下に workspace-scoped で永続化し、workspace `./.yoi/`、Pod protocol、transcript、Worker/session history、model context には影響させないこと。保存対象は typed `Segment` vector、non-blank、連続重複抑止、workspace ごと最大 30 件程度。破損ファイルは startup を致命的に壊さず fallback する。受け入れ基準と validation は Ticket 本文に十分記録済みで、Orchestrator が routing 可能なため ready とする。
+
+---
+
+<!-- event: state_changed author: intake at: 2026-06-08T13:14:53Z from: planning to: ready reason: intake_ready field: workflow_state -->
+
+## State changed
+
+Intake 確認により、既存 Ticket は実装 routing 可能な状態です。未解決の blocking open question はありません。主な reviewer focus は user-data persistence 境界、private/secret 混入前提の非露出、workspace 分離、既存 TUI recall semantics の回帰防止です。
+
 ---