v0.2: release evidence schema for solver-boundary artifacts

[doomhammerhell]

Problem

The release evidence package should include solver-boundary artifacts that are deterministic, concise, and easy to audit. v0.2 should distinguish local baselines from optional external or ecosystem-derived reports.

Acceptance Criteria

• Extend docs/results/ generation with v0.2 solver-boundary evidence.
• Include QUBO exchange hash, replay status, optional Ocean availability, optional Qiskit availability, and metadata boundary fields.
• Keep committed baselines deterministic and host-independent.
• Keep measured runtime output separate from committed deterministic evidence.
• Update docs/reproducibility.md and benchmark documentation.

Boundary

Do not commit machine-specific runtime claims as release evidence.