release: bump to 1.0.2 with UTF-8 PS console + verbose verify errors

Ships v1.0.2 with two UX-level fixes plus the version-bump housekeeping:

- windows/scripts/wsl-common.ps1: force console I/O to UTF-8 (cp65001)
  at dot-source time.  Windows PowerShell 5.x defaults to GBK (936) on
  zh-CN hosts, which mangled the Chinese strings in install-*.ps1 logs
  and corrupted stdout captured from WSL commands.  Applied in the
  shared file so every install-*.ps1 entry point inherits it via the
  existing `. wsl-common.ps1` line.

- windows/installer.iss: the wizard's Verify button used to collapse
  every failure mode into "Verification failed. You can configure
  later." — same message for "no host Python", "401 Unauthorized",
  "unknown model", "DNS failure".  Now capture stdout+stderr of both
  the host-python and WSL-python3 attempts into %TEMP%\agent-pack-
  verify.log and show the tail in an MsgBox so the user can actually
  see which one failed and why (with the full log path included for
  triage).

Version strings bumped in installer.iss, build-pkg.sh, and the README
download tables / build-from-source outputs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: yysjasmine

README.md

@@ -89,9 +89,9 @@ Pre-built installers live on the [GitHub Releases page](https://github.com/Sense
 
 | Platform | Download | How to Use |
 |----------|----------|------------|
-| Windows | [`AgentPack-1.0.1-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-windows-x64.exe) | Double-click and follow the wizard; installation runs inside WSL2, and the PowerShell window is taken over by the installed agent when setup finishes |
-| macOS | [`AgentPack-1.0.1-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-macos-universal.pkg) | Double-click, then complete setup in the Terminal window that opens; the same window becomes the agent's REPL / gateway once installation finishes |
-| Linux | [`AgentPack-1.0.1-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-linux.sh) *or* the one-liner below | Download and run `chmod +x AgentPack-1.0.1-linux.sh && ./AgentPack-1.0.1-linux.sh`, or paste `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — either way the shell that ran the installer is handed over to the agent via `exec` |
+| Windows | [`AgentPack-1.0.2-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-windows-x64.exe) | Double-click and follow the wizard; installation runs inside WSL2, and the PowerShell window is taken over by the installed agent when setup finishes |
+| macOS | [`AgentPack-1.0.2-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-macos-universal.pkg) | Double-click, then complete setup in the Terminal window that opens; the same window becomes the agent's REPL / gateway once installation finishes |
+| Linux | [`AgentPack-1.0.2-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-linux.sh) *or* the one-liner below | Download and run `chmod +x AgentPack-1.0.2-linux.sh && ./AgentPack-1.0.2-linux.sh`, or paste `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — either way the shell that ran the installer is handed over to the agent via `exec` |
 
 ## Building from Source
 
@@ -104,7 +104,7 @@ cd windows
 iscc installer.iss
 ```
 
-Output: `dist/AgentPack-1.0.1-windows-x64.exe`
+Output: `dist/AgentPack-1.0.2-windows-x64.exe`
 
 ### macOS (.pkg)
 
@@ -115,7 +115,7 @@ cd macos
 ./build-pkg.sh
 ```
 
-Output: `dist/AgentPack-1.0.1-macos-universal.pkg`
+Output: `dist/AgentPack-1.0.2-macos-universal.pkg`
 
 ### Linux
 

README.zh-CN.md

@@ -88,9 +88,9 @@ Bundled skills 已经直接放进 `repos/hermes-agent/skills/` 和 `repos/opencl
 
 | 平台 | 下载 | 使用方式 |
 |------|------|---------|
-| Windows | [`AgentPack-1.0.1-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-windows-x64.exe) | 双击运行向导；安装过程在 WSL2 中执行，安装完成后当前 PowerShell 窗口会被接管，直接跑起 agent |
-| macOS | [`AgentPack-1.0.1-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-macos-universal.pkg) | 双击后在自动打开的 Terminal 窗口中完成安装；安装结束后同一个窗口会变成 agent 的 REPL / gateway |
-| Linux | [`AgentPack-1.0.1-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.1-linux.sh) 或下面的一行命令 | 下载后 `chmod +x AgentPack-1.0.1-linux.sh && ./AgentPack-1.0.1-linux.sh`，或直接粘贴 `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — 两种方式都会在安装结束后用 `exec` 在当前 shell 里拉起 agent |
+| Windows | [`AgentPack-1.0.2-windows-x64.exe`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-windows-x64.exe) | 双击运行向导；安装过程在 WSL2 中执行，安装完成后当前 PowerShell 窗口会被接管，直接跑起 agent |
+| macOS | [`AgentPack-1.0.2-macos-universal.pkg`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-macos-universal.pkg) | 双击后在自动打开的 Terminal 窗口中完成安装；安装结束后同一个窗口会变成 agent 的 REPL / gateway |
+| Linux | [`AgentPack-1.0.2-linux.sh`](https://github.com/SenseTime-FVG/agent_pack/releases/latest/download/AgentPack-1.0.2-linux.sh) 或下面的一行命令 | 下载后 `chmod +x AgentPack-1.0.2-linux.sh && ./AgentPack-1.0.2-linux.sh`，或直接粘贴 `curl -fsSL https://raw.githubusercontent.com/SenseTime-FVG/agent_pack/main/linux/install.sh \| bash` — 两种方式都会在安装结束后用 `exec` 在当前 shell 里拉起 agent |
 
 ## 从源码构建
 
@@ -103,7 +103,7 @@ cd windows
 iscc installer.iss
 ```
 
-产物：`dist/AgentPack-1.0.1-windows-x64.exe`
+产物：`dist/AgentPack-1.0.2-windows-x64.exe`
 
 ### macOS (.pkg)
 
@@ -114,7 +114,7 @@ cd macos
 ./build-pkg.sh
 ```
 
-产物：`dist/AgentPack-1.0.1-macos-universal.pkg`
+产物：`dist/AgentPack-1.0.2-macos-universal.pkg`
 
 ### Linux
 

macos/build-pkg.sh

@@ -8,7 +8,7 @@ SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 BUILD_DIR="$SCRIPT_DIR/build"
 DIST_DIR="$PROJECT_ROOT/dist"
-VERSION="1.0.1"
+VERSION="1.0.2"
 SCRIPTS_DIR="$BUILD_DIR/scripts"
 
 rm -rf "$BUILD_DIR"

windows/installer.iss

@@ -2,7 +2,7 @@
 ; Requires Inno Setup 6.x
 
 #define MyAppName "Agent Pack"
-#define MyAppVersion "1.0.1"
+#define MyAppVersion "1.0.2"
 #define MyAppPublisher "Agent Pack"
 #define MyAppURL "https://github.com/SenseTime-FVG/agent_pack"
 
@@ -271,15 +271,53 @@ begin
   Result := Args;
 end;
 
-// Try to run verify-llm.py through the host's Python.  Returns True iff the
-// process launched AND exited 0.  Any other combination (Python not found,
-// API failure, etc.) returns False so the caller can fall through to WSL.
-function TryVerifyViaHostPython(const ScriptPath, Args: String): Boolean;
+// Read up to MaxBytes of LogPath; return a trimmed string.  Used to grab the
+// stdout+stderr of the verify step so we can show the user the actual error
+// (Python not found, 401, unknown model, ...) instead of a blanket "failed".
+function ReadLogTail(const LogPath: String; MaxBytes: Integer): String;
+var
+  Lines: TArrayOfString;
+  i, StartIdx: Integer;
+  Body: String;
+begin
+  Result := '';
+  if not FileExists(LogPath) then begin
+    Exit;
+  end;
+  if not LoadStringsFromFile(LogPath, Lines) then begin
+    Exit;
+  end;
+  // Show the last ~20 lines — enough for a python traceback + the
+  // "ERROR: <urllib.error ...>" line that verify-llm.py emits.
+  StartIdx := GetArrayLength(Lines) - 20;
+  if StartIdx < 0 then StartIdx := 0;
+  Body := '';
+  for i := StartIdx to GetArrayLength(Lines) - 1 do begin
+    Body := Body + Lines[i] + #13#10;
+  end;
+  if Length(Body) > MaxBytes then begin
+    Body := Copy(Body, Length(Body) - MaxBytes + 1, MaxBytes);
+  end;
+  Result := Trim(Body);
+end;
+
+// Try to run verify-llm.py through the host's Python.  Captures combined
+// stdout+stderr into LogPath (caller-provided) so we can report the actual
+// error back to the user on failure.  Returns True iff the process launched
+// AND exited 0.  Any other combination (Python not found, API failure, etc.)
+// returns False so the caller can fall through to WSL.
+function TryVerifyViaHostPython(const ScriptPath, Args, LogPath: String): Boolean;
 var
   ResultCode: Integer;
   FullCmd: String;
 begin
-  FullCmd := '/c python "' + ScriptPath + '"' + Args;
+  // Prepend a marker line so the user can see which backend the message
+  // came from when the log bubbles up in the error dialog.
+  SaveStringToFile(LogPath, '=== host python ===' + #13#10, False);
+  // `>> ... 2>&1` appends both streams; the marker line above becomes
+  // the first entry of the log for this backend.
+  FullCmd := '/c python "' + ScriptPath + '"' + Args
+    + ' >> "' + LogPath + '" 2>&1';
   Result := Exec('cmd.exe', FullCmd, '', SW_HIDE, ewWaitUntilTerminated, ResultCode)
     and (ResultCode = 0);
 end;
@@ -306,12 +344,14 @@ end;
 // Fallback: run verify-llm.py through WSL's python3.  Every Windows install
 // target already has WSL2 + a distro set up (Agent Pack requires it), so
 // python3 is reliably available there even when the user hasn't installed
-// Python on the Windows host.  Returns True iff wsl.exe ran AND exited 0.
-function TryVerifyViaWsl(const ScriptPath, Args: String): Boolean;
+// Python on the Windows host.  Captures combined stdout+stderr into LogPath.
+// Returns True iff wsl.exe ran AND exited 0.
+function TryVerifyViaWsl(const ScriptPath, Args, LogPath: String): Boolean;
 var
   ResultCode: Integer;
   WslPath, BashCmd, Cmd: String;
 begin
+  SaveStringToFile(LogPath, #13#10 + '=== WSL python3 ===' + #13#10, True);
   // wslpath -a converts C:\foo\bar.py → /mnt/c/foo/bar.py; easier to shell
   // the conversion out than to translate path separators ourselves.
   // We wrap the full bash program in single quotes and escape any ' inside
@@ -320,19 +360,23 @@ begin
   WslPath := ExpandConstant('{app}') + '\shared\verify-llm.py';
   BashCmd := 'python3 "$(wslpath -a "' + WslPath + '")"'
     + BashSingleQuoteEscape(Args);
-  Cmd := '/c wsl.exe -- bash -lc ''' + BashCmd + '''';
+  Cmd := '/c wsl.exe -- bash -lc ''' + BashCmd + ''' >> "' + LogPath + '" 2>&1';
   Result := Exec('cmd.exe', Cmd, '', SW_HIDE, ewWaitUntilTerminated, ResultCode)
     and (ResultCode = 0);
 end;
 
 procedure OnVerifyClick(Sender: TObject);
 var
-  ScriptPath, Args, Provider: String;
+  ScriptPath, Args, Provider, LogPath, LogTail, Dialog: String;
   Ok: Boolean;
 begin
   Provider := GetProviderName(GetSelectedProviderIndex);
   ScriptPath := ExpandConstant('{app}') + '\shared\verify-llm.py';
   Args := BuildVerifyArgs(Provider);
+  // Redirect both attempts' stdout+stderr to one log so we can replay the
+  // full story in the error dialog.  Lives in %TEMP% so it doesn't leak
+  // the API key beyond this session (deleted on logoff with the rest).
+  LogPath := ExpandConstant('{tmp}') + '\agent-pack-verify.log';
 
   VerifyLabel.Caption := 'Verifying...';
   VerifyLabel.Font.Color := clBlue;
@@ -341,17 +385,32 @@ begin
   // ANY reason — missing python.exe, network error, bad key, wrong model —
   // fall through to WSL.  That way a teammate without Windows Python still
   // gets a real verification against the API rather than a false "failed".
-  Ok := TryVerifyViaHostPython(ScriptPath, Args);
+  Ok := TryVerifyViaHostPython(ScriptPath, Args, LogPath);
   if not Ok then begin
-    Ok := TryVerifyViaWsl(ScriptPath, Args);
+    Ok := TryVerifyViaWsl(ScriptPath, Args, LogPath);
   end;
 
   if Ok then begin
     VerifyLabel.Caption := 'Connection verified!';
     VerifyLabel.Font.Color := clGreen;
   end else begin
-    VerifyLabel.Caption := 'Verification failed. You can configure later.';
+    VerifyLabel.Caption := 'Verification failed. Click Verify for details.';
     VerifyLabel.Font.Color := clRed;
+    // Show the actual error in a dialog.  Common cases:
+    //   - "'python' is not recognized..."  → no host Python (fell through
+    //     to WSL, which also failed — usually because WSL isn't set up yet)
+    //   - "ERROR: HTTP Error 401: Unauthorized"       → wrong API key
+    //   - "ERROR: Unknown model ..."                  → typo in model id
+    //   - "ERROR: <urlopen error ...>"                → no network / DNS
+    LogTail := ReadLogTail(LogPath, 3000);
+    if LogTail = '' then begin
+      LogTail := '(no output captured — the verify command probably could not be launched)';
+    end;
+    Dialog := 'Verification failed.' + #13#10#13#10
+      + 'Details:' + #13#10 + LogTail + #13#10#13#10
+      + 'Full log: ' + LogPath + #13#10#13#10
+      + 'You can continue the install and fix the config later.';
+    MsgBox(Dialog, mbError, MB_OK);
   end;
 end;
 

windows/scripts/wsl-common.ps1

@@ -1,4 +1,19 @@
 Set-StrictMode -Version Latest
+
+# Force UTF-8 for console I/O.  Windows PowerShell 5.x defaults to GBK (936)
+# on zh-CN hosts, which mangles the Chinese strings in our install-*.ps1
+# messages and also corrupts stdout captured from WSL commands that emit
+# UTF-8.  Setting both Input and OutputEncoding to 65001 applies to every
+# script that dot-sources this file (all four install-*.ps1 do).  This is a
+# no-op on PowerShell 7+, which already defaults to UTF-8.
+try {
+    [System.Console]::OutputEncoding = [System.Text.Encoding]::GetEncoding(65001)
+    [System.Console]::InputEncoding = [System.Text.Encoding]::GetEncoding(65001)
+} catch {
+    # Some hosts (e.g. Inno Setup's hidden console) can't mutate encoding —
+    # ignore the failure rather than aborting the install.
+}
+
 $script:RegionChecked = $false
 $script:IsChinaRegion = $false