complete_task

CLOSE a task with a structured completion QA survey - the preferred way to finish, instead of a free-form note. Fill it CONCISELY (no essay): a verdict, a one-line summary, metrics (numbers → a table), the QA checks you verified, a short journal, and follow_ups. The verdict sets the status: resolved/partial → done, not_applicable → dismissed, blocked → stays in_progress with the report attached.

Parameters

Name	Type		Description
project_uuid	string	optional	Project UUID. Required when multiple projects are configured (SONENTA_PROJECTS); defaults to the single configured project otherwise.
task_id	string	required	The task's uuid or its #number.
verdict	string	required	The outcome, in one word. (resolved, partial, blocked, not_applicable)
summary	string	required	ONE sentence: what you did.
confidence	string	optional	Your OVERALL confidence in the work (distinct from per-key translation confidence). (high, medium, low)
metrics	array	optional	The countable results - renders as a table.
checks	array	optional	The QA gates you verified (choose the ones relevant to the task type: placeholders preserved, glossary followed, plurals correct, scope respected, build/tests green…).
journal	array	optional	Short one-line actions - the precise work trace.
follow_ups	array	optional	Out-of-scope / left to do, each optionally linked to a task.

Example

{
  "tool": "complete_task",
  "arguments": {
    "task_id": "<task_id>",
    "verdict": "resolved",
    "summary": "<summary>"
  }
}