Assert terminal E2E chrome roles

tools/TERMINAL_E2E.md

@@ -15,20 +15,25 @@ Matrix input profiles:
 
 Artifact roles:
 
-- `manifest.tsv`: stable scenario facts, hashes, bare-LF status, and artifact list.
+- `manifest.tsv`: stable scenario facts, hashes, bare-LF status, seen ANSI roles,
+  and artifact list.
 - `visible-controls.normalized.txt`: primary semantic failure artifact. It shows
   CR as `␍`, LF as `␊`, ESC as `␛`, tabs as `⇥`, and normalizes volatile temp
   paths.
-- `transcript.txt`: semantic terminal grid after escape/control interpretation.
-- `screenshot.svg` and `terminal.html`: browser-viewable visual evidence.
+- `transcript.txt`: semantic terminal grid after escape/control interpretation,
+  including debug-only role markers such as `☻` for a cursor cell and `░` for
+  selection.
+- `screenshot.svg` and `terminal.html`: browser-viewable visual evidence. SVG
+  includes color swatches for seen cursor/current-line/status/selection roles.
+- `widths.tsv`: per-line semantic width report used to catch viewport overflow.
 - `raw.bin`: exact PTY bytes for low-level debugging.
 
 Golden policy:
 
 - Investigate before updating any expected artifact or assertion.
 - Prefer semantic artifacts (`manifest.tsv`, `visible-controls.normalized.txt`,
-  `transcript.txt`) for assertions; visual artifacts explain what a user would
-  see.
+  `transcript.txt`, `widths.tsv`) for assertions; visual artifacts explain what a
+  user would see.
 - Updating artifacts is safe only after the change is intentional and the receipt
   names the changed UI/control-byte behavior.
 - Adding a mobile scenario must preserve the `ios-default-qwertz-space-path`