fix(deps): update @doist/comms-sdk to 2.0.2

[scottlovegrove]

Picks up Doist/comms-sdk-typescript#69, released as @doist/comms-sdk@2.0.2.

Why it matters here

Attachment uploads have never reached the server with a file attached. The SDK built the multipart body with the global FormData while dispatching through undici's own fetch, which does not recognise that class and stringifies it — so every upload was sent as the literal "[object FormData]" with content-type: text/plain.

That is exactly the path this CLI takes: td thread create --file and td thread reply --file go through uploadAttachments in src/lib/attachments.ts → client.attachments.upload.

Verification

npm test (858 tests), npm run type-check, npm run lint:check and npm run check:skill-sync all green on Node 24.18.0 and Node 26.4.0.

Also exercised the real upload path end to end against a local server with no mocks — openLocalFileAsBlob → attachments.upload, the same two calls lib/attachments.ts makes:

node 24.18.0 / 26.4.0 | comms-sdk 2.0.2 — CLI upload path, no mocks
  content-type : multipart/form-data; boundary=----comms-sdk-…
  multipart    : true
  file bytes   : true

Before the SDK fix the same harness reported content-type: text/plain;charset=UTF-8 and a body of "[object FormData]".

🤖 Generated with Claude Code

[doistbot]

This PR updates fix(deps): update @doist/comms-sdk to 2.0.2. No issues were flagged in the reviewed diff.

_{Share Feedback • Review Logs}

[doist-release-bot]

🎉 This PR is included in version 2.0.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[craigcarlyle]

✅