Checkpoint web parity through Chromium input tasks
This commit is contained in:
22
docs/status/M13-04E.md
Normal file
22
docs/status/M13-04E.md
Normal file
@@ -0,0 +1,22 @@
|
||||
# M13-04E Status
|
||||
|
||||
status: done
|
||||
task: pinned Blender server startup
|
||||
updated: 2026-08-19 America/New_York
|
||||
enablingTask: false
|
||||
parityStateChange: false
|
||||
|
||||
Pinned Blender 5.2.0 LTS now passes a real server preflight using only `--background`,
|
||||
`--factory-startup`, the fixed `tools/web/server-job-startup.py`, and a fixed business argument.
|
||||
The structured receipt confirms background mode, runtime version and argv. Execution remains
|
||||
`DISABLED`; this task does not claim result publication.
|
||||
|
||||
Evidence: `node tools/web/check-server-job-startup.mjs` output
|
||||
`server-job-startup-ok blender=5.2 background=1 factory=1 userPrefs=0 fixedScript=1 execution=DISABLED next=M13-04F`;
|
||||
typecheck, lint and `git diff --check` passed. Artifact hashes: startup
|
||||
`c8c5b5a7a7880d4df9477a94a98e54e328baf582ade649807067f988484e1f12`, checker
|
||||
`66b2e25efe0e7455348e8f488cd0f6ebef07f916fcf6541680e7d18e4f69ab10`, report
|
||||
`c67d2972e584782d03479dbdb36dae0976074978f4ce9a48e41e7ad5aea66089`, manifest
|
||||
`a24ea87bcf305bc15d8ae70b2abd03aa16ffbd6b127d5e9da9da23617d7201cc`.
|
||||
|
||||
Next task: `M13-04F`, bounded and redacted stdout/stderr.
|
||||
Reference in New Issue
Block a user