The repository states the reasoning plainly: vibing is very good at showing what a screen should feel like, and very bad
at satisfying this codebase's authorization, audit, and durability rules. Splitting the work at that seam lets each side
do what it is good at, and it is why a prototype is judged on whether the states are drawn — empty, loading, error,
success — rather than on whether the code is clean.
The no-client-data rule is not workshop etiquette. Every pull request against the product is scanned for exactly this,
and a mockup carrying real client information is closed and its attachments deleted. Invent your Virgo. It costs nothing
and it is the difference between a prototype you can show anyone and one you cannot show at all.
When a screen you vibed should become part of Navigator itself, file it as a design mockup issue — a GIF of the
interaction plus the source that produced it — and an engineer translates it into the real application. What you attach
is read, never merged, never served, and never a dependency. The shipped screen is Rust and it will look like your
design without containing your files.