@mmerterden/multi-agent-pipeline 15.10.1 → 15.11.0

package/CHANGELOG.md

@@ -16,6 +16,17 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [15.11.0] - 2026-08-21
+
+### Changed
+- **Nothing the pipeline posts carries a decorative glyph any more.** The work summary rendered task marks and a phase strip in checkmarks and hourglasses, the PR review emitter prefixed every finding with a coloured dot and signed it with a robot, and the GitHub issue Progress table was three traffic lights. All of it now reads in words: `[done]` / `[pending]` for tasks, `done · active · failed · skipped · pending` for the phase strip, `done` / `partial` / `pending` for the issue flags, and the severity is the bold label it always was. `channels/jira.md` had banned decorative glyphs in a comment body for releases while the renderers filled it with them; the rule and the emitters now agree, and `smoke-channel-glyphs.sh` holds them to it. The pipeline's own terminal output is deliberately out of scope: a `✓` in a console summary is a UI affordance, not a document somebody reads later.
+
+### Fixed
+- **Jira no longer manufactures smileys the pipeline never typed.** Comments are posted as Jira wiki markup, and Jira's renderer converts `:)` `:D` `;)` and, far more easily hit in technical prose, `(x)` `(/)` `(!)` `(i)` `(y)` `(+)` `(on)` `(*)` into emoticon images at render time. Nothing escaped them. `channels/jira.md` now carries the escaping table and orders it after the markdown conversion and before the POST. This was never something the humanizer could fix: the text is legitimate, and `(x)` in a comparison table renders correctly on GitHub and Confluence - only the Jira conversion knows the target parser.
+
+### Tests
+- `smoke-channel-glyphs.sh` (8 checks) and a glyph assertion in `smoke-work-summary.sh`. Both detect with node's `\p{Extended_Pictographic}` rather than `grep -P`: the first draft of the gate used a PCRE class, reported a clean tree with a checkmark deliberately planted in an emitter, and passed. Under `bash` on a stock macOS `grep` is BSD grep, which has no `-P` at all - it exits 2 with "invalid option", the `2>/dev/null` swallowed the message, and an empty result read as "no glyphs". The gate now opens by proving its own detector fires on a planted glyph before it trusts any verdict, and both gates were re-checked by planting one and watching them go red.
+
 ## [15.10.1] - 2026-08-21
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "15.10.1",
+  "version": "15.11.0",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",

package/pipeline/commands/multi-agent/channels/SKILL.md

