Recently a behavior of the Path object was clarified in the documentation. This was existing behavior, so the only thing that has changed is that the documentation now stipulates the behavior so we should have a test that verifies it.

This is more than just a theoretical condition because we will need to eventually replace the current Path implementation. The work is low enough priority that by the time we implement the replacement we may forget this documented requirement so a test will make sure the implementation remains compliant with future work.