Prepare nestum 0.3.2 release

Author: eboody

Cargo.lock

@@ -42,6 +42,13 @@ match self {
 
 That is the whole pitch. `nestum` keeps the same nested-enum model, keeps the same compile-time invariant, and removes most of the tuple-wrapping tax.
 
+## Start Here
+
+- want the pitch quickly: read this intro and [When Nestum Is Worth It](#when-nestum-is-worth-it)
+- want to see real usage: jump to [Flagship Use Case](#flagship-use-case) and [Migration Guide](#migration-guide)
+- want framework integration: see [Cookbooks](#cookbooks)
+- want the mechanism and limits: read [Authority Surface](#authority-surface) and [Limitations](#limitations)
+
 ## When Nestum Is Worth It
 
 Use `nestum` when all of these are true:

README.md

@@ -1,13 +1,13 @@
 [package]
 name = "nestum-examples"
-version = "0.3.1"
+version = "0.3.2"
 edition = "2024"
 publish = false
 
 [dependencies]
 axum = "0.8"
 clap = { version = "4.5", features = ["derive"] }
-nestum = { path = "../nestum", version = "0.3.1" }
+nestum = { path = "../nestum", version = "0.3.2" }
 serde = { version = "1", features = ["derive"] }
 sqlx = { version = "0.8", default-features = false, features = ["sqlite", "runtime-tokio-rustls", "macros"] }
 tokio = { version = "1", features = ["macros", "rt-multi-thread", "net", "sync"] }

nestum-examples/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "nestum"
-version = "0.3.1"
+version = "0.3.2"
 edition = "2024"
 description = "Proc-macro for nested enum paths like Enum1::Variant1::VariantA"
 license = "MIT"