Version 2026.9.20, and an install.sh that tells the truth

brand_version! goes to 2026.9.20 (SPEC.md 2.6: YYYY.M.D), the version this
release is tagged at. Verified from the built binary rather than the
source: --version prints "2026.9.20 (Stalwart 0.16.22)" and --help leads
with "INBUXA Server 2026.9.20 (Stalwart 0.16.22)".

install.sh still said "See https://inbuxa.org once it's up", which stopped
being true when the site went up this morning, and offered nothing but a
cargo line. It now names both ways to build, says what a server with no
configuration does, and points at the releases page and the docs.

The installer it stands in for is still unbuilt (SPEC.md 6.1), and the
script says so plainly: an installer trusted with a mail host is not a
thing to improvise, so it declines rather than half-doing one.

README: inbuxa.org is up, so stop saying it is not, and link the docs.

crates/types/src/branding.rs

@@ -71,12 +71,12 @@ pub fn env_var(name: &str) -> Result<String, std::env::VarError> {
 #[macro_export]
 macro_rules! brand_version {
     () => {
-        "2026.9.18"
+        "2026.9.20"
     };
 }
 
 /// The version with the Stalwart release it's built on, e.g.
-/// `2026.9.18 (Stalwart 0.16.22)`. The base comes from Cargo, which follows
+/// `2026.9.20 (Stalwart 0.16.22)`. The base comes from Cargo, which follows
 /// upstream, so it's always the base actually compiled in. It matters because
 /// Stalwart's data upgrades are one-way. Once INBUXA stops tracking upstream,
 /// this becomes just the version.