Audit the Rust worktrees and rendering reports

I checked the old Rust worktrees against main. Their commits were already ancestors of main; the leftover uncommitted menu examples, race replay, live-race lap override and VM runner were reviewed and integrated. I saved recovery patches and untracked files outside the repository, preserved the ignored local worktree settings, then removed the stale checkouts and their merged local branches.

I ran cargo fmt --all -- --check, shfmt -d run/vm/e2e.sh, Python bytecode compilation and cargo test --release --workspace. The workspace suite passed, including the six POD race replays and Un-POD's live-race tests. The VitePress site build also passed.

The actual Rust championship run reaches Galleria and then the AI lane follower reads point 1824 from a list of 1824. I reproduced it in a standalone Galleria race and recorded the failure in the controller notes. The local Gold executable has the expected 1997-10-26 link timestamp. The last parsed point lies beyond every declared lane range; the original's behavior at that boundary is still unknown, so I left the controller unchanged.

For the renderer report, the stand-in paints unresolved triangle pages gray. Source FLAT and GOURAUD faces are page-less and POD sends those kinds through color drawers. The world check finds no dropped triangles or invalid texture pages across Gold's .BL3 tracks. The screenshot's apparent roof gaps remain unconfirmed without a POD frame from the same track and camera. No game assets were extracted in this session.