openstatspec 0.2.0__tar.gz → 0.3.0__tar.gz

{openstatspec-0.2.0 → openstatspec-0.3.0}/.github/workflows/ci.yml

@@ -20,7 +20,7 @@ jobs:
         uses: actions/checkout@v7
         with: &specification-checkout
           repository: OpenStatSpec/specification
-          ref: fef0dc6f4b17ff7141dad3f49d0524c63efbfed5
+          ref: 79339ec3d8f8aa81789b7e85f6b8afa6f1374e50
           path: openstatspec-specification
       - name: Checkout required SPSS engine
         uses: actions/checkout@v7
@@ -63,7 +63,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        postgres: ["17", "18"]
+        postgres: ["17.10", "18.4"]
     services:
       postgres:
         image: postgres:${{ matrix.postgres }}
@@ -77,6 +77,7 @@ jobs:
           --health-interval 10s --health-timeout 5s --health-retries 5
     env:
       OPENSTATSPEC_POSTGRES_URL: postgresql+psycopg://openstatspec:openstatspec@localhost:5432/openstatspec
+      OPENSTATSPEC_EXPECTED_POSTGRES_VERSION: ${{ matrix.postgres }}
     steps: &sql-test-steps
       - uses: actions/checkout@v7
       - name: Checkout OpenStatSpec specification fixtures
@@ -99,7 +100,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        mysql: ["8.4", "9.7"]
+        mysql: ["8.4.11", "9.7.2"]
     services:
       mysql:
         image: mysql:${{ matrix.mysql }}
@@ -114,6 +115,7 @@ jobs:
           --health-interval 10s --health-timeout 5s --health-retries 10
     env:
       OPENSTATSPEC_MYSQL_URL: mysql+pymysql://openstatspec:openstatspec@localhost:3306/openstatspec
+      OPENSTATSPEC_EXPECTED_MYSQL_VERSION: ${{ matrix.mysql }}
     steps: *sql-test-steps
 
   mariadb-integration:
@@ -122,7 +124,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        mariadb: ["11.4", "11.8", "12.3"]
+        mariadb: ["11.4.12", "11.8.8", "12.3.2"]
     services:
       mariadb:
         image: mariadb:${{ matrix.mariadb }}
@@ -137,13 +139,24 @@ jobs:
           --health-interval 10s --health-timeout 5s --health-retries 10
     env:
       OPENSTATSPEC_MARIADB_URL: mysql+pymysql://openstatspec:openstatspec@localhost:3306/openstatspec
+      OPENSTATSPEC_EXPECTED_MARIADB_VERSION: ${{ matrix.mariadb }}
     steps: *sql-test-steps
 
   dolt-integration:
-    name: Dolt 2.2.2 integration
+    name: Dolt ${{ matrix.dolt }} integration
     runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - dolt: "2.2.2"
+            image: dolthub/dolt:2.2.2@sha256:ae85afdd95317f0a982cab87fa3092a5a2e6689bc5de822ad7ae4f65b86d39a1
+          - dolt: "2.2.3"
+            image: dolthub/dolt:2.2.3@sha256:1a651e738a2e7275b9c69fec8c5f42c6e23954314405c412f4dc9287ee7c0080
     env:
       OPENSTATSPEC_DOLT_URL: mysql+pymysql://openstatspec:openstatspec@127.0.0.1:13308/openstatspec
+      OPENSTATSPEC_EXPECTED_DOLT_VERSION: ${{ matrix.dolt }}
+      OPENSTATSPEC_DOLT_IMAGE: ${{ matrix.image }}
     steps:
       - uses: actions/checkout@v7
       - name: Checkout OpenStatSpec specification fixtures
@@ -155,29 +168,29 @@ jobs:
       - uses: actions/setup-python@v7
         with:
           python-version: "3.12"
-      - name: Initialize Dolt 2.2.2
+      - name: Initialize Dolt ${{ matrix.dolt }}
         run: |
           mkdir -p "$RUNNER_TEMP/openstatspec-dolt"
           docker run --rm \
             --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
             --workdir /var/lib/dolt \
