… fail

`gh api graphql -f variables="$variables"` does not parse the value as
JSON; gh forwards it as a string and GitHub responds with the misleading
`Variable $input of type CreateCommitOnBranchInput! was provided invalid
value` instead of accepting the request. The `supported-integrations-push`
job has been silently broken since it landed; the most recent failure is
run 25309510001 on PR #8246. The same broken pattern lives in
`update-3rdparty-licenses`, where the push step rarely fires so nobody
noticed.

Build the full `{query, variables}` body with `jq -nc` and pipe it to
`gh api graphql --input -`. Reproduced locally on gh 2.89 that the new
pattern returns proper `NOT_FOUND` / `STALE_DATA` errors when the SHA
doesn't match, instead of the type-validation noise.

Drive-by: `update-3rdparty-licenses` also had `jq -c` instead of
`jq -nc`, which silently produces empty output on a runner since there
is no piped stdin — a second latent bug in the same shell snippet. The
new pattern uses `-nc` everywhere, so the two workflows stay in lockstep.

… fail

`gh api graphql -f variables="$variables"` forwards the value as a
string instead of parsing it as JSON; GitHub returns the misleading
`Variable $input ... was provided invalid value`. Latest failure: run
25309510001 on PR #8246. The same pattern lives in
`update-3rdparty-licenses`; that job's push step rarely fires so nobody
noticed.

Drive-by fix: `update-3rdparty-licenses` also had `jq -c` instead of
`jq -nc`, silently producing empty output on a runner with no stdin.

#8252)

`gh api graphql -f variables="$variables"` forwards the value as a
string instead of parsing it as JSON; GitHub returns the misleading
`Variable $input ... was provided invalid value`. Latest failure: run
25309510001 on PR #8246. The same pattern lives in
`update-3rdparty-licenses`; that job's push step rarely fires so nobody
noticed.

Drive-by fix: `update-3rdparty-licenses` also had `jq -c` instead of
`jq -nc`, silently producing empty output on a runner with no stdin.

#8252)

`gh api graphql -f variables="$variables"` forwards the value as a
string instead of parsing it as JSON; GitHub returns the misleading
`Variable $input ... was provided invalid value`. Latest failure: run
25309510001 on PR #8246. The same pattern lives in
`update-3rdparty-licenses`; that job's push step rarely fires so nobody
noticed.

Drive-by fix: `update-3rdparty-licenses` also had `jq -c` instead of
`jq -nc`, silently producing empty output on a runner with no stdin.