Repository navigation
Refresh the STU-383 account review screenshots - #128
Merged
Merged
Conversation
All eight PNGs in screenshots/stu-383/ were last regenerated 2026-09-23 (d4306b3), so they still showed the pre-redesign account surfaces — three weeks and a full visual redesign out of date. They are the human-review artifacts the STU-383 criteria name, so stale copies are worse than none: they read as the current design. Captured from the e2e spec itself (e2e/stu383-account-overview.spec.js, "capture account screenshots for human visual review"), which regenerates all eight and asserts the layout while doing it: the account card renders non-empty, stays inside the viewport, and the surface has no horizontal overflow. That test passes, and the captures were checked by eye for desktop and mobile. Sizes grew roughly 1.8-1.9x in height (free-zero-usage desktop 1440x1511 to 1440x2765; mobile 360x2029 to 360x3957) — the account surface carries more content than the September design, not a broken layout. Binary-only: no source, spec or dist change.
Contributor
|
No reviewable files after applying ignore patterns. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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.
Why
All eight PNGs in
screenshots/stu-383/were committed 2026-09-23 (d4306b3) — before the redesign landed. They are the human-review artifacts the STU-383 criteria name, so being three weeks stale is worse than having none: anyone eyeballing them sees a design that no longer exists.I first hit this while working on the composer/paywall PRs: a full test run leaves all eight modified, and the diff looked like a broken account layout (~1250px taller). It wasn't — it was accumulated redesign drift.
What
Regenerated from the spec that owns them,
e2e/stu383-account-overview.spec.js→ "capture account screenshots for human visual review", run against currentmain.That test asserts layout while capturing — the account card renders non-empty, stays inside the viewport right edge, and the surface has no horizontal overflow — and it passes. I also checked the desktop and mobile captures by eye: the plan card, FlutterFlow connection card, usage card and prompt recap all render correctly, with no clipping or blank regions.
Sizes
Height grew ~1.8–1.9x across all eight, in both viewports:
That is the account surface carrying more content than the September design, not a regression — confirmed by comparing against
mainand by the fact that thefree-zero-usagescenario (0 of 2 generations used) cannot render the paywall at all, so recent paywall work cannot be the cause.Scope
Binary-only — no source, spec or
distchange.git diff --statis 8 files, 0 insertions, 0 deletions.