Release notes: prevent unsupported automatic recovery and UX claims #748

The generated v0.2.172 release notes said: “Native socket connections recover automatically after capture failures” and claimed hook ordering prevents UI flicker. The actual patch reaccepts socket peers and detects capture loss with explicit relaunch guidance; automatic hardware-stream/sidecar restart is absent, and no shipping UI flicker was reproduced. Notes have been corrected for this release.

Acceptance: preserve the distinction between transport reconnect, capture-loss detection, and hardware/process recovery in generated notes; retain opt-in/experimental and unperformed native acceptance qualifiers; validate summary claims against the final implementation and review before publication. Avoid inventing observed user symptoms from static correctness fixes. Source: #732 and docs/internal/native-audio-recovery.md.