What problem does it solve? In the "Armado en México" site, the client store hydrates from the D1 database, which overrides the seed data shipped in the code. Publishing changes to data.js or DEFAULT_PAGES alone leaves returning visitors seeing the stale catalog stored in D1, so fixes in the repo never reach production until D1 is reseeded. ## Core Features & Use Cases - Dry-run diff: Compares the code-derived catalog against what D1 currently serves, showing sizes, counts, and marker strings without writing anything. - Safe reseed: Writes the code-derived domain (armas or pages) to production D1 with a single atomic parameterized UPDATE through the Cloudflare D1 query API. - Admin-edit protection: Warns about ids that exist only in D1 (possible admin-created entries) that would be lost by reseeding. - Use Case: After publishing thirteen new firearm entries to data.js, run the script to discover production still serves the old count, then apply the reseed and verify D1 matches the code. ## Quick Start Ask the AI to run the sincronizar-d1 reseed script for the armas domain in dry-run mode first, review the diff, and then apply it to D1 after your confirmation.