Tested caller policy: a4d1efc5f74f9ddc0cfc62fba90f76a9a3aa2f3c. The actual imported label module, compiler/linker arguments and dependencies are identified in inputs.json and the before/after manifests.

The Windows standalone WGPU build and all 32 rendering probes passed: zero invalid controls, zero candidate findings, and 12 cases whose actual ink exceeded layout advances. The unchanged true corridor has width 160 or 760; a 3-unit inset on each side leaves text budgets 154 or 754. Backplate world bounds stayed inside the fixed corridor, and painted plate/text pixels satisfied the declared one-physical-pixel halo. Coverage, actual canvas payload, integer translation and blocker-preservation controls passed. This does not turn advance bounds into ink bounds or establish a universal 3-unit overhang limit.

The original uninset policy remains rejected in its separate record. Its raw evidence was not changed or duplicated here.

Archive verification independently checked all 235 original output-manifest entries, all 7 explicit current input files, the equal dependency/native before/after inventories, and the executed binary's SHA256. pixels.zip contains all 225 original pixel-directory files, totaling 101,843,266 uncompressed bytes; every uncompressed entry's path, size and SHA256 matched output-artifacts.json. metrics/ and summary.txt provide directly readable reports. verification.json records the checks; report.json inventories this archive. The executable is identified by receipt.json and verification.json rather than copied into the repository.

Reproduce using the pinned source's build-and-run.ps1 in a new output directory, with the exact compiler, matching Iced/unicode artifacts, clang linker and native search path recorded in inputs.json. Do not overwrite either historical gate. Parent-owned local gate paths in raw receipts record what ran; remote reproduction requires its own equivalent checkout/toolchain. No rerender occurred while archiving.

Scope is these 32 strings/styles/width/zoom/DPI combinations on the recorded Windows environment, with the stated raster threshold and halo. This is not production Scene/corridor integration, a general ink-containment proof, native application acceptance, Linux verification or a release. Narrow corridors at or below the 6-unit reserve, self/reversed-message corridor choice, actual activation/frame interactions and production performance remain separate work.