If the user gives a rambling, multi-item update in one message (e.g.
"finished the login screen, still working on the API integration, and
I'm blocked on AWS permissions"), call this tool ONCE PER DISTINCT ITEM
rather than logging it as one combined entry.

Infer `status` from the language used for each item:
- "done" -> finished, shipped, completed, past tense ("fixed", "wrote")
- "in_progress" -> still working on, in the middle of, ongoing, todo, to do, need to, planning to
- "blocked" -> blocked, stuck, waiting on, can't proceed until

IMPORTANT: Always normalize status to exactly one of: "done", "in_progress", "blocked".
Never use "todo", "to do", "in progress" (with space), or any other variant.

`tag` is an optional project/category label (e.g. "frontend", "acme-client",
"customer-advisor", "infra", "github"). Set it whenever the user's phrasing implies
a category, using any of these patterns:
- "log ___ under/as/for [category]"
- "tag this as [category]"
- "categorize/sort this as [category]"
- simply mentioning a known project/client name in the task description
Each distinct tag automatically gets a consistent colored-circle emoji
in every response, so tasks stay visually grouped by category over time.
If no category is stated or inferable from context, leave `tag` unset.

`due_date` is an optional ISO date (YYYY-MM-DD) deadline. Set it whenever
the user mentions a due date, deadline, or "by [date]" in their message.
Parse natural language dates (e.g. "due Friday", "by next week", "due Aug 21")
into ISO format.

If `status` is "blocked" and there's already an open blocker with a very
similar description, this updates that existing entry's date instead of
creating a duplicate — so a recurring blocker doesn't pile up as
multiple rows across days.

Use this when the user says a previously logged item has changed state
— e.g. a blocker just got resolved, or something in progress is now
done. `status` must be one of: "done", "in_progress", "blocked".

Use this whenever the user wants to retroactively add, change, or
remove a category/tag on a task they already logged — e.g. "tag #12
as infra" or "remove the tag from #7". This is the correct tool for
that; do NOT delete and re-log the task, since that rewrites its
original log_date and loses history.

Pass tag=None (or an empty string) to clear an existing tag.

Note: if the task has subtasks (other tasks tagged "subtask:<task_id>"),
those are untouched by this call — only task_id's own tag changes.

Use this whenever the user wants to set, change, or clear a due date on
a task they already logged — e.g. "the behavioral stories task is due
today EOD" or "push #12's due date to Sept 1" or "clear the due date on
#7". This is the correct tool for that; do NOT delete and re-log the
task, since that rewrites its original log_date and loses history.

`due_date` must be an ISO date (YYYY-MM-DD). Parse natural language
dates (e.g. "today", "EOD today", "Friday", "next week") into ISO
format before calling this — relative phrasing stored as-is will not
sort or display correctly in the checklist dashboard.

Pass due_date=None (or an empty string) to clear an existing due date.

Optionally filter to a single `tag`/project.

Use this for "what did I do last week" style questions instead of
calling get_tasks_by_date multiple times. Optionally filter to a single
`tag`/project.

Automatically groups items by tag/project if any logged tasks have one.
Set include_weekly=True to append a rollup covering the last `range_days`
days (default 7). The rollup follows the standard three-question standup
format — Done / In Progress / Blocked — for that whole period, not just
completed items, so it works for a weekly retro, a 1:1, or any custom
stretch of time by adjusting range_days.

Uses standard Markdown (**bold**, _italic_, - bullets) so it renders
cleanly in Claude's chat UI. If pasting into Slack, swap ** for single
* around headers (Slack uses single asterisks for bold).