For each live version versionViews MUST make a schema api_<label> (the pattern is a setting) and in it a view of each table of that version with that version's names for the table and its columns, over the tables of FR-001, where a column the version knows by another name than the tables use is selected under the version's name; it MUST be made as a unit that the lifecycle applies again when the tables change.
Enforced (check): .github: cd commons/data && bun run verify — suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used; suite/rollout.test.ts: the schema's pattern and the primary version are settings, DuckDB's views read, and SQLite's views carry the version's label in their names
Proved by: data/suite/rollout.test.ts
Written in: data/sql/extensions/rollout/views.ts
Tests: passed: suite/rollout.test.ts on PostgreSQL two versions use one database at once under their own names, the expand dest; passed: suite/rollout.test.ts the schema's pattern and the primary version are settings, DuckDB's views read, and SQLite
Cited by: Data, sql/extensions/rollout/views