Feature storytelling stays benefit-first: QR ordering, kitchen visibility, cashier workflows, loyalty, events, delivery, and localization all surface as product outcomes.
Each public route now lands inside the same navigation and footer system.
Empty, loading, denied, retry, and release-aware cues stay explicit in the UI.
Local rendering does not replace later two-FTP host evidence and smoke gates.
The foundation shell makes non-happy paths visible at the screen level so later runtime wiring does not hide denial, retry, loading, or release dependencies.
QR menus, table ordering, cashier flows, events, and loyalty are described as outcomes, not internals.
Service, kitchen, and operational coordination stay benefit-level and public safe.
Additional locale content is prepared for English and RTL-safe expansion.
Internal mailer, deployment, and runtime paths remain intentionally absent from the feature shell.