stado product deliver schema

Invocation

stado product deliver schema [OPTIONS] --engine <engine>

Purpose

Apply the verified release's migrations to the product's database on its engine. postgres: verify WISENT_RELEASE_ARCHIVE against WISENT_RELEASE_SHA256, read its one database-schema.tar, then apply the migrations the database SCHEMA_DATABASE_URL names has not recorded yet, each with its version recorded in wisent_schema_migrations; writes schema-receipt.json. supabase: push supabase-source.tar (migrations, functions) to the project SUPABASE_PROJECT_REF with SUPABASE_ACCESS_TOKEN and SUPABASE_DB_PASSWORD, carrying split migrations in as applied. Declared supabase/function-secrets.json names are resolved from injected environment values before mutations and published before functions deploy; writes supabase-receipt.json with secret names, never values. sqlite has no delivery: the product applies its own migrations on open

Required inputs and options

Input or option	Contract
`--catalog <catalog>`	Independent authoritative catalog path
`--engine <engine>`	The engine the schema runs on [possible values: sqlite, postgres, supabase]
`--migrations <migrations>`	Directory inside database-schema.tar's source/ root; *.sql files run in file-name order (sqlite and postgres) [default: migrations]
`--workspace <workspace>`	The workspace of canonical checkouts this operation reads and builds from; default WISENT_WORKSPACE, else ~/Documents/CodingProjects/Wisent
`--project-dir <project-dir>`	Directory inside the bundle that holds supabase/ (supabase; default: the bundle root) [default: .]

Output and state effect

It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.

Refusals

Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.