docs(thread): document group IDs in --notify help text

`tdc thread reply/create --notify` already accepts custom group IDs
(partitioned via resolveNotifyIds → groups), but the help text only
mentioned "user IDs". Since Comms group IDs are non-numeric base58
strings that look nothing like user IDs, the capability was effectively
undiscoverable from --help. Mention groups in both option descriptions
and add a group-notify example to the reply command's existing example
block (alongside --close / --file).

No behaviour change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: lmjabreu

src/commands/thread/index.ts

@@ -50,7 +50,7 @@ Examples:
             withUnvalidatedChoices(
                 new Option(
                     '--notify <recipients>',
-                    'Notification recipients: EVERYONE, EVERYONE_IN_THREAD, or comma-separated user IDs (default: EVERYONE_IN_THREAD)',
+                    'Notification recipients: EVERYONE, EVERYONE_IN_THREAD, or comma-separated user and/or group IDs (default: EVERYONE_IN_THREAD)',
                 ),
                 ['EVERYONE', 'EVERYONE_IN_THREAD'],
             ),
@@ -68,6 +68,7 @@ Examples:
   tdc thread reply 12345 "Sounds good!"
   echo "Long reply" | tdc thread reply 12345
   tdc thread reply 12345 "Done" --close --json
+  tdc thread reply 12345 "Heads up" --notify 67890,Cbzzm11ZeYZoJYD4a6rti
   tdc thread reply 12345 "See attached" --file ./diagram.png
   tdc thread reply 12345 --file ./a.png --file ./b.pdf`,
         )
@@ -76,7 +77,7 @@ Examples:
     thread
         .command('create <channel-ref> <title> [content]')
         .description('Create a new thread in a channel')
-        .option('--notify <recipients>', 'Comma-separated user IDs to notify')
+        .option('--notify <recipients>', 'Comma-separated user and/or group IDs to notify')
         .option(
             '--unarchive',
             'Unarchive after creation so the thread appears in your Inbox (overrides userSettings.unarchiveNewThreads when false)',