/**
 * Canonical wall-clock deadline for an AILF pipeline/ask job.
 *
 * This is the single source of truth for "how long a job is allowed to run,
 * and how long a client waits for it." Every surface that used to hard-code a
 * 45-minute value now derives from this constant, so a future change lands in
 * exactly one place:
 *
 *   - API gateway job `deadlineAt` — pipeline + ask routes
 *     (`packages/api/src/routes/{pipeline,ask}.ts`)
 *   - Cloud Run task `timeout`
 *     (`packages/api/src/execution/cloud-run-dispatcher.ts`)
 *   - eval-side job store default deadline
 *     (`packages/eval/src/job-store.ts`)
 *   - CLI API client poll deadline
 *     (`packages/eval/src/adapters/api-client/api-client.ts`) — the client
 *     waits the full server deadline so it never abandons a job the backend
 *     is still allowed to run. Before unification this was 20 minutes, which
 *     made the CLI throw `ApiTimeoutError` on healthy long jobs that completed
 *     server-side.
 *
 * Surfaces that cannot import TypeScript must mirror this value and point back
 * here as the source of truth:
 *   - `infra/cloud-run/job-template.yaml` (`timeoutSeconds`)
 *   - `.github/workflows/*.yml` eval/ask jobs (`timeout-minutes`)
 */
export declare const JOB_EXECUTION_DEADLINE_MS: number;
/**
 * The same deadline expressed in whole seconds, for surfaces that want a
 * seconds value (e.g. the Cloud Run `timeout: "<n>s"` string).
 */
export declare const JOB_EXECUTION_DEADLINE_SECONDS: number;
