Prove multi-file terminal coding loop
This commit is contained in:
@@ -29,14 +29,16 @@ Artifact roles:
|
||||
- `keystrokes.tsv`: logical user key-event count and raw byte count for scenario
|
||||
payloads. A CSI sequence such as PageDown counts as one attached-key event
|
||||
while still recording all raw bytes sent.
|
||||
- `saved-files.tsv`: per-file hashes/byte counts for scenarios that assert more
|
||||
than the launched file, such as multi-file coding workflows.
|
||||
- `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`, `widths.tsv`, `keystrokes.tsv`) for assertions; visual
|
||||
artifacts explain what a user would see.
|
||||
`transcript.txt`, `widths.tsv`, `keystrokes.tsv`, `saved-files.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`
|
||||
|
||||
Reference in New Issue
Block a user