Fix reporting to jira burying pr link

Author: IgGusev

.claude/commands/jira-resolve.md

@@ -12,10 +12,12 @@ Run the **RESOLVE** procedure in `.claude/skills/jira/SKILL.md` for `$ARGUMENTS`
 - Resolve the key from the argument, or infer it from the current branch's `DOCS-XXXX` prefix.
 - Stop if the ticket is already in Review/Closed (idempotent).
 - Find the PR link (`gh pr view` or the `DOCS-XXXX` commit on `origin/main`); ask if none found.
-- Comment with the PR link (`contentFormat="markdown"`).
-- Post the **fact-check report** (found by key under `reports_dir`, grouped by space:
-  `<space>/DOCS-XXXX/report.md`) as a second Markdown comment if it exists, set its `Status:` to
-  `handed-off`, and regen `INDEX.md`; warn (and ask) if the doc ticket has no report.
+- Post **one combined Markdown comment**: the `**Docs PR:**` link pinned at the top, then the
+  **fact-check report** (found by key under `reports_dir`, grouped by space:
+  `<space>/DOCS-XXXX/report.md`) below a `---` divider if it exists. Keeping the link at the top of
+  a single comment stops the long report from pushing it out of sight. Set the report's `Status:`
+  to `handed-off` and regen `INDEX.md`; warn (and ask) if the doc ticket has no report (still post
+  the PR-link line in that case).
 - Transition to **`Review`** (match by name). This does **not** close the ticket — the reviewer
   runs `/jira-close` after merge.
 - Confirm with `Ticket / Status: Review / PR link / report posted`.

.claude/skills/jira/SKILL.md

@@ -158,28 +158,29 @@ Use when the doc PR is open and ready for editorial review. Moves the ticket to
    git log origin/main --oneline --grep="DOCS-XXXX" -1
    ```
    If none found, ask the user for the PR URL.
-4. **Comment with the PR/commit link** (Markdown):
-   ```
-   addCommentToJiraIssue(cloudId, issueIdOrKey="DOCS-XXXX",
-     commentBody="Docs PR: [<repo>#<n>](<pr-url>)", contentFormat="markdown")
-   ```
-   `contentFormat="markdown"` is required or links render as literal text.
-5. **Post the fact-check report** (the paper trail — `dev-docs/cookbook-fact-trail.md`). Read
+4. **Locate the fact-check report** (the paper trail — `dev-docs/cookbook-fact-trail.md`). Read
    `reports_dir` from `.claude/doc-sources.local.json` and find the report by key (it's grouped by
    space, so don't assume a flat path):
    ```bash
    report="$(find "$reports_dir" -type d -name 'DOCS-XXXX' -not -path '*/runs/*' | head -1)/report.md"
    ```
-   - If found, post its **full contents** as a second Markdown comment:
-     ```
-     addCommentToJiraIssue(cloudId, issueIdOrKey="DOCS-XXXX",
-       commentBody="### Fact-check report\n\n<report file contents>", contentFormat="markdown")
-     ```
-     Then update the report's header `Status:` to `handed-off` and regenerate `INDEX.md` (cookbook).
-   - If **not found**, don't fabricate one — warn the user that this ticket has no fact-check
-     report (expected from `/doc-ticket`) and ask whether to resolve without it. A doc edit with
-     no report is a gap, not a hard stop.
-   - Skip silently for tickets that aren't doc-content edits (e.g. an Epic, a tooling task).
+5. **Post one combined comment** — PR link pinned at the top, report below a divider — so the
+   `Docs PR:` line stays visible regardless of Jira's comment sort order and never gets buried
+   under the (long) report:
+   ```
+   addCommentToJiraIssue(cloudId, issueIdOrKey="DOCS-XXXX",
+     commentBody="**Docs PR:** [<repo>#<n>](<pr-url>)\n\n---\n### Fact-check report\n\n<report file contents>",
+     contentFormat="markdown")
+   ```
+   `contentFormat="markdown"` is required or the link renders as literal text.
+   - If the report was found, include its **full contents** after the divider, then update the
+     report's header `Status:` to `handed-off` and regenerate `INDEX.md` (cookbook).
+   - If **no report is found**, still post the `**Docs PR:**` line (drop the divider and report
+     section), and warn the user that this ticket has no fact-check report (expected from
+     `/doc-ticket`); ask whether to resolve without it. A doc edit with no report is a gap, not a
+     hard stop.
+   - For tickets that aren't doc-content edits (e.g. an Epic, a tooling task), post just the
+     `**Docs PR:**` line and skip the report section silently.
 6. **Transition to `Review`** (id 2) — fetch live transitions, match by name.
 7. **Confirm**: `Ticket / Status: Review / PR link / report posted (yes|no)`.
 
@@ -244,8 +245,8 @@ confirmed in chat before it is sent**.
      ```
    - **`DOCS-XXXX`** → just that ticket (`getJiraIssue` with the same `fields`). If it isn't in
      **Review**, say so and stop — there's nothing to chase.
-3. **Identify the reviewer(s)** from the comment thread. The handoff comment (`Docs PR: …`, left
-   by `/jira-resolve`) marks when review was requested; the reviewer is whoever was **@-mentioned
+3. **Identify the reviewer(s)** from the comment thread. The handoff comment (starts with
+   `**Docs PR:** …`, left by `/jira-resolve`) marks when review was requested; the reviewer is whoever was **@-mentioned
    to review** there or named in a later comment. If no reviewer is identifiable, **don't
    guess** — list the ticket as *reviewer unclear* and ask the user who to chase.
 4. **Decide whether to skip.** A reviewer has **already responded** (skip them, noting why) if