Add low-friction reproducibility clinic intake

[seva9523]

What changed

• add a low-friction Reproducibility check request issue form that asks for two exact public revisions and a narrow evaluation contract
• publish the public-alpha Reproducibility Clinic scope, selection criteria, safety boundaries, and validation ladder
• link the intake flow from the README and contribution guide

Why

The existing design-partner call asks potential users to understand the product before submitting a case. This change reduces the first step to a repository/workflow, baseline, candidate, and drift question. It also distinguishes a submitted problem, a reproduced comparison, external review, downstream installation, repeat use, and real drift caught so one-off analysis is not overstated as adoption.

User impact

A maintainer, user, or researcher can request a bounded public comparison without installing EvalRepro first. Accepted cases may receive hash-only evidence and an optional integration proposal, subject to safety, reproducibility, fit, and maintainer capacity.

Validation

• compared main...agent/reproducibility-clinic: four intended files, 172 additions, no unrelated changes
• issue-form fields use existing enhancement label and require public-reproducibility, publication, and safety declarations
• documentation preserves the three-case public-alpha target in Beta: seeking three public evaluation workflows for design-partner testing #11 and does not promise acceptance, turnaround, adoption, or endorsement

AI-assisted work disclosure

AI assistance was used to draft the form and documentation and to publish this branch. The maintainer should review the wording and GitHub issue-form rendering before merge.