This should be fixed.
The problem was as I described in the comments: We were checking if you had the close/reopen privilege based on whether or not you could reopen that post. Since the returned question was locked, you couldn't reopen it, so you couldn't see the close reasons.
The logic has been simplified to only check if the user has the privilege.
Are “too broad” and “needs more focus” abolishable?
Yes but it depends on the site and the community -- i.e. what the community wants or chooses to allow.
And therefore no, it's usually not possible -- i.e. most communities want to use the site for questions with a narrower focus (instead of a broader or wide-angle focus).
One SE community that I know of ...
Don't we already have this tag? status-norepro
Even the excerpt is applicable:
Indicates that the site developers were not able to replicate the behavior reported.
but the tag wiki needs some work. I'm essentially proposing to re-purpose that tag to include obsolete bug reports. In both cases, the final status of the bug is 'we won't fix it, but not ...