mxdev and cookieplone with filesystem packages needs a manual symlink

[1letter]

what i have done:

i create two backend addons with uvx cookieplone

in the first addon i add to mx.ini

[my.secondaddon]
url = /home/dev/Projects/projects/my.secondaddon
vcs = fs

and run make install and get an error

traceback:

# Read infiles
Read [r]: requirements.txt
Read [c]: https://dist.plone.org/release/6.1.3/constraints.txt
###############################################################################
# Fetch sources from VCS
Queued 'my.secondaddon' for checkout.
Can not execute action!
Traceback (most recent call last):
  File "/home/dev/Projects/projects/my.firstaddon/.cache/uv/archive-v0/BVRUJvoCIdKYwlz-vNaZg/lib/python3.12/site-packages/mxdev/vcs/common.py", line 428, in worker
    output = action(**kwargs)
             ^^^^^^^^^^^^^^^^
  File "/home/dev/Projects/projects/my.firstaddon/.cache/uv/archive-v0/BVRUJvoCIdKYwlz-vNaZg/lib/python3.12/site-packages/mxdev/vcs/filesystem.py", line 32, in checkout
    raise FilesystemError(
mxdev.vcs.filesystem.FilesystemError: Directory 'sources/my.secondaddon' for package 'my.secondaddon' doesn't exist. Check in the documentation if you need to add/change a 'sources-dir' option in your [buildout] section or a 'path' option in [sources].

my workaround, i set a symlink to the second addon manually

mkdir -p ./sources
cd ./sources
ln -s /home/dev/Projects/projects/my.secondaddon my.secondaddon
cd ..
make install

My question: Shouldn't mxdev be responsible for creating a symlink?