[Feature Request] Stacks Adopt dialog should browse remote node filesystem when environment is Hawser-backed

[naga1090]

Problem statement

When using the Adopt dialog to link compose stacks to a remote Hawser environment, the file browser always shows the local Dockhand server's filesystem — not the remote node's. There is no way to browse or discover stacks that exist on the remote node's disk through the UI.

Environment

1. Dockhand: v1.0.22
2. Hawser: v0.2.39 (edge mode)
3. Dockhand host: Mac mini (macOS), OrbStack
4. Remote node: Raspberry Pi 4B, Debian GNU/Linux 13 (Trixie), arm64

Steps to reproduce:

1. Set up a remote node (e.g. Raspberry Pi) running the Hawser edge agent
2. Connect it to Dockhand as a Hawser environment — connection works, containers are visible
3. Open Stacks → Adopt with the remote environment selected
4. The file browser shows the Dockhand server's local paths and directories, not the remote node's

Proposed solution

My proposed solution would likely require two pieces:

1. Hawser — a new lightweight endpoint (e.g. GET /_hawser/fs?path=/some/dir) that returns directory listings from the remote node's filesystem. Hawser already proxies Docker API calls over the same connection, so adding a filesystem listing endpoint would follow the same pattern.
2. Dockhand — the Adopt dialog detects when the selected environment is Hawser-backed and calls that endpoint instead of the local scanner. The rest of the Adopt flow (scan, link, deploy) could stay the same.

Happy to help test or contribute if this is something the team is open to.

Alternatives considered

My current workaround

The only workaround today is to mount the remote node's stacks directory into the Dockhand server (e.g. via sshfs or an additional volume bind in the compose file), then add that path as an external stack location in Dockhand settings. This works but:

• Adds an external dependency (network mount or extra volume) that needs to stay in sync
• Feels like Dockhand shouldn't need to "see" a remote node's files locally when it already has a live connection to it via Hawser
• Doesn't scale cleanly as more remote nodes are added

Additional context

In this screenshot I'm connected to Hawser (0.2.39) on raspberry pi from Dockhand (1.0.22) on mac mini on same network. The stacks and dockhand default are both places in mac mini (where dockhand is deployed), can't seem to get or change to different location (remote location pi with hawser on it)