From df030a3a6f365f35a3e533587ee691500c7cb2c6 Mon Sep 17 00:00:00 2001 From: Speculator55005 <50082482+fas89@users.noreply.github.com> Date: Wed, 18 Nov 2026 18:46:06 +0100 Subject: [PATCH 1/2] chore: re-vendor the 0.7.7 preview from forge-cli v0.32.0 The vendored 0.7.7 schema was the v0.31.0 copy. Replace it with the reference implementation's file at the v0.32.0 tag, byte for byte, and regenerate what derives from it: specs/0.7.7/ and schema-diffs/diff-0.7.6-to-0.7.7.md. 0.7.2 to 0.7.6 are byte-identical at the new tag. Only the column type changed. An enum can now name quoted levels, such as enum('Dr.', '>10000', 'O''Brien', 'a, b'). Its pattern narrows at the edge: an empty item, a quote that does not open and close a level, and a tab, a newline or another whitespace control character inside a quoted level are refused, and 0.7.6 accepted them. check-compat reports the changed pattern, so scripts/compat-waivers.txt records it, with the comparison of the two patterns that settled it. tests/meta_test.py put its sample waiver before the last entry of the 0.7.6 to 0.7.7 pair, which kept the file sorted only while the pair had one entry. It now goes before the first. The 0.7.7 corpus gains seven enum cases, three valid and four invalid. upstream.ref is v0.32.0 and upstream.commit is the tag's peeled commit, 8ad55d53987157bac4b0fa1a8004bdfd00b3ca9d. --- schema-diffs/diff-0.7.6-to-0.7.7.md | 28 ++- schema/fluid-schema-0.7.7.json | 4 +- scripts/compat-waivers.txt | 48 ++++- scripts/schema-versions.json | 4 +- specs/0.7.7/fluid-spec.html | 26 ++- tests/0.7.7/contract-schema.json | 290 ++++++++++++++++++++++++++++ tests/meta_test.py | 5 +- 7 files changed, 390 insertions(+), 15 deletions(-) diff --git a/schema-diffs/diff-0.7.6-to-0.7.7.md b/schema-diffs/diff-0.7.6-to-0.7.7.md index d424474..db85ff5 100644 --- a/schema-diffs/diff-0.7.6-to-0.7.7.md +++ b/schema-diffs/diff-0.7.6-to-0.7.7.md @@ -1,9 +1,9 @@ # Schema Changes: 0.7.6 โ†’ 0.7.7 -**Total changes:** 61 +**Total changes:** 63 - โœ… Added: 45 - โŒ Removed: 5 -- ๐Ÿ“ Modified: 11 +- ๐Ÿ“ Modified: 13 --- @@ -857,6 +857,30 @@ "Build/ingestion engine. Transformation engines: dbt, sql, python, spark, glue, custom. Adapter-quali..." ``` +### `$defs.column.properties.type.anyOf` + +**Before:** +```json +[{"type": "string", "enum": ["string", "text", "varchar", "varchar2", "nvarchar", "char", "nchar", "character", "clob", "int", "integer", "int2", "int4", "int8", "int16", "int32", "int64", "tinyint", "smallint", "mediumint", "bigint", "long", "longint", "serial", "bigserial", "float", "float4", "float8", "float32", "float64", "double", "real", "decimal", "dec", "numeric", "number", "bignumeric", "money", "boolean", "bool", "bit", "date", "time", "datetime", "datetime2", "smalldatetime", "timestamp", "timestamptz", "timestamp_tz", "timestamp_ntz", "timestamp_ltz", "timestampntz", "interval", "year", "variant", "object", "array", "struct", "map", "record", "row", "json", "jsonb", "super", "binary", "varbinary", "bytes", "blob", "bytea", "raw", "geography", "geometry", "geom", "point", "uuid", "uniqueidentifier", "guid", "enum", "hll"]}, {"type": "string", "pattern": "(?i)^\\s*(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\\s+with(out)?\\s+time\\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)\\s*(\\(\\s*[0-9A-Za-z_,\\s'\\\"-]*\\s*\\))?\\s*$"}] +``` + +**After:** +```json +[{"type": "string", "enum": ["string", "text", "varchar", "varchar2", "nvarchar", "char", "nchar", "character", "clob", "int", "integer", "int2", "int4", "int8", "int16", "int32", "int64", "tinyint", "smallint", "mediumint", "bigint", "long", "longint", "serial", "bigserial", "float", "float4", "float8", "float32", "float64", "double", "real", "decimal", "dec", "numeric", "number", "bignumeric", "money", "boolean", "bool", "bit", "date", "time", "datetime", "datetime2", "smalldatetime", "timestamp", "timestamptz", "timestamp_tz", "timestamp_ntz", "timestamp_ltz", "timestampntz", "interval", "year", "variant", "object", "array", "struct", "map", "record", "row", "json", "jsonb", "super", "binary", "varbinary", "bytes", "blob", "bytea", "raw", "geography", "geometry", "geom", "point", "uuid", "uniqueidentifier", "guid", "enum", "hll"]}, {"type": "string", "pattern": "(?i)^\\s*(?:enum\\s*\\(\\s*(?:(?:'(?:[^'\\x00-\\x1f\\x7f-\\x9f]|'')*'|\"(?:[^\"\\x00-\\x1f\\x7f-\\x9f]|\"\")*\"|[0-9A-Za-z_-]+(?:\\s+[0-9A-Za-z_-]+)*)\\s*(?:,\\s*(?:'(?:[^'\\x00-\\x1f\\x7f-\\x9f]|'')*'|\"(?:[^\"\\x00-\\x1f\\x7f-\\x9f]|\"\")*\"|[0-9A-Za-z_-]+(?:\\s+[0-9A-Za-z_-]+)*)\\s*)*)?\\)|(?!enum\\s*\\()(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\\s+with(out)?\\s+time\\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)(\\s*\\([0-9A-Za-z_,\\s'\\\"-]*\\))?)\\s*$"}] +``` + +### `$defs.column.properties.type.description` + +**Before:** +```json +"Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form..." +``` + +**After:** +```json +"Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form..." +``` + ### `$defs.packaging.properties.containers.description` **Before:** diff --git a/schema/fluid-schema-0.7.7.json b/schema/fluid-schema-0.7.7.json index c9f2e4a..d247644 100644 --- a/schema/fluid-schema-0.7.7.json +++ b/schema/fluid-schema-0.7.7.json @@ -1011,7 +1011,7 @@ "minLength": 1 }, "type": { - "description": "Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.", + "description": "Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. An enum names its levels in its parameter list, comma-separated: each level is a word list (enum(IE, United Kingdom)) or a quoted string that may hold any character but a control character, with its own quote doubled, as in SQL string literals (enum('Dr.', '>10000', 'O''Brien', 'a, b')). Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.", "anyOf": [ { "type": "string", @@ -1099,7 +1099,7 @@ }, { "type": "string", - "pattern": "(?i)^\\s*(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\\s+with(out)?\\s+time\\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)\\s*(\\(\\s*[0-9A-Za-z_,\\s'\\\"-]*\\s*\\))?\\s*$" + "pattern": "(?i)^\\s*(?:enum\\s*\\(\\s*(?:(?:'(?:[^'\\x00-\\x1f\\x7f-\\x9f]|'')*'|\"(?:[^\"\\x00-\\x1f\\x7f-\\x9f]|\"\")*\"|[0-9A-Za-z_-]+(?:\\s+[0-9A-Za-z_-]+)*)\\s*(?:,\\s*(?:'(?:[^'\\x00-\\x1f\\x7f-\\x9f]|'')*'|\"(?:[^\"\\x00-\\x1f\\x7f-\\x9f]|\"\")*\"|[0-9A-Za-z_-]+(?:\\s+[0-9A-Za-z_-]+)*)\\s*)*)?\\)|(?!enum\\s*\\()(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\\s+with(out)?\\s+time\\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)(\\s*\\([0-9A-Za-z_,\\s'\\\"-]*\\))?)\\s*$" } ] }, diff --git a/scripts/compat-waivers.txt b/scripts/compat-waivers.txt index c2d7947..6d82e1b 100644 --- a/scripts/compat-waivers.txt +++ b/scripts/compat-waivers.txt @@ -67,7 +67,53 @@ 0.7.3->0.7.4 /properties/fluidVersion # --------------------------------------------------------------------------- -# 0.7.6 -> 0.7.7 -- DELIBERATE, in a PREVIEW. The only narrowing in the pair. +# 0.7.6 -> 0.7.7: DELIBERATE, in a PREVIEW. A widening with a narrow edge. +# +# $defs/column/properties/type, the pattern (second anyOf branch). An enum's +# parameters are now a comma-separated list of levels. A level is a quoted +# string, in single or double quotes, that may hold any character but a +# control character, with its own quote doubled as SQL writes it, or an +# unquoted list of words. Through 0.7.6, and in every copy of 0.7.7 published +# here before forge-cli v0.32.0, the parameters were any run of letters, +# digits, underscores, spaces, commas, quotes and hyphens. Every other type +# keeps that character set. +# +# Regex containment is undecidable in general, so the gate reports any changed +# pattern as breaking and asks for a decision. This one rests on comparing the +# two patterns on 1,195,741 strings: every string of up to 5 characters (6 +# after "enum(") over the 9 symbols a 0 - space , ' " . ) after each of the +# 10 prefixes "enum(", "ENUM (", "varchar(", "decimal(", "timestamp with time +# zone(", "map(", "enumx(", "enum", "string" and the empty prefix. A second +# comparison covers 618,821 strings: every string of up to 4 characters (5 +# after "enum(") over the 13 symbols a ' " , ) - space, tab, newline, DEL, +# U+0085, a non-ASCII letter and ">" after each of the 8 prefixes "enum(", +# "ENUM (", "varchar(", "decimal(", "map(", "enum", "string" and the empty +# prefix. In both: +# - no type other than enum changes its verdict; +# - what 0.7.6 accepts and 0.7.7 now refuses (21,676 strings in the first +# run) is an enum with an empty item, a quote that does not open and close +# a level, or a whitespace control character inside a quoted level: +# enum(a,,b) enum(a, ) enum(') enum('it's') enum('a' 'b') +# enum('ab') +# - what 0.7.6 refuses and 0.7.7 now accepts (960 strings in the first run) +# is an enum with a quoted level that holds a character 0.7.6 refused: +# enum('Dr.', '>10000', 'O''Brien', 'a, b') enum("Dr.", "Cir.") +# - unchanged: enum enum() enum(IE, United Kingdom) varchar(255) +# decimal(18,4) varchar('1, 2') +# +# Why it stands: 0.7.7 is a preview and a contract reaches it only by declaring +# "0.7.7". The new grammar is what lets a level hold any character, and the +# spellings it refuses are the ones it cannot read as a list of levels. The +# 0.7.7 corpus pins both sides (tests/0.7.7/contract-schema.json). +# docs/schema/changelog.md and docs/releases/0.7.7.md say the pair is not +# purely additive. +# +# Re-examine when 0.7.7 is promoted: a stable version may not narrow. +0.7.6->0.7.7 /$defs/column/properties/type/anyOf/1 + +# --------------------------------------------------------------------------- +# 0.7.6 -> 0.7.7: DELIBERATE, in a PREVIEW. The other narrowing in the pair is +# the column type pattern, above. # # secretRef (acquisitionSource.connection, acquisitionDeployment.auth and the # kafka-connect schema_registry.auth) was a string matching diff --git a/scripts/schema-versions.json b/scripts/schema-versions.json index 23335a3..a6ac825 100644 --- a/scripts/schema-versions.json +++ b/scripts/schema-versions.json @@ -11,8 +11,8 @@ "repository": "Agenticstiger/forge-cli", "schemaDir": "fluid_build/schemas", "previewSource": "fluid_build/schema_manager.py", - "ref": "v0.31.0", - "commit": "0b72fb1c327ae33acddfdf8bbf9f5d1e7849d19c" + "ref": "v0.32.0", + "commit": "8ad55d53987157bac4b0fa1a8004bdfd00b3ca9d" }, "latestStable": "0.7.6", "preview": ["0.7.7"], diff --git a/specs/0.7.7/fluid-spec.html b/specs/0.7.7/fluid-spec.html index fca95ad..422cdfb 100644 --- a/specs/0.7.7/fluid-spec.html +++ b/specs/0.7.7/fluid-spec.html @@ -3515,8 +3515,15 @@