-            dolthub/dolt:2.2.2 init \
+            "$OPENSTATSPEC_DOLT_IMAGE" init \
             --name "OpenStatSpec CI" --email "ci@openstatspec.org"
           docker run --rm \
             --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
             --workdir /var/lib/dolt \
-            dolthub/dolt:2.2.2 sql \
+            "$OPENSTATSPEC_DOLT_IMAGE" sql \
             -q "CREATE DATABASE openstatspec"
           docker run --rm \
             --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
             --workdir /var/lib/dolt \
-            dolthub/dolt:2.2.2 sql \
+            "$OPENSTATSPEC_DOLT_IMAGE" sql \
             -q "CREATE USER 'openstatspec'@'%' IDENTIFIED BY 'openstatspec'; GRANT ALL PRIVILEGES ON openstatspec.* TO 'openstatspec'@'%'"
           docker run --detach --name openstatspec-dolt \
             --publish 127.0.0.1:13308:3306 \
             --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
             --workdir /var/lib/dolt \
-            dolthub/dolt:2.2.2 sql-server -H 0.0.0.0 -l warning
+            "$OPENSTATSPEC_DOLT_IMAGE" sql-server -H 0.0.0.0 -l warning
       - run: python -m pip install --upgrade pip
       - run: python -m pip install ./openstatspec-pyspssio
       - run: python -m pip install -e ".[dev,sql]"

{openstatspec-0.2.0 → openstatspec-0.3.0}/.github/workflows/release.yml

@@ -47,7 +47,7 @@ jobs:
         uses: actions/checkout@v7
         with:
           repository: OpenStatSpec/specification
-          ref: fef0dc6f4b17ff7141dad3f49d0524c63efbfed5
+          ref: 79339ec3d8f8aa81789b7e85f6b8afa6f1374e50
           path: openstatspec-specification
       - name: Checkout required SPSS engine
         uses: actions/checkout@v7

{openstatspec-0.2.0 → openstatspec-0.3.0}/CHANGELOG.md

@@ -2,6 +2,39 @@
 
 All notable changes to this reference implementation are documented here.
 
+## 0.3.0 — 2026-07-31
+
+### Added
+
+- Added a bounded SPSS-like `RECODE`, `VARIABLE LABELS`, and `VALUE LABELS`
+  parser with stable diagnostics and conformance fixtures.
+- Added canonical Transformation Plan serialization, RFC 8785 hashes, schema
+  binding, deterministic typed operations, and an agent-facing CLI/API.
+- Added product-neutral in-place execution with same dataset/table identity,
+  direct data and metadata mutation, and compact operation audit. Dolt adds
+  expected branch/HEAD and clean-working-set checks.
+
+### Changed
+
+- Version history, diff, rollback, restoration, and commit remain database
+  responsibilities; the transformer creates no derived/copy/snapshot/recovery
+  layer and performs no `DOLT_COMMIT`.
+- SQL server support now distinguishes conservative family claims from exact
+  CI evidence: PostgreSQL 17.x/18.x at 17.10/18.4, MySQL 8.4.x/9.7.x at
+  8.4.11/9.7.2, and MariaDB 11.4.x/11.8.x/12.3.x at
+  11.4.12/11.8.8/12.3.2. Each service job verifies the live normalized version.
+- Dolt remains an independent core profile, now claiming canonical stable
+  versions `>=2.2.2,<2.3.0` and running its complete service suite at exact
+  versions 2.2.2 and 2.2.3 from immutable container-image pins.
+  SQLite retains its core `>=3.24.0,<4.0.0` and optional workflow
+  `>=3.35.0,<4.0.0` tiers. MSSQL remains unsupported and roadmap-only.
+
+### Specification basis
+
+- CI, release validation, and machine-readable capabilities use OpenStatSpec
+  specification release `v0.2.0` at exact commit
+  `79339ec3d8f8aa81789b7e85f6b8afa6f1374e50`.
+
 ## 0.2.0 — 2026-07-30
 
 This release extends the reference adapter while keeping imported source

