diff --git a/packages/producer/tests/distributed/png-sequence/meta.json b/packages/producer/tests/distributed/png-sequence/meta.json
index d52b9f66d..6d3e78faa 100644
--- a/packages/producer/tests/distributed/png-sequence/meta.json
+++ b/packages/producer/tests/distributed/png-sequence/meta.json
@@ -1,6 +1,6 @@
 {
   "name": "Distributed: png-sequence",
-  "description": "60-frame composition (2s @ 30fps) with transparent background, text, and a rotating SVG icon. Output is a directory of zero-padded RGBA PNGs; the assemble path merges chunk frame directories rather than concat-copying mp4 files. renderConfig.chunkSize=15 produces N=4 chunks, exercising the per-frame state continuity across chunk seams that distinguishes the assemble path's directory-merge from mp4's concat-copy.",
+  "description": "60-frame composition (2s @ 30fps) with transparent background, text, and a rotating SVG icon. Output is a directory of zero-padded RGBA PNGs; the assemble path merges chunk frame directories rather than concat-copying mp4 files. renderConfig.chunkSize=15 produces N=4 chunks, exercising the per-frame state continuity across chunk seams that distinguishes the assemble path's directory-merge from mp4's concat-copy. maxFrameFailures=0 makes this a strict byte-identity gate; the upstream byte sources are Chrome's CDP screenshot output and libpng's deflate, so a Chromium or zlib bump in Dockerfile.test will produce identical pixels but different bytes — the failure mode on a Chrome version bump is 'regenerate baselines via docker:test:update', not 'investigate regression'.",
   "tags": ["distributed", "png-sequence", "alpha"],
 
   "minPsnr": 30,