When Jenkins can't read a job, it vanishes from the job-list instead of being replaced with an error marker

As part of JENKINS-23914 I noticed that jobs that Jenkins fails to load completely vanish from the UI. They're still present in jobs/jobname/config.xml, but the only indication they exist in the UI is an error in the log where they failed to load.

It would be a usability improvement helpful if, in cases where the job XML was parsed successfully but the job objects couldn't be created, jenkins displayed a "broken" job in the job-list which shows the exception encountered when loading the job when opened.

Vanishing jobs aren't fun, especially if you don't know how to fix them by hand.