Issues with the Get Started app

[dougreichard]

1. the example does not run properly when deploying to github pages. Both chime.mp3 and webxr.png require "./" in their urls to get it to work properly.

2. "npm run dev" does not start the runtime. This lead to confusion that the app was not runnable. It may need changing to allow that or the doc should specify to run "npm run dev:runtime" first. This step here

3. The "Enter XR" button does not seem to work.

[AkshatRaj00]

Hey team! 👋

I've been going through the Get Started experience and ran into all three of these issues myself while trying to deploy to GitHub Pages. The asset path problem (#1 and #3) is a really common footgun for new users — anyone deploying to a subdirectory hits this immediately, and it kills the first impression of the SDK.

I'd love to take a stab at fixing this. Here's my plan:

For issue #1 & #3 (asset URL paths):
The chime.mp3 and webxr.png references are likely using bare paths like "gltf/..." or "textures/..." instead of "./gltf/..." or using Vite's new URL('./asset', import.meta.url) pattern which respects the configured base. I'll audit all starter asset references and fix them to be base-aware.

For issue #2 (npm run dev not starting runtime):
I'll look into either making dev start the runtime by default, or improving the error/warning message so first-time users aren't left confused staring at a blank screen.

For issue #3 ("Enter XR" button):
Will test end-to-end on the emulator and trace the button handler.

Would you like me to open a PR for just the asset path fixes first (low-risk, high-impact), and follow up with the dev script improvement separately? Happy to do it however works best for the team's review workflow. 🙏