m3ultra 802879fc3e deploy: parse the CF zone id with json, not a greedy sed ... The purge silently did nothing. `sed -n 's/.*"id":"\([a-f0-9]\{32\}\)".*/\1/p'` looks right, but the zones response carries several 32-hex "id" fields (account, plan, ...) and the leading `.*` is greedy, so it returned the LAST one — a valid-looking id for the wrong object. The API then rejected the purge and the old grep-for-success check reported a bare "purge failed" with no reason. Parse with python3 (already a dep — serve.py) and surface the API's own error message when it fails. Verified end to end against the live zone: cf-cache-status HIT -> purge -> MISS -> HIT. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-25 23:27:50 +10:00
..
deploy.sh	deploy: parse the CF zone id with json, not a greedy sed	2026-07-25 23:27:50 +10:00