Print a summary line at the end of validate and metaschema runs

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR adds end-of-run validation summaries to the validate and metaschema commands.

Changes:

• Introduces a shared ValidationSummary structure for validated and failed item counts.
• Adds a shared formatter that prints validated, passed, and failed totals to stderr.
• Replaces command-wide boolean status tracking with per-item summary accounting.
• Updates standard validation flows, including directories and multi-document inputs.
• Updates metaschema validation flows to account for pass/fail totals.
• Preserves JSON, trace, and benchmark-oriented output modes without appending the text summary.
• Retains the existing expected-failure exit behavior when any validation fails.
• Extends CLI integration expectations across validate, metaschema, compile, install, and test command scenarios.

Technical Notes: Summary formatting adds a separator only after diagnostics or verbose/debug output, keeping otherwise-silent successful runs concise.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[cubic-dev-ai]

No issues found across 194 files

_{Re-trigger cubic}

[cubic-dev-ai]

1 issue found across 5 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="test/ci/pass_validate_fuse.sh">

<violation number="1" location="test/ci/pass_validate_fuse.sh:44">
P3: The verbose "ok:"/"matches" trace lines go through LOG_VERBOSE, but this test redirects only stderr (2> output.txt) and leaves stdout on the terminal. If LOG_VERBOSE ever routes to stdout, those lines are silently dropped from output.txt and the summary assertion drifts out of sync, so the test would pass while missing output. The verbose trace and summary are expected to land in the stderr-only file together; capture both streams (2>&1) so every verbose line is actually asserted, consistent with the test's intent to check that verbose output is exactly the expected content.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>