For Training

This is a "how does this affect my workflow" page for Dentolize engineers, not a customer training guide — there is no clinic-facing behavior to teach anyone.

What changes for someone opening a PR

Nothing you have to do differently. If your PR touches clinic-web or clinic-mobile, you'll now see a second automated comment appear on it — 📸 UI changes — sometime after the usual "🚀 Sandbox deployed" comment. It's read-only output; there's no configuration to set, no flag to opt in, and no action required to trigger it.

What changes for reviewers

When reviewing a PR that touches the UI, check for the 📸 UI changes comment before deploying a sandbox and clicking through it yourself — per the PR description, it should already show the screens the PR's own diff affects, screenshotted live from that PR's sandbox. If it's not there yet (and the diff clearly touches UI), it may still be running in the background — see For Support before assuming something is broken.

Treat it as a starting point, not a replacement for testing the PR yourself when the change is non-trivial — the agent decides "which screens are worth a shot" per the PR description, which means it can reasonably miss an edge case a human reviewer would catch by actually interacting with the screen (form validation, an error state, a permission-gated view).

Step-by-step: reading the new workflow step

For anyone onboarding onto CI/infra work on this repo, here's how to trace this feature end-to-end starting from .github/workflows/sandbox.yml:

1. deploy job runs on opened / synchronize / reopened / a

sandbox-relevant edited event (.github/workflows/sandbox.yml:86-90).

1. It deploys the sandbox and collects its info

(.github/workflows/sandbox.yml:151-186).

1. New in this PR: UI screenshot tour fires unconditionally, detached

(.github/workflows/sandbox.yml:198-208).

1. The job continues immediately to Write job summary and the

sandbox-URL PR comment (.github/workflows/sandbox.yml:210-475) — neither of those waits on step 3.

1. Everything past that point — the gate check, the agent run, publishing,

and posting the 📸 UI changes comment — happens outside this repository, on the runner host, and is out of scope to trace further here (see Feature breakdown).