Checkpoint web parity through Chromium input tasks

docs/status/M14-01A.md

@@ -0,0 +1,32 @@
+# M14-01A Status
+
+status: done  
+task: Chromium, engine and archive identity freeze  
+updated: 2026-08-19 America/New_York  
+enablingTask: false  
+parityStateChange: false
+
+## Scope
+
+The Chromium baseline is frozen at `150.0.7871.128`. The checker resolves and hashes the actual browser
+executable, validates every single/pthread engine resource against `engine-manifest.json`, and validates
+both release archives against the regenerated `RC_MANIFEST.json` and `SHA256SUMS.txt`. Execution remains
+disabled.
+
+## Evidence
+
+- `npm --prefix web run release:offline` passed deterministic binary/source rebuild twice.
+- `node tools/web/create-rc-manifest.mjs && node tools/web/check-rc-manifest.mjs` passed.
+- `npm --prefix web run test:chromium-freeze` passed with browser `150.0.7871.128`, two engine variants,
+  and two archive bindings.
+- `npm --prefix web run typecheck` passed; execution remains `DISABLED`.
+- `git diff --check` passed.
+
+## Next Task
+
+`M14-01B`: Firefox capability probe using the frozen field set.
+
+## Rollback
+
+Remove the Chromium freeze checker, report, manifest, package command and this status entry; restore
+`M13-05H` as the queue tail.