SQL Server 2022 DR failover with log shipping: how to handle transactional + merge replication roles?

I have SQL Server 2022 Standard with 2 instances: a primary and a DR instance. DR is maintained via log shipping.

On the primary databases, I also have a mix of transactional replication and merge replication configured with some other SQL server instances:

Important: Replication is not Primary → DR. Replication happens in the primary environment between multiple SQL Server instances and also with external SQL Server environments.

In a disaster scenario, if I fail over to the DR instance (i.e., restore log shipped backups with recovery and bring the DR databases online), what is the recommended way to handle replication?

Specifically:

1. What is the recommended approach to restore replication functionality after failover when the original Primary instance is down?
2. Is there a best-practice way to script and partially automate this (drop/recreate publications/subscriptions, redirect subscribers, rebuild distributor metadata/jobs, etc.) so DR cutover is repeatable and fast??

I understand replication does not automatically fail over with log shipping. I’m looking for a practical, documented approach for minimizing downtime and manual work during DR. (any related blog posts/documentation will be also helpful). Thanks for reading this :-).