import * as React from "react";
import type { ErrorSurfaceProp } from "../../props/components/layout.prop.js";
export type { ErrorSurfaceMaintenanceProp, ErrorSurfaceProp, ErrorSurfaceProp as ErrorSurfaceProps, } from "../../props/components/layout.prop.js";
export type { ErrorSurfaceModeProp, ErrorSurfaceStatusProp } from "../../props/vocabulary/index.js";
/**
 * What the surface owns is the CONTRACT the composition kept losing: - **`mode` is the shell
 * contract.** `application` (400/403/404) renders the surface as the BODY you place inside the
 * `AppShell` the route already provides, so the sidebar, topbar and breadcrumb are PRESERVED — it
 * never reconstructs navigation chrome, because nav data and the user menu are consumer-owned and
 * a component cannot manufacture them. `system` (500/503) owns the page and renders `CenteredShell
 * align="center"`, so the viewport-centred geometry at 1440 / 1024 / 390 is package-owned and the
 * consumer writes no `min-h-dvh`, no flex-centring class, no media query. - **Exactly one recovery
 * action**, structurally (see `singleAction`). - **Semantic metadata slots** instead of free-form
 * paragraphs: `requestId` (mono/tabular so a support id is read out accurately), `permission` and
 * `organization` (which of the two a 403 is actually about), and `maintenance` (ISO-8601 + IANA
 * formatted through `Intl.DateTimeFormat`, with an optional labelled `Progress` meter).
 */
export declare const ErrorSurface: React.ForwardRefExoticComponent<ErrorSurfaceProp & React.RefAttributes<HTMLDivElement>>;