Vagrant Synced Folder Permission Mismatch Between Local Development and CI Production Environments

In a Vagrant setup, the shared folder is mounted using rsync on Linux and SMB on Windows, which relies on matching user IDs between the host and the guest.

When the host's effective user ID differs from the guest's UID—common in CI pipelines or after OS upgrades—the mounted files become inaccessible, causing build failures despite working locally.

The configuration must guarantee consistent file access regardless of host UID variations, yet the current Vagrantfile lacks a mechanism to enforce a stable ownership model across environments.

Can the Vagrantfile be adjusted to preserve file permissions across differing host UIDs, can provisioner settings enforce UID consistency, and does using a dedicated guest user mitigate the issue?