Release v3.8: New profile (blank template renamed), password-mismatch warning stays up, IP-pinning docs

New profile: a File-menu item + Ctrl+N that loads a fresh blank template as a
new unsaved session via a LoadBlankTemplateNext handoff to Program.cs's relaunch
loop — reachable even when "start with a specific profile" boots past the picker
(issue #6). Offers to save the current profile first if dirty; deliberately
silent (no profile-switch cue).

Renamed the user-facing "blank template" to "New profile": the picker's synthetic
entry (now a distinct marker TYPE, collision-safe against a real profile named
"New profile"), the window title ("RemSound — New profile"), and the manual.

Fixed the password-mismatch warning flashing away: it's raised from the 1 Hz
statusTimer, which kept firing into the modal loop and rebuilt the peer lists
(SyncAllPeerLists) under the dialog, knocking it out of the foreground. Now the
tick is frozen while it's up, it's routed through ForegroundDialog, and a
re-entry guard ensures one warning that stays put. Audited: it was the only
popup raised from a recurring timer.

Docs: manual section "Connecting to one specific IP address (and only that one)"
explaining by-name vs by-fixed-IP and that a profile saves the exact address
(issue #7 — functionality already existed); About box + RELEASE_NOTES for v3.8;
MANUAL.md regenerated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

RELEASE_NOTES.md

@@ -1,45 +1,36 @@
-# RemSound v3.7
+# RemSound v3.8
 
-A smoothness-and-diagnosis release: changing devices mid-session no longer crackles, a one-off computer hiccup no longer balloons your latency, the microphone-privacy warning catches the hidden kinds of block, and the log now records enough to prove what happened when something goes wrong.
+A usability release from user reports: you can now create a new profile at any time, the "different passwords" warning stays put, and the manual explains how to pin a connection to a specific IP.
 
-## Changing devices mid-session is smoother
+## New profile, any time
 
-When you change capture devices — ticking sources on or off, or bringing an ASIO driver in or out — RemSound used to rebuild its sound engine immediately on every single change. A quick run of changes meant several rebuilds back to back, each one an audible crackle. Now RemSound **waits a moment for you to finish and rebuilds once**, to the final state. Reconfiguring no longer fights you.
+There's a new **New profile** item at the top of the **File** menu (and **Ctrl+N**). It opens a fresh, unsaved session, so you can build a profile for a different setup from scratch.
 
-## The auto-tuner ignores one-off hiccups
+This closes a real gap: if you'd set RemSound to **start in a specific profile**, you booted straight past the profile picker and had **no way to reach a clean slate** to start something new — your only escape was opening an old profile by luck. Now you always can, without unchecking your startup setting. If your current profile has unsaved changes, New profile offers to save them first. The startup picker and the window title now read **"New profile"** as well, where they used to say "blank template".
 
-Continuous auto-tune sizes your latency cushion from how late packets are arriving. It used to react to the **single worst moment** it had seen — so one brief stall (the kind a driver or Windows hiccup causes once and never again) could balloon the cushion to its maximum and disrupt audio for far longer than the hiccup itself. It now only raises the cushion when late audio **keeps coming** — sustained jitter still gets a fast response, a lone blip gets ignored.
+## The "different passwords" warning stays on screen
 
-## The mic-privacy warning catches hidden blocks
+When you connect to someone whose password doesn't match yours, RemSound warns you. That warning was being raised from the once-a-second status update, which kept rebuilding the peer list underneath it and knocked it out of the foreground — so it could **flash away before you reached OK**. It now holds still and stays in front until you dismiss it.
 
-Windows can block an app's microphone in ways that don't show up as the two obvious switches: a per-app block aimed at one program alone, or a block set by an administrator or workplace policy with no visible switch at all. When one of those is in place, the mic silently sends nothing — and RemSound's warning used to miss both kinds. It now **catches them too**, so "my mic sends silence and nothing warned me" should be gone.
+## Pin a connection to a specific IP (documentation)
 
-## The log can now prove what happened
-
-Four additions to RemSound's diagnostic log, aimed squarely at the questions we couldn't answer from past logs:
-
-- **How loud is what you're sending** (`capPeak` each second) — so silence versus real audio is now a fact in the log, not a guess.
-- **The mic-privacy check's verdict** at every startup — whether or not it warned.
-- **Every device tick/untick you make**, and **every device change Windows reports** — so when the device set changes mid-session, the log shows exactly what drove it.
-- Auto-tune now logs both the worst moment it saw and the value it actually acted on, so you can see when it ignored a one-off spike.
-
-Nothing about these is audible — they just make the next bug report solvable from the first log.
+If a computer has more than one IP address and you want to reach **only one** of them, you can — and you always could: use **Add peer by IP** and type the exact address. RemSound then talks to that address and nothing else (no name lookup, so it can't drift to a different IP). The manual now has a section, *"Connecting to one specific IP address (and only that one)"*, explaining the difference between connecting by name and by a fixed IP, and confirming that a profile remembers exactly what you ticked.
 
 ## Compatibility
 
-**v3.7 talks to v3.3 through v3.6 with no trouble** — the over-the-network format hasn't changed, so you don't have to update both ends at once. (Everyone still needs **v3.3 or newer**, where end-to-end encryption came in.)
+**v3.8 talks to v3.3 through v3.7 with no trouble** — the over-the-network format is unchanged, so you don't have to update both ends at once. (Everyone still needs **v3.3 or newer**, where end-to-end encryption came in.)
 
 ## Install
 
-1. Download `RemSound-v3.7.zip` from this release.
+1. Download `RemSound-v3.8.zip` from this release.
 2. Close RemSound.
 3. Extract the zip **over your existing RemSound folder**, overwriting program files when prompted. The zip is program files only — it won't touch your settings, profiles, logs, recordings, or sounds.
 4. Run `RemSound.exe`.
 
 ## Upgrading
 
-**From v3.6:** Help → Check for updates installs v3.7 with the new in-app updater — and if it ever can't finish, it puts v3.6 back exactly as it was.
+**From v3.6 or v3.7:** Help → Check for updates installs v3.8 with the in-app updater — and if it can't finish, it puts your old version back exactly as it was.
 
-**From v1.9–v3.5:** Check for updates works, but it uses your current version's older updater for this one hop. If auto-update has been failing on your machine, install by hand using the steps above — every update after that uses the new installer.
+**From v1.9–v3.5:** Check for updates works, but it uses your current version's older updater for this one hop. If auto-update has been failing on your machine, install by hand using the steps above.
 
 **v1.8 and earlier:** the auto-updater in those versions can't install updates at all — install by hand using the steps above.