shacraft-core/docs/verification/browser.md

Browser verification — 2026-09-14

The real Codex in-app browser was tested at http://127.0.0.1:4000 through CUA. Separate HTTP/WebSocket processes performed the API tests.

• Fresh page load: manifest, 8 verified resources, lobby entry, and the custom WebGL2 renderer without an initialization error.
• The lobby was visible in a real screenshot: a pixel-textured platform, light pillars, an arch, water, a trampoline, sky, sun, and HUD.
• The catalog opened with 32,367 states. Searching for minecraft:oak_slab returned 6 variants with exact type/waterlogged properties. Selecting type=bottom,waterlogged=false updated the active quick slot.
• Diagnostics showed live tick/ack, revision, coordinates, block count, RAM, and useful cache payload separately. The lobby on this test machine showed 144 FPS, 11,920 triangles, and 0 queued sections.
• After the server process was stopped and replaced, the open page reconnected automatically. The previously selected material remained selected.
• Persistent entities created through the Control API reached the client; an allay was visible in a screenshot and the entity count updated.
• A second fresh browser client loaded the final protocol without receiving the full registry. The hotbar populated through catalog queries; all 8 cached resources passed verification again.
• Selecting gallery switched worlds. A real screenshot showed varied cubic and partial shapes, with the UI leaving the world visible. Diagnostics: 1,614 blocks in the current view, 7,808 triangles, 144 FPS, and 0 queued sections. All 1,197 samples exist in the world, but are not necessarily visible in one view.

FPS describes this browser, hardware, viewport size, and viewing position. It is neither a minimum requirement nor a performance promise for another device. Movement, reach, two-client building, Spleef, reconnection, and crash durability were additionally checked by the reproducible scripts/check_server.mjs harness.