Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(page-audit): re-check nav timeouts with a wider budget so box load stops confirming false errors
nirholasbef7b5520a3e
diff --git a/docs/ops/page-audit.md b/docs/ops/page-audit.mdindex 8af83d581..227fc6c99 100644--- a/docs/ops/page-audit.md+++ b/docs/ops/page-audit.md@@ -173,6 +173,18 @@ is audited again **on its own**, in a fresh context, with nothing else running:uuids, base58 addresses, query strings and bare numbers, so the same defectmatches even though its ids differ every load.+The solo re-check also navigates with a wider budget than the sweep: 60 s+against the sweep's 25 s. The pass removes the contention *this run* creates,+but it cannot remove the load every other process on the box creates, and a+starved browser misses a 25 s navigation on a page that is perfectly healthy.+On 2026-09-08, with three sweeps and two Playwright suites sharing one machine,+`/dashboard/avatars` timed out at 25 s in the sweep and again in the re-check,+and was published as that run's only confirmed error; loaded by itself moments+later it reached `domcontentloaded` in 769 ms with nothing logged. Re-checking a+timeout with the budget that produced it only reproduces the starvation. A+genuinely dead route still fails at 60 s and stays an error, and the sweep's own+budget is unchanged, so a slow page is still caught by the first pass.+Errors that survive this pass reproduced on a page loaded by itself, which iswhat makes the error count worth acting on. `--reverify-cap N` bounds how manypairs get re-checked (default 60, `0` disables the pass); anything past the capdiff --git a/scripts/page-audit.mjs b/scripts/page-audit.mjsindex c49364925..32bf179e2 100644--- a/scripts/page-audit.mjs+++ b/scripts/page-audit.mjs@@ -82,6 +82,25 @@ const MOBILE_ONLY = flag('mobile-only');const STRICT = flag('strict');const CONCURRENCY = Math.max(1, Number(opt('concurrency', 5)) || 5);+// The sweep's own navigation budget, and the wider one the solo re-check gets.+//+// The solo pass removes the contention THIS run creates, but it cannot remove+// the load every other process on the box creates, and a starved browser misses+// a 25 s navigation on a page that is perfectly healthy. On 2026-09-08, with+// three sweeps and two Playwright suites sharing one machine, /dashboard/avatars+// timed out at 25 s in the sweep AND again in the solo re-check, so it was+// published as the run's only confirmed error. The same route, loaded by itself+// moments later, reached domcontentloaded in 769 ms and logged nothing.+//+// Re-checking a timeout with the budget that produced it just reproduces the+// starvation, so the solo pass navigates with a wider one: a page that loads+// fine given room emits no nav-failed, and the original finding demotes as the+// artifact it was. A genuinely dead route still fails at 60 s and stays an+// error. This only widens the re-check; the sweep itself is unchanged, so a+// slow route is still flagged by the first pass.+const NAV_TIMEOUT_MS = 25000;+const REVERIFY_NAV_TIMEOUT_MS = 60000;+// Which engine renders the sweep. Chromium is the default because it is the// only browser every machine here already has, but it cannot see a whole class// of bug on its own: JavaScriptCore and V8 disagree about when a temporal dead@@ -388,7 +407,7 @@ function inPageAudit() {}// ── Per-route audit ───────────────────────────────────────────────────────────-async function auditRoute(ctx, route, viewport) {+async function auditRoute(ctx, route, viewport, { navTimeoutMs = NAV_TIMEOUT_MS } = {}) {const page = await ctx.newPage();const findings = [];const push = (type, severity, detail) => {@@ -436,14 +455,14 @@ async function auditRoute(ctx, route, viewport) {try {const resp = await page.goto(`${BASE_URL}${route}`, {waitUntil: 'networkidle',- timeout: 25000,+ timeout: navTimeoutMs,});navStatus = resp?.status() ?? null;} catch {try {const resp = await page.goto(`${BASE_URL}${route}`, {waitUntil: 'domcontentloaded',- timeout: 25000,+ timeout: navTimeoutMs,});navStatus = resp?.status() ?? null;} catch (e) {@@ -621,7 +640,9 @@ async function reverify(browser, results, viewports, authed) {}let solo;try {- solo = await auditRoute(ctx, suspect.route, viewport);+ solo = await auditRoute(ctx, suspect.route, viewport, {+ navTimeoutMs: REVERIFY_NAV_TIMEOUT_MS,+ });} catch {solo = null; // a crashed re-check proves nothing; leave the finding as-is}