storage-derives-counter-from-existing-nogoods
IN premise
When loading a database without the `network_meta` table (pre-fix schema), `Storage.load()` derives `_next_nogood_id` from the max ID of existing nogoods rather than defaulting to 1, enabling backward-compatible upgrades
Summary
The system handles database upgrades gracefully by looking at what nogood IDs already exist and counting from there, rather than resetting to 1 and risking ID collisions. This means older databases without the newer metadata table can be loaded safely without accidentally reusing or overwriting existing nogood identifiers.
Details
| Source | entries/2026/04/29/tests-test_nogood_id.md |