{openstatspec-0.2.0 → openstatspec-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: openstatspec
-Version: 0.2.0
+Version: 0.3.0
 Summary: Reference adapter for the OpenStatSpec relational contract
 Author: OpenStatSpec
 License: Apache-2.0
@@ -69,12 +69,58 @@ derived datasets through a public catalog API. It uses a separate profile
 catalog and never presents SQL output as an imported source dataset.
 Workflow operations support SQLite only in this milestone and fail closed on
 PostgreSQL/MySQL/MariaDB; core import/export database support is unchanged.
+The core SQLite import/export profile accepts SQLite `>=3.24.0,<4.0.0`; the
+optional transformation workflow deliberately has the narrower
+`>=3.35.0,<4.0.0` runtime preflight. These independent tiers do not change the
+server-profile matrix. Microsoft SQL Server is not supported; its future
+dialect is scoped only in the specification's
+[MSSQL roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
 
 See [the SQL transformation workflow](docs/sql-transformation-workflow.md) for
 Python and CLI examples, migration behavior, hashing, atomicity, and the exact
 implemented capability boundary.
 
-## 0.2.0 support status
+## SPSS-like transformation frontend
+
+The transformation frontend accepts `RECODE`, `VARIABLE LABELS`, and
+`VALUE LABELS`, lowers them to a canonical OpenStatSpec Transformation Plan,
+and mutates the same logical dataset and physical wide table. SQLite,
+PostgreSQL, MySQL, MariaDB, and Dolt connections are allowed. It creates no
+derived dataset, copied table, snapshot, or OpenStatSpec rollback/version layer.
+
+Install the compact operation-audit relation separately, then apply syntax:
+
+```python
+from openstatspec import (
+    apply_spss_in_place,
+    install_in_place_transformation_schema,
+)
+
+database_url = "postgresql+psycopg://user:password@host/database"
+install_in_place_transformation_schema(database_url=database_url)
+result = apply_spss_in_place(
+    database_url=database_url,
+    dataset_id="...",
+    actor="agent@example.org",
+    source_text="""
+      RECODE age (18 THRU 34 = 1) (35 THRU 64 = 2) INTO age_group.
+      VARIABLE LABELS age_group 'Age group'.
+      VALUE LABELS age_group 1 '18-34' 2 '35-64'.
+    """,
+)
+```
+
+Existing-target recodes and metadata mutations use direct DML. SQLite and
+PostgreSQL may also add a target column in the same native transaction. MySQL,
+MariaDB, and Dolt reject such schema-changing plans before mutation because
+their implicit-commit DDL could otherwise leave a partial apply. On Dolt, the
+caller additionally supplies expected branch and HEAD identities, and the
+working set must be clean. The transformer never calls `DOLT_COMMIT`.
+
+See [in-place transformations](docs/in-place-transformation.md) for the full
+execution boundary and CLI form.
+
+## Current support status
 
 The adapter requires `openstatspec-pyspssio==0.5.1.post2` as its sole SPSS
 engine. Its import module remains `pyspssio`; the exact source commit is recorded
@@ -82,13 +128,36 @@ in operation metadata. There is no fallback reader or writer. It supports unencr
 SAV/ZSAV export for the semantics exposed by that engine. SQLite is the local
 reference path.
 PostgreSQL, MySQL, MariaDB, and Dolt are each covered by separate service-backed CI
-conformance checks. Dolt support is an independent core profile pinned to 2.2.2;
-other Dolt versions and unknown MySQL-wire products fail closed. Use these explicit SQLAlchemy URLs:
+conformance checks. Dolt support is an independent core profile for the
+canonical stable range `>=2.2.2,<2.3.0`; earlier patches, other families,
+noncanonical versions, and unknown MySQL-wire products fail closed.
+
+The supported family claims are broader than the deliberately exact CI
+evidence points: PostgreSQL 17.x/18.x is exercised at 17.10/18.4, MySQL
+8.4.x/9.7.x at 8.4.11/9.7.2, and MariaDB 11.4.x/11.8.x/12.3.x at
+11.4.12/11.8.8/12.3.2. Each service job checks the normalized live server
+version against its exact matrix entry before that run can count as evidence.
+Dolt claims the conservative 2.2.x range `>=2.2.2,<2.3.0`; its full service
+suite is exercised independently at exact versions 2.2.2 and 2.2.3 using
+immutable container-image digests.
+
+| Engine/profile | Runtime supported policy | Exact CI-tested versions |
+| --- | --- | --- |
+| SQLite core / optional workflow | Core `>=3.24.0,<4.0.0`; optional workflow `>=3.35.0,<4.0.0` | Runtime-provided SQLite on Python 3.11–3.14 runners; not a pinned server image |
+| PostgreSQL | 17.x and 18.x | 17.10 and 18.4 |
+| MySQL | 8.4.x and 9.7.x | 8.4.11 and 9.7.2 |
+| MariaDB | 11.4.x, 11.8.x, and 12.3.x | 11.4.12, 11.8.8, and 12.3.2 |
+| Dolt | 2.2.x with `>=2.2.2,<2.3.0` | 2.2.2 and 2.2.3 |
+
+Microsoft SQL Server (MSSQL) remains roadmap-only and is not a supported
+runtime profile; see the specification's [MSSQL roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
+
+Use these explicit SQLAlchemy URLs:
 
 - SQLite: `sqlite:///dataset.sqlite`
 - PostgreSQL: `postgresql+psycopg://user:password@host/database`
 - MySQL/MariaDB: `mysql+pymysql://user:password@host/database`
-- Dolt 2.2.2: `mysql+pymysql://user:password@host/database` (detected by server identity)
+- Dolt `>=2.2.2,<2.3.0`: `mysql+pymysql://user:password@host/database` (detected by server identity)
 
 The Dolt core profile supports strict wide-table import, validation, and export;
 the separate Transformation Workflow is unsupported.

{openstatspec-0.2.0 → openstatspec-0.3.0}/README.md

@@ -50,12 +50,58 @@ derived datasets through a public catalog API. It uses a separate profile
 catalog and never presents SQL output as an imported source dataset.
 Workflow operations support SQLite only in this milestone and fail closed on
 PostgreSQL/MySQL/MariaDB; core import/export database support is unchanged.
+The core SQLite import/export profile accepts SQLite `>=3.24.0,<4.0.0`; the
+optional transformation workflow deliberately has the narrower
+`>=3.35.0,<4.0.0` runtime preflight. These independent tiers do not change the
+server-profile matrix. Microsoft SQL Server is not supported; its future
+dialect is scoped only in the specification's
+[MSSQL roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
 
 See [the SQL transformation workflow](docs/sql-transformation-workflow.md) for
 Python and CLI examples, migration behavior, hashing, atomicity, and the exact
 implemented capability boundary.
 
-## 0.2.0 support status
+## SPSS-like transformation frontend
+
+The transformation frontend accepts `RECODE`, `VARIABLE LABELS`, and
+`VALUE LABELS`, lowers them to a canonical OpenStatSpec Transformation Plan,
+and mutates the same logical dataset and physical wide table. SQLite,
+PostgreSQL, MySQL, MariaDB, and Dolt connections are allowed. It creates no
+derived dataset, copied table, snapshot, or OpenStatSpec rollback/version layer.
+
+Install the compact operation-audit relation separately, then apply syntax:
+
+```python
+from openstatspec import (
+    apply_spss_in_place,
+    install_in_place_transformation_schema,
+)
+
+database_url = "postgresql+psycopg://user:password@host/database"
+install_in_place_transformation_schema(database_url=database_url)
+result = apply_spss_in_place(
+    database_url=database_url,
+    dataset_id="...",
+    actor="agent@example.org",
+    source_text="""
+      RECODE age (18 THRU 34 = 1) (35 THRU 64 = 2) INTO age_group.
+      VARIABLE LABELS age_group 'Age group'.
+      VALUE LABELS age_group 1 '18-34' 2 '35-64'.
+    """,
+)
+```
+
+Existing-target recodes and metadata mutations use direct DML. SQLite and
+PostgreSQL may also add a target column in the same native transaction. MySQL,
+MariaDB, and Dolt reject such schema-changing plans before mutation because
+their implicit-commit DDL could otherwise leave a partial apply. On Dolt, the
+caller additionally supplies expected branch and HEAD identities, and the
+working set must be clean. The transformer never calls `DOLT_COMMIT`.
+
+See [in-place transformations](docs/in-place-transformation.md) for the full
+execution boundary and CLI form.
+
+## Current support status
 
 The adapter requires `openstatspec-pyspssio==0.5.1.post2` as its sole SPSS
 engine. Its import module remains `pyspssio`; the exact source commit is recorded
@@ -63,13 +109,36 @@ in operation metadata. There is no fallback reader or writer. It supports unencr
 SAV/ZSAV export for the semantics exposed by that engine. SQLite is the local
 reference path.
 PostgreSQL, MySQL, MariaDB, and Dolt are each covered by separate service-backed CI
-conformance checks. Dolt support is an independent core profile pinned to 2.2.2;
-other Dolt versions and unknown MySQL-wire products fail closed. Use these explicit SQLAlchemy URLs:
+conformance checks. Dolt support is an independent core profile for the
+canonical stable range `>=2.2.2,<2.3.0`; earlier patches, other families,
+noncanonical versions, and unknown MySQL-wire products fail closed.
+
+The supported family claims are broader than the deliberately exact CI
+evidence points: PostgreSQL 17.x/18.x is exercised at 17.10/18.4, MySQL
+8.4.x/9.7.x at 8.4.11/9.7.2, and MariaDB 11.4.x/11.8.x/12.3.x at
+11.4.12/11.8.8/12.3.2. Each service job checks the normalized live server
+version against its exact matrix entry before that run can count as evidence.
+Dolt claims the conservative 2.2.x range `>=2.2.2,<2.3.0`; its full service
+suite is exercised independently at exact versions 2.2.2 and 2.2.3 using
+immutable container-image digests.
+
+| Engine/profile | Runtime supported policy | Exact CI-tested versions |
+| --- | --- | --- |
+| SQLite core / optional workflow | Core `>=3.24.0,<4.0.0`; optional workflow `>=3.35.0,<4.0.0` | Runtime-provided SQLite on Python 3.11–3.14 runners; not a pinned server image |
+| PostgreSQL | 17.x and 18.x | 17.10 and 18.4 |
+| MySQL | 8.4.x and 9.7.x | 8.4.11 and 9.7.2 |
+| MariaDB | 11.4.x, 11.8.x, and 12.3.x | 11.4.12, 11.8.8, and 12.3.2 |
+| Dolt | 2.2.x with `>=2.2.2,<2.3.0` | 2.2.2 and 2.2.3 |
+
+Microsoft SQL Server (MSSQL) remains roadmap-only and is not a supported
+runtime profile; see the specification's [MSSQL roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
+
+Use these explicit SQLAlchemy URLs:
 
 - SQLite: `sqlite:///dataset.sqlite`
 - PostgreSQL: `postgresql+psycopg://user:password@host/database`
 - MySQL/MariaDB: `mysql+pymysql://user:password@host/database`
-- Dolt 2.2.2: `mysql+pymysql://user:password@host/database` (detected by server identity)
+- Dolt `>=2.2.2,<2.3.0`: `mysql+pymysql://user:password@host/database` (detected by server identity)
 
 The Dolt core profile supports strict wide-table import, validation, and export;
 the separate Transformation Workflow is unsupported.

openstatspec-0.3.0/docs/in-place-transformation.md

@@ -0,0 +1,41 @@
+# In-place SPSS-like transformation
+
+`openstatspec.apply_spss_in_place` is the public execution path for the
+SPSS-like frontend. It accepts `RECODE`, `VARIABLE LABELS`, and `VALUE LABELS`,
+binds them to the existing core dataset, and applies the canonical plan to that
+same SQL wide table and metadata catalog.
+
+The caller supplies a supported SQL URL, the existing normative `dataset_id`,
+and a non-empty actor identity. For Dolt, the caller also supplies the expected
+active branch and current `HEAD` hash.
+
+Install the compact audit relation once with
+`openstatspec.install_in_place_transformation_schema(database_url=...)` before
+the first apply. Apply never creates schema-management objects itself.
+
+The adapter uses the engine's ordinary transaction behavior. On Dolt it first
+checks branch and HEAD and requires `dolt_status` to be empty. Existing-target
+recodes are one direct `UPDATE`. SQLite and PostgreSQL can add a new numeric
+`INTO` target to the same table. MySQL, MariaDB, and Dolt require that target
+column and variable metadata to exist before apply because their DDL can commit
+independently of the following data and metadata changes. Label commands
+update/replace the same dataset's normative and compatibility metadata rows.
+
+One compact `transformation_apply` row records operation identity, canonical
+plan/source hashes, actor, status, timestamps, and the observed Dolt branch and
+HEAD. It contains no row values and points to no copied table.
+
+The adapter does not create `derived_dataset` rows, persistent output tables,
+full-table copies, staging datasets, snapshots, rollback tables, retirement
+records, or a recovery/version catalog. It does not call `DOLT_COMMIT`, change
+branches, merge, reset, or tag. After success, the caller reviews `dolt diff`
+and independently decides whether to commit or restore the working set.
+
+The local SQLite tests exercise the public mutation path and assert that
+dataset/table counts and identities do not change. Live PostgreSQL/MySQL/MariaDB and
+exact-version Dolt service evidence remains required before release execution
+claims for those engines.
+
+```text
+openstatspec apply-spss --database-url mysql+pymysql://user:password@host/database --dataset-id ... --actor agent@example.org --expected-branch feature/recode --expected-head ... --syntax-file transform.sps
+```

{openstatspec-0.2.0 → openstatspec-0.3.0}/docs/release-readiness.md

@@ -1,4 +1,4 @@
-# 0.2.0 release readiness
+# 0.3.0 release readiness
 
 This page records the expected release contract, not a publication event.
 Creating a version tag remains a separate maintainer action.
@@ -14,21 +14,30 @@ database contract.
 
 ## SQL profiles
 
-| Profile | Connection URL | Verification |
-| --- | --- | --- |
-| SQLite | `sqlite:///dataset.sqlite` | Python 3.11–3.14 local reference jobs |
-| PostgreSQL | `postgresql+psycopg://…` | PostgreSQL 17 and 18 service jobs |
-| MySQL | `mysql+pymysql://…` | MySQL 8.4 and 9.7 service jobs |
-| MariaDB | `mysql+pymysql://…` | MariaDB 11.4, 11.8, and 12.3 service jobs |
-| Dolt | `mysql+pymysql://…` | Exact Dolt 2.2.2 service job |
+| Profile | Connection URL | Claimed versions | Exact CI evidence |
+| --- | --- | --- | --- |
+| SQLite | `sqlite:///dataset.sqlite` | `>=3.24.0,<4.0.0` | Active Python 3.11–3.14 runner version |
+| PostgreSQL | `postgresql+psycopg://…` | 17.x and 18.x | 17.10 and 18.4 |
+| MySQL | `mysql+pymysql://…` | 8.4.x and 9.7.x | 8.4.11 and 9.7.2 |
+| MariaDB | `mysql+pymysql://…` | 11.4.x, 11.8.x, and 12.3.x | 11.4.12, 11.8.8, and 12.3.2 |
+| Dolt | `mysql+pymysql://…` | 2.2.x with `>=2.2.2,<2.3.0` | 2.2.2 and 2.2.3 |
 
 Separate service matrices test the shared MySQL/MariaDB profile contract while
 retaining distinct active-server identities and version claims. Dolt is an
-independent core profile that fails closed unless the product version is exactly
-2.2.2; the optional Transformation Workflow remains SQLite-only. This does not
+independent core profile that accepts only canonical stable versions in
+`>=2.2.2,<2.3.0`; the optional Transformation Workflow remains SQLite-only. This does not
 claim coverage for every server configuration. The machine-readable capability
 declaration reports both the theoretical profile boundaries and effective
 limits observed from the active connection.
+Every server service job compares the normalized live product version with its
+exact matrix entry, so a moved or mismatched image cannot substantiate the CI
+declaration. SQLite's optional Transformation Workflow retains its narrower
+`>=3.35.0,<4.0.0` live preflight alongside the core `>=3.24.0,<4.0.0` policy.
+Microsoft SQL Server remains unsupported and must not appear in runtime
+capabilities; future implementation requirements are documented in the
+specification's
+[MSSQL dialect roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
+
 
 ## Export-loss policy
 
@@ -53,14 +62,15 @@ machine-readable loss report with the export result.
    first and confirm that a clean environment can download it from PyPI. The
    main package has no fallback SPSS engine.
 2. Run `python -m pytest -m "not services"`.
-3. Confirm the GitHub Actions matrix is green for PostgreSQL 17/18, MySQL
-   8.4/9.7, MariaDB 11.4/11.8/12.3, and exact Dolt 2.2.2.
+3. Confirm the GitHub Actions matrix is green for exact PostgreSQL 17.10/18.4,
+   MySQL 8.4.11/9.7.2, MariaDB 11.4.12/11.8.8/12.3.2, and exact Dolt
+   2.2.2/2.2.3 service evidence from the immutable image pins in CI.
 4. Build with `python -m build` and install the generated wheel in a clean
    environment.
 5. Confirm `openstatspec capabilities` reflects the intended support boundary.
-6. Confirm the `v0.2.0` tag matches package version `0.2.0`, and that CI and
-   release fixtures use specification release `v1.0.0-rc.1` at exact commit
-   `fef0dc6f4b17ff7141dad3f49d0524c63efbfed5`.
+6. Confirm the release tag matches the package version and that CI, release
+   fixtures, and capabilities use OpenStatSpec specification release `v0.2.0`
+   at exact commit `79339ec3d8f8aa81789b7e85f6b8afa6f1374e50`.
 7. Review this document, the README, and CHANGELOG for accurate scope.
 
 The tag-triggered release workflow repeats the non-service test suite, builds

{openstatspec-0.2.0 → openstatspec-0.3.0}/docs/sav-profile.md

@@ -15,12 +15,27 @@ unencrypted .sav and .zsav files, and writes both formats through the same imple
 
 SQLite has a local reference fixture. PostgreSQL, MySQL, MariaDB, and Dolt have
 separate service-backed conformance checks in GitHub Actions that import,
-validate, and export the supported fixture. Dolt is an independent core profile
-pinned to exact server version 2.2.2 and detected over `mysql+pymysql` by active
-server identity; other Dolt versions and unknown MySQL-wire products fail closed.
-The core Dolt profile does not claim support for the separate Transformation
-Workflow. An import that exceeds a target's strict single-table column or row
-envelope fails before it creates a dataset.
+validate, and export the supported fixture. The family claims and exact CI
+points are PostgreSQL 17.x/18.x at 17.10/18.4, MySQL 8.4.x/9.7.x at
+8.4.11/9.7.2, and MariaDB 11.4.x/11.8.x/12.3.x at
+11.4.12/11.8.8/12.3.2. CI compares each live normalized server version with
+that exact evidence point.
+
+Dolt is an independent core profile for canonical stable versions in
+`>=2.2.2,<2.3.0`, detected over `mysql+pymysql` by active server identity and
+service-tested at exact versions 2.2.2 and 2.2.3. Earlier patches, other
+families, noncanonical versions, and unknown MySQL-wire products fail closed.
+The core Dolt profile does not
+claim support for the separate Transformation Workflow. An import that exceeds
+a target's strict single-table column or row envelope fails before it creates a
+dataset.
+
+The core SQLite profile remains `>=3.24.0,<4.0.0`; only the optional
+Transformation Workflow requires `>=3.35.0,<4.0.0`. Microsoft SQL Server is
+not a supported profile. Its driver, SQL-difference, preflight, CI,
+conformance, security, and atomicity work is future scope in the
+specification's
+[MSSQL dialect roadmap](https://github.com/OpenStatSpec/specification/blob/main/docs/mssql-dialect-roadmap.md).
 
 ## Fidelity contract
 

{openstatspec-0.2.0 → openstatspec-0.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "openstatspec"
-version = "0.2.0"
+version = "0.3.0"
 description = "Reference adapter for the OpenStatSpec relational contract"
 readme = "README.md"
 requires-python = ">=3.11"

openstatspec-0.3.0/src/openstatspec/__init__.py

@@ -0,0 +1,32 @@
+"""Public API for the OpenStatSpec Python reference implementation."""
+
+from .api import (
+    apply_spss_in_place, capabilities, capability_matrix, derive_sql_dataset,
+    execute_sql_transformation,
+    export_sav, get_dataset, import_sav, inspect,
+    install_in_place_transformation_schema, list_datasets,
+    register_sql_transformation, reconcile_derived_removals,
+    reconcile_sql_transformation_runs,
+    remove_derived_physical_relation, retire_derived, validate, validate_derived,
+)
+from .core import CapabilityDeclaration, LossReport, UnsupportedOperationError
+from .sql.workflow import TransformationError
+from .transform import (
+    SpssFrontendCompilation, TransformationFrontendError,
+    VariableDefinition, VariableSchema, compile_spss_syntax,
+)
+
+__all__ = [
+    "CapabilityDeclaration", "LossReport", "SpssFrontendCompilation",
+    "TransformationError", "TransformationFrontendError",
+    "VariableDefinition", "VariableSchema",
+    "UnsupportedOperationError", "capabilities", "capability_matrix",
+    "apply_spss_in_place", "compile_spss_syntax", "derive_sql_dataset",
+    "execute_sql_transformation", "export_sav",
+    "get_dataset", "import_sav", "inspect",
+    "install_in_place_transformation_schema", "list_datasets",
+    "register_sql_transformation", "reconcile_derived_removals",
+    "reconcile_sql_transformation_runs",
+    "remove_derived_physical_relation", "retire_derived", "validate",
+    "validate_derived",
+]

{openstatspec-0.2.0 → openstatspec-0.3.0}/src/openstatspec/api.py

@@ -20,6 +20,11 @@ from .sql.workflow import (
     remove_derived_relation as _remove_derived_relation,
     retire_derived_dataset as _retire_derived_dataset,
 )
+from .sql.inplace_transform import (
+    apply_spss_in_place as _apply_spss_in_place,
+    in_place_transformation_capabilities,
+    install_in_place_transformation_schema as _install_in_place_schema,
+)
 from .sql.capabilities import (
     SPECIFICATION_COMMIT, SPECIFICATION_RELEASE, active_connection, catalog_binding,
 )
@@ -37,7 +42,7 @@ def capability_matrix(database_url: str | None = None) -> Mapping[str, Any]:
     """
     declaration = {
         "specification": "OpenStatSpec",
-        "specification_status": "release_candidate",
+        "specification_status": "released",
         "specification_release": SPECIFICATION_RELEASE,
         "specification_commit": SPECIFICATION_COMMIT,
         "profile": "SPSS SAV/ZSAV 1.0",
@@ -84,6 +89,9 @@ def capability_matrix(database_url: str | None = None) -> Mapping[str, Any]:
         "sql_profiles": declared_profiles(database_url),
         "optional_profiles": {
             "sql_transformation_workflow": transformation_capabilities(database_url),
+            "spss_in_place_transformation": (
+                in_place_transformation_capabilities()
+            ),
         },
     }
     return declaration
@@ -130,6 +138,27 @@ def derive_sql_dataset(*, database_url: Any, **options: Any) -> Mapping[str, Any
     return result(_derive_dataset(database_url=str(database_url), **options))
 
 
+def apply_spss_in_place(
+    *, database_url: Any, dataset_id: str, source_text: str,
+    actor: str, expected_branch: str | None = None,
+    expected_head: str | None = None,
+) -> Mapping[str, Any]:
+    """Apply supported SPSS-like syntax to the same SQL dataset/table."""
+    return result(_apply_spss_in_place(
+        database_url=str(database_url),
+        dataset_id=dataset_id,
+        source_text=source_text,
+        actor=actor,
+        expected_branch=expected_branch,
+        expected_head=expected_head,
+    ))
+
+
+def install_in_place_transformation_schema(*, database_url: Any) -> None:
+    """Install the compact apply-audit relation before the first apply."""
+    _install_in_place_schema(database_url=str(database_url))
+
+
 def validate_derived(*, database_url: Any, derived_dataset_id: str) -> Mapping[str, Any]:
     return result(_validate_derived_dataset(
         database_url=str(database_url), derived_dataset_id=derived_dataset_id,