Unexpected behaviour about opendial HOT 2 CLOSED

Yes, there was indeed a mistake in the way the "in" relation was handled, it is 
now corrected in the development trunk.  Thanks for reporting it!

But I also noticed another potential problem in your domain: the effect "<set 
var="count" value="{count}+1"/>" is included in a utility rule when selecting 
the next action.  That makes implicitly "count" as an action variable (since 
the variables in the effects of utility rules are considered as action 
variables).  If another action than [wave, jump, hands_up] is selected (for 
instance, if you type a user input outside the coverage of the domain, such as 
"this is a test"), this variable value will therefore be set to "None" and 
delete the counts. I would therefore recommend you to remove this effect, and 
instead add the following rule in the second model:

<rule>
            <case>
                <condition>
                    <if var="a_m" value="{actions}" relation="in"/>
                </condition>
                <effect>
                    <set var="count" value="{count}+1"/>
                 </effect>
            </case>     
        </rule>