ticket-commentslisted

# Comment on an AzDO Work Item (Markdown-aware) There are two ways to put text on a work item's discussion. Use the **Comments API**, not the `System.History` patch. | Method | Editable? | Deletable? | Markdown? | | -------------------------------------------- | --------- | ---------- | -------------------------------------- | | `PATCH workitems/{id}` with `System.History` | no | no | no (HTML-coerced) | | Comments API `workItems/{id}/comments` | yes | yes | yes, via `format=markdown` query param | The `format` flag lives in the **query string**, not the body. Omit it and the text is stored as HTML, so Markdown shows up literally. This is work-item discussion only. For pull-request thread comments, use `dev-azdo:pr-comments`. ## Step 1: Resolve org and project (always first) Shell variables do **not** survive between Bash calls, so resolve these once, read the printed values, and paste the literals into every later command. Never carry `$BASE` across calls. ```bash # cut -f2- + sed, not `tr -d ' '`. AzDO project names may contain spaces. TRIM="s/^ *//; s/ *$//" ORG_URL="${AZDO_ORG_URL:-$(az devops configure --list | grep '^organization' | cut -d= -f2- | sed "$TRIM")}" PROJECT="${AZDO_PROJECT:-$(az devops configure --list | grep '^project' | cut -d= -f2- | sed "$TRIM")}" : "${ORG_URL:?no organization, set AZDO_ORG_URL or run az devops configure --def