Among the files uploaded, you will see the mapping.jsp file loads run.js and the main.js will run. In the main.js file, you will find two sections, "Scenario A" and "Scenario B" preceeding the "Standard Code" section. "Scenario A" represents the simplest code needed to load a Map object; "Scenario B" represents the minimal amount of code necessary to load only a Map object with the configuration that is loaded in the "Standard Code". "Scenario A", "Scenario B" and "Standard Code" sections are mtutally exclusive and if one section is uncommented, the other two are commented out and not executed. ("Scenario A" and "Scenario B" exist solely for troubleshooting and will be removed before promtion to production.)
If anyone is interested in seeing the other files that are loaded, those can be added but, honestly, I don't think those functionalities even enter into the picture. I see other questions asked here along the same lines (see below) but no replies so. . .I hope this is different.
(The code has been lightly redacted to protect internal assets.)
20190610 Update: This issue was misidentified. The cause for some of this bad behavior was an issue with an networking element called Incapsula being improperly configured. The remaining failures appear to be related to the application believing it has a valid token when it does not. The spatialReference issue appears to be unrelated to both causes.