docs/images/dashboard.png is generated by the screenshot spec but never committed

[mforce]

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.

[mforce]

Shipped in #665, merged as 930ea308. docs/images/dashboard.png is now tracked alongside the other three, and tools/simulation/ui/README.md's image count matches what ships.

The staleness-contract comment in specs-screenshots/screenshots.spec.ts was 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.