fix(commands): use standard markdown for bold in command output

commands/channel-digest.md

@@ -14,13 +14,13 @@ Given the comma-separated channel names provided in $ARGUMENTS (strip leading `#
 3. Present the digest in this format:
 
    ```
-   *Channel Digest — <today's date>*
+   **Channel Digest — <today's date>**
 
-   *#channel-1*
+   **#channel-1**
    - Summary point 1
    - Summary point 2
 
-   *#channel-2*
+   **#channel-2**
    - Summary point 1
    - Summary point 2
 

commands/draft-announcement.md

@@ -12,7 +12,7 @@ Given the topic or context provided in $ARGUMENTS:
    - What tone is appropriate — formal, casual, or urgent?
 
 2. Compose the announcement following Slack formatting best practices:
-   - Use Slack's mrkdwn syntax: `*bold*` for emphasis (not `**bold**`), `_italic_` for secondary emphasis, `>` for callouts.
+   - Use standard markdown: `**bold**` for emphasis, `_italic_` for secondary emphasis, `>` for callouts.
    - Lead with the most important information — don't bury the point.
    - Use a clear, descriptive opening line that works as a headline.
    - Keep paragraphs short (2-3 sentences max).

commands/standup.md

@@ -15,16 +15,16 @@ description: Generate a standup update based on your recent Slack activity
 
 5. Format the standup as:
    ```
-   *Standup for <display name> — <today's date>*
+   **Standup for <display name> — <today's date>**
 
-   *Done:*
+   **Done:**
    - Item 1
    - Item 2
 
-   *Doing:*
+   **Doing:**
    - Item 1
 
-   *Blockers:*
+   **Blockers:**
    - None / Item 1
    ```