Plus adobe support confirmed that -  "public documentation that specifically calls out the behavior of the cq:parentPath property (i.e. that it remains unchanged during folder moves) is not explicitly available." 

For anyone who wants to know answer to it, the reply I got from Adobe support is -  " I further investigated the issue and found out that the unchanged cq:parentPath is an expected behavior in AEM as a Cloud Service. The fact that the cq:parentPath remains unchanged after a move operation is by desi...

We're currently using AEM Cloud. I’ve reviewed the DAM Metadata Writeback workflow and didn’t find any errors. For newly created content fragments, the property appears to be added correctly. I've also raised a support ticket with Adobe to investigate further. Thanks, Tarun —really appreciate your h...

Hi,We had a requirement to rename an asset folder , so we used move* option to rename it to a new name. I checked the update references and republish option and the refrences are updated as expected. But for the content fragments inside the renamed folder , i see the cq:parentPath property isn't upd...

Adding tilde ~ or - hyphen at the end with some value should resolve it. since this is a factory configuration, we’ll follow that up with a tilde, and then postfix this configuration with a unique name. eg config-name~myexample.cfg.json.

Were you able to solve this? I am at exactly same point 

Can you please tell where can i find the logs of this script? like you have used log.info here. where ti find the logs for this?