The test_lemonade_server.yml workflow was missing the install-lemonade
action that verifies lemonade-server is pre-installed on the runner.
This caused the script to fail with "lemonade-server not found" error.

All other workflows (test_api, test_chat_sdk, test_embeddings,
test_gaia_cli_windows, test_rag) include this verification step.

The install-lemonade action:
- Verifies lemonade-server exists on PATH
- Checks version compatibility with GAIA
- Exports LEMONADE_SERVER_PATH environment variable

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

The action previously only checked if lemonade-server was in PATH,
which fails when it's installed but not added to system PATH.

Now the action:
1. First checks PATH (fast path for properly configured runners)
2. If not found, searches common Windows installation locations:
   - %LOCALAPPDATA%\Programs\Lemonade
   - %ProgramFiles%\Lemonade
   - %ProgramFiles(x86)%\Lemonade
   - %USERPROFILE%\Lemonade
   - %LOCALAPPDATA%\Lemonade
3. Automatically adds found directory to GITHUB_PATH for the job
4. Provides clear error with searched paths if not found

This makes the action more robust for self-hosted runners where
lemonade-server may be installed without being in system PATH.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

Added the actual installation path used on CI runners:
- C:\Program Files (x86)\Lemonade Server\bin

This path is now checked first to ensure fast discovery on
self-hosted runners with the standard Lemonade Server installation.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

GitHub Actions self-hosted runners run as a service and may not
inherit updated System/User PATH variables until service restart.

Changes:
- Added PATH debugging to diagnose environment issues
- Proactively add known stx runner path (C:\Program Files (x86)\Lemonade Server\bin) to session PATH
- Check PATH again after addition before falling back to search

This ensures lemonade-server is found even when runner service
hasn't been restarted after PATH updates.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

Enhanced diagnostics to troubleshoot why lemonade-server with space
in path ("Lemonade Server") is not found despite being in PATH.

Now shows:
- System PATH from registry
- User PATH from registry
- Current session PATH (what runner actually sees)
- Filtered view of Lemonade-related paths
- Explicit check if lemonade-server.exe exists at known location

This will reveal if:
- Space in path causes parsing issues
- Runner service inherits PATH correctly
- GITHUB_PATH addition works properly

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

Removed extensive debug output while keeping working logic:
- Proactively check and add known installation path to PATH
- Fallback to searching common locations if needed
- Minimal, clear output focused on operational info

The action now efficiently handles self-hosted runners where
lemonade-server PATH may not be inherited by runner service.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

Re-added ${env:ProgramFiles(x86)}\Lemonade Server\bin to the
fallback search paths array. While this path is checked proactively
at the top, keeping it in the fallback ensures redundancy.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

The stx runner path is already checked proactively at the top and
added to PATH if it exists. Checking it again in the fallback is
redundant - if it existed, we would have already found it.

Fallback now only searches alternative locations that weren't
checked in the initial known-path logic.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>

Now clearly communicates:
- "Found at known location" vs "Not found at known location"
- "Adding to PATH" vs "Already in PATH"
- "lemonade-server not found in PATH, searching alternatives..."
- "Found at alternative location" when using fallback

Makes the CI logs easier to understand and debug.

Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]>