chore(status-light): add VRT coverage

[cdransf]

Description

Adds dedicated test/vrt/ coverage for status-light, following the button/badge VRT pattern: status-light.vrt.ts covers every variant (5 semantic + 14 non-semantic) × size, grouped into one row per variant, plus a Wrapping row and a CJK language row (status-light.css sets a distinct line-height for :lang(ja/zh/ko)); ForcedColors reuses the full permutation set since forced-color-adjust: none is set on the whole component, so every variant's color survives forced-colors mode rather than collapsing to a system color. status-light-custom-properties.vrt.ts covers reference/override rows for all six documented custom properties (dot-size, dot-color, font-size, line-height, text-to-visual, content-color), with verifyCustomPropertyCoverage() checked against the manifest. No global-styles VRT file is included since status-light has no plain-class global stylesheet.

Motivation and context

Closes the VRT coverage gap for status-light called out in SWC-2410.

Related issue(s)

• Jira: SWC-2410

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed the Accessibility Practices for this feature.
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published.
• I have included updated documentation if my change required it.

Accessibility testing checklist

• Keyboard: N/A. Visual-only test coverage; status-light is non-interactive with no focusable parts and no interactive changes.
• Screen reader: No accessibility-relevant changes. The component's existing semantics are untouched by this test-only addition.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f32d315

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📚 Branch Preview Links

• Storybook (Gen2, dev mode)
• Storybook (Gen2, prod mode)
• Documentation Site (Gen1)
• Storybook (Gen1)

🔍 Gen1 Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

Deployed to Azure Blob Storage: pr-6620

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.

[rise-erpelding]

LGTM

[5t3ph]

For the same reason we don't keep button or badge colors for forced-colors, I don't think we should be keeping them for status light. Reason being that relying on color alone to communicate is a WCAG failure, and we also can't know the intent of those colors out of context.

Can you update the dots to use CanvasText as the background-color for forced-colors mode?

Maybe we also need a ticket to investigate some type of like "retain color" opt-in switch so that contextually colors for status light and maybe badge can be kept for forced-colors, or if we just need to add a demo in our customization docs for how to handle that perhaps.

[cdransf]

Can you update the dots to use CanvasText as the background-color for forced-colors mode?

That makes sense (and was something I hadn't considered). I revised the comments and added the background-color change in 134f728. Added SWC-2508 for the retain color research too. ✨

[5t3ph]

A little more simplification can be done for the forced-colors.

[5t3ph]