good first issue: verify source-preview install on Windows 11 + WSL2

[Altairpaca]

Parent

Contributes one bounded row to #8.

Goal

Run the current DSHelm source-preview path inside WSL2 on a Windows 11 host and submit a reproducible, redacted installation record. Focus on the WSL2 boundary: filesystem location, shell/PATH behavior, DSH discovery, permissions, and uninstall safety.

What to record

• Windows 11 build family and WSL distribution/version;
• whether the repository is cloned inside the Linux filesystem or under /mnt/c;
• Node, pnpm, DSH, and DSHelm commit/version;
• whether pnpm preview:init succeeds;
• dsh --profile dshelm --dump-config result;
• node packages/cli/dist/index.js doctor result;
• one redacted node packages/cli/dist/index.js explain ... result;
• uninstall result;
• any PATH, line-ending, permission, proxy, filesystem-performance, or Windows/WSL interop issue.

Suggested workflow

1. Start from a clean clone of main in WSL2.
2. Prefer the Linux filesystem for the first run; record it explicitly.
3. Follow the root README without undocumented workarounds first.
4. Capture the exact redacted error before applying any workaround.
5. Submit the evidence using the repository's Install report Issue Form and link it here.
6. If a WSL2-specific documentation or script fix is small and reproducible, submit it as a focused follow-up PR.

Privacy boundary

Do not post tokens, cookies, Windows account identifiers, private repository names, machine names, or sensitive Windows/Linux home paths. Do not copy product-owned credentials between Windows and WSL merely to complete this task.

Done when

• one real Windows 11 + WSL2 installation report is linked here;
• the filesystem location and tool versions are explicit enough to reproduce the result;
• any platform-specific defect has a focused follow-up issue, or the limitation is documented.

This task is evidence-oriented and intentionally avoids requiring changes to routing internals.