flutter-parity

What problem does it solve?

Produce a Flutter→React port parity register for a module — what to COMPOSE from graduated Signal DS, what's already DONE in the React target, and what's a genuine PORT gap. Use before porting a module so you build the gaps and compose the rest, instead of re-porting components that already exist. Grounded in real files only — never guess.

Core Features & Use Cases

• Enumerate the Flutter surface units. List the real widget files in the module and classify each leaf widget vs screen.
• For each unit, check authority: COMPOSE if graduated in Signal DS, DONE if already built in the React target, or PORT if neither.
• Emit the parity register listing per-unit status so you can prioritize work and avoid re-porting existing components.
• Grounded in actual files and exports; no guessing.

Quick Start

Identify the Flutter module path and run the parity workflow to generate the per-unit parity register against the React target.