docs: cover the reaction verb and comments --show-reactions

docs/tools/forge.md

@@ -21,7 +21,7 @@ under `issue` and `pr` parent commands — `hive-forge pr close 42`,
 refuses an issue number, which the old generic `close` couldn't). Run
 `hive-forge pr --help` / `hive-forge issue --help` for the full subcommand
 list (show/create/edit/status/merge/reviews/commits/diff/view/comment/
-comments/close/reopen/labels/assign/dependency/timeline as applicable).
+comments/close/reopen/labels/assign/dependency/reaction/timeline as applicable).
 
 The flat forms below (`close 42`, `pr-create …`, `pr-status …`, …) still work
 as **hidden back-compat aliases** during the transition and are dropped from
@@ -53,6 +53,10 @@ hive-forge issue dependency 42                # list #42's dependencies (issues
 hive-forge issue dependency 42 add 40 41      # #42 is now blocked by #40 and #41
 hive-forge issue dependency 42 remove 40      # drop the #40 dependency link
 hive-forge pr dependency 55 add 42            # same verb, PR-scoped (Forgejo shares the issue/PR index)
+hive-forge issue reaction 42                  # list #42's reactions
+hive-forge issue reaction 42 add heart        # react to #42 with :heart:
+hive-forge issue reaction 42 --comment 18042 add +1  # react to a specific comment instead
+hive-forge issue reaction 42 remove heart     # remove your own :heart: reaction
 hive-forge issue-create --title "..." --body "..."
 hive-forge issue-create --title "..." --body "..." --label area/ops --label type/bug  # repeatable
 hive-forge issue-edit 42 --title "new title"
@@ -287,6 +291,15 @@ to discover valid label names before triaging or to audit the label set.
   forge UI's dependency panel). Same-repo only, matching the web UI (no
   cross-repo dependency support). `list` (the default action) and `add`/
   `remove` all print the resulting dependency list as JSON.
+- `issue reaction <n> add <content>` / `pr reaction <n> add <content>` add
+  an emoji reaction (Forgejo's shortcode vocabulary — `+1`, `heart`,
+  `rocket`, …, same set the web UI's picker offers, not a raw emoji
+  character); `--comment <id>` targets a specific comment's reactions
+  instead of the issue/PR itself. `list`/`add`/`remove` all print the
+  resulting reaction list as JSON, same shape as `dependency`. `view`,
+  `issue`, `pr`, and `comment-show` always show a reaction summary;
+  `comments --show-reactions` adds one per comment shown (opt-in — one
+  extra request per comment, no server-side inline count).
 - Do NOT use raw `curl` for forge access -- the CLI handles auth,
   error checking, and output formatting.
 - `issue-create --label <name>` / `pr-create --label <name>` are