Fix Prettier formatting error in buildTokens.ts

[Copilot]

Summary

The CI "Test & Lint" workflow was failing due to a Prettier formatting violation in scripts/buildTokens.ts. A single-element array was formatted across multiple lines instead of inline.

List of notable changes:

• fixed formatting in scripts/buildTokens.ts line 170 to match project style

What should reviewers focus on?

• Verify the formatting change matches patterns used elsewhere in the file (lines 156, 185)

Steps to test:

1. Run npm run lint to verify linting passes
2. Run npm run test:unit to verify no functionality broken

Supporting resources (related issues, external links, etc):

• Job URL: https://github.com/primer/primitives/actions/runs/21135607588/job/60776812614

Contributor checklist:

• All new and existing CI checks pass
• Tests prove that the feature works and covers both happy and unhappy paths
• Any drop in coverage, breaking changes or regressions have been documented above
• All developer debugging and non-functional logging has been removed
• Related issues have been referenced in the PR description

Reviewer checklist:

• Check that pull request and proposed changes adhere to our contribution guidelines and code of conduct
• Check that tests prove the feature works and covers both happy and unhappy paths
• Check that there aren't other open Pull Requests for the same update/change
• Verify the design tokens changed in this PR are expected using the diffing results in this PR

Original prompt

Fix the failing GitHub Actions workflow Test & Lint
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 60776812614
Job URL: https://github.com/primer/primitives/actions/runs/21135607588/job/60776812614

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 17f0407

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