Checkpoint web parity through Chromium input tasks
This commit is contained in:
30
docs/status/M13-05H.md
Normal file
30
docs/status/M13-05H.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# M13-05H Status
|
||||
|
||||
status: done
|
||||
task: script audit record integrity
|
||||
updated: 2026-08-19 America/New_York
|
||||
enablingTask: false
|
||||
parityStateChange: false
|
||||
|
||||
## Scope
|
||||
|
||||
The production scripting audit protocol now has an independent integrity gate. Two default-deny audit
|
||||
records are validated with strictly increasing ISO timestamps, contiguous sequence numbers, unique request
|
||||
IDs, canonical entry digests and a continuous previous-entry hash chain. Replay, time reversal, sequence
|
||||
mutation, entry digest mutation and chain mutation all return `SCRIPT_MANIFEST_INVALID`; execution remains
|
||||
disabled.
|
||||
|
||||
## Evidence
|
||||
|
||||
- `npm --prefix web run test:script-audit-integrity` passed 2 unit tests and the checker.
|
||||
- Checker output: `script-audit-integrity-ok entries=2 sequence=1,2 requestIds=unique time=ordered chain=true replay=SCRIPT_MANIFEST_INVALID tamper=3 execution=DISABLED next=M14-01A`.
|
||||
- `git diff --check` passed.
|
||||
|
||||
## Next Task
|
||||
|
||||
`M14-01A`: freeze the current Chromium release, engine and archive hashes.
|
||||
|
||||
## Rollback
|
||||
|
||||
Remove the audit integrity checker/unit, report, manifest, package command and this status entry; restore
|
||||
`M13-05G` as the queue tail.
|
||||
Reference in New Issue
Block a user