scc: Session save and push from GURU-5070 at 2026-05-30 14:47

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

session-logs/2026-05-30-session.md

@@ -286,3 +286,69 @@ Activation requires Mike to close the current (legacy-conhost) session and relau
 - Revert default terminal: Settings → Privacy & security → For developers → Terminal → "Let Windows decide".
 - Revert Wispr elevation: `Unregister-ScheduledTask "Wispr Flow (Elevated)"`; rename `Wispr Flow.lnk.disabled` → `Wispr Flow.lnk`.
 - Windows Terminal delegation GUIDs: Console `{2EACA947-7F5F-4CFA-BA87-8F7FBEEFBE69}`, Terminal `{E12CFF52-A866-4C77-9A90-F570A7AA2C6B}`.
+
+---
+
+## Update: Reverted Wispr Flow elevation; fixed Claude shortcut elevation error (GURU-5070)
+
+Mike asked to undo the Wispr Flow dictation-fix changes and have the Claude shortcut run `wt` without elevation.
+
+### Actions
+
+- **Unregistered scheduled task** `Wispr Flow (Elevated)` — Wispr no longer auto-starts at High integrity.
+- **Restored non-elevated Wispr autostart:** a normal `Wispr Flow.lnk` (non-elevated, targets `...\WisprFlow\Wispr Flow.exe`) was already present in the Startup folder, so removed the now-redundant `Wispr Flow.lnk.disabled` duplicate.
+- **Reverted default-terminal delegation** in `HKCU:\Console\%%Startup`: `DelegationConsole` and `DelegationTerminal` set back to `{00000000-0000-0000-0000-000000000000}` ("Let Windows decide").
+- **Claude shortcut left on `wt`, non-elevated:** `Claude.lnk` already targeted `wt.exe -d "D:\claudetools" "...\claude.exe" --chrome --dangerously-skip-permissions` with RunAsAdmin = False — no change needed. Claude still opens in Windows Terminal because the shortcut invokes `wt.exe` explicitly, independent of the reverted global default.
+
+### Root cause of the `0x800702E4` ("requires elevation") error
+
+After the revert, launching the shortcut threw `ERROR_ELEVATION_REQUIRED` on `claude.exe --chrome --dangerously-skip-permissions`. Cause: per-user **Run as administrator** AppCompat flags set during the earlier elevated session in `HKCU:\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers`:
+
+- `C:\Users\guru\.local\bin\claude.exe` = `~ RUNASADMIN GDIDPISCALING DPIUNAWARE`
+- `C:\Users\guru\AppData\Local\Microsoft\WindowsApps\wt.exe` = `~ RUNASADMIN`
+
+These force elevation on every launch, so a non-elevated shortcut failed.
+
+**Fix:**
+- `claude.exe` → stripped `RUNASADMIN`, kept DPI flags → `~ GDIDPISCALING DPIUNAWARE`
+- `wt.exe` → removed the `RUNASADMIN` value entirely
+
+Both now launch non-elevated. Pending Mike's confirmation that relaunching from `Claude.lnk` opens WT without the elevation error.
+
+### Reference (re-revert / re-apply)
+
+- Re-add RUNASADMIN (if ever needed): set the Layers value back to include `RUNASADMIN` for the exe path.
+- Re-elevate Wispr: re-create the `Wispr Flow (Elevated)` scheduled task (AtLogOn, RunLevel Highest, action = `...\WisprFlow\Wispr Flow.exe`) and disable the Startup `Wispr Flow.lnk`.
+- The AppCompat Layers key is HKCU — editable without elevation.
+
+---
+
+## Update: Claude taskbar/profile icon via dedicated Windows Terminal profile (GURU-5070)
+
+Mike asked whether the taskbar could show the Claude icon instead of the generic Windows Terminal icon when launching via `wt.exe`.
+
+### Constraint
+
+A shortcut's icon only brands the `.lnk` itself. Once `wt.exe` is the running process, the taskbar button belongs to Windows Terminal — it uses WT's window icon and groups under WT's AppUserModelID (AUMID). A `.lnk` icon cannot override that. The controllable lever is WT's **per-profile `icon`**; on WT 1.24 the window/taskbar icon follows the active profile's icon. Taskbar *grouping* is still keyed to WT's AUMID and cannot be changed without leaving `wt.exe` for a terminal that owns its own identity (e.g. WezTerm/Alacritty).
+
+### Actions
+
+- **Extracted the Claude icon** from `C:\Users\guru\.local\bin\claude.exe` (index 0) to a 256x256 PNG at `C:\Users\guru\.local\bin\claude-icon.png` via `user32!PrivateExtractIcons`.
+- **Added a dedicated "Claude" profile** to WT `settings.json` (backed up to `settings.json.bak`):
+  - guid `{9cbe74ea-2403-4e9e-89aa-23780ee3c19a}`
+  - `commandline`: `"C:\Users\guru\.local\bin\claude.exe" --chrome --dangerously-skip-permissions`
+  - `startingDirectory`: `D:\claudetools`
+  - `icon`: `C:\Users\guru\.local\bin\claude-icon.png`
+- **Repointed `Claude.lnk`** to `wt.exe` with args `-p Claude` (profile now carries the command, dir, and icon). Still non-elevated; `IconLocation` left at `claude.exe,0`.
+- Validated `settings.json` parses as JSON after the edit.
+
+### Result / Pending
+
+- Tab icon, new-tab dropdown, and WT jump-list → Claude icon (reliable).
+- Taskbar button → expected to show the Claude icon on WT 1.24, but **pending Mike's visual confirmation** (WT taskbar-icon behavior varies by version). If it stays the generic WT logo, fallback options are a WezTerm/Alacritty terminal with a Claude icon, or a custom-AUMID experiment.
+
+### Reference (revert)
+
+- Restore WT settings: copy `settings.json.bak` over `settings.json` (path: `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\`).
+- Revert shortcut to inline launch: set `Claude.lnk` Args back to `-d "D:\claudetools" "C:\Users\guru\.local\bin\claude.exe" --chrome --dangerously-skip-permissions`.
+- Icon source PNG: `C:\Users\guru\.local\bin\claude-icon.png` (safe to delete if profile removed).