Checkpoint web parity through Chromium input tasks
This commit is contained in:
38
docs/status/M13-04H.md
Normal file
38
docs/status/M13-04H.md
Normal file
@@ -0,0 +1,38 @@
|
||||
# M13-04H Status
|
||||
|
||||
status: done
|
||||
task: stable server process fault codes
|
||||
updated: 2026-08-19 America/New_York
|
||||
enablingTask: false
|
||||
parityStateChange: false
|
||||
|
||||
## Scope
|
||||
|
||||
Timeout, bounded-memory OOM, signal termination and non-zero exit are converted to stable server error
|
||||
codes. Classification precedence is cancellation, timeout, OOM, signal, then non-zero exit. Failed receipts
|
||||
keep the base/current revision equal, set `publish=false`, and expose no internal process details. Execution
|
||||
remains `DISABLED`.
|
||||
|
||||
## Evidence
|
||||
|
||||
- `npm --prefix web run test:server-job-fault-codes` passed 3/3 unit tests and the checker.
|
||||
- Checker output: `server-job-faults-ok timeout=SERVER_JOB_TIMEOUT oom=SERVER_JOB_OOM signal=SERVER_JOB_SIGNAL exit=SERVER_JOB_EXIT_FAILED revisionPreserved=1 publish=0 execution=DISABLED next=M13-04I`.
|
||||
- `git diff --check` passed.
|
||||
|
||||
## Artifact Hashes
|
||||
|
||||
- parent manifest: `7103a25ec7eb4a1c7f0d9f7acfb5ed30da32c87d512d6f9d53e081db275f7b89`
|
||||
- protocol: `858360b4468a7b6cf796fc83a1627ba18626b61a0799f83531de996ea374519b`
|
||||
- checker: `cb67246ef3df111525ca5e14af0546154ea2beee930b9840ad4ac7e2ebbb91ec`
|
||||
- unit: `3551e28d78e5069c3d97eabcacac824bf142f54fdcb3ad4904668909af1cc545`
|
||||
- package: `77bae66fd3885e36d2ead6f261754724144e5f51fafc5ccad9863dfc8e5ab548`
|
||||
- report: `01999232f926496909fc9ef072e19aadb688822d3f9d7e03b42871ac5d54a0f6`
|
||||
|
||||
## Next Task
|
||||
|
||||
`M13-04I`: verify source/settings/build/output hashes before OPFS commit.
|
||||
|
||||
## Rollback
|
||||
|
||||
Remove the fault classifier, unit/checker, report, manifest, package command and this status entry; restore
|
||||
`M13-04G` as the queue tail.
|
||||
Reference in New Issue
Block a user