Site.js should do the right thing if started without an explicit path to serve specified within a .dynamic or .hugo-*, etc., folder
Check the path hierarchy, and, if started within a dot folder (.hugo-*, .dynamic, etc.), re-orient the root to that folder’s parent.
This way, if you’re working on a project and you happen to be in a sub-folder, you can use the site command without worrying about where in the hierarchy you are.
We should not override the person’s preference if a path to serve is explicitly specified, however.