Skip to content

πŸ§ͺ refresh the Linux persona tie baseline - #683

Merged
jrosseel merged 1 commit into
developfrom
feat/refresh-linux-persona-tie-baseline
Aug 19, 2026
Merged

πŸ§ͺ refresh the Linux persona tie baseline#683
jrosseel merged 1 commit into
developfrom
feat/refresh-linux-persona-tie-baseline

Conversation

@jrosseel

Copy link
Copy Markdown
Collaborator

Why

Every develop run is currently red on the Storybook visual contract for features-persona-onboarding-states--resolution, which blocks image publication and therefore any deploy.

The tie-resolution copy changed in 21caf818 ("⚑ explain persona tie choices", #668): the heading, the option labels (Analyst (Blue) / Anchor (Green)), their descriptions, and the button text. That commit refreshed the darwin baseline at 10:19 today but left the Linux baseline untouched β€” it was last written on 10 August. Only CI can generate the Linux rendering, which is why the gap is easy to miss locally.

Evidence: the failing run's own diff shows old copy versus new copy, not anti-aliasing noise (3% of pixels, all text and control labels), and the -actual.png render is clean and complete.

What

The Linux baseline is replaced with the exact rendering CI produced for that story. No component, story, or test changed β€” this is a baseline refresh only, matching the precedent in πŸ§ͺ refresh Linux onboarding visual contracts and πŸ§ͺ align Linux welcome snapshots.

Why it surfaced now

The Storybook steps used to run inside the test job, after ~15 policy guards. On the develop runs since #668 merged, the job failed at an earlier guard and never reached the visual tests, so the stale baseline stayed hidden. #677 moved Storybook into its own parallel job, so it now reports independently β€” this is that change doing its job on its first day.

Unblocks

Develop CI β†’ image publication for the current develop head β†’ the pending testv4.dev.opencrane.ai deploy.

The tie-resolution copy changed in 21caf81 (#668), which refreshed the
darwin baseline but not the Linux one, so every develop run now fails the
visual contract on features-persona-onboarding-states--resolution. The
baseline is replaced with the rendering CI itself produced for that
story; no component or story changed here.

The break went unnoticed because the Storybook steps used to run inside
the test job and earlier guard failures stopped the job before reaching
them. They now run as their own parallel job and report independently.
@jrosseel
jrosseel merged commit 6d4fbf7 into develop Aug 19, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant