What the XSD walk actually did. mergeResults keeps only valid and
issues, so validate() attaches this after the merge.
started is true once validateAgainstXsd is entered. parts are the
relative paths sent to the engine. eligible is how many parts a full
walk would send (a schema is mapped for the part's conformance class; a
Strict root counts only under the strict profile).
XML parts the walk never examined because the run's deadline was
reached (#630). Their eligibility is unknown, so eligible does not
count them; a walk with any is not complete.
What the XSD walk actually did.
mergeResultskeeps onlyvalidandissues, sovalidate()attaches this after the merge.startedis true oncevalidateAgainstXsdis entered.partsare the relative paths sent to the engine.eligibleis how many parts a full walk would send (a schema is mapped for the part's conformance class; a Strict root counts only under the strict profile).