# C-paper-2 amendment: matched release provenance

18 October 2026

Both evidence presentations now carry the same revised SDK release assertion. The reviewed provenance identifies 0.22.1 as the first stable release after the repair whose tag contains the repair commit, with PyPI displaying matching publishing provenance for both artifacts. The repaired development source still declares 0.22.0, so that version string alone remains ambiguous. Publication, artifact-upload and review dates are kept distinct. Artifact contents and Sigstore signatures were not independently verified.

The update refines C-paper-1's earlier release-mapping unknown; the original packets remain unchanged. Six assertions still cover three development families. Five assertion bodies remain unchanged, including Microsoft date/identity caveats and incident dependence/rights limits. The two revised presentations have identical factual strings, source links and status restrictions. A local normalized-text document comparison found all six bodies equal, with no mismatches.

This is a document milestone, not a solver trial, runtime reproduction or performance result. Release provenance does not establish runtime repair success, an upgrade recommendation or execution readiness. No software was installed, empirical evaluation run or publication performed.