fix: upgrade Comms SDK to 2.0.1

[gnapse]

Summary

• upgrade @doist/comms-sdk from 0.11.0 to 2.0.1
• handle restricted workspace-user profiles introduced by SDK 2.x
• preserve nullable email output for restricted channel and group members

Related

• CLI issue Doist/comms-cli#52
• SDK fix PR Doist/comms-sdk-typescript#68
• SDK issue Doist/comms-sdk-typescript#67

Testing

• npm run type-check
• npm test
• npm run lint:check
• npm run build
• npm run check:skill-sync

Fixes #52

[doistbot]

This upgrades @doist/comms-sdk to 2.0.1 and nulls emails for restricted workspace users in channel and group member output.

Few things worth tightening:

• The restricted-user fixtures in the channel and group tests omit email, so email: null would pass even without the isRestrictedWorkspaceUser guard. Give those fixtures an email so the assertions actually prove it is stripped.

I also left one optional follow-up note in the details below.

Optional follow-up note (1)

• src/commands/channel/membership-helpers.ts:23: fetchUsersByIds returns any user resolved by getUserById, which can be either visible or restricted. The return type and map instantiation should use WorkspaceUser instead of VisibleWorkspaceUser so callers receive the accurate union type before narrowing with isRestrictedWorkspaceUser.

_{Share Feedback • Review Logs}

[doist-release-bot]

🎉 This PR is included in version 2.0.3 🎉

The release is available on:

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

Your semantic-release bot 📦🚀