@BrockAdams I discovered that by running the following JS snippet in one's browser console, it's possible to vote to close for old, now-decommissioned close reasons. I tested this out in a SO Team I'm a part of (where all users have binding close powers) and I could close things as "too localized", "noise or pointless", as well as NC and NaRQ.
I'd like to report this bug to SE, but before doing so, I wanted to have a little "proof of concept" user script that uses this snippet to provide these close reason options in the UI (in order to make it more likely that SE will fix it).
The snippet is $.post({url: `https://[site]/flags/questions/[post ID]/close/add`, data: {'fkey': StackExchange.options.user.fkey, 'closeReasonId': [reason ID]}}) where [site] is the site URL (can either be a regular Q&A site or a Teams URL) and [reason ID] is one of these
(though I'm not sure how the target is passed in for "exact duplicate"; this snippet here shows how off-topic custom reasons are passed in, but that's not relevant to the old close reasons
@gparyani Weird, I don't seem to have gotten either an audible nor inbox notice of this ping. So, you're asking me to write a userscript for this? I'm not sure that's necessary if you have a recipe already (posting the recipe is good enough).
Anyway, I'm willing but have limited -- frequently interrupted -- time today. May not be able to finish it before tomorrow evening (Approx 0400 UTC). If you post, or see, a bug report before then, please ping me here so I don't waste my time.
@BrockAdams Probably since you've not chatted here in the last seven days...I should have instead replied to the top-pinned message. All I need is the UI; I already have the functionality.
