From 39d44bb3842a640b4e5be1f9304048f9c933f746 Mon Sep 17 00:00:00 2001 From: claude Date: Fri, 7 Aug 2026 01:48:19 +0400 Subject: [PATCH] Close a Vikunja task with done, and nothing else (V-641) Owner's call, 07-08-2026. A completion summary written into the description on the way out is lost anyway, and the durable record is the commit messages and the merged PR. Written during the V-641 session and left uncommitted; it rides this branch rather than being dropped. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01YMNNEkYx1mZFtHNrFk7uqb --- CLAUDE.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index dbab7d0..f27f9a8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -460,8 +460,11 @@ start of a session rather than one lookup per first use: ToolSearch("select:mcp__vikunja__list_tasks,mcp__vikunja__get_task_details,mcp__vikunja__create_task,mcp__vikunja__update_task") ``` -`update_task` carrying a `description` resets `done` to false, so closing a task with a -write-up takes two calls: the description, then `done: true`. +**Close a finished task with `done: true` and nothing else** (owner's call, 07-08-2026). +Do not write a completion summary into the description on the way out. It is lost anyway, +and the durable record is the commit messages and the merged PR. Note that `update_task` +carrying a `description` resets `done` to false, which is why a write-up ever took two +calls. ## Session workflow