Newly-added PDF assets 404 on the live site (older PDFs serve fine)

[Jesse-Sawa]

Two PDFs I added return 404 on my live site, even though they're committed, pushed, and valid. An older PDF in the same folder serves fine — so it's not my links or paths.

Audits page (where the download buttons live): https://docs.predicate.io/v2/essentials/audits

All three use identical <a href="/security/…pdf" download> markup, but only one loads:

File (direct link)	Status
cantina_2025.pdf	200 ✅ serves as PDF
app_compliance_evm.pdf	404 ❌ served as text/plain
app_compliance_solana.pdf	404 ❌ served as text/plain

It's not a stale cache — the two broken URLs still 404 with a cache-busting query string (?cb=123), straight from the origin. The audits page itself returns 200, so the deploy is otherwise healthy; these two assets just never get served.

The files are fine on my end:

• Committed and pushed to main (HEAD == origin/main)
• Valid PDFs (%PDF-1.7, 287 KB / 250 KB)
• Already tried changing their filenames to force a CDN refresh — no change

Downstream effect: because the links use the download attribute, the browser downloads the 404 page and, since it's text/plain, saves it as app_compliance_evm.pdf.txt. So to a user, the PDF appears to "download as a .txt".

Looks like the same class of issue as #5181, which you fixed server-side. Can you republish/repair the static assets for this project?