CLI reports canonical path instead of symlink (logical) path on WSL Linux

### Describe the bug

When opening the CLI in a symlink folder on WSL Linux (Ubuntu 24.04), the current folder is reported as the canonical (symlink target) folder instead of the logical path (symlink folder). This breaks workflows that rely on the symlinked path.

### Affected version

_No response_

### Steps to reproduce the behavior

1. Create a symlinked folder: `ln -s /real/path /symlinked/path`
2. Enter the symlinked path: `cd /symlinked/path`
3. Open the CLI in this folder.
4. Observe that the folder reported by the CLI is `/real/path` instead of `/symlinked/path`.

### Expected behavior

The CLI should report the logical (symlink) path (`/symlinked/path`) as the current directory, matching user expectation and shell behavior.

### Additional context

- Operating system: WSL Linux (Ubuntu 24.04)
- This impacts scripts and tools that depend on the reported path being identical to the logical location.
- Workaround: none known.

Reproduce the issue on WSL Linux with Ubuntu 24.04 using the symlink setup described, then trace where the CLI determines and reports the current directory. Done means opening the CLI from /symlinked/path reports that logical path rather than /real/path, with the behavior verified in the stated environment.

Written by the indexing model from the issue text.