docs: 0.1.2 release wording

README.md

@@ -281,9 +281,10 @@ place they looked.
 
 Early (0.1.2). Working: everything under *What it does*, on Linux, macOS (arm64) and
 Windows (x64 and Win32 built and tested in CI on every push; the Windows build lacks
-prefetch and parallel ingest); 0.1.2 on PyPI, crates.io, nuget.org and Maven Central. Next: the ADBC Driver
-Foundry validation suite, a driver bootstrap for the open-licence ODBC
-drivers, the Win32 thread shim; then a JDBC bridge on the same model —
+prefetch and parallel ingest); 0.1.2 on PyPI, crates.io, nuget.org and Maven Central. The ADBC Driver
+Foundry validation suite passes on PostgreSQL apart from declared server limits
+([`tests/validation/RESULTS.md`](tests/validation/RESULTS.md)). Next: a driver bootstrap for
+the open-licence ODBC drivers, the Win32 thread shim; then a JDBC bridge on the same model —
 [`docs/ROADMAP.md`](docs/ROADMAP.md).
 
 ## Upstream: giving back

docs/community/faq.md

@@ -181,9 +181,9 @@ One driver library, five wrapper packages that locate and load it:
 | Go | `github.com/singhpratech/adbcbridge/go` over `drivermgr` | `adbcbridge.NewDriver(alloc)` |
 
 All five are built, tested and attached to every
-[GitHub Release](https://github.com/singhpratech/adbcbridge/releases/tag/v0.1.0);
-the wheel, crate and nupkg are also on PyPI, crates.io and nuget.org (Maven Central
-is still to come). Each resolves the library the
+[GitHub Release](https://github.com/singhpratech/adbcbridge/releases/latest);
+the wheel, crate, nupkg and jar are also on PyPI, crates.io, nuget.org and Maven
+Central. Each resolves the library the
 same way and raises an error when it cannot; Rust, C#, Java and Go list every
 place they looked. See
 [Language packages](../../README.md#language-packages).
@@ -379,9 +379,9 @@ Apache-2.0. Every non-vendored source file carries an
 ### What does the 0.1.x version mean?
 
 Early. The read/write path, the 53-database matrix and the five language packages
-are done and 0.1.0 is on PyPI, crates.io and nuget.org; a conformance suite and Maven
-Central are in progress. `v0.1.0` was tagged 2026-08-25 with four platform libraries,
-four wheels plus an sdist, a crate, a NuGet package and a jar. Treat the API as stabilising, not stable. See
+are done and 0.1.2 is on PyPI, crates.io, nuget.org and Maven Central. `v0.1.0` was
+tagged 2026-08-25 with four platform libraries, four wheels plus an sdist, a crate, a
+NuGet package and a jar; 0.1.1 (2026-09-05) and 0.1.2 (2026-09-15) followed. Treat the API as stabilising, not stable. See
 the [roadmap](../ROADMAP.md).
 
 ### What is on the roadmap?

docs/getting-started/install-linux.md

@@ -93,7 +93,7 @@ tar xzf adbcbridge-v0.1.2-linux-x64.tar.gz
 # → linux-x64/libadbc_driver_odbc.so
 ```
 
-The checksum file is signed by the release key (`SHA256SUMS.asc`); releases after v0.1.2 also
+The checksum file is signed by the release key (`SHA256SUMS.asc`); releases after v0.1.0 also
 carry a build-provenance attestation for every asset and an SBOM; [Security](../community/security.md#verifying-a-download)
 shows how to check each.
 

docs/getting-started/install-windows.md

@@ -62,7 +62,7 @@ The Windows release asset is `adbcbridge-<tag>-win-x64.tar.gz`, containing
 
 The release page also carries `SHA256SUMS`; `Get-FileHash adbcbridge-v0.1.2-win-x64.tar.gz -Algorithm SHA256`
 in PowerShell gives the value to compare. [Security](../community/security.md#verifying-a-download)
-covers checking the file's GPG signature, and the provenance and SBOM that releases after v0.1.2 add.
+covers checking the file's GPG signature, and the provenance and SBOM that releases after v0.1.0 add.
 
 ### From the Python wheel
 

docs/how-it-works/connection-keywords.md

@@ -11,7 +11,7 @@ set (in the connection string or in the DSN) is never overridden, nothing that
 changes what a query returns is ever set, and `adbc.odbc.tune=false` turns the
 whole thing off.
 
-The complete list in v0.1.0 is one keyword:
+The complete list as of v0.1.2 is one keyword on every platform, and a second one on Windows only, described below the table:
 
 | driver | condition | what is added | why |
 |---|---|---|---|

docs/index.md

@@ -87,7 +87,7 @@ See [Connection strings](reference/connection-strings.md) and
 adbcBridge is early software — version **0.1.2**, published on
 [GitHub Releases](https://github.com/singhpratech/adbcbridge/releases/tag/v0.1.2).
 
-| | Verified as of 2026-09-04 (rows measured on 0.1.0; 0.1.2 changes native delegation only, re-probed on the 14 PostgreSQL-wire rows on 2026-09-05) |
+| | Verified as of 2026-09-04 (rows measured on 0.1.0; 0.1.1 changed native delegation only, re-probed on the 14 PostgreSQL-wire rows on 2026-09-05; 0.1.2 changes PostgreSQL temporal types and Windows array ingest, re-run on 42 Linux rows on 2026-09-15) |
 |---|---|
 | Databases (one workload: types, NULLs, Unicode, parameters, bulk ingest, batched reads, metadata, errors) | **53 on Linux**, **45 on macOS**, **48 on Windows** |
 | Language packages | **five** — Python, Rust, C#, Java, Go (R is smoke-tested) |

docs/languages/csharp.md

@@ -100,9 +100,9 @@ The same `.nupkg` is attached to each release. On a machine without registry acc
 download it, register the folder that holds it as a package source, then add the package:
 
 ```sh
-# 1. Download AdbcBridge.0.1.0.nupkg from the Release into ./localnuget/
+# 1. Download AdbcBridge.0.1.2.nupkg from the Release into ./localnuget/
 mkdir -p localnuget
-# (place AdbcBridge.0.1.0.nupkg in ./localnuget/)
+# (place AdbcBridge.0.1.2.nupkg in ./localnuget/)
 
 # 2. Register the folder as a NuGet source.
 dotnet nuget add source "$PWD/localnuget" --name adbcbridge-local

docs/languages/java.md

@@ -164,7 +164,7 @@ generates a dependency-less POM, so declare the runtime dependencies alongside:
 
 ```sh
 mvn install:install-file \
-    -Dfile=adbcbridge-0.1.0.jar \
+    -Dfile=adbcbridge-0.1.2.jar \
     -DgroupId=org.adbcbridge \
     -DartifactId=adbcbridge \
     -Dversion=0.1.2 \