Verify BONanza raw Gist content after publish

[maghuro]

Problem

The Gist API can report a successful update while the public raw URL used by Tampermonkey still serves an older cached revision for a short period.

That happened with v1.5.11: the workflow generated and published a 1.5.11 .meta.js, but the raw .meta.js URL was still observed serving the previous version.

Change

After publishing both files, the workflow now:

• fetches the exact public raw URLs used by Tampermonkey
• requests revalidation with Cache-Control: no-cache and Pragma: no-cache
• compares the raw bytes against the just-built .user.js and generated .meta.js
• retries briefly if the raw endpoint is still stale
• fails loudly if the public raw content never catches up

This makes the public update path, rather than only the Gist API response, the final publication check.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.