Checkpoint web parity through Chromium input tasks

docs/status/M13-04I.md

@@ -0,0 +1,38 @@
+# M13-04I Status
+
+status: done  
+task: server result hash binding and atomic OPFS handoff  
+updated: 2026-08-19 America/New_York  
+enablingTask: false  
+parityStateChange: false
+
+## Scope
+
+Server output publication requires request identity plus source, settings and Blender build SHA-256 values
+to match the expected request. Output bytes are staged, read back, atomically renamed to the request result
+path, and read back again before a committed receipt is returned. Tampered output, identity drift, partial
+stage and quota failures remain unpublished. Execution remains `DISABLED`.
+
+## Evidence
+
+- `npm --prefix web run test:server-job-result-binding` passed 2/2 unit tests and the checker.
+- Checker output: `server-job-result-ok source=bound settings=bound build=bound output=verified tamper=blocked quota=blocked atomic=1 execution=DISABLED next=M13-04J`.
+- `git diff --check` passed.
+
+## Artifact Hashes
+
+- parent manifest: `ba530ddff6e6fdd84057444ce757fad05a30d825a5915abebe2d5910a689af7f`
+- protocol: `ecf3bddef53e2766dcc055ec027b04c14e3d884132c7fdea476663617364ad86`
+- checker: `b0fbffd2937ab20e72d337bb5ff63ccf188ccf8a939d8ccc8b4878d80c9a4a19`
+- unit: `c5538798aa6263b8a1c20270a019f8b4fb8b176b141a6411b72aad21a457bfd0`
+- package: `5d269d4e5ff4385d919c0ee33f996dcb814e3e415da25dbf3b4dbdc3312fbe24`
+- report: `ec63faeba35a641a22c3b3a69757bd37e8e9acaa1dda11a64faf7bed80439784`
+
+## Next Task
+
+`M13-04J`: idempotent request retry and conflicting-result isolation.
+
+## Rollback
+
+Remove the result-binding protocol, unit/checker, report, manifest, package command and this status entry;
+restore `M13-04H` as the queue tail.