/> typeType: object
-

Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.

-
+
+

Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. An enum names its levels in its parameter list, comma-separated: each level is a word list (enum(IE, United Kingdom)) or a quoted string that may hold any character but a control character, with its own quote doubled, as in SQL string literals (enum('Dr.', '>10000', 'O''Brien', 'a, b')). Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.

+ +
+
+ +

@@ -3677,7 +3684,7 @@

Must be one of:

/> item 1
Type: string
-Must match regular expression: (?i)^\s*(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\s+with(out)?\s+time\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)\s*(\(\s*[0-9A-Za-z_,\s'\"-]*\s*\))?\s*$ +Must match regular expression: (?i)^\s*(?:enum\s*\(\s*(?:(?:'(?:[^'\x00-\x1f\x7f-\x9f]|'')*'|"(?:[^"\x00-\x1f\x7f-\x9f]|"")*"|[0-9A-Za-z_-]+(?:\s+[0-9A-Za-z_-]+)*)\s*(?:,\s*(?:'(?:[^'\x00-\x1f\x7f-\x9f]|'')*'|"(?:[^"\x00-\x1f\x7f-\x9f]|"")*"|[0-9A-Za-z_-]+(?:\s+[0-9A-Za-z_-]+)*)\s*)*)?\)|(?!enum\s*\()(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\s+with(out)?\s+time\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)(\s*\([0-9A-Za-z_,\s'\"-]*\))?)\s*$ @@ -4369,8 +4376,15 @@

/> type
-

Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.

-

+
+

Column data type. Accepts a canonical FLUID/SQL type name (case-insensitive) or a parameterized form such as decimal(18,4) or varchar(255). The enum lists the canonical bare types; the pattern additionally permits case variants and parameter suffixes. An enum names its levels in its parameter list, comma-separated: each level is a word list (enum(IE, United Kingdom)) or a quoted string that may hold any character but a control character, with its own quote doubled, as in SQL string literals (enum('Dr.', '>10000', 'O''Brien', 'a, b')). Intentionally generous โ€” it rejects obvious garbage (e.g. MYSTERY_TYPE) while admitting the cross-dialect superset.

+ +
+
+ +

/> item 1
Type: string
-Must match regular expression: (?i)^\s*(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\s+with(out)?\s+time\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)\s*(\(\s*[0-9A-Za-z_,\s'\"-]*\s*\))?\s*$ +Must match regular expression: (?i)^\s*(?:enum\s*\(\s*(?:(?:'(?:[^'\x00-\x1f\x7f-\x9f]|'')*'|"(?:[^"\x00-\x1f\x7f-\x9f]|"")*"|[0-9A-Za-z_-]+(?:\s+[0-9A-Za-z_-]+)*)\s*(?:,\s*(?:'(?:[^'\x00-\x1f\x7f-\x9f]|'')*'|"(?:[^"\x00-\x1f\x7f-\x9f]|"")*"|[0-9A-Za-z_-]+(?:\s+[0-9A-Za-z_-]+)*)\s*)*)?\)|(?!enum\s*\()(string|text|varchar|varchar2|nvarchar|char|nchar|character|clob|int|integer|int2|int4|int8|int16|int32|int64|tinyint|smallint|mediumint|bigint|long|longint|serial|bigserial|float|float4|float8|float32|float64|double|real|double\s+precision|decimal|dec|numeric|number|bignumeric|money|boolean|bool|bit|date|time|datetime|datetime2|smalldatetime|timestamp|timestamptz|timestamp_tz|timestamp_ntz|timestamp_ltz|timestampntz|timestamp\s+with(out)?\s+time\s+zone|interval|year|variant|object|array|struct|map|record|row|json|jsonb|super|binary|varbinary|bytes|blob|bytea|raw|geography|geometry|geom|point|uuid|uniqueidentifier|guid|enum|hll)(\s*\([0-9A-Za-z_,\s'\"-]*\))?)\s*$ diff --git a/tests/0.7.7/contract-schema.json b/tests/0.7.7/contract-schema.json index cf5a322..ead35aa 100644 --- a/tests/0.7.7/contract-schema.json +++ b/tests/0.7.7/contract-schema.json @@ -354,6 +354,296 @@ } ] }, + { + "description": "enum column type naming quoted levels that hold a full stop, a comparison sign, a doubled quote, a comma and a non-ASCII letter", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum('Dr.', '>10000', 'O''Brien', 'a, b', 'Z\u00fcrich')" + } + ] + } + } + ] + }, + "valid": true + }, + { + "description": "enum column type naming double-quoted levels", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum(\"Dr.\", \"Cir.\")" + } + ] + } + } + ] + }, + "valid": true + }, + { + "description": "enum column type naming unquoted levels, each a list of words", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum(IE, United Kingdom)" + } + ] + } + } + ] + }, + "valid": true + }, + { + "description": "enum column type with an empty item between two commas", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum(a,,b)" + } + ] + } + } + ] + }, + "valid": false, + "errors": [ + { + "pointer": "/exposes/0/contract/schema/0/type", + "keyword": "anyOf" + } + ] + }, + { + "description": "enum column type with an unbalanced quote inside a level", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum('it's')" + } + ] + } + } + ] + }, + "valid": false, + "errors": [ + { + "pointer": "/exposes/0/contract/schema/0/type", + "keyword": "anyOf" + } + ] + }, + { + "description": "enum column type with two quoted levels and no comma between them", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum('a' 'b')" + } + ] + } + } + ] + }, + "valid": false, + "errors": [ + { + "pointer": "/exposes/0/contract/schema/0/type", + "keyword": "anyOf" + } + ] + }, + { + "description": "enum column type with a tab inside a quoted level", + "contract": { + "fluidVersion": "0.7.7", + "kind": "DataProduct", + "id": "customer_profiles", + "name": "Customer Profiles", + "metadata": { + "owner": { + "team": "customer-analytics" + } + }, + "exposes": [ + { + "exposeId": "profiles_table", + "kind": "table", + "binding": { + "platform": "gcp", + "format": "bigquery_table", + "location": { + "project": "acme-prod", + "dataset": "customers", + "table": "profiles" + } + }, + "contract": { + "schema": [ + { + "name": "customer_id", + "type": "enum('a\tb')" + } + ] + } + } + ] + }, + "valid": false, + "errors": [ + { + "pointer": "/exposes/0/contract/schema/0/type", + "keyword": "anyOf" + } + ] + }, { "description": "column missing the required name", "contract": { diff --git a/tests/meta_test.py b/tests/meta_test.py index 85bf112..33c74e5 100644 --- a/tests/meta_test.py +++ b/tests/meta_test.py @@ -283,9 +283,10 @@ def compat_gate_is_load_bearing() -> None: json.dumps(_set_in(json.loads(target.read_text()), ["properties", "exposes", "minItems"], 2), indent=2) ) waivers = root / "scripts" / "compat-waivers.txt" - # the file must stay sorted, so the new line goes before the last pair's entry + # the file must stay sorted, so the new line goes before the first entry of + # the last pair, whatever number of entries that pair has text = waivers.read_text() - at = text.rindex("\n0.7.6->0.7.7 ") + 1 + at = text.index("\n0.7.6->0.7.7 ") + 1 waivers.write_text(text[:at] + "0.7.4->0.7.5 /properties/exposes\n" + text[at:]) r = run(root, "scripts/check-compat.py", "--from", "0.7.4", "--to", "0.7.5") check("a waiver silences its own pointer", r.returncode == 0, f"exit={r.returncode}") From a154e7499ce6230b33ecd408d1a3ef42706175fe Mon Sep 17 00:00:00 2001 From: Speculator55005 <50082482+fas89@users.noreply.github.com> Date: Wed, 18 Nov 2026 18:46:06 +0100 Subject: [PATCH 2/2] docs: say 0.7.7 has two narrowings, and describe the enum levels The release note, the releases index and the changelog said the 0.7.7 preview had one narrowing, in secret references. It has a second, at the edge of the enum column type. Add an Enum levels section to the release note, with the spellings each version accepts, correct the reading paragraph of the releases index, and move the complete contract's validation claim to data-product-forge 0.32.0. tests/README.md carried a stale coverage figure for 0.7.7. Measured on the base commit and on this branch alike, it is 41.4% (638 of 1541 constraints, 141 redundant), so the figure is corrected, and the README says why the seven new enum cases exist. --- docs/releases/0.7.7.md | 34 ++++++++++++++++++++++++++++------ docs/releases/README.md | 4 ++-- docs/schema/changelog.md | 4 +++- tests/README.md | 11 +++++++++-- 4 files changed, 42 insertions(+), 11 deletions(-) diff --git a/docs/releases/0.7.7.md b/docs/releases/0.7.7.md index 91540bf..c177acd 100644 --- a/docs/releases/0.7.7.md +++ b/docs/releases/0.7.7.md @@ -4,16 +4,16 @@ 0.7.7 is a **preview**. A contract uses it only by declaring `fluidVersion: "0.7.7"`, and its fields and their meaning can still change before it is promoted to stable. The latest stable version is [0.7.6](/fluid/releases/0.7.6). See [Stable and preview versions](/fluid/schema/versions#stable-and-preview-versions). ::: -0.7.7 lets a column declare nested data (structs, arrays and maps, to any depth) and lets an embedded-logic build describe the Kafka records it reads and how they become rows, in place of a SQL statement. Since its first publication here it has also gained rules about valid data (invariants written in FLUID SQL/1), identifier formats, placeholder values and shared attributes, named relationships and the validity window of a slowly changing dimension, a schema registry definition, Spark builds, the `lakeflow` engine, and a stricter grammar for secret references. +0.7.7 lets a column declare nested data (structs, arrays and maps, to any depth) and lets an embedded-logic build describe the Kafka records it reads and how they become rows, in place of a SQL statement. Since its first publication here it has also gained rules about valid data (invariants written in FLUID SQL/1), identifier formats, placeholder values and shared attributes, named relationships and the validity window of a slowly changing dimension, a schema registry definition, Spark builds, the `lakeflow` engine, a stricter grammar for secret references, and quoted levels in an `enum` column type. - **Schema:** [`fluid-schema-0.7.7.json`](/fluid/schema/fluid-schema-0.7.7.json) ยท **Reference:** [`specs/0.7.7/fluid-spec.html`](/fluid/specs/0.7.7/fluid-spec.html) ยท **Diff:** [`diff-0.7.6-to-0.7.7.md`](https://github.com/open-data-protocol/fluid/blob/main/schema-diffs/diff-0.7.6-to-0.7.7.md) -- **Compatibility:** additive over 0.7.6 except for one narrowing, in secret references (see [Secret references](#secret-references)). A valid 0.7.6 contract stays valid when it declares `"0.7.7"` unless it names a `vault://` secret without a `#field`. `scripts/check-compat.py --from 0.7.6 --to 0.7.7` reports that one case, and it is recorded as a waiver in `scripts/compat-waivers.txt`. +- **Compatibility:** additive over 0.7.6 except for two narrowings, in secret references (see [Secret references](#secret-references)) and at the edge of the `enum` column type (see [Enum levels](#enum-levels)). A valid 0.7.6 contract stays valid when it declares `"0.7.7"` unless it names a `vault://` secret without a `#field`, or an `enum(...)` type with an empty item, a quote that does not open and close a level, or a tab, a newline or another whitespace control character inside a quoted level. `scripts/check-compat.py --from 0.7.6 --to 0.7.7` reports both, and each is recorded as a waiver in `scripts/compat-waivers.txt`. --- ## What is new -Every addition below is optional. These are the property paths present in 0.7.7 and absent in 0.7.6. The text of each comes from the schema's own descriptions, which are the place to read the rules in full. +Every addition below is optional. These are the property paths and values present in 0.7.7 and absent in 0.7.6. The text of each comes from the schema's own descriptions, which are the place to read the rules in full. | Path | What it declares | |---|---| @@ -32,12 +32,13 @@ Every addition below is optional. These are the property paths present in 0.7.7 | `exposes[].semantics.relationships[]`, with `sharedColumns` | Named joins from one expose to another, composite keys included, and columns copied through a relationship. | | `exposes[].semantics.dimensions[].typeParams.validityParams` | Marks a time dimension as one bound of the validity window of a type II slowly changing dimension. The entity type `natural` is described as that dimension's key. | | `secretRef` (shared `$defs/secretRef`), `connection.password`, `auth.token` | A per-scheme grammar for secret references, and two write-only members that name what a contract may not hold. | +| `schema[].type` as `enum(...)`, and the `type` of `element`, `key` and `value` | The levels of an enum column, as words or as quoted strings that may hold any character but a control character. See [Enum levels](#enum-levels). | `fluidVersion` accepts `"0.7.7"` in addition to `"0.7.3"` to `"0.7.6"`. `build.engine` gains `lakeflow`. One existing rule changes shape. Through 0.7.6, an embedded-logic build's `properties` always required `sql`. In 0.7.7 it requires `sql` unless the build has a `stream` and either its `parameters.flink` declares `management`, or it has a `mapping` and a `parameters.spark`; the build is then described by the stream and the mapping alone. A `mapping` without a `stream` is refused. Every document that satisfied the old rule satisfies the new one. -The schema carries a second change of meaning, in `secretRef`. See the next section. +The schema carries two further changes of meaning, in `secretRef` and in the `enum` column type. See the next two sections. --- @@ -45,7 +46,28 @@ The schema carries a second change of meaning, in `secretRef`. See the next sect `secretRef` is now one shared definition, `$defs/secretRef`, used by an acquisition source's `connection`, by the `auth` of an acquisition build's `deployment`, and by the `auth` of the `kafka-connect` `schema_registry`. It names a secret held in a store and never carries it. The grammar is `://[#field][?version=n]`. The schemes are `env`, `file`, `vault`, `aws-sm`, `gcp-sm` and `azure-kv`, with the aliases `openbao` (vault), `aws`, `gcp` and `azure`. Any other lower-case scheme, such as `op://`, is passed to the pack that resolves it. `#field` picks one key of a secret that holds several, and `?version=` pins a version where the store keeps them. Each scheme has its own pattern in the schema. -Through 0.7.6 and in the first copy of 0.7.7 published here, a `secretRef` was any string of the form `://`. That is the one place 0.7.7 accepts less than 0.7.6: a `vault://` reference now needs a `#field`, so `vault://secret/data/crm-db` is refused and `vault://secret/data/crm-db#password` is valid. A reference with another scheme or with a `#field` is unaffected. `connection.password` and `auth.token` are declared `writeOnly`, with the description that a contract may not hold the value and names the secret with `secretRef` instead. +Through 0.7.6 and in the first copy of 0.7.7 published here, a `secretRef` was any string of the form `://`. That is the first place where 0.7.7 accepts less than 0.7.6: a `vault://` reference now needs a `#field`, so `vault://secret/data/crm-db` is refused and `vault://secret/data/crm-db#password` is valid. A reference with another scheme or with a `#field` is unaffected. `connection.password` and `auth.token` are declared `writeOnly`, with the description that a contract may not hold the value and names the secret with `secretRef` instead. + +--- + +## Enum levels + +An enum column names its levels in the parameters of its `type`, comma-separated. A level is a list of words, as before (`enum(IE, United Kingdom)`), or a quoted string in single or double quotes. A quoted level may hold any character but a control character, and writes its own quote twice, as a SQL string literal does: `enum('Dr.', '>10000', 'O''Brien', 'a, b')`. The `type` of a nested `element`, `key` or `value` is the same definition. + +Through 0.7.6, and in the copies of 0.7.7 published here before forge-cli v0.32.0, the parameters of every type were any run of letters, digits, underscores, spaces, commas, quotes and hyphens, so a level such as `Dr.` or `>10000` could not be written. Every type other than `enum` keeps that character set. + +That is the second place where 0.7.7 accepts less than 0.7.6, and it is narrow. The parameters of an enum must now read as a list of levels, so 0.7.7 refuses an empty item, a quote that does not open and close a level, and a tab, a newline or another whitespace control character inside a quoted level, all of which 0.7.6 accepted. A valid 0.7.6 contract with none of these stays valid, and `enum`, `enum()` and `enum(IE, United Kingdom)` read as before. + +| `type` | 0.7.6 | 0.7.7 | +|---|---|---| +| `enum(IE, United Kingdom)` | valid | valid | +| `enum('Dr.', '>10000', 'O''Brien', 'a, b')` | refused | valid | +| `enum("Dr.", "Cir.")` | refused | valid | +| `enum(a,,b)` | valid | refused | +| `enum('it's')` | valid | refused | +| `enum('a' 'b')` | valid | refused | + +`scripts/compat-waivers.txt` records the comparison of the two patterns that settled this, on more than a million strings. --- @@ -184,7 +206,7 @@ The schema asks only for a text. `fluid validate` in the reference implementatio ## A complete contract -The reference implementation can deploy a managed Flink job for a build like this one: a Kubernetes cluster that runs the Flink Kubernetes Operator, writing an Iceberg REST catalog table. That is behaviour of one implementation (non-normative), and it needs operator-side allow-lists for the cluster context, namespace, image, service account and secrets the contract names. The contract below validates against the 0.7.7 JSON Schema (Draft 2020-12) and with `data-product-forge` 0.31.0 (`fluid validate` prints `โœ… Valid FLUID contract (schema v0.7.7)`). `fluid validate` refuses a managed Flink build that has no build `id` or no Iceberg output named in `outputs`, so the contract carries both. +The reference implementation can deploy a managed Flink job for a build like this one: a Kubernetes cluster that runs the Flink Kubernetes Operator, writing an Iceberg REST catalog table. That is behaviour of one implementation (non-normative), and it needs operator-side allow-lists for the cluster context, namespace, image, service account and secrets the contract names. The contract below validates against the 0.7.7 JSON Schema (Draft 2020-12) and with `data-product-forge` 0.32.0 (`fluid validate` prints `โœ… Valid FLUID contract (schema v0.7.7)`). `fluid validate` refuses a managed Flink build that has no build `id` or no Iceberg output named in `outputs`, so the contract carries both. ```yaml fluidVersion: "0.7.7" diff --git a/docs/releases/README.md b/docs/releases/README.md index 3e93cf9..f0c9d60 100644 --- a/docs/releases/README.md +++ b/docs/releases/README.md @@ -6,7 +6,7 @@ Release notes for the FLUID specification, newest first. Each entry links to its | Version | Status | Codename | Compatibility | Summary | |---|---|---|---|---| -| **[0.7.7](/fluid/releases/0.7.7)** | **Preview** | Recursive Streaming Types | โš ๏ธ Additive over 0.7.6, except that a `vault://` secret reference needs a `#field` | Adds nested columns (`fields`, `element`, `key` and `value` on a column), and on an embedded-logic build the Kafka `stream` it reads and the `mapping` that turns its records into rows, a schema registry definition, Spark builds and the `lakeflow` engine. Adds rules about valid data (`invariants`), identifier formats, placeholders and shared attributes, and named relationships. `sql` is no longer required when a managed Flink or Spark build has a stream. | +| **[0.7.7](/fluid/releases/0.7.7)** | **Preview** | Recursive Streaming Types | โš ๏ธ Additive over 0.7.6, except that a `vault://` secret reference needs a `#field` and an `enum(...)` column type refuses an empty item, a quote that does not open and close a level, or a whitespace control character inside a quoted level | Adds nested columns (`fields`, `element`, `key` and `value` on a column), and on an embedded-logic build the Kafka `stream` it reads and the `mapping` that turns its records into rows, a schema registry definition, Spark builds and the `lakeflow` engine. Adds rules about valid data (`invariants`), identifier formats, placeholders and shared attributes, and named relationships. An `enum` column type can name quoted levels, such as `enum('Dr.', '>10000')`. `sql` is no longer required when a managed Flink or Spark build has a stream. | | **[0.7.6](/fluid/releases/0.7.6)** | **Stable (latest)** | Declarative Packaging Modes | โœ… Additive over 0.7.5 | Adds top-level `packaging` and `consumers`, cross-mesh pins on `consumes[]` (`upstreamWorkspace` + `upstreamDigest`), `aggParams` on semantic measures, and on bindings `encryption.kms`, `principals` and Lake Formation `bucketPolicy`; an expose's `lifecycle` gains `expire`, masking rules gain typed `params`, and access policies gain `rowFilters` and `access: mask`. Builds can declare `engine: flink` and a `continuous` trigger, and an Iceberg sink can name a REST catalog's credentials by environment variable (`sink.catalogAuth`). Optional Bitol-shaped fields: `metadata.team`, an object root `description`, `consumes[].contractId` and `contractVersion`, `exposes[].contract.id`, column `quality`, `binding.location.host` and `binding.serialization`. | | **[0.7.5](/fluid/releases/0.7.5)** | Stable | Streaming Kafka โ†’ Iceberg Sink & Confluent Tableflow | โœ… Additive over 0.7.4 | Adds an opt-in Iceberg streaming sink on the `kafka-connect` acquisition engine, the `confluent` (Tableflow) and `pgvector` binding platforms, the `pgvector_table` format and `binding.vectorConfig`, and location fields for Tableflow, Iceberg catalogs, Redshift Serverless and Kinesis. | | **[0.7.4](/fluid/releases/0.7.4)** | Stable | Runtime agentPolicy Enforcement at the MCP Gateway | โœ… Additive over 0.7.3 | Adds the optional `exposes[].mcp` block, the `postgres` binding platform, and the `postgres_table` / `athena_table` / `glue_table` formats. | @@ -18,7 +18,7 @@ Release notes for the FLUID specification, newest first. Each entry links to its ## Reading the compatibility column -"Additive" means what [`scripts/check-compat.py`](https://github.com/open-data-protocol/fluid/blob/main/scripts/check-compat.py) checks on every pull request: no document that validates under one version stops validating under the next. Every transition in the table is additive except **0.7.1 โ†’ 0.7.2**, where `$defs/notification` gained `additionalProperties: false`. That break is recorded in [`scripts/compat-waivers.txt`](https://github.com/open-data-protocol/fluid/blob/main/scripts/compat-waivers.txt) and explained in the [0.7.2 note](/fluid/releases/0.7.2#backward-compatibility-with-0-7-1-one-narrowing-change). +"Additive" means what [`scripts/check-compat.py`](https://github.com/open-data-protocol/fluid/blob/main/scripts/check-compat.py) checks on every pull request: no document that validates under one version stops validating under the next. Every stable transition in the table is additive except **0.7.1 โ†’ 0.7.2**, where `$defs/notification` gained `additionalProperties: false`. That break is recorded in [`scripts/compat-waivers.txt`](https://github.com/open-data-protocol/fluid/blob/main/scripts/compat-waivers.txt) and explained in the [0.7.2 note](/fluid/releases/0.7.2#backward-compatibility-with-0-7-1-one-narrowing-change). The 0.7.7 preview narrows in two small places, secret references and the `enum` column type. Both are recorded in the same file and explained in the [0.7.7 note](/fluid/releases/0.7.7). Additive does **not** mean that an older `fluidVersion` may use newer fields. A document is validated against the schema of the version it declares, so to use a field you declare the version that added it. See [Choosing `fluidVersion`](/fluid/schema/versions#choosing-fluidversion). diff --git a/docs/schema/changelog.md b/docs/schema/changelog.md index 7a10036..1d05d56 100644 --- a/docs/schema/changelog.md +++ b/docs/schema/changelog.md @@ -8,7 +8,7 @@ Human-readable summaries of what changed between consecutive versions of the FLU [Full diff โ†’](https://github.com/open-data-protocol/fluid/blob/main/schema-diffs/diff-0.7.6-to-0.7.7.md) ยท [Release note โ†’](/fluid/releases/0.7.7) -One narrowing, in secret references (see **Changed**); everything else is additive. **Preview:** the 0.7.7 schema can still change before it is promoted. The file published here was re-vendored from forge-cli v0.31.0; it was first published from v0.27.0, and the items under "Added since the v0.27.0 copy" came after that. +Two narrowings, one in secret references and one at the edge of the `enum` column type (see **Changed**); everything else is additive. **Preview:** the 0.7.7 schema can still change before it is promoted. The file published here was re-vendored from forge-cli v0.32.0; it was first published from v0.27.0, and the items under "Added since the v0.27.0 copy" came after that. **Added** @@ -25,11 +25,13 @@ One narrowing, in secret references (see **Changed**); everything else is additi - `build.engine` value `lakeflow`. - `packaging.containers` keys `lfTagVocabulary`, `emrApplication`, `schemaRegistry`, `athenaWorkgroup`, `kmsKey` and `mwaaEnvironment`. - `connection.password` and `auth.token` as `writeOnly` members, on an acquisition source and on an acquisition build's `deployment.auth`. + - Quoted levels in an `enum` column type, such as `enum('Dr.', '>10000', 'O''Brien', 'a, b')`: a level is a word list or a quoted string that may hold any character but a control character, with its own quote doubled as SQL writes it. The `type` of a nested `element`, `key` and `value` is the same definition, so it accepts them too. **Changed:** - `embeddedLogicPattern` no longer lists `sql` as unconditionally required. It requires `sql` unless the build has a `stream` and either `parameters.flink` declares `management`, or it has a `mapping` and `parameters.spark`; `mapping` requires `stream` (`dependentRequired`). Every document that carried `sql` is unaffected. - `secretRef` (an acquisition source's `connection`, the `auth` of an acquisition build's `deployment`, and the `kafka-connect` `schema_registry.auth`) is now the shared `$defs/secretRef`: one pattern per scheme (`env`, `file`, `vault`, `aws-sm`, `gcp-sm`, `azure-kv`, and other lower-case schemes). It was any string of the form `://`. This is the narrowing: a `vault://` reference now needs a `#field`, so `vault://secret/data/crm-db` is refused and `vault://secret/data/crm-db#password` is valid. `scripts/check-compat.py` reports it and `scripts/compat-waivers.txt` records it. See the [0.7.7 notes](/fluid/releases/0.7.7#secret-references). +- The parameters of an `enum` column `type` are now a comma-separated list of levels, where 0.7.6 accepted any run of letters, digits, underscores, spaces, commas, quotes and hyphens. This is the second narrowing, and a narrow one: 0.7.6 accepted an empty item (`enum(a,,b)`), a quote that does not open and close a level (`enum('it's')`, `enum('a' 'b')`) and a tab, a newline or another whitespace control character inside a quoted level, and 0.7.7 refuses each. Every other type keeps its characters, and `enum`, `enum()` and `enum(IE, United Kingdom)` are unaffected. `scripts/check-compat.py` reports the pattern as changed and `scripts/compat-waivers.txt` records the comparison that settled it. See the [0.7.7 notes](/fluid/releases/0.7.7#enum-levels). ## 0.7.5 to 0.7.6: Declarative Packaging Modes diff --git a/tests/README.md b/tests/README.md index de126d6..043ec08 100644 --- a/tests/README.md +++ b/tests/README.md @@ -233,8 +233,8 @@ from the denominator; counting them would blame the corpus for a gap it cannot close, and they are findings about the *schema* instead. Today: **41.0%** for 0.7.5 (432 of 1053 falsifiable constraints, 123 -redundant), **45.7%** for 0.7.6 (570 of 1248, 135 redundant) and **48.2%** -for 0.7.7 (632 of 1310, 135 redundant). The gate +redundant), **45.7%** for 0.7.6 (570 of 1248, 135 redundant) and **41.4%** +for 0.7.7 (638 of 1541, 141 redundant). The gate applies to the lowest. Most of what remains is `type` constraints, which need a wrong-typed value for every property in the schema; `--format json` lists the unpinned enums, required members, closed objects and bounds. @@ -277,3 +277,10 @@ change, would have been at 39.7%, under the floor. The cases are in `tests/0.7.6/trigger-continuous.json` and `tests/0.7.6/bitol-fields.json`, and for 0.7.7 in `tests/0.7.7/stream-source.json`, `record-mapping.json` and `nested-columns.json`. + +0.7.7 was re-vendored once more from forge-cli v0.32.0, with quoted levels in +the `enum` column type. That replaced one pattern and added no constraint, so +coverage stayed at 41.4%. The case with an unrecognised type already covered the +pattern, but it cannot tell the old grammar from the new, so seven cases in +`tests/0.7.7/contract-schema.json` pin it: three valid and four invalid, of +which six get the other verdict under the previous copy.