textual-tui-pipeline-interception

To add an interactive review step to a CLI pipeline, use a Textual UI to suspend output and enforce immutable state with frozen dataclass patterns until the user validates generated results before final write.

You enforce immutable state during a CLI approval workflow by applying frozen dataclass patterns within the Textual UI, ensuring data remains auditable and unchanged until final write.

Yes, you can use a Textual UI for keyboard-driven code review in a CLI pipeline, providing fast screen-based controls to accept, reject, edit, and navigate generated items before final output.

The best way to validate data transformation results before writing to output is inserting a Textual review step that exposes a launch_review API to return the same data structure with only accepted items.

No, the launch_review API does not modify the original data structure during pipeline approval; it maintains immutable state and returns the same data structure containing only the accepted items.