docs(readme): add real UI screenshots to the visual intro (#156)#224
Merged
Conversation
Replaces the "スクリーンショット準備中 / 実 UI を起動できないため未添付" placeholder in the 見た目と最初の1コマンド section with three real captures of the running app: operator home (freshness summary + attention list), resource explorer (equipment tree + detail), and point detail (latest value + freshness badge + history chart). The persona restructure part of #156 already landed (#171); this closes the remaining "no images" gap. The screenshots are captured from the real Next.js app driven against the route-mocked e2e API (no backend/Docker needed) via a new committed Playwright spec (e2e/capture-readme-screenshots.spec.ts) so they can be regenerated on UI changes — the README notes they use sample-twin-equivalent data and points readers at `make demo` for live data. Captured with the preinstalled chromium; the caption is honest that these are route-mocked renders, not a live-stack capture. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XEG6csNA9GDkQzT37CwAUp Signed-off-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes the remaining part of #156 — the persona restructure already landed (#171), and the only open item was "README has zero images." This replaces the
スクリーンショット準備中 / 実 UI を起動できないため未添付（メンテナ対応）placeholder in the 見た目と最初の1コマンド section with three real captures of the running app, the exact 3 the issue recommends:operator-home.pngresource-explorer.pngpoint-detail.pngHow they were captured (offline, reproducible)
The placeholder claimed the automation environment can't run the UI — it can, via the repo's existing route-mocked Playwright harness. A new committed spec,
web-client/e2e/capture-readme-screenshots.spec.ts, drives the real Next.js app againstpage.route()mocks (sample-twin-equivalent data, no backend/Docker) using the preinstalled chromium, and writes the PNGs todocs/screenshots/. So the images regenerate on UI changes:The README caption is honest that these are route-mocked renders (not a live-stack capture) and points readers at
make demofor live data.Test plan
npx playwright test e2e/capture-readme-screenshots.spec.ts— 3/3 pass, PNGs verified by eye (clean values, no dev-overlay badge)yarn typecheck— clean ·yarn lint— 0 errorsworkflow_dispatch-only per repo convention, so it won't run this spec in CI)Checklist
README.md)🤖 Generated with Claude Code
Generated by Claude Code