[rasswanth-s]

Summary

Resets the migration system to a clean start. Every protocol and versioned object in syft, syft-job and syft-dataset is back at version 0, and the code that kept older releases (up to 0.10.1) working is removed. Older clients are refused with a clear message.

Changes

• Versions reset to 0: all three protocols, their minimum supported versions, and every versioned object. Jobs live under v0/, and dataset collections use the v0 variant.
• Old versions removed: older object classes and migrations, old job and dataset layouts, and the frozen release artifacts and fixtures of earlier releases. The next release freezes protocol-0.json.
• Older releases refused clearly: a peer on an older release is reported as unsupported, and peering still completes. Logging in on an old SyftBox offers a fresh start. MIN_SUPPORTED_SYFT_VERSION is 0.10.2.
• Other compatibility code removed: pre-hash job receipts, the old folder-wide review grant, the requests/ back-fill, '@' job names, skip_job_names and other deprecated options (full list in CHANGELOG.md).
• Kept for future versions: the syft-migration framework, protocol negotiation and the release-fixture tooling. Fixture generators now run at each package's release tag, and docs/release.md lists that step.

Testing

• Every unit CI suite passes. The one failure, syft-rds test_dataset_only_mock_data_uploaded, also fails on dev.
• New tests cover refusing an unsupported peer and logging in on an old SyftBox.
• Simulated the next release: the export freezes protocol-0.json for each package and the drift checks pass. The release-fixture tests pass against fixtures generated from this code.
• Local runs: a stale setuptools build/ folder in a source checkout still holds the old history files and breaks local job runs. Remove it with rm -rf build.

Asana task