@@ -93,12 +93,12 @@ When the preview does NOT render (no state, or pref explicitly off at global lev
 **Visual flow (TR, pref on + state available):**
 
 ```
-📋 Yapılan iş özeti  -  PROJ-12345
+Yapılan iş özeti  -  PROJ-12345
 ──────────────────────────────────────────────────────────
 {rendered Work Summary block  -  header + scope + diffstat + review + phases}
 ──────────────────────────────────────────────────────────
 
-✅ İş özetini gördün. Şimdi nereye rapor gönderelim?
+[done] İş özetini gördün. Şimdi nereye rapor gönderelim?
 ```
 
 Then 3b renders:
@@ -167,7 +167,7 @@ For each selected **content** source, produce one section body. Each section run
 | Auto-diff | Old enrich Output Template verbatim  -  Root Cause / Solution / Changed Files / Test Scenarios |
 | Manuel not | `### Notes`  -  user-provided paragraph, or LLM-split into subsections if `--message` is plain text and long |
 | Cost özeti | `### Cost Summary`  -  per-phase token tally + est. USD table. Source: `phase-tracker.sh` phase status + optional OTel spans. See "Cost summary generation" below. |
-| Yapılan iş özeti | `### Work Summary`  -  executive one-screen summary: task + branch + base + PR, scope delivered (✅/⏳ per Phase 2 task), changed files with +/- counts (capped at 20 rows), review outcome (accepted/deferred/rejected + approved), phase tick strip. Source: `agent-state.json` + `phase-tracker.json` + `git diff --numstat base...HEAD`. See "Work summary generation" below. |
+| Yapılan iş özeti | `### Work Summary`  -  executive one-screen summary: task + branch + base + PR, scope delivered (done/[pending] per Phase 2 task), changed files with +/- counts (capped at 20 rows), review outcome (accepted/deferred/rejected + approved), phase tick strip. Source: `agent-state.json` + `phase-tracker.json` + `git diff --numstat base...HEAD`. See "Work summary generation" below. |
 
 **Output template (aggregated across selected content options):**
 
@@ -230,8 +230,8 @@ If a cached report exists AND any of the selected channels is PR / Jira / Conflu
 
 | Blocker count | Appended line |
 |---|---|
-| `errors > 0` | `### Store compliance` + `⚠️ {N} blocker(s), {M} warning(s)  -  run /multi-agent:test "store-ready" for the full report.`  -  per-blocker: `- \`{ruleID}\`  -  {Apple ITMS / Play ref}: {message}` (capped at 5 rows, rest collapsed to `+N more`) |
-| `errors == 0, warnings > 0` | `### Store compliance` + `✅ No blockers. {M} warning(s)  -  see /multi-agent:test "store-ready" for detail.` |
+| `errors > 0` | `### Store compliance` + `{N} blocker(s), {M} warning(s)  -  run /multi-agent:test "store-ready" for the full report.`  -  per-blocker: `- \`{ruleID}\`  -  {Apple ITMS / Play ref}: {message}` (capped at 5 rows, rest collapsed to `+N more`) |
+| `errors == 0, warnings > 0` | `### Store compliance` + `[done] No blockers. {M} warning(s)  -  see /multi-agent:test "store-ready" for detail.` |
 | `errors == 0, warnings == 0` | Skip section entirely  -  don't pollute PR body |
 
 The section references `ruleID` + policy ref from the compliance skill catalogs (`apple-archive-compliance` / `google-play-compliance`) verbatim. No translation  -  global identifiers stay as-is.
@@ -243,10 +243,10 @@ If no cached report exists, skip silently  -  this is augmentation, not a gate.
 Emitted only when `reportContent.workSummary === true` and at least one of (`agent-state.json`, `--branch` flag) is available. The shell adapter is `$HOME/.claude/scripts/render-work-summary.sh <taskId>`:
 
 1. **Task header**  -  `taskId`, `branch`, `baseBranch`, `prNumber` from `agent-state.json` (or explicit flags for post-hoc invocation).
-2. **Scope delivered**  -  Phase 2 `planTodos[]` / `tasks[]` rendered as `✅` (status=done) or `⏳` (anything else) rows. Task id + title shown; `(deferred  -  rationale)` appended if the task's `status` is `"deferred"`.
+2. **Scope delivered**  -  Phase 2 `planTodos[]` / `tasks[]` rendered as `done` (status=done) or `pending` (anything else) rows. Task id + title shown; `(deferred  -  rationale)` appended if the task's `status` is `"deferred"`.
 3. **Changed files**  -  `git -C $WORKTREE diff --numstat $baseBranch...HEAD`. Shows `` `path` (+add / -del) `` per row, capped at 20 with a `_... +N more files not shown_` footer when exceeded. Total adds/dels + file count in section header.
 4. **Review outcome**  -  from `reviewConsensus` (pre-v6.1) or `phases["4"].triage`: `{accepted} accepted · {deferred} deferred · {rejected} rejected · approved={bool}`. Hidden entirely when all three buckets are empty (normal for `--dev` / `dev-autopilot` runs that skip Phase 4).
-5. **Phase tick strip**  -  single line from the tracker state (`render-work-summary.sh` resolves worktree/artifacts copies, then `$HOME/.claude/logs/multi-agent/{taskId}/tracker-state.json`): `0 Init ✅ · 1 Analysis ✅ · 2 Planning ✅ · 3 Dev ✅ · 4 Review ✅ · 5 Test ⏭ · 6 Commit ✅ · 7 Report ▶`. Marks: `✅` completed · `▶` in_progress · `❌` failed · `⏭` skipped · `·` pending.
+5. **Phase tick strip**  -  single line from the tracker state (`render-work-summary.sh` resolves worktree/artifacts copies, then `$HOME/.claude/logs/multi-agent/{taskId}/tracker-state.json`): `0 Init [done] · 1 Analysis [done] · 2 Planning [done] · 3 Dev [done] · 4 Review [done] · 5 Test skipped · 6 Commit [done] · 7 Report active`. Marks: `done` completed · `active` in_progress · `failed` failed · `skipped` skipped · `·` pending.
 
 **Output template:**
 
@@ -255,8 +255,8 @@ Emitted only when `reportContent.workSummary === true` and at least one of (`age
 **Task**: `PROJ-1099`  |  **Branch**: `bugfix/PROJ-1099-dark-mode`  |  **Base**: `develop`  |  **PR**: #104
 
 #### Scope delivered
-- ✅ T1 Add failing dark-mode snapshot test
-- ✅ T2 Replace Color.white with design token
+- [done] T1 Add failing dark-mode snapshot test
+- [done] T2 Replace Color.white with design token
 
 #### Changed files (3 files · +48 / -12)
 - `Sources/Auth/LoginView.swift` (+24 / -8)
@@ -267,7 +267,7 @@ Emitted only when `reportContent.workSummary === true` and at least one of (`age
 - 1 accepted · 0 deferred · 0 rejected · approved=true
 
 #### Phases
-- 0 Init ✅ · 1 Analysis ✅ · 2 Planning ✅ · 3 Dev ✅ · 4 Review ✅ · 5 Test ⏭ · 6 Commit ✅ · 7 Report ▶
+- 0 Init [done] · 1 Analysis [done] · 2 Planning [done] · 3 Dev [done] · 4 Review [done] · 5 Test skipped · 6 Commit [done] · 7 Report active
 ```
 
 **Post-hoc invocation** (task already finished, agent-state.json may be archived): pass `--branch` + `--base-branch` explicitly  -  the script still emits task header + changed-files + phases sections (scope + review outcome are state-dependent and will be absent if state is gone).

package/pipeline/lib/post-pr-review.sh

@@ -119,12 +119,7 @@ finding_fingerprint() {
 render_inline_body() {
   local sev="$1" issue="$2" fix="$3" rule_id="$4" fingerprint="${5:-}"
 
-  local emoji label_word fix_label
-  case "$sev" in
-    blocking)  emoji="🔴" ;;
-    important) emoji="🟡" ;;
-    *)         emoji="⚪" ;;  # never reached; suggestions never post
-  esac
+  local label_word fix_label
 
   if [ "$OUT_LANG" = "tr" ]; then
     case "$sev" in
@@ -140,14 +135,17 @@ render_inline_body() {
     fix_label="Suggestion"
   fi
 
-  printf '%s **%s**  -  %s\n\n' "$emoji" "$label_word" "$issue"
+  # The severity is the bold label, not a coloured dot. A review comment is
+  # read as technical prose, and the glyph carried no information the word did
+  # not already carry.
+  printf '**%s**  -  %s\n\n' "$label_word" "$issue"
   if [ -n "$fix" ] && [ "$fix" != "null" ]; then
     printf '**%s:** %s\n\n' "$fix_label" "$fix"
   fi
   if [ -n "$rule_id" ] && [ "$rule_id" != "null" ]; then
     printf '_%s_\n\n' "$rule_id"
   fi
-  printf -- '---\n🤖 _Multi-Agent Review · iteration #%s_\n' "$ITERATION"
+  printf -- '---\n_Multi-Agent Review · iteration #%s_\n' "$ITERATION"
   # Dedupe marker  -  dedupe-style. Re-runs of /multi-agent:review skip a
   # finding when an existing comment carries the same fingerprint.
   if [ -n "$fingerprint" ]; then

package/pipeline/multi-agent-refs/channels/confluence.md

@@ -152,6 +152,6 @@ Successful POST → URL prepended to `prefs.projects[<project>].confluenceUrls`
 - Section order is fixed: `overview` → `flow` (cond.) → `technical_details` → `api_contracts` (cond.) → `references` (cond.). Conditional sections may be omitted but never reordered.
 - Humanizer pass runs **after** body assembly and **before** storage-XML conversion. Tone: formal, stakeholder-readable. No "we are excited", no first-person plural.
 - Body content language follows `prefs.global.outputLanguage`. Code identifiers, API paths, file paths, type names, JSON keys, and the storage-XML markup stay verbatim. The template (this doc) is English because `promptLanguage="en"` is locked.
-- No decorative/emotive emoji or smileys (😊 🙂 🎉 👍 🚀 ✨) anywhere in the page body. Stakeholder-readable technical prose only.
+- No decorative/emotive emoji or smileys (    ) anywhere in the page body. Stakeholder-readable technical prose only.
 - Adapter failures are non-blocking. 401 / network timeout / parent-not-found → `failed` status, loop continues.
 - If `--dry-run`, print the assembled storage XML to stdout and return without POST.

package/pipeline/multi-agent-refs/channels/issue-comment.md

@@ -85,7 +85,7 @@ Ref: #<issueNumber>
 
 - No "Co-Authored-By: Claude" trailer. No "🤖 Generated with ..." footer. No mention of Claude / Copilot / AI / model names anywhere in the body.
 - No em-dashes (` - `) in prose. Use ` · ` or `→` per `feedback_no_em_dash.md`.
-- No decorative/emotive emoji or smileys (😊 🙂 🎉 👍 🚀 ✨) in the body prose. Only a fixed-template functional mark (e.g. a `✅/⏳` scope tick) is allowed; free text carries none.
+- No decorative/emotive emoji or smileys (    ) in the body prose. Only a fixed-template functional mark (e.g. a `done/pending` scope tick) is allowed; free text carries none.
 - No HTML entities. Use raw markdown.
 - No links to internal `/tmp/*` or local-machine paths.
 - No screenshots embedded as base64  -  link to wiki / Figma instead.

package/pipeline/multi-agent-refs/channels/jira.md

@@ -77,6 +77,22 @@ Body markdown is rewritten to Jira wiki markup before POST:
 
 The `\|` sequences in the two link/table rows are this table's own escape for a literal pipe  -  the emitted Jira markup carries `|`, never `\|`.
 
+### Emoticon escaping (required)
+
+Jira's wiki renderer turns ASCII sequences into emoticon images. This is not something the pipeline writes; Jira manufactures it at render time, which is why a comment can show a smiley nobody typed. Escape every sequence below with a leading backslash before POST:
+
+| Sequence | Renders as | Escaped |
+|---|---|---|
+| `:)` `:(` `:P` `:D` `;)` | face icons | `\:)` `\:(` `\:P` `\:D` `\;)` |
+| `(y)` `(n)` | thumbs | `\(y)` `\(n)` |
+| `(i)` `(?)` `(!)` | info / question / warning icons | `\(i)` `\(?)` `\(!)` |
+| `(/)` `(x)` | tick / cross icons | `\(/)` `\(x)` |
+| `(+)` `(-)` | plus / minus icons | `\(+)` `\(-)` |
+| `(on)` `(off)` | lightbulb icons | `\(on)` `\(off)` |
+| `(*)` `(*r)` `(*g)` `(*b)` `(*y)` | star icons | `\(*)` `\(*r)` ... |
+
+The parenthesised forms are the ones that actually bite: `(x)` in a comparison table, `(!)` in a caution note, and `(/)` in a path fragment are ordinary technical prose, and each becomes an image. Apply the escape AFTER the markdown conversion above and BEFORE the POST, and skip it inside `{code}` / `{noformat}` blocks, where Jira does not expand emoticons anyway.
+
 Lines outside these patterns pass through verbatim. Multi-paragraph blocks are joined with one blank line.
 
 Every row above is load-bearing, including the ones that look cosmetic. The table must cover each construct the section templates in this file actually emit  -  `##` for the three required headings, `**Given**` / `**When**` / `**Then**` in the test-scenario skeleton, and `1.`-numbered scenarios. A missing row does not degrade gracefully: the "pass through verbatim" fallback POSTs `## Test Senaryoları` and `**Given**` as literal text, so the comment renders with visible `##` and stray asterisks. Single `*bold*` in Markdown means *italic* in Jira wiki  -  never map `**bold**` to `*bold*` by dropping one asterisk mechanically without checking the source was bold, not italic.
@@ -135,6 +151,6 @@ When the **Wiki** adapter writes pages on the same run AND `prefs.global.wikiToJ
 - UTF-8 in, UTF-8 out  -  the body file is UTF-8 and `--data-binary` ships its bytes verbatim. Never round-trip the body through `unicode_escape`, `latin-1`, or any re-encode step, and never hand-roll a Python/curl helper that re-decodes it: that mangles Turkish chars (ç ş ı ö ü ğ) into mojibake (`Çözüm` → `Ãözüm`). Use the `jq --rawfile` + `--data-binary @file` path above as-is. Same rule for the PR / Confluence / Wiki adapters.
 - Section order is fixed: `summary` → `test_scenarios` → `context_refs`. Never insert sections between them; never reorder.
 - Humanizer pass runs **after** body assembly and **before** wiki-markup conversion. Tone target: informal but technical. No marketing voice, no "we are excited", no "I have...".
-- **No decorative/emotive emoji or smileys** (😊 🙂 🎉 👍 🚀 ✨) anywhere in the comment body. The comment is plain technical prose; emoji do not belong in it.
+- **No decorative glyphs anywhere in the comment body**  -  neither emotive (    ) nor status glyphs ([done] [pending] failed skipped active ). The comment is plain technical prose. Status is written in words: `[done]` / `[pending]`, and `done · active · failed · skipped · pending` in the phase strip. This applies to every channel, not only Jira  -  see `channels/README` note in `phase-7-report.md`.
 - Body content language follows `prefs.global.outputLanguage`. Code identifiers, file paths, type names, branch names, and the wiki-markup syntax stay verbatim. The `promptLanguage="en"` lock means any LLM prompt that produces the body is in English; the body itself is then rendered in the user's language.
 - Adapter failures are non-blocking  -  a missing token or 401 returns `skipped`/`failed`, the loop keeps going for PR / Confluence / Wiki.

package/pipeline/multi-agent-refs/channels/pr-review-actions.md

@@ -32,7 +32,7 @@ Body language follows `prefs.global.outputLanguage`. Both forms below are 1:1  -
 ### Turkish (outputLanguage = "tr")
 
 ```markdown
-{severityEmoji} **{severityLabelTr}**  -  {issueTr}
+**{severityLabelTr}**  -  {issueTr}
 
 **Öneri:** {fixTr}
 
@@ -40,29 +40,29 @@ Body language follows `prefs.global.outputLanguage`. Both forms below are 1:1  -
 _apple-archive-compliance / no-force-unwrap  -  Guideline 2.1.1_
 
 ---
-🤖 _Multi-Agent Review · iteration #{iterationNumber}_
+_Multi-Agent Review · iteration #{iterationNumber}_
 ```
 
 Severity labels (TR):
-- `blocking` → `🔴 **Blocker**`
-- `important` → `🟡 **Önemli**`
+- `blocking` → `**Blocker**`
+- `important` → `**Önemli**`
 
 ### English (outputLanguage = "en")
 
 ```markdown
-{severityEmoji} **{severityLabelEn}**  -  {issueEn}
+**{severityLabelEn}**  -  {issueEn}
 
 **Suggestion:** {fixEn}
 
 {Optional rule reference}
 
 ---
-🤖 _Multi-Agent Review · iteration #{iterationNumber}_
+_Multi-Agent Review · iteration #{iterationNumber}_
 ```
 
 Severity labels (EN):
-- `blocking` → `🔴 **Blocker**`
-- `important` → `🟡 **Important**`
+- `blocking` → `**Blocker**`
+- `important` → `**Important**`
 
 ### Anchoring
 

package/pipeline/multi-agent-refs/channels/wiki.md

@@ -63,5 +63,5 @@ Adapter implementation chooses the right git push target + commit message format
 - Per the `figma-pipeline.md` rules, every component wiki page must include a variant matrix, accessibility identifiers, analytics events, and 3-layer test summary.
 - Screenshots cover light/dark + LTR/RTL  -  wiki adapter refuses to commit if any quadrant is missing.
 - Body content language follows `prefs.global.outputLanguage`. Code identifiers, file paths, type names, design token names, and Markdown formatting stay verbatim across languages (wiki pages are `.md` files  -  "wiki markup" in this doc set means Jira's dialect, which never appears here). The template (this doc) is English because `promptLanguage="en"` is locked.
-- No decorative/emotive emoji or smileys (😊 🙂 🎉 👍 🚀 ✨) in the page prose. Only functional/structural marks a fixed template defines are allowed.
+- No decorative/emotive emoji or smileys (    ) in the page prose. Only functional/structural marks a fixed template defines are allowed.
 - Autopilot always pauses at the channels menu (per `phase-7-report.md` autopilot contract)  -  even in autopilot mode the user gets to confirm wiki scope.

package/pipeline/multi-agent-refs/phases/phase-7-report.md

@@ -129,7 +129,7 @@ The Progress flag values come from `state.flags`:
 | `codeConnect`    | Code Connect   |
 | `wiki`           | Wiki           |
 
-Each value is `true` (🟢), `"yellow"` (🟡), or `false`/missing (⚪). Phase 3 / 5 / 6 are responsible for setting these honestly  -  Phase 7 only mirrors what's already in state.
+Each value renders as `done` (`true`), `partial` (`"yellow"`), or `pending` (`false`/missing). Phase 3 / 5 / 6 are responsible for setting these honestly  -  Phase 7 only mirrors what's already in state.
 
 **Hard rule (per `$HOME/.claude/multi-agent-refs/channels/issue-comment.md`):** never run only one of the two actions. The comment is the human-readable audit; flags are the machine-readable status. Either both or neither.
 

package/pipeline/scripts/render-work-summary.sh

@@ -22,9 +22,9 @@
 #   **Task**: <jiraId>  |  **Branch**: <branch>  |  **Base**: <base>  |  **PR**: #<N>
 #
 #   #### Scope delivered
-#   - ✅ T1 <title>
-#   - ✅ T2 <title>
-#   - ⏳ T3 <title> (deferred  -  rationale)
+#   - [done] T1 <title>
+#   - [done] T2 <title>
+#   - [pending] T3 <title> (deferred  -  rationale)
 #
 #   #### Changed files (<N> files · +<ADD> / -<DEL>)
 #   - `path/a.ext`  (+12 / -4)
@@ -34,7 +34,7 @@
 #   - <A> accepted · <D> deferred · <R> rejected · approved=<bool>
 #
 #   #### Phases
-#   - 0 Init ✅ · 1 Analysis ✅ · 2 Planning ✅ · 3 Dev ✅ · 4 Review ✅ · 5 Test ✅ · 6 Commit ✅ · 7 Report ▶
+#   - 0 Init done · 1 Analysis done · 2 Planning done · 3 Dev done · 4 Review done · 5 Test done · 6 Commit done · 7 Report active
 #
 # Exit codes: 0 = rendered, 2 = missing state (caller should skip section).
 
@@ -176,11 +176,11 @@ if [ -n "$TRACKER_FILE" ]; then
     | map(. as $i |
         ($labels[$i | tonumber]) as $label |
         ($ph[$i] // {}) as $p |
-        (if   $p.status == "completed"   then "✅"
-         elif $p.status == "in_progress" then "▶"
-         elif $p.status == "failed"      then "❌"
-         elif $p.status == "skipped"     then "⏭"
-         else                                  "·" end) as $mark |
+        (if   $p.status == "completed"   then "done"
+         elif $p.status == "in_progress" then "active"
+         elif $p.status == "failed"      then "failed"
+         elif $p.status == "skipped"     then "skipped"
+         else                                  "pending" end) as $mark |
         "\($label) \($mark)")
     | join(" · ")
   ' "$TRACKER_FILE" 2>/dev/null || echo "")
@@ -223,16 +223,22 @@ if [ -n "$DIFF_IN" ]; then
   fi
 fi
 
-# Task list with ✅ / ⏳ marks. plan-todos.schema.json's todo items carry
-# `.task` (not `.title`/`.subject`) and a status enum of
+# Task list with [done] / [pending] marks. plan-todos.schema.json's todo items
+# carry `.task` (not `.title`/`.subject`) and a status enum of
 # pending|in_progress|completed|skipped|failed (not "done"/"deferred") -
-# the old check here never matched real data, so every todo rendered ⏳.
+# the old check here never matched real data, so every todo rendered pending.
+#
+# The marks are words, not check/hourglass glyphs. This summary is section 1 of
+# the Jira comment, and channels/jira.md bans decorative glyphs in a comment
+# body while this renderer was filling it with them. Words also survive every
+# adapter unchanged: `- [x] ` is rewritten to a numbered list by the Jira
+# markdown->wiki conversion, which would have dropped the distinction entirely.
 tasks_block=""
 if [ "$(jq 'length' <<< "$state_tasks")" != "0" ]; then
   tasks_block=$(jq -r '
     .[] |
     "- " +
-    (if (.status // "pending") == "completed" then "✅ " else "⏳ " end) +
+    (if (.status // "pending") == "completed" then "[done] " else "[pending] " end) +
     (.id // "") +
     (if (.id // "") != "" then " " else "" end) +
     (.task // "(untitled)")

package/pipeline/scripts/update-issue-progress.sh

@@ -82,7 +82,7 @@ if [ "$TASK_ID" = "--rewrite" ]; then
     echo "usage: update-issue-progress.sh --rewrite <body-file>" >&2
     exit 64
   fi
-  rewrite_progress_body "$(build_progress_block "⚪" "⚪" "⚪" "⚪")" "$BODY_IN"
+  rewrite_progress_body "$(build_progress_block "pending" "pending" "pending" "pending")" "$BODY_IN"
   exit 0
 fi
 
@@ -122,9 +122,9 @@ F_WIKI=$(jq -r '.flags.wiki          // false' "$AGENT_STATE")
 # Each flag may be: true | false | "yellow" (validated against older impl).
 glyph_for() {
   case "$1" in
-    true)   echo "🟢" ;;
-    yellow) echo "🟡" ;;
-    *)      echo "⚪" ;;
+    true)   echo "done" ;;
+    yellow) echo "partial" ;;
+    *)      echo "pending" ;;
   esac
 }