ci: treat a too-early Context7 refresh as a skip

[cardmagic]

Why

The first run of the Context7 refresh workflow from #64 failed on main: curl timed out after 60 seconds with no response. Later calls returned HTTP 400 {"error":"too-early","message":"Too early to refresh the project. Last update was 0 days ago. Minimum 10 days required between updates."}. Context7 limits how often one library refreshes, so the workflow would fail on most pushes to main.

What changes

• The request allows 180 seconds for a response and prints the body.
• A too-early answer ends the job with a workflow notice instead of a failure.
• Any other non-200 answer still fails the job.

Validation

• actionlint and Prettier pass.
• Against the live API, the old script exited 56 on the too-early answer. The new script, extracted from the workflow file, exits 0 with the notice.

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Changes how the build system handles a third-party API call.

The PR appears safe to merge; the latest commit fixes the JSON spacing issue without weakening the error check.

What we checked:

• Other errors still fail: The skip requires HTTP 400 and an error value of too-early. Other responses reach exit 1.

Summary

The workflow allows 180 seconds for the refresh request, prints the response, and skips HTTP 400 responses whose error is too-early.

• The latest commit uses jq instead of matching raw text, fixing the previous spacing issue.
• No new actionable issues or repository-rule violations were found.

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

[cardmagic]

@greptileai Please review the latest commit 8362900. It reads the error field with jq, as suggested, so harmless JSON spacing no longer fails the job.