channel-formatting

# Channel Formatting This skill wires channel-aware Markdown conversion into the outbound pipeline so Claude's responses render natively on each platform — no more literal `**asterisks**` in WhatsApp or Telegram. | Channel | Transformation | |---------|---------------| | WhatsApp | `**bold**` → `*bold*`, `*italic*` → `_italic_`, headings → bold, links → `text (url)` | | Telegram | same as WhatsApp, but `[text](url)` links are preserved (Markdown v1 renders them natively) | | Slack | same as WhatsApp, but links become `<url\|text>` | | Discord | passthrough (Discord already renders Markdown) | | Signal | passthrough for `parseTextStyles`; `parseSignalStyles` in `src/text-styles.ts` produces plain text + native `textStyle` ranges for use by the Signal skill | Code blocks (fenced and inline) are always protected — their content is never transformed. ## Phase 1: Pre-flight ### Check if already applied ```bash test -f src/text-styles.ts && echo "already applied" || echo "not yet applied" ``` If `already applied`, skip to Phase 3 (Verify). ## Phase 2: Apply Code Changes ### Ensure the upstream remote ```bash git remote -v ``` If an `upstream` remote pointing to `https://github.com/qwibitai/nanoclaw.git` is missing, add it: ```bash git remote add upstream https://github.com/qwibitai/nanoclaw.git ``` ### Merge the skill branch ```bash git fetch upstream skill/channel-formatting git merge upstream/skill/channel-formatting ``` If there are merge conflicts on `package-loc...