Add a getTokenValue resolver to the design-system token-loader for component consumption

[1nonlypiece]

📌 Description

design-system/src/utils/token-loader.ts exposes loadTokens/getAllTokens,
but there's no ergonomic way to resolve a single token by a dotted path
(e.g. color.primary.light) with mode awareness. Consumers that want one value
must traverse the raw DTCG tree themselves.

This issue adds a getTokenValue(path, mode?) resolver to the loader.

🎯 Requirements and Context

• Add getTokenValue(path, mode?) to token-loader.ts resolving dotted paths
  and returning the $value (light/dark aware where applicable).
• Return undefined for unknown paths; never throw on missing tokens.
• Re-export from design-system/src/index.ts.
• Keep existing loader behavior intact.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b feature/get-token-value

2. Implement changes

• Extend design-system/src/utils/token-loader.ts; re-export from index.ts.
• Update design-system/src/__tests__/token-loader.test.ts.
• Document it in design-system/documentation/token-catalog.md.

3. Test and commit

• Run npm test in design-system.
• Cover edge cases: valid path, unknown path, light vs dark, non-color token.

Example commit message

feat: add getTokenValue resolver to design-system token-loader

✅ Guidelines

• Minimum 95% test coverage on new/changed lines.
• No regressions in token-loader tests.
• Timeframe: 96 hours.

🏷️ Labels

type-feature · type-enhancement · area-frontend · MAYBE REWARDED · GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the Disciplr contributor Discord to coordinate, ask questions, and get unblocked fast: https://discord.gg/xvNAvMJf
• Please introduce yourself in the channel before you start so we can avoid duplicate work, pair you with a reviewer, and get your PR merged quickly.
• Maintainers actively triage this channel and aim for fast, clear, respectful reviews — reach out any time you're blocked.

[N-i-xx]

@N-i-xx has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Dear maintainer
Please assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @N-i-xx to this issue.

[grantfox-oss]

🦊 GrantFox — @N-i-xx has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #310)
2. Your PR will be reviewed by the Disciplr-Org maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @N-i-xx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @N-i-xx: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