Fix escaped markdown in spec-change-impact PR comments

[jeremy]

Summary

• Read comment body directly from $RESPONSE_FILE instead of through a shell variable, which was mangling markdown (literal **, broken lists)
• Create path: --body "$VAR" → --body-file "$RESPONSE_FILE"
• Update path: echo "$VAR" | jq -Rs . → jq -Rs . "$RESPONSE_FILE"

Test plan

• Push a change that touches spec/ or openapi.json and confirm the PR comment renders markdown correctly (bold, lists, checkboxes)

---

Summary by cubic

Fixes mangled markdown in Spec Change Impact PR comments by reading the comment body from the response file instead of a shell variable. Bold text, lists, and checkboxes now render correctly.

• Bug Fixes
  • Update path: use jq to read the file as a raw string in the GraphQL mutation: jq -Rs . "$RESPONSE_FILE".
  • Create path: use --body-file "$RESPONSE_FILE" instead of --body "$COMMENT_BODY".

^{Written for commit 386a321. Summary will update on new commits.}

[github-actions]

Sensitive Change Detection (shadow mode)

This PR modifies control-plane files:

• .github/workflows/ai-labeler.yml

Shadow mode — this check is informational only. When activated, changes to these paths will require approval from a maintainer.

[cubic-dev-ai]

No issues found across 1 file

[Copilot]

Pull request overview

This PR fixes markdown rendering in the “Spec Change Impact” PR comment posted by the spec-impact job by avoiding shell-variable/echo mangling and instead posting/updating directly from the generated response file.

Changes:

• Switch new-comment creation from gh pr comment --body "$VAR" to gh pr comment --body-file "$RESPONSE_FILE".
• Switch comment updates from piping a shell variable into jq to reading the body directly from the response file via jq -Rs . "$RESPONSE_FILE".

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.