v0.2.3

RELEASE-MANIFEST.txt

@@ -1,4 +1,12 @@
-RustBox 0.2.2 release manifest
+RustBox 0.2.3 release manifest
+
+0.2.3 feature/configuration changes:
+- optional Sieve, diagnostics and About feature switches
+- API namespace has an explicit 404 fallback so disabled/unknown API routes cannot be served by the SPA fallback
+- opt-in security response headers (disabled by default)
+- authenticated reset-all-settings endpoint/UI
+- two-node Docker topology with Envoy, Valkey, PostgreSQL, OpenSearch and Garage S3
+- no schema migration; V047 remains current and V048 remains next
 
 Architecture:
 - database_backend = sqlite | mysql | pgsql selects authoritative SQL only
@@ -53,18 +61,19 @@ SQLite test isolation (0.2.2):
 
 Docker examples:
 - docker/compose-single-sqlite.yml
+- docker/compose-ha-garage.yml (2x RustBox + Envoy + Valkey + PostgreSQL + OpenSearch + Garage S3)
 - docker/compose-postgres-s3-opensearch.yml (PostgreSQL + SILO/S3 + OpenSearch)
 - docker/compose-mysql-nfs-opensearch.yml (MySQL + real NFS volume + OpenSearch)
 
 Operations/docs:
-- README.md documents 0.2.2 storage/search configuration
+- README.md documents 0.2.3 storage/search configuration
 - docker/README.md documents Compose variants
 - docs/STORAGE_SEARCH_OPERATIONS.md documents failure modes, shared-storage requirements and migration behavior
 - TODO.md leaves live SILO/MinIO/AWS/Ceph and real multi-node acceptance validation explicitly pending
 
 Build/release metadata:
 - `scripts/package-release.sh` runs the full Rust release gate before creating ZIP/SHA256 artifacts
-- Cargo.toml version = 0.2.2
+- Cargo.toml version = 0.2.3
 - rust-toolchain.toml pins Rust 1.88.0
-- Cargo.lock is intentionally not shipped because this environment could not regenerate it after dependency changes
+- Cargo.lock is intentionally not shipped; the release gate regenerates it before locked checks
 - CI and scripts/build-release.sh generate Cargo.lock, then run locked tests/Clippy/release build