{"version":"2.1.219","anchor":"workshop-artifacts-get-a-parse-and-serialize-fixed-point-che","canonical_anchor":"workshop-artifacts-get-a-parse-and-serialize-fixed-point-che","heading":"Workshop artifacts get a parse and serialize fixed-point check at publish time","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/workshop-artifacts-get-a-parse-and-serialize-fixed-point-che","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Workshop artifacts get a parse and serialize fixed-point check at publish time\n\nWorkshop artifacts that would silently mutate on republish are now blocked at publish time.\n\n**What**\n\nPages the verifier classifies as a workshop surface are re-parsed and re-serialized before publishing, and the publish is refused if the round trip changes anything. This catches artifacts that would silently mutate on every decision confirm, since each confirm republishes the page.\n\n**Details**\n\n- two checks run: the round-tripped page must still pass the strict contract, and a second round trip must produce byte-identical output\n- two new violation rules, `reparse-divergence` and `reparse-not-fixed-point`, block the publish and point at the first divergence\n- only reached for pages that verify as a workshop surface; other pages are unaffected\n\n**Evidence**\n\n`reparse-not-fixed-point`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}