ticket: close commit noise policy

.yoi/tickets/00001KTJ42528/item.md

@@ -1,8 +1,8 @@
 ---
 title: "Ticket lifecycle commit noise を減らし commit / publication policy を一本化する"
-state: "planning"
+state: 'closed'
 created_at: "2026-06-07T22:43:09Z"
-updated_at: "2026-06-11T05:45:00Z"
+updated_at: '2026-06-18T12:22:10Z'
 ---
 
 ## 背景

.yoi/tickets/00001KTJ42528/resolution.md

@@ -0,0 +1,11 @@
+Closed as resolved by current dogfooding workflow rather than a new broad implementation.
+
+The active policy is now operationally established:
+- do not commit one Ticket lifecycle event per Git commit mechanically;
+- batch related Ticket-only updates when they belong to the same decision/work burst;
+- keep implementation/code commits separate from Ticket publication commits unless a merge step requires both;
+- stage only exact Ticket paths and never broad auto-commit unrelated user changes;
+- use orchestration worktree/branch for active progress and publish to the main workspace at explicit merge/close/follow-up boundaries;
+- keep audit evidence in Ticket files/thread/resolution even when Git commits are batched.
+
+Future changes should be filed as targeted Tickets, such as Panel dirty-state UX, workflow prompt wording, or automated queue commit behavior.

.yoi/tickets/00001KTJ42528/thread.md

@@ -4,4 +4,32 @@
 
 Created by LocalTicketBackend create.
 
+---
+
+<!-- event: state_changed author: hare at: 2026-06-18T12:22:10Z from: planning to: closed reason: closed field: state -->
+
+## State changed
+
+Ticket を closed にしました。
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-18T12:22:10Z status: closed -->
+
+## 完了
+
+Closed as resolved by current dogfooding workflow rather than a new broad implementation.
+
+The active policy is now operationally established:
+- do not commit one Ticket lifecycle event per Git commit mechanically;
+- batch related Ticket-only updates when they belong to the same decision/work burst;
+- keep implementation/code commits separate from Ticket publication commits unless a merge step requires both;
+- stage only exact Ticket paths and never broad auto-commit unrelated user changes;
+- use orchestration worktree/branch for active progress and publish to the main workspace at explicit merge/close/follow-up boundaries;
+- keep audit evidence in Ticket files/thread/resolution even when Git commits are batched.
+
+Future changes should be filed as targeted Tickets, such as Panel dirty-state UX, workflow prompt wording, or automated queue commit behavior.
+
+
 ---