Migration guides#
Level: Expert
You will: move a reproducible run or configuration between package
versions and verify compatibility before comparing results.
Before you start: the Compatibility policy.
Services: None.
FraudTwin treats generated output identity and public schemas as compatibility boundaries. Upgrade notes belong here when a release changes a public API, configuration field, output contract, benchmark pack, or reproducibility rule.
Current release#
The current documentation and API reference describe the package version named in the project metadata. Use the version selector to compare examples against another release and consult the changelog for feature-level notes.
When upgrading, validate an existing configuration, regenerate a bounded fixture, and compare its manifest and schema fingerprints before adopting a new benchmark result.
Next#
Review Release evidence before publishing the upgraded package or comparing new benchmark output.