If a user is fast enough, they can press the "travel" button in the bottom navigation bar after refreshing the page and successfully navigate there:
I've navigated to this page using this method repeatedly, and I have 0 approved hours.
After a brief code review, I'm pretty sure this can be solved by initializing the state variable travelLocked in BottonNavigation.svelte to true instead of false.
The API call getHourCounts() in the onMount hook is async and takes a while to load, meaning that there's a small delay before the travel tab is locked.