Checkpoint web parity through Chromium input tasks

2026-08-19 10:39:03 -04:00
parent 5a11045ca5
commit 380cbed4ff
634 changed files with 41862 additions and 212 deletions
--- a/docs/status/M14-04A.md
+++ b/docs/status/M14-04A.md
@@ -0,0 +1,25 @@
+# M14-04A Status
+
+status: done  
+task: Chromium GPU/memory budget device tier selection  
+updated: 2026-08-19 America/New_York  
+enablingTask: false  
+parityStateChange: false
+
+## Scope
+
+Added a bounded device-budget selector driven only by the real Chromium M14-01D identity report.
+The observed SwiftShader renderer and unavailable WebGPU adapter select `CONSERVATIVE`; untrusted,
+missing, or fallback adapters cannot expand budgets. Fixed `CONSERVATIVE`, `BALANCED`, and `HIGH`
+limits are explicit and unknown tiers fail closed. Firefox/WebKit are excluded by the iron rule.
+
+## Evidence
+
+- `npm --prefix web run test:chromium-device-budget` passed: 3 unit tests plus the production identity
+  report checker.
+- Checker output: `chromium-device-budget-ok tier=CONSERVATIVE reason=UNTRUSTED_ADAPTER identity=3c6f898e1b6ffd39862505b8e7dde8fd29369204e1670a013859f74ccaf1c1eb execution=DISABLED next=M14-04B`.
+- `npm --prefix web run typecheck` and `git diff --check` passed.
+
+## Next Task
+
+`M14-04B`: Chromium DPR 1/1.5/2/3 canvas and raycast consistency.