[MichaelWave369]

R15: test the real assembled PixelForge Pages path before live embed claims

Grounded merged baseline

PhiOS #412 merged at 52141a9e3e234cf001fea005a815776acec1ca11. Its post-merge native qualification, two-origin Chromium, Pages site and ecosystem catalog are green.

New gap and test

PixelForge's production Pages build does not serve VR Studio at origin /; it publishes through /parallax-pixelforge/vr-studio/. The existing PhiOS Chrome test only served a raw source folder at /, so it did not catch public site route/base/copy failures.

• Keep exact reviewed PixelForge Add experimental AgentCeption dispatch and field-guided cognitive-architecture recommendation (MCP Phase 16/17) #89 merge source SHA b1c6314da005de801ba3b0417ffe4b4abe461828 in checkout and browser assertion.
• Build the actual PixelForge site React+Vite Pages distribution via its existing build/assembly script. Require the exported dist/vr-studio HTML and bridge files.
• Serve the assembled artifact at the real GitHub project Pages base /parallax-pixelforge/ on a distinct ephemeral loopback origin. Require all four critical VR Studio/bridge files byte-identical to their reviewed pinned source, and return 404 instead of a silent SPA fallback if scripts are missing.
• Run existing real Chrome default-deny, consent, revocation-on-V2-drift, reapproval, disconnect/reconnect and zero-world-file checks against that published-shaped build. Keep Home launcher no-auto-frame gate.
• Document separate proof of production public URL response headers, embed policy, deployment and actual native installation as still unverified.

Review and hold

Require assembled Pages browser test, offline ecosystem catalog, PhiShell tests and full native-image/VM qualification all green. This PR does not deploy anything, add a trusted production origin, grant access, fetch user files, create app permissions or claim a live remote website is frameable. Keep draft pending review.