fix: handle multiline discussion body in GITHUB_OUTPUT (send-to-power-automate)

[Copilot]

Writing discussion.body directly to $GITHUB_OUTPUT via echo breaks when the body contains newlines — the runner parses each line as key=value and throws Invalid format '' on blank/continuation lines, aborting all downstream steps.

Changes

• toJSON() for title/body env vars — encodes newlines as \n, keeping values single-line safe for env var expansion
• Write title/body to temp files instead of $GITHUB_OUTPUT — decoded via jq -r ., bypassing the runner's line-format requirement entirely
• Build Payload reads from temp files — TITLE=$(cat /tmp/discussion_title.txt) instead of steps.inputs.outputs.title

# Before — breaks on multiline body
echo "body=$EVENT_BODY" >> "$GITHUB_OUTPUT"

# After — safe for any content
EVENT_BODY_JSON: ${{ toJSON(github.event.discussion.body) }}
...
printf '%s' "$EVENT_BODY_JSON" | jq -r . > /tmp/discussion_body.txt

Only label, number, url, author, and created_at (all guaranteed single-line) continue to use $GITHUB_OUTPUT.

Original prompt

Fix the failing GitHub Actions workflow send-to-power-automate
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 65541082228
Job URL: https://github.com/golclinics/discussions/actions/runs/22618815084/job/65541082228

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.