Existing review-host routing recovery
Observed at2026-10-01T23:23UTC: the existing direct comment worker returnsHTTP429 with Cloudflare1027. The same-origin proxy returnsHTTP200 HTML fallback, not valid comment JSON. No successful persistence is claimed.
The existing mirror had no _routes.json. The existing shared _worker.js has exactly three functions: root redirect, review-comment proxy and review-image proxy. Every other request returns env.ASSETS.fetch(request). Cloudflare confirms that static requests otherwise invoke Functions by default and can be excluded with routing configuration. Official routing documentation. Official quota/reset documentation.
Recovery: restrict function invocation to root and the two existing proxy path families. All static documents/media continue to serve as static assets. No backend code, record, access layer, account plan or paid subscription changes. This reduces unnecessary function requests. It does not itself reset the existing daily quota or prove which traffic exhausted it.
The publisher locks the shared mirror, backs up the exact changed routes and global generated files, records that the previously absent _routes.json must be removed for restoration, preserves all unrelated content hashes and checks the live manifest before deployment. A failed deployment restores the exact narrow backup. Later deployed readback must verify ordinary route bytes, proxy JSON, existing IDs/history and a disposable/intercepted persistence fixture.