How can I prevent accidental public exposure of Framework7's built-in admin panel when deploying to production?

When developing a Framework7‑Vue application I have added an admin section under the route /admin. I want to be certain that this section cannot be reached by unauthenticated users after the app is built and served publicly, but I am unsure how Framework7’s navigation guard mechanism behaves in production builds. The build process bundles the router configuration, and I am concerned that a mis‑configured guard could leave the admin page exposed. What specific steps does Framework7 take to evaluate route guards at runtime, and how can I verify that the guard is enforced after the app is deployed? Are there any built‑in utilities or test modes that simulate an unauthenticated request to confirm the protection works?