reconfigured test string; construction-level test still succeeds(because its coded to error out of recursive states/levels (with non-zero stack)) - this points out a major error in the test that needs to be solved, prob easy as 'the size of string that gets registered must be same as the recursive construct in the test string, plu since we can actually keep track of maximum reached depth level we can use this also as backup to the registered construct size to determine whether the test success (of course I dont think this complete either, why, think about the case where there are two alterations that start and end outside of eachother, and both embedded inside yet another alteration, /[(/[(x)]/[(y)])], let x denote another set of recursive constructs that are recursively embedded to form a max depth, y is the same but one depth level shorter, if y errorrs out in the non data region, the structual regions, because of a bug, that is to say that it should SUCCEED but in reality doesnt, but errors gracefully as not to set off alarms, WHEN IT SHOULD, then even by our adjustments we would be none the wiser, unfortunately -- also merge test fails outright...this worries me a bit, but first things first fix the test in general