[Bug?]: Executing a running task leaves you in the wrong directory.

[quisido]

Self-service

• I'd be willing to implement a fix

Describe the bug

This is a really niche bug. As a testament for how much I love Yarn, I feel the need to report it, as it's the biggest problem I personally face with it.

If I have a running process ^1, and my shell dies ^2, my restored shell state is always in the package directory instead of the root directory.

1. e.g. a running process, a Node server
2. my shell dies, because my computer reboots or my SSH tunnel disconnects when I close VS Code

To reproduce

# Start a process, e.g. NextJS.
/path/to/app > yarn packages/xyz run dev

# close the terminal

# open the terminal
/path/to/app/packages/xyz

Environment

OS:
Windows, VS Code terminal, running Yarn
Windows, VS Code terminal, connected to Linux host running Yarn with zsh

Binaries:
Yarn 4.5, but I believe this has been long-standing since the introduction of Yarn workspaces.

Additional context

Expected behavior:

After opening the terminal, my restored state should be /path/to/app instead of /path/to/app/packages/xyz.