No problem, happy building!
As for the latter item, it would likely be an issue that is only caught at browser runtime (i.e., the developer console). To investigate further, I'd try opening your site externally and opening the browser console via the following guide (these steps are roughly the same between browsers):
https://developer.chrome.com/docs/devtools/console/reference#open
See if any red error logs appear. If so, you can likely right click, select 'Copy Message' (or the equivalent available option), and paste the error directly into Shakespeare. The agent should be able to understand where to look based on that context and attempt to resolve the issue. You might have to repeat this process a few times to resolve any remaining errors.
I'm currently investigating to see if we can automate this post-deployment check directly in mkstack/Shakespeare; this will allow the agent to perform this process automatically.
Let me know if you have any questions, and best of luck!
