/**
 * The ONE source of truth for the app-build deadlines (speed-core lane).
 * Before this module the server build watchdog (4 min, packages/apps) and the
 * UI polling cutoff (5 min, packages/ui) were two unrelated literals — a slow
 * build could die silently in the gap, and retuning one side desynced the
 * other. The UI cutoff always STRICTLY exceeds the effective watchdog, so the
 * watchdog's terminal buildFailed record (with its honest reason and retry
 * affordance) lands before the client gives up with the generic deadline beat.
 */
/**
 * A dead-man timer, so it has to outlast the work it guards.
 *
 * It was 4 minutes, which is shorter than a build: three real box builds took
 * 229 s, 414 s and 450 s on 2026-08-24, and the first was killed at exactly 4:00
 * while the box was still installing from npm. The bound that matters is the
 * box's own — it gives ONE message 15 minutes (`MESSAGE_BUDGET_MS`,
 * `@vendoai/vendo`) before giving up and reporting a failure itself — so
 * this sits above that plus boot, collect and seal. Anything shorter cannot
 * distinguish a lane that died from one that is working, which is the only
 * question it exists to answer. Pinned against the box's budget in
 * `packages/vendo/tests/build-lane.test.ts`, the one package that sees both.
 *
 * The cost, stated: a screen create that dies SILENTLY (`startBuildWatchdog`,
 * doors/build-surface.ts) now shows as building for this long instead of four
 * minutes. `VENDO_APP_BUILD_WATCHDOG_MS` is the operator's escape hatch either way.
 */
export declare const BUILD_WATCHDOG_MS: number;
export declare const APP_BUILD_UI_DEADLINE_MS: number;
/** The effective watchdog window: the `VENDO_APP_BUILD_WATCHDOG_MS` operator
 *  override (test seam and escape hatch) where a `process` env is visible —
 *  this module also runs on edge/Worker and browser targets with no `process`
 *  global, which simply get the constant. */
export declare const effectiveBuildWatchdogMs: () => number;
/** The effective UI polling cutoff: derives from the effective watchdog, so
 *  the strict cutoff > watchdog invariant holds under the env override too. */
export declare const effectiveAppBuildUiDeadlineMs: () => number;
/** Whether `AppDocument.building` still names a build in flight. Time-bounded
 *  for the placement read's reason: past the window either the watchdog landed
 *  a terminal record or the build's process died, and a flag that never cleared
 *  would leave the app unmountable forever. */
export declare const buildInFlight: (building: string | undefined) => boolean;
//# sourceMappingURL=build-deadlines.d.ts.map