Task-tool reminder fires repeatedly even when tasks are being actively tracked

Friction: The "task tools haven't been used recently" system-reminder fires throughout long sessions even when TaskCreate/TaskUpdate are being actively used. Observed ~12 firings in a single /plan + /execute arc where 10 tasks were created across two batches and updated as phases finished. Also hit 5+ times in a short /orient + feedback-triage session today, where task tracking would have been overkill for the work. The trigger appears to be "time since last task-tool call" rather than "multi-step work detected without tasks tracked."

Cost: Each firing inserts ~50-100 tokens of identical reminder text for zero signal. By the third firing it's just noise the model has to consciously ignore in every response — and ironically biases toward over-using TaskCreate on work that doesn't warrant it.

Suggestion: Tighten the heuristic so the reminder fires only when (a) no tasks exist OR all tasks are pending/stale AND (b) the recent action sequence looks multi-step (3+ distinct file edits / tool calls without a task wrapping them). Or expose a per-session suppression once Claude has demonstrated task hygiene by creating + completing tasks in the session.