Are you able to open /crx/explorer or /system/console .Try to check bundle status .

RepoinitFor the following cases, it is preferable to take the approach of hand coding explicit content creation repoinit statements in OSGI factory configurations:Create/delete/disable service usersCreate/delete groupsCreate/delete usersAdd ACLsCheck https://experienceleague.adobe.com/docs/experienc...

Can you share the log snippet from console as well as error log from publisher. 

Are you using connected assets ? If yes then take a look https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/use-assets-across-connected-assets-instances.html?lang=en#configure-a-connection-between-sites-and-assets-deployments  

For every environment you have config interface available there you config the values  https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/environment-variables.html?lang=en  https://experienceleague.adobe.com/docs/experience-manager-clou...

set the redirect path while calling your SAML auth handler.

Yes you can using sling superResourcetype , the only issue is if there is any upgrade happen in acs-commons version in future then the referred field will also get impacted. 

Check ACLs whether you have write permission or not.

Check from developer console .Ref : https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developing/development-guidelines.html?lang=en  

Connect with the product team also check your user rights.