sqlrush · sqlrush · Sep 23, 2026 · Sep 23, 2026
@@ -1 +1 @@
-0.132.0-pre1.1
+0.132.0
@@ -4,13 +4,15 @@ Author: SqlRush <sqlrush@gmail.com>
 
 ## Current release
 
-[v0.132.0-pre1.1](v0.132.0-pre1.1.md) is the four-VM ARM64/GFS2 laboratory
-milestone prerelease line. Publication requires its complete four-VM, normal
-restart and exact-commit CI results; it is not production HA or RHEL/x86
-certification. The stable single-host MVP line remains v0.131.0 below.
+[v0.132.0](v0.132.0.md) is the stable source release for the qualified four-VM
+ARM64/GFS2 laboratory scope. It promotes the accepted
+[v0.132.0-pre1.1](v0.132.0-pre1.1.md) milestone without changing product logic,
+formats, configuration or acceptance requirements. Stable does not mean
+production HA, RHEL/x86 certification or four independent physical hosts.
+Publication still requires complete release CI on the exact final commit.
 
 [v0.131.0 — undo-header locality and UPDATE diagnostics](v0.131.0.md) is the
-current source release line. Stable publication requires the exact-commit CI
+previous single-host MVP source release. Its publication binds exact-commit CI
 and four-round correctness qualification recorded with its GitHub Release.
 Stable means the documented MVP scope, not production HA, independent-host
 shared-storage certification or a performance guarantee.
@@ -45,6 +47,7 @@ Versions use `MAJOR.MINOR.PATCH`, optionally followed by a prerelease label:
 | `v0.130.1` | Correctness maintenance release within the same MVP scope |
 | `v0.131.0` | Undo-header locality improvement and optional UPDATE diagnostics |
 | `v0.132.0-pre1.1` | Four-VM ARM64/GFS2 laboratory milestone prerelease |
+| `v0.132.0` | Stable release within the qualified PRE1 four-VM laboratory scope |
 | `-mvp.N`, `-alpha.N`, `-beta.N` | Numbered evaluation prereleases |
 | `-rc.N` | Release candidates with their own published qualification scope |
 | No suffix | Stable release; only after its acceptance criteria pass |
@@ -63,8 +66,8 @@ the superseded release's evidence and limitations.
 ## Selecting a version
 
 ```sh
-git fetch origin tag v0.131.0
-git switch --detach v0.131.0
+git fetch origin tag v0.132.0
+git switch --detach v0.132.0
 git rev-parse HEAD
 cat PGRAC_VERSION
 ```

@@ -0,0 +1,93 @@
+# PGRAC v0.132.0 — stable four-VM PRE1 milestone
+
+Author: SqlRush <sqlrush@gmail.com>
+
+Release line: 2026-09-23. PostgreSQL base: 16.13. Distribution: stable source.
+
+## What changed
+
+This release promotes the qualified [v0.132.0-pre1.1](v0.132.0-pre1.1.md)
+milestone to a stable version within its existing, limited deployment scope.
+Only the source version label and release documentation change. No database
+product logic, test predicate, configuration, persistent format or wire format
+changes. The original prerelease tag and evidence remain immutable.
+
+## Qualified scope
+
+Four Ubuntu 24.04 ARM64 KVM/libvirt guests share an iSCSI DATA LUN through
+shared LVM/DLM/GFS2 and use three separate raw voting LUNs. The qualified
+`pre1-gfs2-arm64-lab-v1` laboratory runs on one physical Mac host; its guests
+are independent kernels, not independent physical failure domains. This is an
+operator-assisted, fixed-schema deployment, not a turnkey production HA system.
+
+Each instance retains its own native PGDATA, catalog, control and WAL. Business
+relations are shared. Same-source initialization, directed network/data access,
+remote row-lock wait/cancel, remote consistent reads and relation extension are
+covered. Normal whole-cluster shutdown and unchanged-data restart are covered.
+
+The promotion retains the completed prerelease qualification:
+
+- Real shared-filesystem and per-guest storage-fencing witnesses before admission.
+- Remote row-lock COMMIT and ROLLBACK waits exceeding 75 seconds, plus cancellation.
+- Both isolated negative transaction-terminal legs with real lease expiration.
+- Six single-block microbenchmark phases with correctness and cleanup checks.
+- Four valid formal samples, each four nodes × 32 clients, one million rows,
+  5-second warmup and 35-second measurement. Complete-attempt client/server
+  errors were zero; no forced cancellation was accepted. All-node ordered full
+  data comparison, health, invariants and debt checks passed.
+- Normal shutdown, unchanged-data restart, complete pre-business comparisons,
+  another business run, complete data/health/debt checks and final normal shutdown.
+
+The formal TPS readings were 60.89, 71.58, 70.17 and 74.54. They were measured
+in an assertion-enabled nested laboratory; they are not comparable performance
+claims against the single-host MVP or Oracle. Performance was recorded, not a
+correctness acceptance threshold.
+
+The field-qualified Linux executable SHA-256 remains
+`2c96461810dd18113474e87d87b52133767f9e0b1582f84e4e2d33e11128e201`.
+This identifies that retained binary, not every subsequent source build. The
+release must additionally pass every required Fast and MVP release CI job on
+its exact final commit. See the [published release](https://github.com/sqlrush/pgrac/releases/tag/v0.132.0)
+for that commit, CI links and the attached verification evidence.
+
+## Install or promote an existing installation
+
+```sh
+git fetch origin tag v0.132.0
+git switch --detach v0.132.0
+git rev-parse HEAD
+cat PGRAC_VERSION
+```
+
+Follow the [four-VM operator guide](../deployment/pre1-quickstart.md),
+[row-lock wait/cancel guide](../deployment/pre1-row-lock-wait.md) and
+[cold shutdown/snapshot/restart guide](../deployment/pre1-cold-snapshots.md).
+The promoted source label is `0.132.0`. The legacy compiled `pgrac_version()`
+string is not the release identifier; preserve the tag, commit, build options,
+configuration and executable hash together.
+
+An already qualified prerelease installation does not need a product rebuild
+or data rewrite merely to acquire this release designation. If replacing a
+binary, use the documented homogeneous whole-cluster normal stop/start and
+identity checks. Do not mix versions or silently recover an unclean fixture.
+An older single-host MVP data set is not automatically a four-VM PRE1 data set;
+the existing installation and migration restrictions remain in force.
+
+## Known limitations retained
+
+- No database crash recovery, automatic failover, shared native catalog/control/
+  WAL, runtime cross-node DDL, online membership changes or rolling upgrade.
+- No RHEL/x86, other filesystem/cloud platform, raw DATA backend or production
+  HA qualification. Storage-fence witnesses do not enable database external-
+  fencing admission.
+- Earlier isolated transaction-authority and MultiXact proof refusals remain
+  recorded; their independent causes are not claimed fixed just because later
+  accepted samples did not reproduce them.
+- Original failed attempts and CI replays remain visible. Stable promotion does
+  not retroactively turn failures into passes or expand the test scope.
+- Historical extended tests remain non-blocking under the already approved MVP
+  CI policy; their unsupported crash/2PC scenarios are not described as passed.
+
+Keep the laboratory on an isolated trusted network. Do not expose its lab-only
+superuser access policy to untrusted clients. Preserve rejected restart scenes;
+do not clear voting ALIVE, guess identities or reset data to bypass a refusal.