zynagent-first application framework

Check command#

Usage:
  zyn check [--timings] [-j N|--jobs N]

Check formatting, database artifacts, compilation, and application tests. Use test for tests only.

Example:
  zyn check

Documentation: zyn docs cli/check

Checks the current application in four stages:

  1. verifies formatting for build.zig, hand-written Zig under src, and db/seeds.zig without changing them;
  2. checks committed database artifacts without starting PostgreSQL;
  3. compiles the application and its framework contracts without starting a server; and
  4. runs the same isolated application suite as zyn test.

The database stage requires db/zyn_schema.sql to match the running Zyn release, db/types.zig to retain its generated-file marker, and the migration versions recorded in db/schema.sql to exactly match valid migration files. Snapshots with legacy checksum rows are accepted without comparing the checksums to migration files. It does not prove that the SQL snapshot and generated Zig field shapes are semantically equivalent; run zyn db verify to replay migrations into a disposable database and compare the generated schema and types.

Formatting or database-artifact failures do not prevent compilation and tests. An application compilation failure skips tests. The command reports every stage as PASS, FAIL, or SKIP and exits unsuccessfully when any stage fails.

--timings, -j, and --jobs have the same test-runner behavior and bounds as zyn test.

The command may synchronize the ignored framework package, refresh ignored metadata and caches under .zyn, and start isolated test PostgreSQL or loopback HTTP fixtures when application tests request them. It does not format files, run migrations or seeds, touch the development database, start a development server, build the production executable, or contact a deployment host.