ata-validator

isValid() on a buffer disagreed with validate() on the parsed value for 294 of 2208 cases in the official suite, in both directions. Two causes: the path returned the code generator's false directly, which is ambiguous between "invalid" and "the plan stopped at a composition opcode and the walker should finish", so every schema using allOf, anyOf, oneOf or $ref was rejected outright; and it ended in a second, simpler walker that had drifted from the one validate() uses. It now calls the same walker with all errors off, so there is one set of semantics rather than two kept in step by hand. The disagreement drops to 243 cases, the rest being the on-demand plan answering before the walker runs, which is engine work rather than a setting.

tests/test_buffer_path_parity.js records that number so it cannot widen, and the README and the edge runtimes guide now state the gap, since isValid, countValid and batchIsValid are shipped APIs and a caller has no way to know otherwise.