Release version 1.2 with Supernode user window

README.md

@@ -45,7 +45,8 @@ Install dependencies, then start the Tauri development window:
     npm install
     npm run tauri dev
 
-The portable build creates `release/super-n2n-portable.zip`. It contains
+The portable build creates a versioned archive such as
+`release/super-n2n-portable-1.2.zip`. It contains
 `n2n/edge.exe`, `n2n/supernode.exe`, and the official TAP-Windows installer in
 `drivers/tap-windows-9.24.7-I601-Win10.exe`; on Windows Super N2N starts the n2n
 programs with the relative paths `./n2n/edge.exe` and `./n2n/supernode.exe`.
@@ -60,6 +61,20 @@ select a specific existing adapter. Connection settings, including advanced
 settings, are stored beside `super-n2n.exe` in `super-n2n.config.json` and are
 restored on the next application launch.
 
+### Supernode and special server
+
+The `创建服务器` home starts Supernode on the configured UDP port and can
+optionally restrict communities and the Supernode address-assignment pool.
+The optional special server listens on its own TCP port. A special client only
+needs that server address and port; it receives the community, static TAP IP,
+gateway, DNS, and Supernode port automatically. The client username is sent as
+the n2n edge description (`-I`) and defaults to the Windows computer name.
+
+The special address pool must be a subnet inside the normal Supernode pool, and
+its community must be present in the allowed-community list when that list is
+restricted. Supernode's compact client window polls the management API and
+marks addresses issued by the special server.
+
 ## Gitea Actions
 
 `.gitea/workflows/build-windows.yml` runs when a Release is published and uploads