if statements are implemented with proxy nodes, which while functional requires guesstimating which sets of characters count as "valid" to forward them before joining DFAs.

This goes somewhat wrong with the wait match, which intentionally sets itself up as its own error handler (since otherwise
any usage of it would be ambiguous).

There are two separate problems here:

• Using a wait match in an if body does not work.
• Doing so silently does the wrong thing.

Both of these issues should be fixed by 0.5.0.

Subj + perhaps also an option to disable it.

e.g.

case {
    /\/[a-z]+\/?/, "/" -> {     
        target_url = PAGE_HTML; 
        is_cacheable = false;   
        optional {              
            /[#?][^ ]*/;        
        }                       
    }                           
}

seems to only put the start actions onto the paths that actually take the optional.