Checkpoint web parity through Chromium input tasks
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

This commit is contained in:
mes123456
2026-08-19 10:39:03 -04:00
parent 5a11045ca5
commit 380cbed4ff
634 changed files with 41862 additions and 212 deletions

24
docs/status/M13-04D.md Normal file
View File

@@ -0,0 +1,24 @@
# M13-04D Status
status: done
task: server job network policy
updated: 2026-08-19 America/New_York
enablingTask: false
parityStateChange: false
Server jobs default to `DENY`. Only an explicitly declared canonical HTTPS or loopback origin is
`ALLOWED`; missing, undeclared, credential-bearing, path-bearing, public HTTP and invalid origins
return `SERVER_NETWORK_DENIED` or `SERVER_NETWORK_POLICY_INVALID`. Execution remains `DISABLED`.
Evidence: `node --test web/tests/unit/server-job-network-policy.test.mjs` 2/2;
`npm --prefix web run test:server-job-network-policy` passed; checker output
`server-job-network-ok default=DENY declaredOrigin=ALLOWED missing=SERVER_NETWORK_DENIED undeclared=SERVER_NETWORK_DENIED execution=DISABLED next=M13-04E`;
typecheck, lint and `git diff --check` passed.
Artifact hashes: protocol `0dc3698383fbfa511bebfeca41504c7c04a8302d47168cfae94f01f2a11a316c`,
checker `6f3e9cd9f988313863345f392036e6dbb522102c969197034800f419e497ad92`, unit
`c0ba10ccd2fb6ec8878a1b4a54bc6a12e49d35818566e0d55ef307779e8c8b77`, report
`37bcba2666e8c76c2e07d23e285737004affbb0372ec6dd84bb6802dba551527`, manifest
`11ce246597e3321b346ed4fed00edba22708d97250163d332d7ba8a003d8849a`.
Next task: `M13-04E`, fixed Blender background/factory-startup runtime identity.