Repository navigation
docs/images/dashboard.png is generated by the screenshot spec but never committed #663
Description
tools/simulation/ui/specs-screenshots/screenshots.spec.ts captures four images. Only three are tracked:
$ git ls-files docs/images/
docs/images/daily-entry.png
docs/images/reports.png
docs/images/sales.png
Running npm run screenshots therefore always leaves docs/images/dashboard.png as an untracked file, which reads as an accidental artefact rather than a deliberate omission — and git checkout -- docs/images/ does not clean it up, so it survives a tidy-up that looks complete.
Pre-existing; noticed while capturing before/after comparisons for #661, not introduced by it.
Either commit it beside the other three, or exclude it from the capture spec. The staleness contract in specs-screenshots/screenshots.spec.ts should say which.
Activity
docs(sim): commit the dashboard screenshot, capture the palette matri…
mforce commentedon Sep 2, 2026
Shipped in #665, merged as
930ea308.docs/images/dashboard.pngis now tracked alongside the other three, andtools/simulation/ui/README.md's image count matches what ships.The staleness-contract comment in
specs-screenshots/screenshots.spec.tswas updated to say all four captures are committed, so the next reader is not left wondering whether the fourth was a deliberate omission — which is exactly the ambiguity this issue was filed about.chore(main): release 0.1.0 (#542)