Lawmatics

Create a task in Lawmatics. Requires a name and a due date. Optionally assign firm users, set a priority, tags, or a recurrence rule, and associate the task with at most one matter, contact, or company (omit all three for an unattached task). Returns a `relationships` envelope of {id,type} pointers to related records (the associated matter/contact/company via `taskable`, assigned users, documents, files, subtasks, and comments).

Delete a task from Lawmatics by ID. This is irreversible.

Fetch a single task from Lawmatics by ID, including a `relationships` envelope of {id,type} pointers to related records (the associated matter/contact/company via `taskable`, assigned users, documents, files, subtasks, and comments).

List tasks from Lawmatics with optional pagination, filtering, and sorting. Filter by the associated matter/contact/company/client id, an assigned user id, or task fields like done, priority, and due_date. Each row carries a `relationships` envelope with a to-one `taskable` {id,type} pointer to the associated record; use get-task for the full envelope including to-many pointers (users, documents, files, subtasks, comments).

Update an existing task in Lawmatics by ID. Provide any combination of name, description, due date, assigned users, priority, completion status, tags, recurrence rule, or a new associated matter/contact/company. Returns a `relationships` envelope of {id,type} pointers to related records (the associated matter/contact/company via `taskable`, assigned users, documents, files, subtasks, and comments). Known Lawmatics quirk: marking a RECURRING task done (and any later update to that completed recurring task) is applied but returns an upstream error — on such an error, verify the result with get-task instead of retrying.