chore: onboard CrystalLattice to the fleet catalog - #28
Merged
Conversation
Adds the catalog row, the ground-truth screenshot, and the regenerated landing page. The screenshot is a screen-1 capture through the sim's own ScreenshotGenerator, same as the rest of the fleet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sa4YLoQJ4SwMSEkGxCcpg3
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
5 tasks
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
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.
Description
Brings OpenPhysics/CrystalLattice — a five-screen crystal structure sim — into the fleet catalog, and regenerates the landing page from it.
structure/repos.json— new row, inserted alphabetically betweenCarnotHeatEngineandDopplerEffectscreenshots/CrystalLattice.png— ground-truth capture of screen 1, taken with this repo's ownscripts/screenshot.mjsso it goes through the sim'sScreenshotGeneratorlike every other sim'sdocs/assets/CrystalLattice.webp+docs/index.html— regenerated byscripts/generate-pages-index.shThe
docs/index.htmldiff is only the new card plus the two counts (17 → 18 originals, 31 → 32 total); no other card moved.Onboarding puts the sim in the weekly compliance fan-out, so a companion change on the sim's own
claude/three-ui-gaps-58uiombranch fixes the README-outline failure that surfaced — it led with## Screens, which the six-section outline does not allow, andcheck-repo-compliance.shhas a specific message for exactly that case. With that branch checked out,scripts/check-repo-compliance.shpasses against it, leaving only the two standing warnings (documented hardcoded colours, andghunavailable locally). That branch has no PR open yet, so onmainas it stands today the sim would fail the compliance gate.Type of change
Catalog + landing page content; no script or workflow changes.
Related issues
None.
Testing
scripts/check-repos-catalog.sh— Catalog OK (41 repos, schemaVersion 1.1.0), all structural invariants passnpx bats tests/— 69/69 pass, including the pages-index golden-page testscripts/check-repo-compliance.sh /path/to/CrystalLattice— passes (against the branch noted above)npm run lint/check/build— not applicable to this repoHow to test
scripts/check-repos-catalog.sh— expectCatalog OK (41 repos, …)npx bats tests/— expect 69 passingdocs/index.htmland confirm the Crystal Lattice card renders with its thumbnail, links tohttps://openphysics.github.io/CrystalLattice, and that the footer reads 32 live simulationsChecklist
Note
The card links to
https://openphysics.github.io/CrystalLattice, which currently 404s — that repo's Deploy workflow has never run (zero runs; no push-event run of any workflow exists there, though PR-event runs do). Its Pages source likely still needs setting to GitHub Actions in repo settings. The card will start resolving once that is done and a deploy lands; nothing in this PR depends on it.