SaveTether test recipe

Use a test project, a new empty local output folder, and the distributed fixtures: CurrentValid.json, Previous.json, and CurrentWithCycle.json. The panel also has Load valid example and Load cycle example controls.

1. Open Tools > SaveTether. If the Tether family menu is active, use Tools > Tether > SaveTether.
2. Load CurrentValid.json and select Previous.json as the earlier release. Choose an existing local Output directory; the plugin will create a new result folder for the operation.
3. Run Review identifiers. Select result rows to inspect their evidence before acting on them.
4. Expect complete coverage: A and B are Conserved, C is Removed, and D is Added. Transient is excluded because it is not persistent. The explicit C → D proposal is accepted; it records declared intent and does not migrate data.
5. Choose Export changes. Open Report.html, Changes.csv, and Report.json in the newly created report folder. Confirm the status and coverage before sharing it.
6. Load CurrentWithCycle.json and review again. The identity diff stays the same, but A → B → A is rejected as a cycle. The review may still have complete coverage while containing a rejected mapping.
7. Only a current, complete review with no rejected mappings can use Capture release. Keep the resulting Manifest.json as the next baseline; do not reuse its release ID.

To test a first release instead, use Clear previous release and run a review with current declarations only. SaveTether does not validate your game’s real loader, inspect save files, or migrate data.