ci: read the Context7 error field with jq

[cardmagic]

Same fix as the review feedback on cardmagic/solid-objects-js#65. The too-early check in the Context7 refresh workflow matched the exact string "error":"too-early", so valid JSON with other spacing would fail the job instead of skipping. The workflow now reads the field with jq -e '.error == "too-early"'.

Validation

• actionlint passes.
• On four sample bodies, grep missed {"error": "too-early"} and jq skipped it. Both still fail on another error and on a body that is not JSON.
• Against the live API, the workflow script exits 0 with the notice.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Workflow script uses a different tool to parse JSON.

The PR appears safe to merge.

What we checked:

• Other errors still fail: The skip requires HTTP 400 and an error value equal to "too-early". A different value or invalid JSON leaves the job on its failure path.

Summary

The workflow now reads the Context7 error field with jq instead of matching exact text.

• HTTP 400 responses with "error": "too-early" skip successfully, regardless of JSON spacing.
• Other errors still fail the job.
• No actionable issues found.

_{Reviews (1) · Last reviewed commit: "ci: read the Context7 error field with j..." · Reviewed by Greptile}