Storybook builds don't reflect example app changes

🐛 Bug Report

In Chromatic August 2026 a change was introduced where if turbosnap does not detect any changes then the storybook build is not uploaded to chromatic at all. The feature is called bypassed builds.

Because we include some extra generated content in storybook (react / angular example apps for lighthouse checks, performance results, etc) those changes are not published in the storybook if there are no source changes to stories themselves that turbosnap can detect.

See https://github.com/chromaui/chromatic-cli/issues/1472

💻 Repro or Code Sample

The following PR demonstrates the behavior where with an example app only change the storybook publish was skipped: #3051

Workaround

Not ideal since it's a waste of snapshots for no reason but for example app / performance test only changes a workaround until a fix / feature is available from chromatic is bump the guid preview.js manually: https://github.com/ni/nimble/blob/76640ba3459409eba3495b8a58ca4072a48cf851/packages/storybook/.storybook/preview.js#L106

You probably need to do it in each subsequent commit in a PR that is non-story changes to, i.e., the example apps if you want to see the result of the changes in the built storybook.

Start by reviewing PR #3051 and packages/storybook/.storybook/preview.js, then compare the linked Chromatic Turbosnap and bypassed-build documentation. Done means changes limited to the React or Angular example apps are reflected in the published Storybook without manually bumping the preview GUID.