@@ -20,7 +20,8 @@ concurrency:
 
 env:
   # Match the test suite to the native runner built from this exact revision.
-  VGI_REF: fc3e08f7e7fd800165a0edc00313de46fed15329
+  VGI_REF: a83ff7e8cd46aa840a10e78fe9b31603931824c2
+  VGI_NATIVE_RUNNER_BRANCH: release/vgi-v3-ci-20261028
   # Disable local sibling substitution: validate the released Maven dependency.
   VGI_RPC_JAVA_DIR: /nonexistent
 
 
@@ -188,18 +188,18 @@ change to `~/Development/vgi-rpc-java/` doesn't show up, run
 ## Releasing (Maven Central)
 
 Published: **`farm.query:vgi`** (this repo) and **`farm.query:vgirpc`** /
-`vgirpc-oauth` (the sibling). Latest as of 2026-10-23: **vgi 0.44.0 → vgirpc
-0.33.1**. To cut a release: bump `version` in `build.gradle.kts`, push, then
+`vgirpc-oauth` (the sibling). The VGI 3 release uses **vgi 0.45.0 → vgirpc
+0.33.2**. To cut a release: bump `version` in `build.gradle.kts`, push, then
 create a GitHub Release whose tag is the version (`v0.2.0` for `0.2.0`). The
 `release.yml` workflow (trigger: `release: published`) verifies tag == version,
 runs tests, and publishes. Both repos now set
 `publishToMavenCentral(automaticRelease = true)`, so a release goes **live on
 Maven Central with no manual Portal click** once it passes validation (changed
 2026-06-13 — was `false`/click-gated through vgi 0.1.0 + vgirpc 0.10.1).
 
-**VGI 3 preparation (2026-10-27):** this branch now pins the prepared RPC
-`0.33.2` candidate for scalar dictionary-field annotations. It is not published
-yet. Keep the dependency pin unmerged until RPC 0.33.2 is on Maven Central;
+**VGI 3 release (2026-10-28):** RPC `0.33.2` supplies the scalar dictionary-field
+annotations required by the successor catalog records. Release qualification must
+resolve the published Maven artifacts with the composite source override disabled;
 qualification against an isolated local Maven artifact is not publication proof.
 
 **The cross-repo ordering trap.** The `release.yml` build resolves
 
@@ -19,7 +19,7 @@ VGI lets [Haybarn](https://github.com/Query-farm-haybarn/haybarn) — Query Farm
 
 Wire-compatible with the [Python reference implementation](https://github.com/Query-farm/vgi-python) and the [Go port](https://github.com/Query-farm/vgi-go): all three serve the same integration suite against the same C++ extension.
 
-The prepared protocol uses VGI wire 3.0.0 under `vgi.v3` and requires a native VGI client speaking wire 3.0.x. Upgrade clients and workers together; published `vgi.v2` clients are incompatible. See [catalog metadata and publication](docs/catalog_publication.md).
+Version 0.45.0 uses VGI wire 3.0.0 under `vgi.v3` and requires a native VGI client speaking wire 3.0.x. Upgrade clients and workers together; `vgi.v2` clients are incompatible. See [catalog metadata and publication](docs/catalog_publication.md).
 
 ## What you can serve
 
@@ -45,7 +45,7 @@ Artifacts are published to Maven Central under the `farm.query` group.
 
 ```kotlin
 dependencies {
-    implementation("farm.query:vgi:0.44.0")
+    implementation("farm.query:vgi:0.45.0")
 }
 ```
 
@@ -55,7 +55,7 @@ dependencies {
 <dependency>
   <groupId>farm.query</groupId>
   <artifactId>vgi</artifactId>
-  <version>0.44.0</version>
+  <version>0.45.0</version>
 </dependency>
 ```
 
 
@@ -8,7 +8,7 @@ plugins {
 
 allprojects {
     group = "farm.query"
-    version = "0.44.0"
+    version = "0.45.0"
 
     repositories {
         mavenCentral()
 
@@ -1,4 +1,4 @@
-# Catalog metadata and publication (wire 2.2)
+# Catalog metadata and publication (wire 3.0)
 
 `catalog_contents` returns six nullable Arrow IPC streams: `schemas`, `tables`, `views`, `functions`, `macros`, and `indexes`. A stream can contain multiple rows and record batches spanning multiple schemas. Empty categories are null. Functions and macros retain their subtype fields. Per-schema listing RPCs keep their existing item shapes, except `SchemaInfo` no longer carries attachment bytes; real attach request/result and function state remain intact.
 
@@ -17,12 +17,9 @@ The manager exposes startup warming, trusted manifest import, and conditional in
 
 Java: call `Worker.catalogSnapshot(policy)`. Use `policy.manager.warm`, `importPublication`, and `invalidate`. This implementation requires `farm.query:vgirpc:0.33.2`, including scalar dictionary annotations, its collection row codec and idempotent IPC stream termination.
 
-The prepared protocol requires native clients and workers on wire 3.0.x under `vgi.v3`; published `vgi.v2` peers are incompatible. CI and release builds must resolve RPC 0.33.2 from Maven Central.
+Version 0.45.0 requires native clients and workers on wire 3.0.x under `vgi.v3`; `vgi.v2` peers are incompatible. CI and release builds resolve RPC 0.33.2 from Maven Central.
 
-**Release preparation (October 27):** RPC 0.33.2 is a prepared candidate and has
-not been published. This branch pins that candidate so it receives the scalar
-`DICT_INT16_UTF8` record fix required by macro and constraint metadata. Publish
-RPC 0.33.2 before merging this dependency pin or releasing the SDK. Qualification
-uses the packaged candidate in an isolated Maven repository with the composite
-source override disabled; it does not prove Maven Central availability. No local
-repository fallback is part of the SDK build.
+RPC 0.33.2 includes the scalar `DICT_INT16_UTF8` record fix required by macro and
+constraint metadata. Release qualification disables the composite source override
+and resolves that published dependency from Maven Central. No local repository
+fallback is part of the SDK build.
@@ -5,7 +5,7 @@ plugins {
 
 dependencies {
     // farm.query is the published group (see ../build.gradle.kts allprojects).
-    // Prepared dependency; publish RPC 0.33.2 before merging this pin (see docs/catalog_publication.md).
+    // RPC 0.33.2 preserves declared scalar dictionary fields in catalog records.
     api("farm.query:vgirpc:0.33.2")
     implementation("org.slf4j:slf4j-api:2.0.17")
     // Cross-process aggregate state store. DuckDB spawns multiple worker