This isn't covered by How does Meta Stack Exchange work?, as that just explains the tags, but I want to know how they are used by the staff. From experience this differs from the tag description.
As an example, see this answer:
Marking this as status-declined since we are not going to be able to get to it in the near term due to the difficulty of fixing issues like this in chat (and it's accompanying Elastic service that is used for search indexing). It will stay in our books as an issue to fix if/when we are able to prioritize chat issues like this again.
Where the excerpt for status-declined reads as:
Indicates that the feature request will not be implemented, or that a bug will not be fixed at present time.
with its extended description reading:
A feature request or bug report is considered declined if the report is reviewed and the site developers disagree that the feature should be implemented or the bug should be fixed.
However status-deferred's excerpt reads as:
Indicates that the feature request or bug has merit to consider, but will not be implemented or fixed in the near term.
with the extended description saying:
A feature request or bug with this tag is something that has been evaluated as positive on potential, but is not present in the current work timeline. It is also not guaranteed to be implemented - when it resurfaces, the proposal may be re-evaluated and a new decision made depending on how the situation has changed since then.
By all rights, based on the wiki excerpts it looks like that feature-request should have had status-deferred. but my understanding, based on private conversations with staff, is that status-deferred is only used for things that are part of a long term plan, i.e. absolutely intended to be done, just not soon.
My guess is there is no plan long term or otherwise to get the linked chat issue completed, even though they recognise it would be worth doing. Had it been status-deferred it would imply that feature was planned, regardless of how far off implementing that plan would be (years, decades, whatever).
Is this how the staff use the tag? Do the tag wikis need updating?