diff --git a/docs/spec/SPEC.md b/docs/spec/SPEC.md
index 9043dba..cdccb7a 100644
--- a/docs/spec/SPEC.md
+++ b/docs/spec/SPEC.md
@@ -132,7 +132,10 @@ repository. Instead:
   default: the OIDC-directory, tenant and archiving suites; the four
   telemetry suites (alerts, metrics, tracing, webhooks); and the LLM parts of
   the spam-filter suite. Each gate carries an `inbuxa: pending-rebuild` comment
-  and comes off when its feature is rebuilt.
+  and comes off when its feature is rebuilt. All nine features were rebuilt by
+  2026-09-19, so every gate came off and the feature itself was removed from
+  `tests/Cargo.toml` that day. A spec that still describes a suite as gated is
+  describing the state at its own date.
 - Those gated suites are shared, AGPL test code that exercises Enterprise
   behavior. That makes them a clean source for the feature specs, and ready-made
   acceptance tests for the rebuilds.
diff --git a/tests/Cargo.toml b/tests/Cargo.toml
index a64969a..c62730c 100644
--- a/tests/Cargo.toml
+++ b/tests/Cargo.toml
@@ -4,10 +4,9 @@ version = "0.16.22"
 edition = "2024"
 
 [features]
-# Tests for Enterprise features the fork hasn't rebuilt yet. Off by default, so
-# the crate compiles without them. Each gate is marked `inbuxa: pending-rebuild`,
-# and comes off when its feature's rebuild lands.
-pending-rebuild = []
+# `pending-rebuild` held the shared tests of features the fork hadn't rebuilt
+# yet. All nine are built and every gate is off, so the feature went on
+# 2026-09-19 (docs/spec/SPEC.md §2.2b).
 #default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "nats", "azure", "foundationdb"]
 #default = ["sqlite", "postgres", "mysql", "rocks", "s3", "redis", "foundationdb"]
 default = ["rocks", "sqlite"]