reversa-screen-translator

Legacy UI screens are translated into executable, token-driven migration specifications by enforcing a two-phase workflow that first captures a human-approved translation mode, then generates per-screen specs.

Golden file parity testing validates migration accuracy by emitting golden files and a manifest.yaml, allowing the Inspector to run constructive parity tests when the legacy system can be executed as an oracle.

Design-system tokens resolve UI elements during screen translation, logging any deviations between the legacy source and the target design system to ensure strict textual preservation by default.

Yes, a human-in-the-loop modernization mode is required, forcing an explicit selection of literal, modernized, or hybrid translation modes to prevent silent redesign decisions during TUI to modern UI migrations.

Yes, screen translation detects source and target platforms across supported adapter pairs, capturing a human-approved translation mode before generating per-screen specifications for the migration.

Automated screen translation should not be used without an initial human decision on the modernization mode, as the workflow strictly requires explicit selection of literal, modernized, or hybrid options to proceed.