/**
 * Phase 5 — Stage 1: Phase 4 Artifact Validation
 *
 * Loads the phase4-manifest.json and validates that required artifacts exist:
 * - Deployment configs (Dockerfile, cloudbuild.yaml, cloud-run-service.yaml)
 * - ERP client files
 * - HTTP server files
 * - Schema files (if database-backed)
 *
 * Error codes:
 *   ECLI-P5-002  Phase 4 manifest not found or invalid
 *   ECLI-P5-003  Required Phase 4 artifact missing
 */
import type { Phase5Context, Phase5StageOutput } from '../types.js';
/**
 * Stage 1: Load and validate Phase 4 artifacts.
 *
 * Reads `phase4-manifest.json` from the Phase 4 output directory, verifies
 * its shape and success flag, confirms that required deployment artifacts
 * exist on disk, and populates `context.phase4Artifacts` with the loaded data.
 *
 * The Phase 4 directory is located by examining `context.phase4Dir`. If the
 * manifest is in the parent directory's `phase4/` subdirectory, we resolve
 * that path as well.
 *
 * @param context - The mutable Phase 5 pipeline context
 * @returns Stage output describing success or failure
 */
export declare function validatePhase4Artifacts(context: Phase5Context): Phase5StageOutput;
//# sourceMappingURL=phase4-validator.d.ts.map