ok, I see the issue here, the content fragment when deactivated and activated again from author has cq:lastReplicationAction_publish as Deactivate in the publish instance, but if you simply activate the same content fragment again, the status gets modified correctly in publish with the latest timest...