Bug: pulse-on-sequence

Current implementation of pulse-on-sequence is not very robust. Searching for SEQ “XY” will fail to spot “XXY” since it matches 1st X, then determines second X is not next character in sequence, but does not see that it can be the 1st character in SEQ. It is not a simple fix since building a map of all possible character repeats for longer strings is not trivial; the simpler (but more compute & memory intensive) solution would be to compare the last length(SEQ) of input characters with SEQ.

Current solution also appears to have trouble with special characters like FFh. I assume use of Xstring is doing an implicit conversion. I’ve noticed that concat will convert FFh byte into “FFh” string rather than a single special character, but accumulate-string outputs FFh as a single special character.