Okay, that makes sense, but there's still the problem (as in my original
example) that the TOPICS command can end up suggesting a topic that isn't
available (because the TopicEntry belongs directly to the Actor and is
masked by a DefaultTopic in an ActorState). This looks analogous to the
situation for which the limitSuggestions property was added to ConvNode, so
I wonder if there'd be a case to adding it to ActorState too, or perhaps
simply moving it to the TopicDatabase class.
I agree - I'll add this.