diff --git a/.github/workflows/test-native.yml b/.github/workflows/test-native.yml
index 0c0f2d4..1838802 100644
--- a/.github/workflows/test-native.yml
+++ b/.github/workflows/test-native.yml
@@ -34,13 +34,15 @@ name: Test native (arcadedb)
 on:
   pull_request:
     types: [opened, synchronize, reopened, ready_for_review]
+    # tests/ and src/arcadedb/ are shared by both backends: a change there can break the native parity suite, so it runs too.
     paths: &native_paths
       - "native/**"
-      - "src/arcadedb/_native/**"
-      - "tests/test_native_*.py"
-      - "tests/conftest.py"
+      - "src/arcadedb/**"
+      - "tests/**"
       - "scripts/select_native_matrix.py"
-      - "tests/test_select_native_matrix.py"
+      - "scripts/smoke_wheel.py"
+      - "pyproject.toml"
+      - "setup.py"
       - ".github/workflows/test-native.yml"
   push:
     branches: [main]
diff --git a/docs/modules/ROOT/pages/development/ci.adoc b/docs/modules/ROOT/pages/development/ci.adoc
index 3a4d00c..efd3d8a 100644
--- a/docs/modules/ROOT/pages/development/ci.adoc
+++ b/docs/modules/ROOT/pages/development/ci.adoc
@@ -62,7 +62,7 @@ The names of the test jobs do not change: `Test arcadedb (<platform>, Python <ve
 
 The workflow `test-native.yml` builds the native image of the `arcadedb` package and runs the test suite against the installed wheel. It does not follow the table above. It never publishes; `release-native.yml` calls it on a version tag.
 
-* A pull request runs it only when native paths change: `native/**`, `src/arcadedb/_native/**`, the native tests, or `test-native.yml` itself. It then runs on `linux-x86_64` with Python 3.12 only.
+* A pull request runs it only when native paths change: `native/**`, `src/arcadedb/**`, `tests/**`, `scripts/select_native_matrix.py` or `test-native.yml` itself. Changes under `tests/` and `src/arcadedb/` are included because both backends share those files, so a shared test or source can break native parity without touching a native file; docs outside those paths do not run it. It then runs on `linux-x86_64` with Python 3.12 only.
 * A push to `main`, the nightly run, a manual run (dispatch) run all four platforms: `linux-x86_64`, `linux-aarch64`, `macos-arm64` and `windows-x64` (Python 3.12 and 3.14). A release (`release-native.yml` calls the workflow with `release: true`) runs the same four platforms on all four Python versions, 16 legs.
 * The `pyver` job installs the already built `linux-x86_64` wheel (no rebuild) into the Pythons that the full parity runs of the event leave out (3.11, 3.13 and 3.14 on a pull request; 3.11 and 3.13 on a push to `main`, the nightly run and a dispatch; none on a release) into 3.15 and into the free-threaded 3.14t, and runs 13 test files there (14 where polars installs; 3.15 has no jpype1 wheel, so it leaves out the two files that need jpype1), about 20 seconds of tests per Python. It is informational: `release-native.yml` reads only the `native-passed-*` markers and the `native-wheel-*` wheels, so a red `pyver` leg never blocks a release. The 3.14t leg has no polars (no free-threaded wheel exists), so it skips `test_dataframe_ingest.py`. `scripts/select_native_matrix.py` decides its legs.
 * A native image build takes about 1 to 2.5 hours for each platform. The organisation shares one runner limit with upstream ArcadeDB, so do not add runs lightly. Change the paths or the matrix of `test-native.yml` only for a reason that you can write down.