/**
 * Phase 4 Pipeline — Stage 3: ERP-Native SQL Schema Generator
 *
 * Generates domain-aware CREATE TABLE DDL statements in the SQL dialect of the
 * detected ERP system's database engine. Reads the DDD domain model to extract
 * aggregates, entities, and value objects, then generates columns specific to
 * each bounded context rather than cookie-cutter templates.
 *
 * Supported dialects:
 *   hana-sql     — SAP HANA COLUMN TABLE syntax
 *   tsql         — Microsoft SQL Server / Azure SQL / Azure Synapse T-SQL syntax
 *   oracle-sql   — Oracle Database syntax (VARCHAR2, NUMBER, SYSTIMESTAMP)
 *   db2-sql      — IBM Db2 syntax
 *   postgresql   — PostgreSQL / Cloud SQL / Supabase / Aurora PostgreSQL
 *   mysql        — MySQL / Aurora MySQL / PlanetScale / MariaDB
 *   bigquery-sql — Google BigQuery (STRING, INT64, no FK/indexes)
 *   sqlite       — SQLite / Turso / libSQL
 *
 * Error codes:
 *   ECLI-P4-004  Schema file write failure
 */
import type { Phase4Context, Phase4StageOutput } from '../types.js';
/**
 * Stage 3: Generate ERP-native SQL schema files for all DDD bounded contexts.
 *
 * Reads the ERPResolution from the previous stage and the Phase 2 domain model
 * from context.phase3Artifacts. For each bounded context:
 *   1. Checks the domain table registry for context-specific schemas
 *   2. Falls back to generating tables from DDD aggregates/entities/VOs
 *
 * Generates per-context migration files plus a master migration.
 *
 * @param context - The Phase 4 pipeline context
 * @returns Stage output describing success, skip, or failure
 */
export declare function generateSchemas(context: Phase4Context): Phase4StageOutput;
//# sourceMappingURL=schema-generator.d.ts.map