Bidirectional Porting
Features are designed, built, and tested in this standalone first. When stable, they're copied and adapted into the parent molino-staging application. The standalone remains the clean, canonical reference — no travel-specific code, no commercial integrations.
Reference patterns flow the other way too: generic code from the parent (auth, edit mode, dashboard components) can be copied into _reference/ for comparison and adaptation.
The primary flow: Standalone → parent. Build here, prove it, port it.