Workflow 2.5.13 rejects malformed canonical version-marker bounds before replay consumes or skips a retained marker. Missing or non-integer bounds, inverted ranges and a recorded version outside its recorded bounds fail explicitly. Valid historical duplicates keep their positions and clocks, and compatible patch, version and deprecation helpers retain the same numeric decision with their own result projections.
This compatible correction is based on published 2.5.12. The production change is limited to VersionResolver and VersionDecisions, with unchanged marker and command wire shapes. It excludes later main/Nexus work. Existing retained histories and shared fixture cohorts remain unchanged.
Source qualification: PR #768, full stable run 38335116238, 3,862 unit tests / 49,805 assertions, v2 line coverage 93.49%, all MySQL/PostgreSQL/MariaDB and Laravel 9–13 source profiles passed. The committed conformance mirror matches public suite 47 and its pinned protocol resolver digests. Main correction #767 and contract #744 provide the implementation and agreed semantics.
Published-package verification and affected consumer rollout receipts are tracked in #744. A new library tag does not update pinned Server images or native/shared qualification. Broader #744 coverage and #747/#748 remain separate work.