The Schema Foundation Is in Place

The first ForgeSchema development session establishes the input contract for the engine. A versioned YAML file describes one PostgreSQL schema, its tables, columns, basic primary keys and ordinary indexes. The validator checks names, types and references, then produces canonical JSON with stable ordering.

This checkpoint includes a Go command line program, examples, automated validation tests and a populated PostgreSQL fixture for subsequent work. Schema fingerprints are available in the Go package; they identify canonical representations and are not a security signature.

The current binary can validate schema files. It cannot inspect a database, generate a migration or execute SQL. Those boundaries matter: this session supplies the foundation for the next stage, which will read PostgreSQL catalogs and compare the resulting snapshot with the same schema contract.