Validation: bind author reports to policy and source

[zkwentz]

What & Why

Isolation alone is insufficient if a report can describe a different policy, plan, or source snapshot. This PR binds author reports to canonical source content and validates their spec, policy, and exact criterion metadata against the initiating plan.

Risk & Review Guidance

• Risk level: HIGH — report provenance controls whether publish evidence is trustworthy
• Task class: security
• Review focus: src/openenv/validation/remote.py:117 for canonical hashing; src/openenv/validation/remote.py:551 for report-contract checks; src/openenv/validation/planner.py for pinned spec/adapter selectors
• Blast radius: A mismatch could let stale, truncated, or forged results pass the publish gate.

Decisions & Alternatives

• Content digest is authoritative — Git SHA is emitted only for a clean tree and is not substituted for the filtered snapshot hash.
• Compare exact criterion order and metadata — rejected trusting aggregate passed fields.
• Pin supported spec/adapter versions in policy — prevents ambient adapter upgrades from changing meaning.

Verification

• PASS: PYTHONPATH=src:envs .venv/bin/python -m pytest tests/ -q -m 'not integration' — 1,559 passed, 114 skipped, 31 external integration tests deselected on the complete stack.
• PASS: Fork whole-stack CI — 7/7 checks passed, including Python 3.11/3.12, lint, docs, lock validation, and package smoke tests.
• NOT verified: Signed registry verification and immutable image identity are not implemented.

Scope & Non-Goals

• The author report is still unsigned and uncertified; signatures belong to the official registry.

Stack

PR 14 of 17; depends on #954.

Full 17-PR stack

1. #942 RFC 008: Spec-neutral local and remote validation architecture
2. #943 Validation foundation: spec-neutral contracts and adapters
3. #944 Validation policy: spec-aware check registry and planner
4. #945 Validation executor: hardened shared reports and eligibility
5. #946 Local validation API: execution-model-aware profiles
6. #947 CLI: validation profiles and shared reports
7. #948 HF runtime: dedicated sandbox execution mode
8. #949 HF certification: enforce trusted dedicated isolation
9. #950 [RFC 008] Define remote author validation and publish gating
10. #951 Validation: unify CLI reports and add a strict publish profile
11. #952 Validation: add structured author diagnostics and remediation
12. #953 Validation: run author validation in dedicated HF Sandboxes
13. #954 Validation: isolate submitted code in author Sandboxes
14. #955 Validation: bind author reports to policy and source ← current
15. #956 CLI: scaffold publish requirements
16. #957 CLI: gate pushes on staged remote validation
17. #958 Docs: explain local, remote, and publish validation

All upstream PRs remain draft while RFC 008 is under review.