max / makenotwork

tagtree: exclude model_valid's semantic-depth guard, which is equivalent The confirming run put `oracle.rs:594:30 replace > with >= in model_valid` back in the missed list, and the previous commit's message had it as one of the two bounds the new tests kill. That was a misread of the line: 594 is `config.semantic_depth > 0`, and the max_depth bound the test actually kills is 591. Both bounds are dead; this is a third mutant that was never in that pair. It is equivalent, and it is the same mutant as `src/lib.rs:189:30` in `validate_with` sitting in the model that reimplements it. `>= 0` is always true for a usize, so the mutant evaluates `segs.len() < semantic_depth + 1` with `semantic_depth == 0`, which asks `segs.len() < 1`. `model_valid` returns false for the empty tag on its first line and `str::split` yields at least one segment for every non-empty string, so the extra check cannot fire. With `semantic_depth > 0` the guard is true either way. List-diff verified: 149 to 140, exactly the nine intended. The max_depth `>` at 591 stays in scope and stays caught, which is the check that the exclusion is aimed at the right line this time.