Problem
Spec/schema validators want a consistent fail-soft shape (collect errors with a path prefix rather than throwing on the first).
Proposed change
Provide a ~15-line recursive validator idiom (one-shot recursion guard + path-prefixed error list + early-return verify helper), parameterised over our own tree type. Use FQN/deterministic names for definitions to avoid simple-name collisions.
Acceptance
Priority: low · Effort: small
Problem
Spec/schema validators want a consistent fail-soft shape (collect errors with a path prefix rather than throwing on the first).
Proposed change
Provide a ~15-line recursive validator idiom (one-shot recursion guard + path-prefixed error list + early-return verify helper), parameterised over our own tree type. Use FQN/deterministic names for definitions to avoid simple-name collisions.
Acceptance
Priority: low · Effort: small