v0.1.4

Reports an absent assignee or group as null rather than 0 in ticket update's field report. Freshdesk represents "nobody" by omitting the key, which decodes to 0, and 0 is not an id anything can hold — reporting it raw reads like a real assignee to whoever is checking what the write did.

v0.1.3

ticket update — writes status, priority, assignee, group and custom fields of one ticket in a single PUT (contract §4.8). Numeric ids only: turning a label like 进行中 into an id is catalog resolve's job against the tenant directory. --status requires --baseline; --status 5 is refused and points at ticket close; --unassign sends an explicit null and is mutually exclusive with --responder. A partial landing reports write_failed with the ticket's real current values.

v0.1.2

Record structurally damaged images as corrupt instead of shipping bytes that no decoder will accept.

v0.1.1

Two defects found during production acceptance.

• guard_duplicate went blind after re-bundling: the check only looked past the baseline, so re-running bundle after a send folded that reply into the new baseline and the second send went through. send now also covers anything sent within 24h; reply verify is unchanged (its question is attribution, not prevention).
• ticket close could not close a ticket whose helpdesk marks a custom field mandatory on close. --custom-field name=value (repeatable) writes under custom_fields only — responder, group, priority and requester stay unreachable.

The write surface is still exactly three commands.

v0.1.0

First public release. Read-only evidence gathering plus three guarded, single-shot writes; JSON envelopes, a distinguishable error type and exit code per failure, and all-or-nothing collections. See docs/CONTRACT.md for the authoritative semantics.