feat(mcp): ingest validation command summaries v2

[JSONbored]

Parent roadmap: #82

Background

Validation evidence matters to maintainers and branch preflight. Users should be able to provide test command summaries without uploading logs or source.

Goal

Parse validation command summaries into structured evidence for branch analysis and PR packets.

Current Behavior

MCP can accept validation hints, but parsing is limited and may miss useful evidence.

Desired Behavior

CLI supports structured validation summaries for passed, failed, skipped, focused, and unknown commands.

Implementation Requirements

• Add CLI flags/input schema for validation summaries.
• Parse command name, exit status, duration, and short summary.
• Treat passed validation as test evidence even without test-file changes.
• Keep raw logs out of API payloads by default.
• Add clear truncation and redaction rules.

Public/Private Output Boundaries

MCP may return private scoreability and risk context to authenticated users. It must never upload source contents by default, and public-safe packet output must exclude private score/reward/trust/reviewability details.

Acceptance Criteria

• Passed validation suppresses false no-test warnings.
• Failed validation becomes actionable.
• Long summaries are bounded.
• Raw logs/source are not uploaded.

Testing Requirements

• npm run test:ci must pass.
• Global coverage must remain at or above 97% for lines, statements, functions, and branches.
• Aim for 98%+ branch coverage locally to avoid CI variance.
• Add tests for every new branch, fallback path, sanitizer rule, and regression.
• Add invariant/property-style tests when behavior depends on sorting, gating, scoring, queue pressure, source-upload safety, public/private boundaries, or upstream drift.
• Public GitHub output must be tested against forbidden language: wallet, hotkey, raw trust score, payout, reward estimate, farming, private reviewability, and public score estimate.
• MCP/local tooling must prove source contents are not uploaded.

Additional Test Scenarios

• Passed command fixture.
• Failed command fixture.
• Long output truncation.
• No test file but validation passed.
• Source/log upload guard.