- The reason it's relative is that a full path is pretty unreadable (with the VIrtual...), if there was home root path it would make more sense, I'll make sure whether \sub is an issue or not.
- I didn't make so the path would not contain ```..``` on purpose, this way you can deploy files to ```site\...``` or even to kuduservice directory.
- Kudusync will create the target path if it doesn't exist.
- This feature enables deploying to places other than wwwroot, one possible scenario is first ftp or webdeploying a site and then having to deploy using git only a part of it, this can also help for future scenarios where we want to deploy things other than a web site where the deployment target is not wwwroot.
- For the third question, I'm not sure what you mean by initial full deployment but even if it's the first time you deploy and have a different target path (than wwwroot), this is where the artifacts will be copied to.