v0.2.25

RELEASE-MANIFEST.txt

@@ -1,4 +1,11 @@
-RustBox 0.2.25 release manifest
+RustBox 0.2.26 release manifest
+
+0.2.26 release changes:
+- licensing: GNU AGPL v3 (`LICENSE`) with an optional paid commercial license (`LICENSING.md`); `NOTICE.md` keeps the MIT notice for parts originating from Oxi; Cargo metadata declares `AGPL-3.0-only`
+- removes the Oxi synchronisation tooling (`scripts/*upstream*.sh`, `scripts/oxi-*.sh`, `UPSTREAM_BASE`, `docs/UPSTREAM.md`); RustBox is developed independently
+- redesigned Settings → About (author, repository, license, origin)
+- documentation: `docs/FEATURES.md` with screenshots in `docs/screenshots/`, rewritten README and user-facing CHANGELOG
+- Polish settings notes are rendered after translations load; verbose code comments trimmed
 
 0.2.25 release changes:
 - filters: "Apply now" runs a visual Sieve rule on messages already in a folder; `POST /api/filters/match` finds matches with IMAP `UID SEARCH` (exact lower bound, superset upper bound, the gap decided from the local cache; undecidable messages are reported and skipped), and the client applies flags/labels, copies and a final move; per-rule "Apply now" in the rule list and an "apply to existing messages" option in the quick filter dialog
@@ -111,14 +118,14 @@ Docker examples:
 
 Operations/docs:
 - standalone `scripts/migrate_roundcube.py` imports Roundcube contacts/identities using RustBox config.toml and supports SQLite/MySQL/PostgreSQL targets
-- README.md documents 0.2.25 configuration
+- README.md documents 0.2.26 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.25
+- Cargo.toml version = 0.2.26
 - rust-toolchain.toml pins Rust 1.99.1
 - Cargo.lock is retained for reproducible application builds; the release gate generates it only when missing
 - CI and scripts/build-release.sh use the retained Cargo.lock (generating it only if missing), then run locked tests/Clippy/release build