Self-hosted, Self-Improving, Federated Everything App — dev management, agent orchestration, persistent mind, digital twin, second brain, and creative pipeline from a single dashboard over Tailscale to port the user into the OS
JavaScript ai-agentsdashboarddeveloper-toolsdigital-twinquantified-selfsecond-brainself-hostedtailscale
fix: load the Chrome resolver before the fidelity toolchain uses it (#12293)
[._.]/ Adam Eivy432383fe273f
diff --git a/scripts/browser-fidelity.js b/scripts/browser-fidelity.jsindex 116d6ac3d4..0977dbda49 100644--- a/scripts/browser-fidelity.js+++ b/scripts/browser-fidelity.js@@ -41,12 +41,12 @@ export function fidelityChildEnv(env, diagnostics) {async function fidelityToolchain(env) {const { findFfmpeg } = await import('../server/lib/ffmpeg.js');const { _testChromeCaptureArgs } = await import('../server/services/htmlComposition/testBrowserCleanup.js');+ const { probeChromeH264, describeH264Probe, resolveTestChrome } = await import('../server/lib/browserSuiteGate.js');const chromePath = resolveTestChrome(env);const ffmpegPath = await findFfmpeg();if (!chromePath || !ffmpegPath) throw Error('Fidelity Chrome/FFmpeg toolchain unavailable.');// Surface the structured probe cause here: the suite's own prerequisite gate// reports through vitest output, which this command's refusal never relays.- const { probeChromeH264, describeH264Probe, resolveTestChrome } = await import('../server/lib/browserSuiteGate.js');const probe = await probeChromeH264(chromePath);if (!probe.ok) throw Error(describeH264Probe(probe));const version = (path, args) => {