@a11ign/screenreader-fleet 0.2.0 → 0.4.0

package/dist/capture-client.d.mts

@@ -46,4 +46,3 @@ export function captureTolerantly({ worker, body, timeoutMs, beforeRecovery, onP
     onProgress?: (progress: object) => void;
     sync?: boolean;
 }): Promise<any>;
-//# sourceMappingURL=capture-client.d.mts.map

package/dist/capture-client.mjs

@@ -1,352 +1,190 @@
-// @ts-check
-/**
- * ONE CAPTURE, TOLERANT OF THE SOCKET DYING UNDER IT — and the only place that knows how.
- *
- * The worker has stored completed captures under a caller-chosen id since the `captureId` work landed:
- * `POST /capture {captureId}` then `GET /capture/<id>` returns the original response verbatim, so a lost
- * socket costs a round trip instead of 12-520 s of real screen-reader work. That is the idempotency-key
- * shape, for the reason payment APIs use it.
- *
- * TEN CLIENTS POST TO `/capture`. ONE USED THE RECOVERY. This repo's most expensive recurring shape is a
- * remedy applied at one call site when the behaviour reaches several — `anchorToTop`, `ensureSpeechChannel`,
- * `waitForAnnouncement`, `refreshBrowseBuffer` — and this is that shape at its largest here.
- *
- * MEASURED COST, 2026-08-28: `gate:stability` lost THREE canaries to `FAILED read ETIMEDOUT` across two
- * runs — `filter-status-silent-solar/bad` on one box, then `form-error-silent/bad` and
- * `disclosure-state-silent/good` on two others. Different pages, different machines, so it is the transport
- * and not either. Each one turned the determinism gate INCONCLUSIVE while the capture it lost had already
- * COMPLETED and was sitting in the worker's store, which is precisely what the store exists to serve back.
- *
- * The worker is bare metal on real Ethernet with real power management, which is why this arrived now: on
- * three VMs sharing one Mac the socket was a virtual bridge and effectively lossless.
- *
- * MOVED HERE from `packages/lab/src/capture/capture-client.mjs` — architecture-audit.md §5, item 6: the
- * product CLI sent no `captureId` at all, so this recovery path was unavailable to the one caller that is
- * a user. `packages/cli` can depend on `@a11ign/screenreader-fleet` (it already does, for `requestJson`)
- * but must never depend on `@a11ign/lab`, which is private and never published — so this is the
- * seventh capture client and the last one, not an eighth copy of the recovery logic beside it.
- */
 import { randomUUID } from "node:crypto";
-import { requestJson, CAPTURE_CLIENT_TIMEOUT_MS } from "./worker-http.mjs";
+import { CAPTURE_CLIENT_TIMEOUT_MS, requestJson } from "./worker-http.mjs";
 import { isTransient } from "./transient-fault.mjs";
-/** Long enough to survive a worker that is briefly busy, short enough not to double a capture's cost. */
-const RECOVERY_TIMEOUT_MS = 30_000;
-/**
- * THE ESCAPE HATCH BACK TO THE SYNCHRONOUS PATH, and it says so when used.
- *
- * Kept because a protocol change wants a way back that does not need a deploy, and removed only once a
- * corpus run has gone through the async path end to end.
- */
-/**
- * READ PER CALL, NOT AT MODULE LOAD, and the difference is not stylistic. A value fixed at import is one
- * no test can vary and no process can change -- `fileProductVersion` memoised Edge's version that way and
- * stamped five days of captures with a build they were not taken under. So it is a PARAMETER with an env
- * default, which also lets both paths be driven from one test file.
- */
-const syncByEnv = () => process.env.A11Y_SYNC_CAPTURE === "1";
-/** Accepting a capture is a handshake, not the work: it either answers in seconds or the box is unwell. */
-const ACCEPT_TIMEOUT_MS = 30_000;
-/** Between polls. Short enough that a 12 s capture is not padded, long enough not to hammer a busy box. */
-const POLL_MS = 2_000;
-/** A read of an array already in memory; if this cannot answer, the guest's event loop is blocked. */
-const PROGRESS_TIMEOUT_MS = 10_000;
-/**
- * Consecutive failed POLLS before giving up.
- *
- * Not one: a single dropped poll is precisely the transport fault this design exists to survive, and
- * treating it as a failed capture would reintroduce the defect through the new door. Not unbounded either,
- * or a box that has genuinely gone would be waited on for the whole capture budget.
- */
+const RECOVERY_TIMEOUT_MS = 30000;
+const syncByEnv = ()=>"1" === process.env.A11Y_SYNC_CAPTURE;
+const ACCEPT_TIMEOUT_MS = 30000;
+const POLL_MS = 2000;
+const PROGRESS_TIMEOUT_MS = 10000;
 const MAX_POLL_FAILURES = 5;
