Implement Peft hosting basics in this game.

First check whether this feature is already implemented. Verify existing behavior against the requirements and acceptance cases below, using tests and available runtime checks. If it already satisfies them, leave working code unchanged and report the verification evidence. If it is partial or broken, implement only the missing behavior or fixes; do not duplicate integrations, callbacks, or state. Report anything you could not verify instead of assuming success.

Inspect the existing game first and implement only this integration. Preserve gameplay, networking, and any Peft features already present. Do not replace the networking protocol. Add focused tests, run the available checks, and report changed files, test commands/results, external services, and real limitations. Do not claim live Peft acceptance unless you exercised it.

Packaging:
- Deliver one self-contained UTF-8 HTML file, or a ZIP with UTF-8 index.html at its root and the required assets beneath it.
- Use relative release assets, not root-absolute /assets/ paths, local-machine paths, traversal paths, symlinks, nested/encrypted archives, secrets, or development artifacts.
- Keep gameplay tuning organized and assets appropriately sized. Document required HTTPS/WSS signaling and external asset services.
- With trailing game subroutes, resolve assets from the iframe's room-root asset base rather than the subroute. Never hardcode a private runtime capability.

Sandbox:
- Peft runs scripts and pointer lock in an opaque-origin iframe. Same-origin access, parent DOM access, top navigation, popup escape, hub cookies/storage, and service workers are unavailable.
- Handle unavailable localStorage, cookies, and IndexedDB explicitly without crashing playable behavior. Do not weaken Peft's sandbox or request account cookies.
- Networking must work from an opaque null origin where applicable. Configure your own service safely; do not disable authentication or allow arbitrary credentialed CORS.
- Use user gestures for clipboard, fullscreen, and audio where required. Provide clear fallbacks, such as selectable invite text.
- Document APIs that fundamentally require a normal origin instead of hiding incompatibility.
- Keep essential controls accessible on phones, tablets, and desktops, including meaningful touch controls.

Screenshots:
- Peft captures an initial screen at 1280 x 800 in a renderer with no external network access.
- Package enough visuals to show a recognizable title/menu/game scene promptly, without remote CDNs or successful multiplayer connections.
- The preview room is PREVIEW. Failed joining must leave an informative offline/menu state, not crash, invent a real room, or automatically create a session.
- Do not depend on invented clicks or unsupported preview query parameters. Document when automatic capture is impractical; do not change production networking solely for screenshots.

Verify the packaged assets and initial screen with external networking unavailable. Exercise core controls at phone, tablet, and desktop sizes, and test graceful handling of unavailable browser storage and permissions.