Un-POD dispatches both measured textured face paths

POD 2.8's face reader (FUN_00465d54) copies the trailing face word into runtime flags. Its face loops use the visibility bit, and the textured filler uses flag 4 to select the row-span path; without it the game fills a fan and draws affine gradient spans. The Rust format reader now retains the source word, and Un-POD carries its visibility, keyed-texel and two-sided bits to the scene renderer. pod-render::scene dispatches between both measured fill paths.

Headless capture from the POD race recording. It confirms the app path runs; it is not a same-camera comparison with WINPOD.EXE.

view::project uses the POD race projection's measured near, face-cut and far-plane ratios. It triangulates quads for output but shares route and facing decisions across both halves using the source corners. The app still uses floating-point camera and clipping math, so this is not whole-frame parity and does not yet prove that the reported roof gaps are fixed. The POD car and track reader tests, pod-world, pod-render, the 21 Un-POD binary tests, and the VitePress build pass. The broad format suite's image writer remained CPU-bound on all 212 image files for over ten minutes; I stopped that run and reran its car and track checks directly. See the render notes and checklist.