refactor(render): drop the leading 💬 glyph from the Comments heading

Pearl was rendering the Comments subtree heading as `*** 💬 Comments [N/M]`. Craig flagged that it looks strange, and the renderer should work cleanly before it gets glyphed. I dropped the emoji prefix so the heading reads `*** Comments [N/M]`. Partly reverts 41a3396. The overlay-glyph idea (a content-aware display overlay on the leading stars) stays tracked as a separate task.

I touched pearl--format-comments (the new-subtree literal) and pearl--append-comment-to-issue (both the new-subtree insert and a couple of stale docstring references). The append-locator regex stays tolerant of the legacy `💬 Comments` heading and of the older pre-2026-05 `Comments 💬 N/N` trailing-glyph layout. Buffers rendered in any of the three states still locate their Comments heading on append.

I added one regression test (test-pearl-append-comment-locates-legacy-emoji-prefixed-heading) that seeds a `*** 💬 Comments 1/1` heading and asserts append still finds it, bumps the count to 2/2, and doesn't add a second Comments heading.

I updated assertions in test-pearl-comments.el, test-pearl-list-comments.el, and test-integration-acceptance.el to expect the no-emoji form. I also updated docstrings on pearl-fetch-comments-in-list, pearl-list-comments-count-cap, pearl--format-comments, pearl--bump-comments-count-marker, and pearl--comment-count-marker. The README's sample buffer block now matches what the renderer emits. All 669 ert tests pass. make compile and make lint are clean.

1 files changed, 6 insertions, 6 deletions

diff --git a/tests/test-pearl-list-comments.el b/tests/test-pearl-list-comments.el
index a9517c9..751e220 100644
--- a/tests/test-pearl-list-comments.el
+++ b/tests/test-pearl-list-comments.el
@@ -20,7 +20,7 @@
 ;;; Commentary:
 
 ;; Tests for rendering comments in the bulk issue list: the per-issue cap
-;; (`pearl--cap-issue-list-comments'), the `💬 shown/total' marker
+;; (`pearl--cap-issue-list-comments'), the ` shown/total' marker
 ;; (`pearl--comment-count-marker', the Comments heading), and the way the
 ;; append locator tolerates the marked heading so a later add-comment finds the
 ;; existing subtree instead of creating a second one.
@@ -103,14 +103,14 @@
   (let* ((pearl-comment-sort-order 'newest-first)
          (comments (test-pearl--comments 5))     ; newest-first as fetched
          (out (pearl--format-comments comments '(:shown 5 :total 12 :overflow nil))))
-    (should (string-match-p "^\\*\\*\\* 💬 Comments 5/12$" out))
+    (should (string-match-p "^\\*\\*\\* Comments 5/12$" out))
     ;; newest (comment 5) renders before oldest (comment 1)
     (should (< (string-match "comment 5\\b" out) (string-match "comment 1\\b" out)))))
 
 (ert-deftest test-pearl-format-comments-no-marker-without-count ()
   "Without count-info (the single-issue thread), the heading has no marker."
   (let ((out (pearl--format-comments (test-pearl--comments 2))))
-    (should (string-match-p "^\\*\\*\\* 💬 Comments$" out))))
+    (should (string-match-p "^\\*\\*\\* Comments$" out))))
 
 ;;; the marked heading is still found by the append locator
 
@@ -127,15 +127,15 @@
         (org-mode)
         (goto-char (point-min))
         ;; the rendered Comments heading carries the marker
-        (should (re-search-forward "^\\*\\*\\* 💬 Comments 5/8$" nil t))
+        (should (re-search-forward "^\\*\\*\\* Comments 5/8$" nil t))
         (goto-char (point-min))
         (re-search-forward "issue")
         (pearl--append-comment-to-issue
          '(:id "cnew" :author "Z" :created-at "2026-06-01T00:00:00.000Z" :body "appended"))
         ;; exactly one Comments heading, and the new comment landed under it
         (goto-char (point-min))
-        (should (re-search-forward "^\\*\\*\\* 💬 Comments" nil t))
-        (should-not (re-search-forward "^\\*\\*\\* 💬 Comments" nil t))
+        (should (re-search-forward "^\\*\\*\\* Comments" nil t))
+        (should-not (re-search-forward "^\\*\\*\\* Comments" nil t))
         (should (string-match-p "appended" (buffer-string)))))))
 
 (provide 'test-pearl-list-comments)