Harden recording renderer CLI bounds
This commit is contained in:
@@ -290,7 +290,8 @@ Known local toolchain state:
|
||||
context.
|
||||
- `pano_cli record-render` exposes the recording renderer through JSON
|
||||
automation, including readback command/byte totals, and is covered by
|
||||
`pano_cli_record_render_smoke`.
|
||||
`pano_cli_record_render_smoke` plus
|
||||
`pano_cli_record_render_rejects_oversized_target`.
|
||||
- `pano_cli simulate-document-history` exposes `pp_document::DocumentHistory`
|
||||
apply/undo/redo state through JSON automation and is covered by
|
||||
`pano_cli_simulate_document_history_smoke`.
|
||||
|
||||
@@ -818,7 +818,8 @@ Results:
|
||||
context.
|
||||
- `pano_cli record-render` exercises that headless recording renderer and emits
|
||||
JSON command counts, target dimensions, backend name, trace/draw summary, and
|
||||
readback command/byte totals for agent automation.
|
||||
readback command/byte totals for agent automation, with an expected-failure
|
||||
smoke for oversized render/readback targets.
|
||||
- `pano_cli simulate-document-history` exercises pure document history
|
||||
apply/undo/redo behavior and emits JSON layer/frame/history state for agent
|
||||
automation.
|
||||
|
||||
Reference in New Issue
Block a user