Problem
The v2 platform conformance authority correctly advances the machine-readable suite from version 35 to version 36 when the exact Rust artifact changes to 2.0.0-rc.4. The architecture narrative, however, now says suite version 33 introduced the current rc.4 pin. Suite 33 originally bound a different product-train tuple, so later train bumps are retroactively changing what the older suite version is documented to mean. Consumers cannot reliably map a recorded conformance suite version to the exact artifact tuple it required.
Acceptance criteria
- Attribute the
2.0.0-rc.4 artifact requirement to suite version 36.
- Preserve an accurate immutable account of earlier suite-version bindings, or rephrase the narrative so a current tuple is not attributed to an older version.
- Add a focused guard that prevents future product-train advances from silently rewriting the artifact identity attributed to a prior suite version.
- Keep the machine-readable suite version, digest, and current artifact tuple aligned.
Delete when
Delete when every version-specific artifact claim in the conformance documentation identifies the suite version that introduced it and automated coverage rejects future historical drift.
Problem
The v2 platform conformance authority correctly advances the machine-readable suite from version 35 to version 36 when the exact Rust artifact changes to
2.0.0-rc.4. The architecture narrative, however, now says suite version 33 introduced the currentrc.4pin. Suite 33 originally bound a different product-train tuple, so later train bumps are retroactively changing what the older suite version is documented to mean. Consumers cannot reliably map a recorded conformance suite version to the exact artifact tuple it required.Acceptance criteria
2.0.0-rc.4artifact requirement to suite version 36.Delete when
Delete when every version-specific artifact claim in the conformance documentation identifies the suite version that introduced it and automated coverage rejects future historical drift.