RhenCloud 1a0500b812 fix: prevent data loss in routes, fragments, and group operations ... Found and fixed multiple critical bugs with similar patterns: 1. routeStatements() used DELETE FROM d1_routes before re-inserting - Could cause data loss if interrupted or if logic changes - Now uses DELETE with WHERE clause + INSERT...ON CONFLICT (upsert) 2. saveFragments() used DELETE FROM d1_fragments before re-inserting - Same pattern as routes, fixed with targeted deletes + upsert - Added loadFragments() call to determine what to delete 3. adminGroupRename() didn't update fragment groupId - When renaming a group, fragments were left pointing to old groupId - Now updates fragments alongside routes, secrets, and invites All changes follow the same safe pattern: - Load existing data to identify what needs deletion - Delete only removed items with WHERE clauses - Use INSERT...ON CONFLICT DO UPDATE for upserts - Never use bare DELETE FROM table Testing: All 339 tests pass.		2026-09-10 22:35:43 +08:00
..
config-store.ts	fix: prevent data loss in routes, fragments, and group operations	2026-09-10 22:35:43 +08:00
d1.ts	chore: auto-fix lint & formatting [skip ci]	2026-08-17 07:51:36 +00:00
payload.ts	chore: auto-fix lint & formatting [skip ci]	2026-08-17 07:51:36 +00:00