Skip to content

docs(readme): show an example validation report screenshot#79

Merged
dadachi merged 1 commit into
mainfrom
docs/readme-validation-report-screenshot
May 22, 2026
Merged

docs(readme): show an example validation report screenshot#79
dadachi merged 1 commit into
mainfrom
docs/readme-validation-report-screenshot

Conversation

@dadachi
Copy link
Copy Markdown
Contributor

@dadachi dadachi commented May 22, 2026

What

Adds a full-page screenshot of an example validation-report.html to the README's Validation report section, which until now described the report only in prose.

The image is a real free-edition run of "a walk-in queue for small veterinary clinics" — all three layers green (Layer 1 3/3 · Layer 2 3/3 · Layer 3 2/2 · Reviewer PASS). It shows the overall verdict badge, the platform×layer matrix, per-layer detail, the embedded iOS + Android home-screen captures with the vision judge's rationales, the contract-parity check, and the domain rename plan.

Captured via the Path A workflow documented in docs/validation-report.md §10.

Files

  • docs/images/validation-report.png (1280×4526, 474 KB) — new
  • README.md — self-linking image + one-line caption in the Validation report section

Docs only.

🤖 Generated with Claude Code

The "Validation report" section described the report textually but had no
visual. Add a full-page screenshot of a real free-edition run (all three
layers green) so readers see the artifact — verdict, platform×layer
matrix, embedded iOS/Android home captures, contract check, rename plan.

Captured via the Path A workflow (docs/validation-report.md §10).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dadachi dadachi merged commit 8ed0b8f into main May 22, 2026
1 check passed
@dadachi dadachi deleted the docs/readme-validation-report-screenshot branch May 22, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant