openstatspec 0.7.1__tar.gz → 0.8.0__tar.gz

{openstatspec-0.7.1 → openstatspec-0.8.0}/.github/workflows/ci.yml

@@ -20,7 +20,7 @@ jobs:
         uses: actions/checkout@v7
         with: &specification-checkout
           repository: OpenStatSpec/specification
-          ref: cd8f198c68b849eb8ed018a894670a0904c2181d
+          ref: 864e84479f554b8ee250ffed44c4dfb963750d4a
           path: openstatspec-specification
       - name: Checkout required SPSS engine
         uses: actions/checkout@v7
@@ -53,9 +53,9 @@ jobs:
       - run: python -m pip install --upgrade pip build
       - run: python -m build
       - run: python -m venv /tmp/openstatspec-wheel-smoke
-      - run: /tmp/openstatspec-wheel-smoke/bin/python -m pip install ./openstatspec-pyspssio
       - run: /tmp/openstatspec-wheel-smoke/bin/python -m pip install dist/*.whl
-      - run: /tmp/openstatspec-wheel-smoke/bin/openstatspec capabilities
+      - run: env -u PYTHONPATH /tmp/openstatspec-wheel-smoke/bin/openstatspec capabilities
+        working-directory: /tmp
 
   postgres-integration:
     name: PostgreSQL ${{ matrix.postgres }} integration
@@ -143,7 +143,7 @@ jobs:
     steps: *sql-test-steps
 
   dolt-integration:
-    name: Dolt ${{ matrix.dolt }} read-only / fail-closed integration
+    name: Dolt ${{ matrix.dolt }} default-write integration
     runs-on: ubuntu-latest
     strategy:
       fail-fast: false
@@ -155,6 +155,7 @@ jobs:
             image: dolthub/dolt:2.2.3@sha256:1a651e738a2e7275b9c69fec8c5f42c6e23954314405c412f4dc9287ee7c0080
     env:
       OPENSTATSPEC_DOLT_URL: mysql+pymysql://openstatspec:openstatspec@127.0.0.1:13308/openstatspec
+      OPENSTATSPEC_TEST_DOLT_ADMIN_URL: mysql+pymysql://openstatspec_test_admin:ci-admin@127.0.0.1:13308/
       OPENSTATSPEC_EXPECTED_DOLT_VERSION: ${{ matrix.dolt }}
       OPENSTATSPEC_DOLT_IMAGE: ${{ matrix.image }}
     steps:
@@ -186,6 +187,11 @@ jobs:
             --workdir /var/lib/dolt \
             "$OPENSTATSPEC_DOLT_IMAGE" sql \
             -q "CREATE USER 'openstatspec'@'%' IDENTIFIED BY 'openstatspec'; GRANT ALL PRIVILEGES ON openstatspec.* TO 'openstatspec'@'%'"
+          docker run --rm \
+            --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
+            --workdir /var/lib/dolt \
+            "$OPENSTATSPEC_DOLT_IMAGE" sql \
+            -q "CREATE USER 'openstatspec_test_admin'@'%' IDENTIFIED BY 'ci-admin'; GRANT ALL PRIVILEGES ON *.* TO 'openstatspec_test_admin'@'%' WITH GRANT OPTION"
           docker run --detach --name openstatspec-dolt \
             --publish 127.0.0.1:13308:3306 \
             --volume "$RUNNER_TEMP/openstatspec-dolt:/var/lib/dolt" \
@@ -218,6 +224,7 @@ jobs:
                   break
           PY
       - run: python -m pytest -m "services and not candidate_evidence"
+      - run: python -m pytest tests/test_read_only_export.py
       - name: Show Dolt logs on failure and stop server
         if: always()
         run: |

{openstatspec-0.7.1 → openstatspec-0.8.0}/.github/workflows/release.yml

@@ -48,7 +48,7 @@ jobs:
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           repository: OpenStatSpec/specification
-          ref: cd8f198c68b849eb8ed018a894670a0904c2181d
+          ref: 864e84479f554b8ee250ffed44c4dfb963750d4a
           path: openstatspec-specification
       - name: Checkout specification package source
         uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
@@ -159,9 +159,9 @@ jobs:
       - run: python -m pip install -e ".[dev]"
       - run: python -m pytest -m "not services"
       - run: python -m venv /tmp/openstatspec-release-smoke
-      - run: /tmp/openstatspec-release-smoke/bin/python -m pip install ./openstatspec-pyspssio
       - run: /tmp/openstatspec-release-smoke/bin/python -m pip install dist/openstatspec/openstatspec-*.whl
-      - run: /tmp/openstatspec-release-smoke/bin/openstatspec capabilities
+      - run: env -u PYTHONPATH /tmp/openstatspec-release-smoke/bin/openstatspec capabilities
+        working-directory: /tmp
       - name: Smoke-test specification wheel
         run: |
           python -m venv /tmp/openstatspec-specification-release-smoke

{openstatspec-0.7.1 → openstatspec-0.8.0}/CHANGELOG.md

@@ -6,6 +6,30 @@ All notable changes to this reference implementation are documented here.
 
 _No unreleased changes._
 
+## 0.8.0 - 2026-09-07
+
+### Changed
+
+- Pin released specification `v0.5.0` at exact commit
+  `864e84479f554b8ee250ffed44c4dfb963750d4a`, with normative status `released`.
+  Capabilities identify adapter version 0.8.0 and explicitly select SAV/ZSAV 1.0
+  with `database_io_policy=openstatspec-database-io-v1`.
+- Reads, inspection, validation, and SAV/ZSAV export no longer write database
+  operation/fidelity audit records, including on failure. Export diagnostics
+  and loss consent remain operation-scoped; export results omit `operation_id`.
+- Default Dolt writes use the packaged tested exact-version policy for 2.2.2
+  and 2.2.3 without user-supplied evidence files. Unknown/untested versions
+  remain blocked before mutation; explicit external overrides remain strict.
+  Safety budgets are not claimed as proven native server limits.
+- Dolt reads no longer require write-version declarations or the write
+  variable-count ceiling. Missing SQLite files are rejected without creation.
+- Exact Dolt 2.2.2/2.2.3 CI explicitly runs SELECT-only export success/failure
+  tests using a separate fixture-admin account; normal service permissions
+  and adapter permissions are unchanged. Wheel smoke installs resolve the
+  required engine from PyPI rather than a source checkout.
+
+No optional Transformation Workflow 0.3 implementation is claimed.
+
 ## 0.7.1 - 2026-08-12
 
 ### Changed

{openstatspec-0.7.1 → openstatspec-0.8.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: openstatspec
-Version: 0.7.1
+Version: 0.8.0
 Summary: Reference adapter for the OpenStatSpec relational contract
 Author: OpenStatSpec
 License: Apache-2.0
@@ -23,6 +23,10 @@ The reference Python implementation of the OpenStatSpec specification.
 
 This package implements the specification; it does not define or extend it.
 The normative model lives in the `OpenStatSpec/specification` repository.
+Python 0.8.0 pins released specification `v0.5.0` at
+`864e84479f554b8ee250ffed44c4dfb963750d4a` and selects SAV/ZSAV 1.0 with
+`database_io_policy=openstatspec-database-io-v1`. This does not claim
+implementation of the optional Transformation Workflow 0.3 profile.
 
 ## Boundaries
 
@@ -115,17 +119,19 @@ 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 for the
-canonical stable range `>=2.2.2,<2.3.0`; earlier patches, other families,
-noncanonical versions, and unknown MySQL-wire products fail closed.
+exact write-supported versions 2.2.2 and 2.2.3; all other versions (including
+2.3.0), noncanonical versions, and unknown MySQL-wire products fail closed for writes.
 
 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.
+Dolt's default-write service checks run independently at exact versions 2.2.2
+and 2.2.3 using immutable container-image digests. Release/CI owns this evidence;
+normal callers need no declaration or evidence files. The optional explicit
+`DoltConformanceSource` override remains strict and does not fall back to the
+default policy if its declarations are missing, invalid, or mismatched.
 
 | Engine/profile | Runtime supported policy | Exact CI-tested versions |
 | --- | --- | --- |
@@ -133,7 +139,7 @@ immutable container-image digests.
 | 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 |
+| Dolt writes | Exactly 2.2.2 and 2.2.3 | 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).
@@ -143,7 +149,7 @@ 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,<2.3.0`: `mysql+pymysql://user:password@host/database` (detected by server identity)
+- Dolt 2.2.2 or 2.2.3: `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.
@@ -151,8 +157,16 @@ the separate Transformation Workflow is unsupported.
 Run `openstatspec capabilities` before an integration to inspect the
 machine-readable feature matrix. Export is deliberately strict: if known
 dictionary semantics cannot be reproduced, it stops until you pass the exact
-diagnostic code with `--allow-loss`. This avoids silent loss while making an
-intentional lossy export auditable.
+diagnostic code with `--allow-loss`. Diagnostics are returned to the caller, not
+persisted. Reads, validation, and SAV/ZSAV export never write to the database,
+including on failure. Export returns no `operation_id` and needs only read
+permissions; Dolt reads have no write-version or write-variable-count gate.
+Read operations reject missing SQLite files without creating them. Imports and transformations
+use the packaged exact-version policy by default. Active driver/identity checks,
+limit preflight, and the clean expected branch/HEAD guard for in-place apply
+remain mandatory. Dolt's reported limits are adapter safety budgets, narrowed
+by the active packet limit, not proven native server ceilings; full boundary
+conformance is not claimed.
 
 The matrix is also available to Python callers as
 `openstatspec.capability_matrix()`. It distinguishes supported semantics from

{openstatspec-0.7.1 → openstatspec-0.8.0}/README.md

@@ -4,6 +4,10 @@ The reference Python implementation of the OpenStatSpec specification.
 
 This package implements the specification; it does not define or extend it.
 The normative model lives in the `OpenStatSpec/specification` repository.
+Python 0.8.0 pins released specification `v0.5.0` at
+`864e84479f554b8ee250ffed44c4dfb963750d4a` and selects SAV/ZSAV 1.0 with
+`database_io_policy=openstatspec-database-io-v1`. This does not claim
+implementation of the optional Transformation Workflow 0.3 profile.
 
 ## Boundaries
 
@@ -96,17 +100,19 @@ 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 for the
-canonical stable range `>=2.2.2,<2.3.0`; earlier patches, other families,
-noncanonical versions, and unknown MySQL-wire products fail closed.
+exact write-supported versions 2.2.2 and 2.2.3; all other versions (including
+2.3.0), noncanonical versions, and unknown MySQL-wire products fail closed for writes.
 
 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.
+Dolt's default-write service checks run independently at exact versions 2.2.2
+and 2.2.3 using immutable container-image digests. Release/CI owns this evidence;
+normal callers need no declaration or evidence files. The optional explicit
+`DoltConformanceSource` override remains strict and does not fall back to the
+default policy if its declarations are missing, invalid, or mismatched.
 
 | Engine/profile | Runtime supported policy | Exact CI-tested versions |
 | --- | --- | --- |
@@ -114,7 +120,7 @@ immutable container-image digests.
 | 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 |
+| Dolt writes | Exactly 2.2.2 and 2.2.3 | 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).
@@ -124,7 +130,7 @@ 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,<2.3.0`: `mysql+pymysql://user:password@host/database` (detected by server identity)
+- Dolt 2.2.2 or 2.2.3: `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.
@@ -132,8 +138,16 @@ the separate Transformation Workflow is unsupported.
 Run `openstatspec capabilities` before an integration to inspect the
 machine-readable feature matrix. Export is deliberately strict: if known
 dictionary semantics cannot be reproduced, it stops until you pass the exact
-diagnostic code with `--allow-loss`. This avoids silent loss while making an
-intentional lossy export auditable.
+diagnostic code with `--allow-loss`. Diagnostics are returned to the caller, not
+persisted. Reads, validation, and SAV/ZSAV export never write to the database,
+including on failure. Export returns no `operation_id` and needs only read
+permissions; Dolt reads have no write-version or write-variable-count gate.
+Read operations reject missing SQLite files without creating them. Imports and transformations
+use the packaged exact-version policy by default. Active driver/identity checks,
+limit preflight, and the clean expected branch/HEAD guard for in-place apply
+remain mandatory. Dolt's reported limits are adapter safety budgets, narrowed
+by the active packet limit, not proven native server ceilings; full boundary
+conformance is not claimed.
 
 The matrix is also available to Python callers as
 `openstatspec.capability_matrix()`. It distinguishes supported semantics from

{openstatspec-0.7.1 → openstatspec-0.8.0}/docs/release-readiness.md

@@ -1,8 +1,15 @@
-# 0.7.1 release readiness
+# 0.8.0 release readiness
 
 This page records the expected release contract, not a publication event.
 Creating a version tag remains a separate maintainer action.
 
+The release selects SAV/ZSAV 1.0 with the optional Database I/O Execution
+Policy `openstatspec-database-io-v1`. Reads and exports, including failures,
+write no database audit records; export results omit `operation_id` and return
+diagnostics to the caller. Reads must not create missing SQLite files or apply
+Dolt write-variable-count ceilings. This release does not claim implementation
+of the optional Transformation Workflow 0.3 profile.
+
 ## Supported workflow
 
 For a supported unencrypted SAV or ZSAV source, the adapter imports one source
@@ -20,15 +27,17 @@ database contract.
 | 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 |
+| Dolt writes | `mysql+pymysql://…` | Exactly 2.2.2 and 2.2.3 | 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 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.
+independent core profile with a packaged exact-version write policy; normal
+callers supply no conformance files. An explicit external declaration source
+remains a strict override. Read-only validation/export has no write-version gate.
+The optional Transformation Workflow remains SQLite-only. This does not claim
+coverage for every server configuration or proven Dolt native limit ceilings.
+Dolt capabilities report adapter safety budgets and active packet constraints;
+full boundary conformance remains pending.
 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
@@ -102,6 +111,51 @@ implemented openstatspec.frontends.spss package. Stata and SAS remain empty
 source-tree placeholders and must expose no compiler, apply API, CLI choice,
 capability claim, or implied support.
 
+## Prior default Dolt write verification (before the 0.8.0 pin)
+
+Local release verification used the exact 2.2.2 and 2.2.3 image digests in
+`.github/workflows/ci.yml`, isolated ports 13482/13483, and disposable `/tmp`
+database directories. With `PYTHONPATH=src:../pyspssio`,
+`OPENSTATSPEC_SPECIFICATION_DIR=/tmp/oss-php-spec-cd8f198`, and each matching
+`OPENSTATSPEC_DOLT_URL` / `OPENSTATSPEC_EXPECTED_DOLT_VERSION`:
+
+- `../python/.venv/bin/python -m pytest`: **366 passed, 49 skipped per pin**.
+- CI selection `-m 'services and not candidate_evidence'`: **7 passed,
+  41 skipped per pin**; other database services were not configured locally.
+- Dolt 2.3.0 on port 13387: read-only export and unknown-version write rejection
+  checks passed (**19 passed**) using disposable fixture databases/users.
+- `python -m compileall -q src tests` and `git diff --check` passed.
+
+Live failures exposed and now cover two previously dormant write blockers:
+owned table additions being misclassified as unrelated diffs, and Dolt retaining
+`@@autocommit=1` despite the driver's setting. Writes now explicitly begin their
+transaction. The candidate storage/identifier/column smoke probe also passed on
+both pins; it does **not** establish full value/row/statement limit conformance.
+
+## 0.8.0 local verification
+
+Using `../python/.venv/bin/python`, `PYTHONPATH=src:../pyspssio`, and
+`OPENSTATSPEC_SPECIFICATION_DIR=/tmp/oss-python-spec-v050-5dSTna` (an archive
+of exact `864e84479f554b8ee250ffed44c4dfb963750d4a`):
+
+- `python -m pytest -ra`: **381 passed, 49 skipped**, with
+  `OPENSTATSPEC_TEST_DOLT_ADMIN_URL=mysql+pymysql://root@127.0.0.1:13387/`
+  exercising live Dolt 2.3.0 through disposable SELECT-only users.
+- Both immutable CI images, exact Dolt 2.2.2/2.2.3, bootstrapped with the
+  unchanged service user and separate global fixture admin on ports 13582/13583:
+  `python -m pytest -m 'services and not candidate_evidence'`: **7 passed,
+  41 skipped, 382 deselected per pin**; explicit
+  `python -m pytest tests/test_read_only_export.py`: **33 passed per pin**.
+- `python -m compileall -q src tests`, `git diff --check`, wheel/sdist build,
+  and `python -m twine check /tmp/oss-python-v080-dist/*` passed.
+- A clean wheel install resolved the required engine from PyPI. Isolated
+  imports came only from the smoke environment's `site-packages`; installed
+  capabilities reported adapter 0.8.0, the selected policy, released v0.5.0
+  provenance, and exactly 2.2.2/2.2.3 for default Dolt writes.
+
+Other database services were not configured locally. This is local evidence,
+not a claim that the updated remote CI or release publication has completed.
+
 ## Maintainer checks before tagging
 
 1. Publish the pinned `openstatspec-pyspssio==0.5.1.post2` engine distribution
@@ -110,14 +164,28 @@ capability claim, or implied support.
 2. Run `python -m pytest -m "not services"`.
 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.
+   2.2.2/2.2.3 service evidence from the immutable image pins in CI. The Dolt
+   jobs must perform default import/validate/SAV+ZSAV export, in-place recode
+   and labels with unchanged dataset/table counts and HEAD, injected data,
+   catalog, and audit rollback checks, and failed-import cleanup. Release/CI
+   owns this evidence, not per-user runtime declaration files. Candidate limit
+   probes remain non-claiming and separate from these write gates.
+   Each Dolt job must also run `python -m pytest tests/test_read_only_export.py`
+   explicitly, outside the `services` marker filter. Bootstrap a separate
+   `openstatspec_test_admin` on the isolated CI server with global database/user
+   creation and grant privileges, and set `OPENSTATSPEC_TEST_DOLT_ADMIN_URL`.
+   The fixture creates its own database and SELECT-only reader and removes
+   both afterward; the normal service user remains unchanged.
 4. Build with `python -m build` and install the generated wheel in a clean
-   environment.
+   environment, resolving `openstatspec-pyspssio==0.5.1.post2` from PyPI.
+   Run the installed CLI outside the source checkout with `PYTHONPATH` unset;
+   verify adapter version `0.8.0` and the selected database I/O policy.
 5. Confirm `openstatspec capabilities` reflects the intended support boundary.
 6. Confirm CI, release fixtures, and capabilities use the published OpenStatSpec
-   specification `v0.3.0` at exact commit
-   `cd8f198c68b849eb8ed018a894670a0904c2181d`, publish
-   `specification_status=stable`, and set `specification_release` to `v0.3.0`.
+   specification `v0.5.0` at exact commit
+   `864e84479f554b8ee250ffed44c4dfb963750d4a`, publish
+   `specification_status=released`, and set `specification_release` to `v0.5.0`.
+   Use an exact checkout via `OPENSTATSPEC_SPECIFICATION_DIR` for local tests.
 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.7.1 → openstatspec-0.8.0}/docs/sav-profile.md

@@ -49,7 +49,7 @@ equivalence of supported values, order, and dictionary metadata.
 
 The `openstatspec capabilities` command and the
 `openstatspec.capability_matrix()` function are the machine-readable declaration
-of this boundary. It records the pinned source commit and installed engine version, and the adapter stores the same identity in every import and export operation record. The matrix deliberately distinguishes a supported feature from a feature that the underlying engine cannot observe or write faithfully.
+of this boundary. It records the pinned source commit and installed engine version, and the adapter stores the same identity in import operation records. Export is database-read-only: no operation, fidelity, recovery, or Dolt-history records are written, even on failure. Loss diagnostics are returned to the caller. Dolt export identifies the server and validates the catalog and data without requiring write-conformance declarations; write entry points retain that requirement. The matrix deliberately distinguishes a supported feature from a feature that the underlying engine cannot observe or write faithfully.
 
 | SPSS semantic | Pinned pyspssio status | Behaviour |
 | --- | --- | --- |

{openstatspec-0.7.1 → openstatspec-0.8.0}/openstatspec-specification/.github/workflows/ci.yml

@@ -19,4 +19,6 @@ jobs:
       - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97
         with:
           python-version: "3.13"
+      - run: python -m pip install --disable-pip-version-check -e ".[dev]"
+      - run: python -m pytest
       - run: python tools/validate_repository.py

{openstatspec-0.7.1 → openstatspec-0.8.0}/openstatspec-specification/CHANGELOG.md

@@ -2,15 +2,53 @@
 
 ## Unreleased
 
-Future changes will be listed here.
+### v0.5.0 (prepared; not yet published)
+
+- Add normative optional `openstatspec-database-io-v1`, explicitly selected by
+  capability field `database_io_policy`. Reads, validation and export perform
+  no database writes, including audit, temporary DDL and failure paths; export
+  loss diagnostics are returned while safe file publication remains required.
+- Permit default Dolt writes through packaged exact tested 2.2.2/2.2.3 policy
+  backed by adapter release CI, with no runtime user declaration/evidence files.
+  External declarations and their unchanged validator remain an optional
+  advanced override. Identity, limits, atomicity, security and branch/HEAD
+  checks remain mandatory; unknown or untested versions fail closed.
+- Preserve unselected adapters' old requirements, SAV 1.0 source semantics,
+  catalog/data/metadata schema and fixtures, and all canonical plan, frontend
+  and SQL binding contracts. This pre-1.0 minor release adds an independently
+  selected policy; it does not silently revise an existing profile.
+- Keep the separately released `openstatspec-specification` companion package
+  at `0.1.0`. No adapter conformance or package release is asserted here.
+
+## v0.4.1 - 2026-08-21
+
+OpenStatSpec `v0.4.1` is a documentation and release-bookkeeping patch for
+the stable `v0.4.0` specification. It changes no normative contract or
+conformance artifact.
+
+- Aligned the SPSS frontend roadmap with the published Frontend 0.3 profile.
+- Corrected release metadata fixtures and validation coverage for the public
+  README and current release status.
+
+## v0.4.0 - 2026-08-21
+
+OpenStatSpec `v0.4.0` publishes SPSS Syntax Frontend 0.3 as a stable optional
+profile. The release tag is the immutable specification identity for this
+release.
+
+- Added comments, existing-variable `TO`, grouped supported forms, predicate
+  aliases and bounded `NOT`, open recode ranges, and additive value labels.
+- Frontend 0.3 emits only immutable Plan 0.1/0.2 objects and adds no SQL
+  binding operation.
+- Repository validation now covers all Plan/Frontend/Binding schemas,
+  manifests, references, inherited cases, and canonical hashes.
+- Adapter claims remain downstream and separately gated; this release does not
+  assert PHP or Python implementation conformance.
 
 ## v0.3.0 - 2026-08-12
 
-Release preparation for the planned stable `v0.3.0` tag. Until a protected or
-signed `v0.3.0` tag targets this exact release commit, implementations MUST
-identify it with `specification_status: release_candidate`,
-`specification_release: null`, and the exact immutable specification commit.
-The entries below become the stable release only when that tag exists.
+OpenStatSpec `v0.3.0` is the stable public specification release at immutable
+specification commit `cd8f198c68b849eb8ed018a894670a0904c2181d`.
 
 - Added backward-compatible Transformation Plan and SPSS Syntax Frontend 0.2
   contracts for sequential numeric `COMPUTE` and conditional `IF`, bounded

{openstatspec-0.7.1 → openstatspec-0.8.0}/openstatspec-specification/README.md

@@ -13,6 +13,19 @@ MySQL 8.4.x/9.7.x, MariaDB 11.4.x/11.8.x/12.3.x and PostgreSQL 17.x/18.x
 series while requiring exact patch-version CI evidence. Microsoft SQL Server
 remains an explicitly unsupported [future dialect](docs/mssql-dialect-roadmap.md).
 
+## Optional database I/O execution policy
+
+Prepared for specification `v0.5.0`, the normative optional
+[Database I/O Execution Policy v1](docs/database-io-policy-v1.md) is explicitly
+selected with `database_io_policy: "openstatspec-database-io-v1"`.
+It requires database-read-only reads, validation and exports (including errors
+and loss diagnostics), and permits default Dolt writes on packaged exact tested
+2.2.2/2.2.3 policy backed by adapter release CI, without user evidence files.
+External declarations remain an optional advanced override. Unselected adapters
+retain existing requirements; SAV 1.0 semantics, schemas, fixtures and canonical
+Plan/Frontend/Binding contracts are unchanged. Publication and downstream
+adapter support remain separately gated.
+
 ## Core contract
 
 - One source dataset maps to exactly one dedicated SQL data table.
@@ -37,10 +50,11 @@ 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 release-candidate [Transformation Plan Profile 0.2](docs/transformation-plan-profile-0.2.md)
-adds sequential bounded numeric assignment and conditional assignment to the
+The released [Transformation Plan Profile 0.2](docs/transformation-plan-profile-0.2.md)
+was released in OpenStatSpec `v0.3.0` and 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)
+[released SPSS Syntax Frontend Profile 0.2](docs/spss-syntax-frontend-profile-0.2.md)
+was released in OpenStatSpec `v0.3.0` and
 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
@@ -50,6 +64,10 @@ creates no derived dataset, data copy, or OpenStatSpec undo layer; Dolt-specific
 history and commits remain Dolt's. MySQL, MariaDB, and Dolt require a new target
 to be provisioned separately before an in-place transformation apply.
 
+The released [SPSS Syntax Frontend Profile 0.3](docs/spss-syntax-frontend-profile-0.3.md)
+was published in OpenStatSpec `v0.4.0`. It adds syntax-only expansion over the
+released Plan 0.1/0.2 contracts and does not change SQL binding behavior.
+
 ## Repository layout
 
 - `sql/server-version-policy.md` — server release-series claims and exact reference-CI targets.
@@ -72,8 +90,18 @@ to be provisioned separately before an in-place transformation apply.
 - `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.2.json` and
-  `conformance/spss-syntax-frontend-0.2.json` — additive plan and frontend
+- `docs/spss-syntax-frontend-profile-0.1.md`,
+  `docs/spss-syntax-frontend-profile-0.2.md`, and
+  `docs/spss-syntax-frontend-profile-0.3.md` — bounded syntax frontend
+  profiles and their contract boundaries.
+- `transformation/spss-syntax-frontend-0.1.schema.json`,
+  `transformation/spss-syntax-frontend-0.2.schema.json`, and
+  `transformation/spss-syntax-frontend-0.3.schema.json` — frontend request
+  schemas.
+- `conformance/transformation-plan-0.2.json`,
+  `conformance/spss-syntax-frontend-0.1.json`,
+  `conformance/spss-syntax-frontend-0.2.json`, and
+  `conformance/spss-syntax-frontend-0.3.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. The 0.1 schemas and fixtures remain unchanged.

{openstatspec-0.7.1 → openstatspec-0.8.0}/openstatspec-specification/RELEASING.md

@@ -12,6 +12,27 @@ Package tags use the `package-vX.Y.Z` convention; specification tags use
 `vX.Y.Z`. A specification tag MUST NOT publish the package, and a package tag
 MUST match the version declared in `pyproject.toml`.
 
+## Prepared v0.5.0 scope
+
+This release prepares the normative optional
+[Database I/O Execution Policy v1](docs/database-io-policy-v1.md). It is not
+published until the gates below complete. Release notes MUST identify explicit
+`database_io_policy` selection, database-read-only export with returned loss
+diagnostics, and packaged exact tested Dolt 2.2.2/2.2.3 write policy with optional
+external evidence. Existing unselected-profile requirements, SAV 1.0 semantics
+and fixtures, schemas, and canonical Plan/Frontend/Binding artifacts are unchanged.
+This is a pre-1.0 minor optional addition under [VERSIONING](VERSIONING.md).
+
+Run `python -m pytest` and `python tools/validate_repository.py` at the selected
+commit. Adapter package release CI supplies real exact-version write and
+read-only/failure-path evidence under the new policy; neither fabricated
+repository declarations nor user-supplied evidence files are release substitutes.
+Python `v0.8.0` and PHP `v0.7.0` are downstream adapter release targets, not
+conformance claims made by this specification. Their pins and publication are
+managed separately. The companion `openstatspec-specification` distribution
+remains `0.1.0`: no package API, schema or validator contract change requires a
+package release for this documentation policy addition.
+
 ## Before preparing a release
 
 - Choose an exact reviewed commit on the appropriate branch and record its