Add conditional transformation profile 0.2

CHANGELOG.md

@@ -2,9 +2,24 @@
 
 ## Unreleased
 
+Target stable specification release: `v0.3.0` (not published).
+
+Until a protected or signed `v0.3.0` tag targets this work, implementations MUST identify it with `specification_status: release_candidate`, `specification_release: null`, and the exact immutable specification commit. The entries below do not constitute a stable release.
+
 - Prepared `openstatspec-specification` 0.2.1 with the reusable,
   fail-closed Dolt adapter declaration validator and packaged schema resources.
   This package update adds no concrete Dolt support declaration.
+- Added backward-compatible Transformation Plan and SPSS Syntax Frontend 0.2
+  contracts for sequential numeric `COMPUTE` and conditional `IF`, bounded
+  comparison/`AND`/`OR` expressions, `FORMATS`, `VARIABLE LEVEL`, and
+  `EXECUTE`.
+- Defined exact SQL three-valued missing semantics and deterministic complete
+  plan JSON hashing while preserving every 0.1 contract, fixture, and hash.
+- Kept create-target apply fail-closed on MySQL, MariaDB, and Dolt; these
+  profiles require a separately versioned physical-and-catalog provisioning
+  action followed by an existing-target apply with no automatic Dolt commit.
+- Added independent synthetic golden fixtures, hashes, examples, and repository
+  validation gates for the new contracts.
 
 ## v0.2.0 - 2026-07-31
 

README.md

@@ -37,15 +37,18 @@ permits a transformation to mutate a core import.
 That separate derived-data profile is not used by the SPSS-like in-place
 frontend below.
 
-The [Transformation Plan Profile 0.1](docs/transformation-plan-profile-0.1.md)
-adds a canonical, language-neutral operation plan. The
-[SPSS Syntax Frontend Profile 0.1](docs/spss-syntax-frontend-profile-0.1.md)
-lowers a deliberately small `RECODE`, `VARIABLE LABELS`, and `VALUE LABELS`
-subset into that plan. The
-[in-place binding](docs/transformation-plan-sql-binding-0.1.md) applies the plan
+The release-candidate [Transformation Plan Profile 0.2](docs/transformation-plan-profile-0.2.md)
+adds sequential bounded numeric assignment and conditional assignment to the
+unchanged 0.1 operations. The
+[SPSS Syntax Frontend Profile 0.2](docs/spss-syntax-frontend-profile-0.2.md)
+lowers `COMPUTE`, `IF`, `FORMATS`, `VARIABLE LEVEL`, and `EXECUTE`
+alongside the 0.1 `RECODE`, `VARIABLE LABELS`, and `VALUE LABELS` subset.
+Programs using only the 0.1 subset retain exact 0.1 plan identity and hash. The
+[in-place binding](docs/transformation-plan-sql-binding-0.2.md) applies the plan
 to the same dataset and same physical wide table on supported SQL profiles. It
 creates no derived dataset, data copy, or OpenStatSpec undo layer; Dolt-specific
-history and commits remain Dolt's.
+history and commits remain Dolt's. MySQL, MariaDB, and Dolt require a new target
+to be provisioned separately before an in-place transformation apply.
 
 ## Repository layout
 
@@ -62,17 +65,19 @@ history and commits remain Dolt's.
 - `transformation/plan-0.1.schema.json` — canonical transformation-plan schema.
 - `sql/transformation-plan-profile-schema.sql` — compact in-place apply audit;
   it is not a dataset-version catalog.
-- `conformance/transformation-plan-0.1.json` and
-  `conformance/spss-syntax-frontend-0.1.json` — plan and frontend conformance
-  cases with canonical hashes; `conformance/in-place-transformation-0.1.json`
+- `conformance/transformation-plan-0.2.json` and
+  `conformance/spss-syntax-frontend-0.2.json` — additive plan and frontend
+  conformance cases with independent golden hashes; `conformance/in-place-transformation-0.2.json`
   fixes the same-dataset/same-table execution invariants and the additional
-  controlled Dolt context.
+  controlled Dolt context. The 0.1 schemas and fixtures remain unchanged.
 - `examples/` — small illustrative mapping fixtures.
 
 ## Conformance principle
 
 Implementations must preflight target capabilities before import. If the target cannot faithfully create one wide table because of column, identifier, string, or row limits, import must fail atomically with a machine-readable capability diagnostic. It must never silently truncate, drop, split, transpose, pivot, or transform source data.
 
+This specification repository publishes only normative Transformation Plan and SPSS syntax frontend schemas, documentation, and declarative fixtures. Executable validation or behavioral conformance code, including parser, SQL-engine, transaction, and adapter behavior, belongs in each implementation or adapter repository.
+
 ## Who it is for
 
 OpenStatSpec is for people and projects that need to move statistical datasets between SPSS and relational databases without turning the data into a different model. It is especially relevant to:

VERSIONING.md

@@ -11,6 +11,15 @@ core source profile. Adding or revising an optional profile does not authorize
 changes to core datasets. A breaking workflow-profile change increments that
 profile's major version even when the core version is unchanged.
 
+Transformation Plan and frontend contracts are selected by their exact
+contract identifiers. An implementation may support multiple versions
+simultaneously. It MUST preserve the canonical bytes and hashes of accepted
+older plans and MUST NOT silently reinterpret or rewrite an older plan under a
+newer schema. A frontend that accepts a newer request contract but receives a
+program entirely inside the 0.1 command subset emits the exact 0.1 plan
+contract. Explicit recompilation to a newer plan is a new identified operation,
+not migration of the old plan or audit row.
+
 The SPSS SAV/ZSAV profile is versioned independently in its document and manifest. A conforming implementation must publish the exact profile version, immutable specification commit, specification status, supported directions, supported SQL profiles, and engine capability declaration it tested.
 
 The immutable commit is mandatory for both release candidates and stable releases. `specification_release` is additive provenance, not an alternative to the commit: