Checkpoint web parity through Chromium input tasks
This commit is contained in:
37
docs/status/M13-05G.md
Normal file
37
docs/status/M13-05G.md
Normal file
@@ -0,0 +1,37 @@
|
||||
# M13-05G Status
|
||||
|
||||
status: done
|
||||
task: fuzz crash minimization and regression capture
|
||||
updated: 2026-08-19 America/New_York
|
||||
enablingTask: false
|
||||
parityStateChange: false
|
||||
|
||||
## Scope
|
||||
|
||||
The deterministic runner replays 16 mutations in each of the blend, image, font, node-graph and script
|
||||
manifest domains using seed `1511506142`. Every case returns one structured `ACCEPTED` or `REJECTED`
|
||||
receipt; a non-zero runner exit first writes a replayable corpus sample. This run completed 80 cases with
|
||||
zero crashes and an empty minimized corpus. Script execution remains disabled.
|
||||
|
||||
## Evidence
|
||||
|
||||
- `npm --prefix web run test:fuzz-regression` passed.
|
||||
- Checker output: `fuzz-regression-ok seed=1511506142 cases=80 crashes=0 corpus=0 execution=DISABLED next=M13-05H`.
|
||||
- `git diff --check` passed.
|
||||
|
||||
## Artifact Hashes
|
||||
|
||||
- parent manifest: `34043df0515f4b422a2b265d38978dd3c7f21acd12753c99f9a50f9b23f8bd60`
|
||||
- runner: `a4d5d1b743b454705b1c3a257f1f36d1fea8abd77442e11fb1fec9e2905a3f79`
|
||||
- checker: `55c8fa3776b22eb3f2e2ffd1629f0092384df30ef3913699a1ba93b283d641d8`
|
||||
- package: `1feb509789d7f06019390bd86197bb9851cd520fd9fe310d1e29bfc3d2ef3f18`
|
||||
- report: `5eb4a5469732697be7910fded3ce34cf2898735f767d94c1abbe0dd264bcc0d9`
|
||||
|
||||
## Next Task
|
||||
|
||||
`M13-05H`: fuzz corpus replay and release-boundary exclusion.
|
||||
|
||||
## Rollback
|
||||
|
||||
Remove the fuzz runner/checker, report, manifest, package command and this status entry; restore
|
||||
`M13-05F` as the queue tail.
|
||||
Reference in New Issue
Block a user