Reference wrangler deploy wipes page routes

wrangler deploy for the Links edge Worker silently deletes the per-page Cloudflare routes that get created dynamically via the API when a page is published (discovered during the 2026-07-12 go-live deploy: a live page briefly 404'd right after deploy).

Why: Wrangler's route management in wrangler.toml only tracks the routes declared in config; any routes added out-of-band via the Cloudflare API (one per published page) aren't in wrangler's model, so a deploy treats them as drift and removes them.

How to apply: Any future deploy of the Links edge Worker MUST be followed by running scripts/forge_links_routes_reconcile.py to restore all published pages' routes, and purge the cache. This is now a required post-deploy step in the runbook, not optional. Wildcard route patterns were also added to wrangler.toml to reduce (not eliminate) the blast radius. See Link In Bio module.

[auto-memory session c0fc2a98-0158-47cc-aa62-ec9cf35e5e4b, confidence 0.85, mode direct]

Auto-memory addendum 2026-07-12T22:03:40.260638¶

wrangler deploy for the Links Edge Worker silently deletes the per-page routes that publishing created, which briefly took a live page (/secretdrop) offline during the v3 go-live deploy on 2026-07-12.

Why: Wrangler's route config in wrangler.toml doesn't know about routes the API added dynamically for published pages, so a deploy overwrites/clears them.

How to apply: Any time the Links Edge Worker is deployed, immediately run scripts/forge_links_routes_reconcile.py afterward to restore all published pages' routes. This is now a required post-deploy step in the runbook, alongside wildcard route patterns in the Worker config as a partial mitigation. Related: [[reference_links_module]], [[reference_links_publish_live_dev_leak]].

[auto-memory session c0fc2a98-0158-47cc-aa62-ec9cf35e5e4b, confidence 0.85]