ECHOES-397 Add issue location marker layer 3 tokens

[2amelia]

Summary

• add new semantic design tokens for issue location marker states in light and dark themes
• regenerate the public themed token outputs with the new token names
• extend the design token cssVar test to cover the new contract

Validation

• yarn build-tokens --brand=Brand-A
• yarn jest src/utils/tests/design-tokens-test.ts
• yarn ts-check
• yarn build
• yarn test-ci
• DESIGN_TOKEN_BRAND=Brand-A yarn validate-ci

Review notes

• introduces new layer-3 semantic tokens, so designer/developer review of the token contract is recommended

[netlify]

✅ Deploy Preview for echoes-react ready!

Name	Link
🔨 Latest commit	7c8696e
🔍 Latest deploy log	https://app.netlify.com/projects/echoes-react/deploys/6a6f894aa3a4180008bb8d27
😎 Deploy Preview	https://deploy-preview-743--echoes-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hashicorp-vault-sonar-prod]

ECHOES-397

[gitar-bot]

💡 Quality: New issue-location-marker design tokens need designer+dev review

This PR introduces new layer-3 semantic design tokens (issue-location-marker.colors.background.{default,hover,selected} and foreground.{default,selected}) in both light.json and dark.json. Per the design-token review policy, new tokens should be reviewed by both a designer and a developer as a checkpoint (not a blocker) to confirm the token contract, naming, and palette/alpha choices are intentional. The generated outputs (dark uses alpha-modified red.400 for background default/hover and red.200 for selected/foreground; light uses solid red palette values) appear consistent, so this is just the recommended sign-off.

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Adds new layer-3 semantic design tokens for issue location markers across light and dark themes. Consider designer and developer review of the new token contract to ensure intended usage.

💡 Quality: New issue-location-marker design tokens need designer+dev review

📄 design-tokens/tokens/component/dark.json:59-73 📄 design-tokens/tokens/component/light.json:59-73

This PR introduces new layer-3 semantic design tokens (issue-location-marker.colors.background.{default,hover,selected} and foreground.{default,selected}) in both light.json and dark.json. Per the design-token review policy, new tokens should be reviewed by both a designer and a developer as a checkpoint (not a blocker) to confirm the token contract, naming, and palette/alpha choices are intentional. The generated outputs (dark uses alpha-modified red.400 for background default/hover and red.200 for selected/foreground; light uses solid red palette values) appear consistent, so this is just the recommended sign-off.

🤖 Prompt for agents

Code Review: Adds new layer-3 semantic design tokens for issue location markers across light and dark themes. Consider designer and developer review of the new token contract to ensure intended usage.

1. 💡 Quality: New issue-location-marker design tokens need designer+dev review
   Files: design-tokens/tokens/component/dark.json:59-73, design-tokens/tokens/component/light.json:59-73

   This PR introduces new layer-3 semantic design tokens (`issue-location-marker.colors.background.{default,hover,selected}` and `foreground.{default,selected}`) in both light.json and dark.json. Per the design-token review policy, new tokens should be reviewed by both a designer and a developer as a checkpoint (not a blocker) to confirm the token contract, naming, and palette/alpha choices are intentional. The generated outputs (dark uses alpha-modified red.400 for background default/hover and red.200 for selected/foreground; light uses solid red palette values) appear consistent, so this is just the recommended sign-off.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube