Fix WasmTestOnChrome: exclude browser/wasi from gen-debug-dump-docs.py helix post-command

[Copilot]

Description

WasmTestOnChrome and related WASM CI jobs were failing because gen-debug-dump-docs.py was scheduled as a Helix post-command for all non-Windows CoreCLR targets, but the script is not present in the correlation payload for browser/wasi targets.

Changes

• src/libraries/sendtohelixhelp.proj: Added browser and wasi exclusions to the non-Windows HelixPostCommands condition for gen-debug-dump-docs.py, consistent with the existing pattern already used for TestEnvFileName in the same file:

<!-- Before -->
<HelixPostCommands Condition="'$(TargetOS)' != 'windows'">

<!-- After -->
<HelixPostCommands Condition="'$(TargetOS)' != 'windows' and '$(TargetOS)' != 'browser' and '$(TargetOS)' != 'wasi'">

Changes

• src/libraries/sendtohelixhelp.proj

Testing

Change is a build/CI pipeline configuration fix; validated by inspection against the existing pattern in the same file.

Fixes #126706

[Copilot]

Pull request overview

This PR fixes WASM Helix job failures by preventing gen-debug-dump-docs.py from being added as a Helix post-command on browser/wasi targets, where that script is not present in the correlation payload. The change aligns the post-command gating with the existing TestEnvFileName OS-exclusion pattern already used in the same project file.

Changes:

• Update the non-Windows HelixPostCommands condition to exclude browser and wasi, avoiding a missing-script failure on those targets.

Show a summary per file

File	Description
src/libraries/sendtohelixhelp.proj	Excludes browser/wasi from the non-Windows gen-debug-dump-docs.py Helix post-command condition to prevent Helix post-step failures on WASM jobs.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 0