Class TraceSubAgentValidatorOracle

Validates which sub-agents an agent run dispatched, and how many iterations it took.

This oracle was referenced by shipped metadata before it existed. Both stock research-agent tests configure trace-validate-sub-agents and weight it at 0.25 and 0.3 respectively; with no implementation registered, the engine logged Oracle not found and a quarter to a third of each test's weight silently vanished from the score. The tests reported green on the remaining oracles. That is the defect this closes (test plan §2, gap 5).

Traversal. Sub-agent runs are reached through the Sub-Agent step's TargetLogID, not through AIAgentRun.ParentRunID. The generated ORM is explicit that ParentRunID "records parentage but is not a link the tree traverses", and the platform's own run-tree walk uses the step link — so querying by ParentRunID would find runs the platform does not consider part of this tree, and miss none that it does. The walk recurses, because a sub-agent may dispatch its own, and a required agent two levels down was still dispatched by this run.

Configuration (as the shipped tests already supply it):

• requiredAgents: names that must appear
• forbiddenAgents: names that must not
• minIterations: minimum Prompt steps on the top-level run