In Cadence, the identifier for the set of of task types that a Worker processes, was referred to as a Task List.
It would appear that this is a better Identifier for this Type than Task Queue. A more accurate Identifier would be Tasks Keys Set or my personal preference (Tasks Hashs Set, as I prefer to use Hash vs Key for these types of Identifiers, but this is a subtle semantic that can be elaborated in documentation to my own code). In any case, this would appear to be a set, not a list.
Back to the point at hand, this isn’t actually a Queue at all, it drives an Internal Queue sure, but referring to this set of keys, as a Queue as opposed to a List (which it is), eliminates the usage of Task Queue for actual datastructure that is the Task Queue, the internal Task Queue. Now, if you were to document in a complete manner the workings of the Temporal System, you would repeatedly be specifying that you are in fact NOT referring to the Internal Task Queue when talking about Worker Task Queue (the list of Keys that the client SDKs are passing on Worker construction).
Anyway, my main point is that you have assigned/implied a Datastructure behavior (a Queue) to an Entity that isn’t a Queue at all.