-const sleep = (/** @type {number} */ ms) => new Promise((r) => setTimeout(r, ms));
-const base = (/** @type {string} */ worker) => String(worker).replace(/\/$/, "");
-/**
- * What is left of the OPERATION'S budget, never negative — architecture-audit.md §14.5.
- *
- * Every wait inside the poll loop used its own fixed constant regardless of how little of `timeoutMs`
- * remained: a two-second sleep, a ten-second progress read and a thirty-second result read, none clipped
- * to what was actually left. A caller asking for `timeoutMs: 20` measured 2,012 ms before an answer,
- * because the unconditional sleep ran to completion first regardless of the deadline it was about to blow
- * past. This is the one place that number is computed, so every wait below shares one clock.
- *
- * @param {number} deadline
- */
-const remaining = (deadline) => Math.max(0, deadline - Date.now());
-/**
- * Ask the worker for a capture we already paid for but may not have received.
- *
- * Returns null when there is nothing to recover — a worker predating the endpoint (404 from the router's
- * fallback), one that restarted and lost its memory, or a capture still running. Null means "capture
- * again", which is what every client did before the endpoint existed.
- *
- * A recovered FAILURE is RETURNED rather than swallowed, so a replay is indistinguishable from the original
- * response. That keeps the worker's `fault` code — the thing it worked out, and which we would otherwise
- * replace with "no answer" — and lets the caller's own classification decide, as it would have all along.
- * (The dataset runner's version THREW here, because it wrapped a `fetchJson` that rejects on non-2xx;
- * `requestJson` resolves instead, so the same intent is expressed by returning the response.)
- *
- * @param {string} worker @param {string} captureId
- */
-export async function recoverCapture(worker, captureId) {
+const sleep = (ms)=>new Promise((r)=>setTimeout(r, ms));
+const base = (worker)=>String(worker).replace(/\/$/, "");
+const remaining = (deadline)=>Math.max(0, deadline - Date.now());
+async function recoverCapture(worker, captureId) {
     let response;
     try {
-        response = await requestJson(`${base(worker)}/capture/${captureId}`, { timeoutMs: RECOVERY_TIMEOUT_MS });
-    }
-    catch (error) {
-        // The worker went away again mid-question. Not worth a second round trip; the caller falls back to
-        // capturing, which is what it would have done anyway.
-        void error;
+        response = await requestJson(`${base(worker)}/capture/${captureId}`, {
+            timeoutMs: RECOVERY_TIMEOUT_MS
+        });
+    } catch (error) {
         return null;
     }
-    // 500 IS AN ANSWER, NOT AN OBSTACLE: it is the worker's own account of a failed capture, carrying the
-    // `fault` code it worked out. Returning it lets the caller's existing classification decide, exactly as
-    // it would have on the original response -- and losing it replaces a diagnosis with "no answer", which
-    // this project has repeatedly misread as a dead machine.
-    if (response.status === 500)
-        return response;
-    // 404 from the endpoint, or from an older worker's router fallback: nothing kept, so capture again.
-    if (response.status === 404)
-        return null;
-    if (!response.ok)
-        return null;
-    // "Still running" and "never heard of it" are DIFFERENT ANSWERS and must stay that way. Neither is
-    // recoverable here, but only one means the work is still being done.
-    if ( /** @type {any} */(response.json)?.state === "running")
-        return null;
+    if (500 === response.status) return response;
+    if (404 === response.status) return null;
+    if (!response.ok) return null;
+    if (response.json?.state === "running") return null;
     return response;
 }
-/**
- * POST a capture, and on a TRANSIENT failure ask whether it actually finished before paying again.
- *
- * Returns what `requestJson` returns — `{status, ok, text, json}` — plus `recovered`, so this is a
- * drop-in at the call sites that already POST `/capture` and read `response.ok` / `body.error`. Keeping
- * their own classification is deliberate: a shared client that also decided what counts as a failure would
- * be changing ten behaviours at once while claiming to change one.
- *
- * `requestJson` RESOLVES on an HTTP error and REJECTS only on a transport one, so the `catch` below is
- * reached exactly by the case this exists for — `ETIMEDOUT`, `ECONNRESET`, a socket dying mid-answer.
- *
- * `waitForWorker` is deliberately NOT called here. The dataset runner has one, tuned to a corpus run's
- * tolerance for a box gone for minutes; a gate wants an answer quickly. So this asks once, immediately,
- * and a caller that wants to wait first passes `beforeRecovery`.
- *
- * @param {{ worker: string, body: object, timeoutMs?: number,
- *           beforeRecovery?: (error: unknown) => Promise<void>,
- *           onProgress?: (progress: object) => void, sync?: boolean }} request
- */
-export async function captureTolerantly({ worker, body, timeoutMs = CAPTURE_CLIENT_TIMEOUT_MS, beforeRecovery, onProgress, sync = syncByEnv() }) {
+async function captureTolerantly({ worker, body, timeoutMs = CAPTURE_CLIENT_TIMEOUT_MS, beforeRecovery, onProgress, sync = syncByEnv() }) {
     const captureId = randomUUID();
-    if (!sync)
-        return pollForResult({ worker, body, captureId, timeoutMs, onProgress });
-    // Said once, at the moment it applies, rather than at import: the synchronous form holds a connection
-    // open and silent for the whole capture, which is the shape that lost 9 of 40 responses on this fleet.
+    if (!sync) return pollForResult({
+        worker,
+        body,
+        captureId,
+        timeoutMs,
+        onProgress
+    });
     process.stderr.write("A11Y_SYNC_CAPTURE — holding one connection open for this capture\n");
     try {
-        return { ...await post(worker, { ...body, captureId }, timeoutMs), recovered: false, pollsSurvived: 0 };
-    }
-    catch (error) {
-        if (!isTransient(error))
-            throw error;
-        // The error is handed over so a caller can SAY why it is waiting. The dataset runner prints
-        // "worker unreachable (<message>)" before a multi-minute wait, and a wait with no stated cause is
-        // one an operator kills.
-        if (beforeRecovery)
-            await beforeRecovery(error);
+        return {
+            ...await post(worker, {
+                ...body,
+                captureId
+            }, timeoutMs),
+            recovered: false,
+            pollsSurvived: 0
+        };
+    } catch (error) {
+        if (!isTransient(error)) throw error;
+        if (beforeRecovery) await beforeRecovery(error);
         const recovered = await recoverCapture(worker, captureId);
-        // A recovered capture is the ORIGINAL response, returned rather than re-requested. `recovered` travels
-        // with it because a caller measuring the transport needs to know this one cost a round trip and not a
-        // capture -- reporting it as a clean first attempt would hide the very fault this exists for.
-        if (recovered)
-            return { ...recovered, recovered: true, pollsSurvived: 0 };
-        return { ...await post(worker, { ...body, captureId: randomUUID() }, timeoutMs), recovered: false, pollsSurvived: 0 };
+        if (recovered) return {
+            ...recovered,
+            recovered: true,
+            pollsSurvived: 0
+        };
+        return {
+            ...await post(worker, {
+                ...body,
+                captureId: randomUUID()
+            }, timeoutMs),
+            recovered: false,
+            pollsSurvived: 0
+        };
     }
 }
-/**
- * DISPATCH, THEN POLL — the async path, and the reason this module exists.
- *
- * `POST {async:true}` returns 202 in milliseconds, so no connection is held while NVDA reads a page. The
- * result is collected from the store with `GET /capture/<id>`, which is the endpoint that has existed for
- * this shape all along and was only ever reached after a failure. **The recovery path is now the normal
- * path**, which is what stops it rotting: a route that runs only when something breaks is one nobody
- * notices has broken.
- *
- * A dropped poll costs one round trip and is simply retried; the capture is unaffected because nothing is
- * riding on that socket. That is the whole difference from the synchronous form, where the answer existed
- * only in the connection that was carrying it.
- */
-/**
- * @param {{ worker: string, body: object, captureId: string, timeoutMs: number,
- *           onProgress?: (progress: object) => void }} request
- */
 async function pollForResult({ worker, body, captureId, timeoutMs, onProgress }) {
     const deadline = Date.now() + timeoutMs;
     let accepted;
     try {
-        accepted = await post(worker, { ...body, captureId, async: true }, ACCEPT_TIMEOUT_MS);
-    }
-    catch (error) {
-        if (!isTransient(error))
-            throw error;
+        accepted = await post(worker, {
+            ...body,
+            captureId,
+            async: true
+        }, ACCEPT_TIMEOUT_MS);
+    } catch (error) {
+        if (!isTransient(error)) throw error;
         const reconciled = await reconcileLostAcceptance(worker, captureId, deadline);
-        if (reconciled.state === "done")
-            return { ...reconciled.response, recovered: true, pollsSurvived: 0 };
-        if (reconciled.state === "unknown") {
-            // CONFIRMED nothing is running under this id -- only now is a fresh one safe, exactly as the
-            // synchronous escape hatch already does for the identical failure. Minting one on the first sign
-            // of trouble, before asking, is what the audit's remedy forbids: it would risk a second real
-            // capture running under a worker that already accepted the first.
-            return pollForResult({
-                worker, body, captureId: randomUUID(), timeoutMs: Math.max(0, deadline - Date.now()), onProgress,
-            });
-        }
-        // reconciled.state === "running": the worker DID accept it under the id we already hold -- the 202
-        // was lost, not the acceptance. Fall through to the ordinary poll loop below exactly as a received
-        // 202 would have.
+        if ("done" === reconciled.state) return {
+            ...reconciled.response,
+            recovered: true,
+            pollsSurvived: 0
+        };
+        if ("unknown" === reconciled.state) return pollForResult({
+            worker,
+            body,
+            captureId: randomUUID(),
+            timeoutMs: Math.max(0, deadline - Date.now()),
+            onProgress
+        });
     }
-    // A worker too old to know `async` runs the capture SYNCHRONOUSLY and answers 200 with the result. That
-    // is not an error and must not be retried -- it is the additive-field contract this project uses for
-    // every wire change, and it means a host can be deployed before the fleet.
-    if (accepted && accepted.status !== 202)
-        return { ...accepted, recovered: false, pollsSurvived: 0 };
-    return awaitCompletion({ worker, captureId, deadline, timeoutMs, onProgress });
+    if (accepted && 202 !== accepted.status) return {
+        ...accepted,
+        recovered: false,
+        pollsSurvived: 0
+    };
+    return awaitCompletion({
+        worker,
+        captureId,
+        deadline,
+        timeoutMs,
+        onProgress
+    });
 }
-/**
- * ASKING ABOUT A CAPTURE WE MAY OR MAY NOT HAVE STARTED, using the SAME three-way discrimination a
- * dropped poll already relies on (`pollOnce`) rather than `recoverCapture`, which collapses "running"
- * and "unknown" into one null and cannot tell them apart -- the exact distinction this exists to make.
- *
- * A 404 here is not quite `pollOnce`'s documented "worker restarted mid-capture": no 202 was ever
- * received, so there is nothing to have restarted AWAY FROM. It means the POST itself never reached the
- * worker, which is what makes minting a fresh id safe once this returns "unknown" and not before.
- *
- * The audit's own caveat applies in principle: "unknown does not prove execution never occurred" if the
- * result were evicted (§14.4) before this ever asks — but that needs seven OTHER captures to finish on
- * this worker in the seconds between the lost 202 and this reconciliation, which the worker's own `busy`
- * gate (one capture at a time) makes impossible while nothing else is running under this id.
- *
- * @param {string} worker @param {string} captureId @param {number} deadline
- * @returns {Promise<{ state: "running" } | { state: "unknown" } | { state: "done", response: any }>}
- */
 async function reconcileLostAcceptance(worker, captureId, deadline) {
     let lastError;
-    while (Date.now() < deadline) {
+    while(Date.now() < deadline){
         const poll = await pollOnce(worker, captureId, Math.min(RECOVERY_TIMEOUT_MS, remaining(deadline)));
-        if (poll.running)
-            return { state: "running" };
-        if (poll.done)
-            return { state: "done", response: poll.response };
-        if (poll.lost)
-            return { state: "unknown" };
+        if (poll.running) return {
+            state: "running"
+        };
+        if (poll.done) return {
+            state: "done",
+            response: poll.response
+        };
+        if (poll.lost) return {
+            state: "unknown"
+        };
         lastError = poll.error;
         await sleep(Math.min(POLL_MS, remaining(deadline)));
     }
-    // Never resolved within the budget: neither confirmed running nor confirmed absent. The ORIGINAL
-    // acceptance failure is the fault that actually occurred, so it is what surfaces -- not a generic
-    // timeout that would hide which of the two things went wrong.
-    throw lastError ?? Object.assign(new Error(`could not confirm capture ${captureId} was accepted, within its remaining budget`), { code: "ETIMEDOUT" });
+    throw lastError ?? Object.assign(new Error(`could not confirm capture ${captureId} was accepted, within its remaining budget`), {
+        code: "ETIMEDOUT"
+    });
 }
-/**
- * DISPATCH, THEN POLL — the async path, and the reason this module exists.
- *
- * `POST {async:true}` returns 202 in milliseconds, so no connection is held while NVDA reads a page. The
- * result is collected from the store with `GET /capture/<id>`, which is the endpoint that has existed for
- * this shape all along and was only ever reached after a failure. **The recovery path is now the normal
- * path**, which is what stops it rotting: a route that runs only when something breaks is one nobody
- * notices has broken.
- *
- * A dropped poll costs one round trip and is simply retried; the capture is unaffected because nothing is
- * riding on that socket. That is the whole difference from the synchronous form, where the answer existed
- * only in the connection that was carrying it.
- *
- * @param {{ worker: string, captureId: string, deadline: number, timeoutMs: number,
- *           onProgress?: (progress: object) => void }} request
- */
 async function awaitCompletion({ worker, captureId, deadline, timeoutMs, onProgress }) {
     let transportFailures = 0;
     let survived = 0;
-    while (Date.now() < deadline) {
-        // CLIPPED, EACH TIME, TO WHAT IS LEFT — architecture-audit.md §14.5. A budget of 20 ms must not spend
-        // a full 2 s sleeping before it is even allowed to check the clock again.
+    while(Date.now() < deadline){
         await sleep(Math.min(POLL_MS, remaining(deadline)));
-        if (onProgress)
-            await readProgress(worker, onProgress, Math.min(PROGRESS_TIMEOUT_MS, remaining(deadline)));
+        if (onProgress) await readProgress(worker, onProgress, Math.min(PROGRESS_TIMEOUT_MS, remaining(deadline)));
         const poll = await pollOnce(worker, captureId, Math.min(RECOVERY_TIMEOUT_MS, remaining(deadline)));
-        if (poll.done) {
-            // WHAT THE TRANSPORT DID, carried out with the result. Under the synchronous protocol a dropped
-            // response destroyed the capture; here it costs one poll -- but "harmless" and "not happening" are
-            // different facts, and only one of them means the network is healthy. Reporting it keeps the
-            // question answerable after the fix that stopped it mattering.
-            return { ...poll.response, recovered: false, pollsSurvived: survived };
-        }
-        if (poll.lost) {
-            throw Object.assign(new Error(`worker forgot capture ${captureId} after accepting it — it restarted `
-                + "mid-capture, so the work is gone and the case must be re-issued"), { code: "CAPTURE_LOST" });
-        }
-        // A FAILED POLL IS NOT A FAILED CAPTURE, and conflating them would give back the defect this design
-        // removes: the worker is still working, we merely could not ask. Retried until a RUN of them says the
-        // box has gone, rather than on the first one -- a single dropped request is the exact fault this exists
-        // to survive.
-        if (poll.unreachable)
-            survived += 1;
+        if (poll.done) return {
+            ...poll.response,
+            recovered: false,
+            pollsSurvived: survived
+        };
+        if (poll.lost) throw Object.assign(new Error(`worker forgot capture ${captureId} after accepting it — it restarted mid-capture, so the work is gone and the case must be re-issued`), {
+            code: "CAPTURE_LOST"
+        });
+        if (poll.unreachable) survived += 1;
         transportFailures = poll.unreachable ? transportFailures + 1 : 0;
-        if (transportFailures >= MAX_POLL_FAILURES)
-            throw poll.error;
+        if (transportFailures >= MAX_POLL_FAILURES) throw poll.error;
     }
-    throw Object.assign(new Error(`capture ${captureId} did not finish within ${timeoutMs} ms`), { code: "ETIMEDOUT" });
+    throw Object.assign(new Error(`capture ${captureId} did not finish within ${timeoutMs} ms`), {
+        code: "ETIMEDOUT"
+    });
 }
-/**
- * ONE POLL, WITH FOUR DISTINCT ANSWERS — and keeping them apart is the whole job.
- *
- *   done        the capture finished (200 or 500); the 500 carries the worker's own fault code
- *   lost        404 AFTER a 202 acceptance: the worker restarted, the work is gone, re-issue
- *   running     202; keep waiting
- *   unreachable we could not ask; the capture is unaffected
- *
- * NOT `recoverCapture`, and that is the correction. It SWALLOWS a transport error and returns null, which
- * is right for its own job — "we already failed, is the result there?" — and wrong here, because it makes
- * "could not ask" indistinguishable from "still running". Written that way first, and the retry counter
- * built on it was unreachable: found by mutation, since deleting the retry changed nothing.
- *
- * @param {string} worker @param {string} captureId @param {number} [timeoutMs] clipped to the operation's
- *   remaining budget by the caller — see `remaining()` — so this read cannot outlive the deadline it is
- *   answering to on its own.
- */
 async function pollOnce(worker, captureId, timeoutMs = RECOVERY_TIMEOUT_MS) {
     let response;
     try {
-        response = await requestJson(`${base(worker)}/capture/${captureId}`, { timeoutMs });
-    }
-    catch (error) {
-        return { unreachable: true, error };
+        response = await requestJson(`${base(worker)}/capture/${captureId}`, {
+            timeoutMs
+        });
+    } catch (error) {
+        return {
+            unreachable: true,
+            error
+        };
     }
-    if (response.status === 404)
-        return { lost: true };
-    if (response.status === 202)
-        return { running: true };
-    // 200 and 500 are both ANSWERS: the second is the worker's diagnosis, and losing it would replace a
-    // fault code with silence -- which this project has repeatedly misread as a dead machine.
-    if (response.ok || response.status === 500)
-        return { done: true, response };
-    // Anything else is a worker speaking a protocol we do not know; treat it as unreachable rather than as
-    // an answer, so it is retried and then surfaces with its own status rather than being read as a capture.
-    return { unreachable: true, error: new Error(`unexpected ${response.status} polling ${captureId}`) };
+    if (404 === response.status) return {
+        lost: true
+    };
+    if (202 === response.status) return {
+        running: true
+    };
+    if (response.ok || 500 === response.status) return {
+        done: true,
+        response
+    };
+    return {
+        unreachable: true,
+        error: new Error(`unexpected ${response.status} polling ${captureId}`)
+    };
 }
-/** The phase the worker is IN, so a caller can tell a slow capture from a wedged one. */
-async function readProgress(/** @type {string} */ worker, /** @type {(p: object) => void} */ onProgress, 
-/** @type {number} */ timeoutMs = PROGRESS_TIMEOUT_MS) {
+async function readProgress(worker, onProgress, timeoutMs = PROGRESS_TIMEOUT_MS) {
     try {
-        const { json } = await requestJson(`${base(worker)}/progress`, { timeoutMs });
-        if (json && typeof json === "object")
-            onProgress(json);
-    }
-    catch (error) {
-        // Progress is a convenience; failing to read it must never fail a capture that is going fine.
-        void error;
-    }
+        const { json } = await requestJson(`${base(worker)}/progress`, {
+            timeoutMs
+        });
+        if (json && "object" == typeof json) onProgress(json);
+    } catch (error) {}
 }
-/** @param {string} worker @param {object} body @param {number} timeoutMs */
 function post(worker, body, timeoutMs) {
-    // `requestJson` serialises the body and sets the headers; passing a string here would double-encode it.
-    return requestJson(`${base(worker)}/capture`, { method: "POST", body, timeoutMs });
+    return requestJson(`${base(worker)}/capture`, {
+        method: "POST",
+        body,
+        timeoutMs
+    });
 }
-//# sourceMappingURL=capture-client.mjs.map
+export { captureTolerantly, recoverCapture };

package/dist/check-worker-code.d.mts

@@ -31,4 +31,3 @@ import { configuredWorkers } from "./fleet-env.mjs";
 declare function localPoolUrls(): any;
 import { inventoryWorkerUrls } from "./fleet-env.mjs";
 export {};
-//# sourceMappingURL=check-worker-code.d.mts.map