ticket: close task feature state move

This commit is contained in:
Keisuke Hirata 2026-06-05 11:24:26 +09:00
parent 9eceb189ba
commit 6cc2e9ade7
No known key found for this signature in database
7 changed files with 12 additions and 2 deletions

View File

@ -2,12 +2,12 @@
id: 20260605-004807-task-feature-own-store-reminder-hooks id: 20260605-004807-task-feature-own-store-reminder-hooks
slug: task-feature-own-store-reminder-hooks slug: task-feature-own-store-reminder-hooks
title: Task: move TaskStore and reminders into Task feature title: Task: move TaskStore and reminders into Task feature
status: open status: closed
kind: task kind: task
priority: P1 priority: P1
labels: [tasks, hooks, feature-registry, history] labels: [tasks, hooks, feature-registry, history]
created_at: 2026-06-05T00:48:07Z created_at: 2026-06-05T00:48:07Z
updated_at: 2026-06-05T02:23:00Z updated_at: 2026-06-05T02:24:23Z
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
--- ---

View File

@ -0,0 +1 @@
Moved TaskStore and Task reminder state/logic into the built-in Task feature. Task tools share the feature-owned session store; Task feature hooks now record Task tool usage and append TaskReminder via SystemItemAppendHandle. Pod/PodInterceptor no longer own TaskStore/TaskReminderState or special-case Task tool reminder emission. Reminder append accounting was fixed so usage and request-threshold compaction see the post-append context. External review approved. Merge validation passed: cargo test -p pod task_reminder --lib, cargo test -p pod hook --lib, cargo test -p pod --lib, cargo test -p llm-worker --lib, cargo fmt --check, cargo check --workspace --all-targets, ./tickets.sh doctor, git diff --check, nix build .#yoi, ./result/bin/yoi pod --help.

View File

@ -385,4 +385,13 @@ I did not rerun full workspace tests or `nix build .#yoi` as part of this rerevi
Residual risk is low for this ticket. The main area to watch is future expansion of `YieldWith(Vec<Item>)`: it should remain an internal worker/interceptor mechanism for preserving already-authorized, host-created history appends across yield/compaction boundaries, not a public raw-history injection mechanism. Residual risk is low for this ticket. The main area to watch is future expansion of `YieldWith(Vec<Item>)`: it should remain an internal worker/interceptor mechanism for preserving already-authorized, host-created history appends across yield/compaction boundaries, not a public raw-history injection mechanism.
---
<!-- event: close author: hare at: 2026-06-05T02:24:23Z status: closed -->
## Closed
Moved TaskStore and Task reminder state/logic into the built-in Task feature. Task tools share the feature-owned session store; Task feature hooks now record Task tool usage and append TaskReminder via SystemItemAppendHandle. Pod/PodInterceptor no longer own TaskStore/TaskReminderState or special-case Task tool reminder emission. Reminder append accounting was fixed so usage and request-threshold compaction see the post-append context. External review approved. Merge validation passed: cargo test -p pod task_reminder --lib, cargo test -p pod hook --lib, cargo test -p pod --lib, cargo test -p llm-worker --lib, cargo fmt --check, cargo check --workspace --all-targets, ./tickets.sh doctor, git diff --check, nix build .#yoi, ./result/bin/yoi pod --help.
--- ---