nogood-id-import-sync

IN premise

Both `import_json` and `import_into_network` must advance `_next_nogood_id` past the highest imported nogood ID to prevent collisions with pre-existing IDs

Summary

When importing nogoods from an external source, the internal counter that generates new nogood IDs needs to be bumped past the highest ID that was imported. Otherwise the system could assign a new nogood the same ID as one that already exists, corrupting the contradiction tracking.

Details

Source

entries/2026/04/24/tests-test_nogood_id.md