Expose scenario report verification as a packaged command

[cbeaulieu-gt]

Summary

Provide a stable packaged console command for validating daemon session reports against the scenario expectations delivered by #243.

Context

The matcher currently runs through python -m baton_harness.scenario.verify, while release orchestration is shell-based. The assertion engine is application functionality; runner placement and credentials remain release/deployment concerns.

Acceptance criteria

• Add a documented packaged console command for scenario/report verification.
• Preserve the scenario names, report schema validation, exit codes, and diagnostics established by Design: daemon session report + init-sandbox scenario harness (replaces bespoke verifier scripts) #243.
• The command runs from a wheel installation without a Harness checkout.
• Shell scenario runners delegate report assertions to the packaged command.
• Tests cover valid reports, mismatches, malformed reports, unsupported schema versions, and stable exit behavior.
• Update scenario and release-validation documentation.

Dependencies

• Depends on Establish a frozen wheel installation foundation and dependency lock #360 and completion or explicit re-scope of Design: daemon session report + init-sandbox scenario harness (replaces bespoke verifier scripts) #243.
• Relates to #243 Phase 5a-ci — pre-release real-daemon scenario gate #307 and Disposable-host bundle-only end-to-end scenario campaign #308.

Out of scope

Seeding repositories, supplying live credentials, selecting runners, or executing the real daemon scenarios.

🤖 Generated by Codex on behalf of @cbeaulieu-gt