Node - #user_intent#

For Xmind ChatTree, the first line of the node content must be "#user_intent#", then the content of the second line is the content of the intent, and the third line is the re-enter intent content (optional). Both lines can be followed by an optional intent constraint "(...)", such as:
```
#user_intent#
...intent...(...intention constraint...)
...re-enter intent...(...re-enter intent constraint...)
```

For Python ChatTree, the first parameter of chattree.create_node() must be "#user_intent#", and there are 4 keys in the second parameter dict (only the first key is required), such as:

intent_node = chattree.create_node("#user_intent#", {
    "intent": "...",
    "intent_constraints": "...", # optional
    "re_enter_intent": "...", # optional
    "re_enter_intent_constraint": "..." # Optional
})

If this node is behind the "#single_turn_interact#" node with "topic" InfoItem modifier, it can have "re_enter_intent" and "re_enter_intent_constraint" (these attribute is available in the "TMC" ChatTree example in "ChatTree Examples"), otherwise it can only have "intent" and "intent_constraint" attributes, for example:
```
#user_intent#
Consulting on divorce legal issues
Consulting again on another divorce legal issues
```
Be careful with the description of "re_enter_intent" and use it with caution, otherwise it will have the side effect of clearing related InfoItems after re enter.
For more details about "(re_enter_)intent" and "(re_enter_)intent_constraint", see "intent"
This node is either behind the "#single_turn_interact#" node or behind the "#trigger#" node, and cannot be behind other nodes.
- When following the "#single_turn_interact#" node (the "#single_turn_interact#" node must be followed by at least 2 "#user_intent#" nodes), these intents are mutually exclusive optional limiting values for the InfoItems that need to be extracted from the node (pay attention to the completeness of these optional limiting values); there may be no "#user_intent#" node behind the "#single_turn_interact#" node; "TMC", "TMC_book_flights" and "911" ChatTree examples in "ChatTree Examples" have this situation of the node.
- When following the "#trigger#" node, these intents represent the judgment conditions for starting the trigger process (i.e. entering "trigger", for details, see "Node - #trigger#"), such as "requiring face-to-face communication"; the "TMC" ChatTree example in "ChatTree Examples" has this situation of the node.
The "#user_intent#" node after "#single_turn_interact#" and "#trigger#", the higher the priority (or the higher the position) is, the higher the priority of being matched; but if the "topic" InfoItem is not recognized as the user intent after "#single_turn_interact#", but as a topic, there is no such priority order, and re-entering the topic takes precedence over switching topics, and all "#user_intent#" after "#trigger#" will take precedence over "#user_intent#" after "#single_turn_interact#" regardless of whether it is a topic