docs(readme,release-notes): M136 缺 client id 的对外文案改成现行行为

M132 之后界面已经直接说「微软登录未配置 + 要设 ULL_MSA_CLIENT_ID」并刻意不给重试按钮，
而 README / README.zh-CN / release-notes 还写着「只会弹通用登录失败 + Code: other」——
那是修前行为。三处改成：标题/正文/Code: msa_not_configured/无重试，并保留「其余失败
仍只给分类文案 + 码，原文只进日志」这半句（那是真的，也是有意的）。

packaging/release-notes.md

@@ -89,9 +89,12 @@ Get-FileHash .\unlucky-launcher_{{VERSION}}_windows_x64.exe -Algorithm SHA256
 
 - Microsoft (MSA) sign-in needs an Azure public client id, and release binaries do not carry one: set
   `ULL_MSA_CLIENT_ID=<id>` before launching, or build with that variable set. Without it sign-in stops
-  before any network call; in the GUI that shows up as the generic "Sign-in failed" banner with
-  `Code: other` (the full reason goes to the launcher log), and `ull accounts add msa` prints the exact
-  fix. Offline profiles and authlib-injector servers need no id.
+  before any network call, and the GUI banner says so plainly: the title "Microsoft sign-in is not
+  configured", a body naming `ULL_MSA_CLIENT_ID=<id>` (set it, or build with it, then restart the
+  launcher — a running process does not pick up a new variable) and `Code: msa_not_configured`, with
+  no Retry button. Every other sign-in failure keeps the generic banner plus its own `Code:` line,
+  with the full reason only in the launcher log. `ull accounts add msa` prints the same fix on the
+  command line. Offline profiles and authlib-injector servers need no id.
 - Binaries are not code-signed / notarized yet: Windows SmartScreen and macOS Gatekeeper warn on first
   launch. The checksums above are the integrity reference for now.
 - macOS ships the bare binary (single-file promise), not a `.app` bundle: no Dock icon or Finder