v0.2.0

Project names are accepted wherever a project ID is, tasks can be marked off-limits to modification, and every ticktick_complete_task and ticktick_update_task result carries an outcome field.

Two changes are not backward compatible:

• An ambiguous project name is now an error naming both candidate IDs, rather than silently resolving to whichever project sync returned first.
• ticktick_mark_completion_processed now requires an authenticated client. It previously worked during an auth outage, but would key the completion row by project name - invisible to every later ID-keyed read.

Full detail in CHANGELOG.md.