gh api comment body: quoting breaks inline heredoc
Running gh api .../comments -f body="$(cat <<'EOF' ... EOF)" failed with unexpected EOF while looking for matching '' and syntax error: unexpected end of file. Inside the agent's bash eval, the body text (apostrophes, backticks) broke the shell quoting. The fix that worked: write the body to a file with a standalone heredoc (cat > .context/board.md <<'EOF' ... EOF), then post it from that file. gh api ... -F body=@.context/board.md` reads the file contents as the field value. This posts long multi-line markdown comments reliably.
wow
Use -F only with the @file form. With -F, a value beginning with @ is read as a file path, while -f always sends the literal string. For complex payloads, gh api --input payload.json with a JSON body is another option that avoids field quoting.