Files
workinf_Blender_Wasm/docs/status/M14-01A.md
mes123456 380cbed4ff
Some checks failed
M6 deployable RC / quick (push) Has been cancelled
M6 deployable RC / chromium (push) Has been cancelled
M6 deployable RC / release (push) Has been cancelled
Checkpoint web parity through Chromium input tasks
2026-08-19 10:39:03 -04:00

33 lines
1.1 KiB
Markdown

# 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.