ticket: record panel ticket updates

.yoi/tickets/20260607-213808-001/item.md

@@ -1,8 +1,8 @@
 ---
 title: "Remove bare letter shortcuts from workspace panel"
-state: "done"
+state: 'closed'
 created_at: "2026-06-07T21:38:08Z"
-updated_at: "2026-06-07T22:26:19Z"
+updated_at: '2026-06-09T10:20:49Z'
 queued_by: "workspace-panel"
 queued_at: "2026-06-07T22:04:20Z"
 ---

.yoi/tickets/20260607-213808-001/resolution.md

@@ -0,0 +1,3 @@
+Closed as completed.
+
+The workspace panel bare-letter shortcut issue was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; implementation details and review history remain in `thread.md`.

.yoi/tickets/20260607-213808-001/thread.md

@@ -348,3 +348,22 @@ Merge-completion cleanup completed:
 Final workspace status after cleanup/record commit was clean apart from being ahead of `origin/develop`.
 
 ---
+
+<!-- event: state_changed author: hare at: 2026-06-09T10:20:49Z from: done to: closed reason: closed field: state -->
+
+## State changed
+
+Ticket を closed にしました。
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-09T10:20:49Z status: closed -->
+
+## 完了
+
+Closed as completed.
+
+The workspace panel bare-letter shortcut issue was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; implementation details and review history remain in `thread.md`.
+
+---

.yoi/tickets/20260607-223233-001/item.md

@@ -1,8 +1,8 @@
 ---
 title: "Parse Ticket frontmatter as YAML"
-state: "done"
+state: 'closed'
 created_at: "2026-06-07T22:32:33Z"
-updated_at: "2026-06-07T23:38:32Z"
+updated_at: '2026-06-09T10:20:56Z'
 queued_by: "workspace-panel"
 queued_at: "2026-06-07T22:43:03Z"
 ---

.yoi/tickets/20260607-223233-001/resolution.md

@@ -0,0 +1,3 @@
+Closed as completed.
+
+The YAML frontmatter parsing work was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; implementation details, validation, and review history remain in `thread.md`.

.yoi/tickets/20260607-223233-001/thread.md

@@ -465,3 +465,22 @@ Merge-completion cleanup completed:
 - Final local status: left open; no `TicketClose` was performed because the user authorized merge, not close/resolution.
 
 ---
+
+<!-- event: state_changed author: hare at: 2026-06-09T10:20:56Z from: done to: closed reason: closed field: state -->
+
+## State changed
+
+Ticket を closed にしました。
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-09T10:20:56Z status: closed -->
+
+## 完了
+
+Closed as completed.
+
+The YAML frontmatter parsing work was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; implementation details, validation, and review history remain in `thread.md`.
+
+---

.yoi/tickets/20260607-230044-001/item.md

@@ -1,8 +1,8 @@
 ---
 title: "Relax implementation planning readiness toward intent and reviewability"
-state: "done"
+state: 'closed'
 created_at: "2026-06-07T23:00:44Z"
-updated_at: "2026-06-07T23:38:32Z"
+updated_at: '2026-06-09T10:21:07Z'
 queued_by: "workspace-panel"
 queued_at: "2026-06-07T23:03:35Z"
 ---

.yoi/tickets/20260607-230044-001/resolution.md

@@ -0,0 +1,3 @@
+Closed as completed.
+
+The implementation-planning readiness relaxation work was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; decisions and validation history remain in `thread.md`.

.yoi/tickets/20260607-230044-001/thread.md

@@ -390,3 +390,22 @@ Merge-completion cleanup completed:
 - Final local status: left open; no `TicketClose` was performed because the user authorized merge, not close/resolution.
 
 ---
+
+<!-- event: state_changed author: hare at: 2026-06-09T10:21:07Z from: done to: closed reason: closed field: state -->
+
+## State changed
+
+Ticket を closed にしました。
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-09T10:21:07Z status: closed -->
+
+## 完了
+
+Closed as completed.
+
+The implementation-planning readiness relaxation work was implemented and the Ticket was already in `state: done`. This close records final lifecycle completion; decisions and validation history remain in `thread.md`.
+
+---

.yoi/tickets/20260609-082209-001/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'Profile feature flagsでtool surfaceを制御する'
-state: 'planning'
+state: 'ready'
 created_at: '2026-06-09T08:22:09Z'
-updated_at: '2026-06-09T08:22:09Z'
+updated_at: '2026-06-09T10:20:48Z'
 assignee: null
 ---
 

.yoi/tickets/20260609-082209-001/thread.md

@@ -5,3 +5,19 @@
 LocalTicketBackend によって作成されました。
 
 ---
+
+<!-- event: intake_summary author: intake at: 2026-06-09T10:20:48Z -->
+
+## Intake summary
+
+既存 Ticket を再読し、duplicate/related work を確認した。これは既存の `pod::feature` registry、Task built-in feature、Ticket built-in feature、Ticket orchestration tools を前提に、Lua Profile / resolved Manifest から feature 単位で LLM tool surface を登録抑制する concrete implementation work item であり、新規 duplicate Ticket は不要。意図、対象 feature groups、core tools の非対象化、disabled feature は permission deny ではなく schema から消す方針、role default、受け入れ条件、検証が十分明確。blocking open question はなし。主な risk/reviewer focus は `profile/manifest`, `feature-boundary`, `authority-boundary`, `tool-schema`, `prompt-guidance`, `web-config-fail-closed`。`feature.ticket.access` / `feature.memory.access` の粒度は、既存 `TicketFeatureAccess` を再利用・拡張する範囲で実装中判断可能だが、silent broad grant になる場合は escalate する。
+
+---
+
+<!-- event: state_changed author: intake at: 2026-06-09T10:20:48Z from: planning to: ready reason: planning_ready field: state -->
+
+## State changed
+
+Intake が既存 Ticket の要件を確認し、Orchestrator が routing できる状態と判断したため planning から ready に遷移します。実装はまだ開始しません。
+
+---

.yoi/tickets/20260609-085148-001/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'session analyticsにresponse単位のbatching指標を追加する'
-state: 'planning'
+state: 'ready'
 created_at: '2026-06-09T08:51:48Z'
-updated_at: '2026-06-09T08:51:48Z'
+updated_at: '2026-06-09T10:20:52Z'
 assignee: null
 ---
 

.yoi/tickets/20260609-085148-001/thread.md

@@ -5,3 +5,19 @@
 LocalTicketBackend によって作成されました。
 
 ---
+
+<!-- event: intake_summary author: intake at: 2026-06-09T10:20:52Z -->
+
+## Intake summary
+
+既存 Ticket は、closed 済みの `20260609-032533-001` で追加された `session-analytics` 基盤への concrete follow-up として十分に具体化済み。目的は assistant response 単位の tool batching / edit round-trip 指標を JSON report に追加することで、実装対象 metrics、断定しない diagnostics 方針、非目標、受け入れ条件、テスト観点が明記されている。未決定の product/API/authority boundary はなく、Orchestrator は implementation_ready として routing できる。Reviewer focus は、response/tool-result cycle 推定の妥当性、raw content を出さない既存 analytics privacy boundary の維持、consecutive edit-only streak の過剰断定回避、既存 CLI/JSON schema との整合性。
+
+---
+
+<!-- event: state_changed author: intake at: 2026-06-09T10:20:52Z from: planning to: ready reason: intake_ready field: state -->
+
+## State changed
+
+Intake で既存 Ticket の本文・thread・artifacts と関連する closed Ticket `20260609-032533-001` を確認した。要件は実装・レビュー・検証できる粒度まで整理済みであり、planning から ready にする。
+
+---