geo-three tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of geo-three3d-tilesgeolocationmapmap-tilesopenstreetmapthreejs
Session recording
Download the original recording · fingerprint 1182a8c1dbd27327...
What the test found
geo-three installs, builds, and renders 3D map tiles via three.js in headless Chrome; all major modes (PLANAR, HEIGHT, SPHERICAL, HEIGHT_SHADER), LOD strategies (Raycast, Frustum, Radial), and coordinates conversions work correctly.
npm install (311 packages, 31s) and rollup build succeeded. Library verified in headless Chromium via Puppeteer: all 3 example pages (basic, transition, orthographic) load with WebGL rendering and no page errors. All exports (MapView, DebugProvider, OpenStreetMapsProvider, UnitsUtils, LOD* classes, MapNodeGeometry) confirmed as functions. MapView modes PLANAR/HEIGHT/SPHERICAL/HEIGHT_SHADER construct correctly. LOD strategies Raycast/Frustum/Radial instantiate. Coordinate conversions roundtrip precisely. OpenStreetMapsProvider.fetchTile returns a Promise. No third-party API keys needed for DebugProvider or OpenStreetMapsProvider. The only non-fatal warnings were MapView.heightProvider is null for HEIGHT/HEIGHT_SHADER modes when no height provider is set (expected behavior), plus a trivial favicon.ico 404.
Argusic installed geo-three in 2.5 minutes and launched it; verification reached Verified running for real.
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.