Add `pnpm test` script and baseline Vitest coverage for core website utilities

[danielmarv]

Description

The repository already includes Vitest and related testing dependencies, but there is currently no pnpm test script defined in package.json. At the same time, the website contains core utility logic that would benefit from baseline automated test coverage. As of the current package.json, the available scripts include dev, build, start, lint, format, and format:check, but no test script, while vitest, jsdom, and Testing Library packages are already present. :contentReference[oaicite:0]{index=0}

This issue focuses on introducing a standard pnpm test entry point and adding initial Vitest coverage for core website utilities so contributors can validate behavior more reliably during development and review. :contentReference[oaicite:1]{index=1}

---

Problem

• The repository includes Vitest-related tooling but does not expose a standard pnpm test script for contributors. :contentReference[oaicite:2]{index=2}
• Core utility logic is not protected by baseline automated tests.
• Utility regressions can be harder to catch during refactors or content pipeline changes.
• Contributor workflows are less consistent without a clear test command.

---

Goal

Add a pnpm test script and establish baseline Vitest coverage for core website utilities so the repository has a clear, maintainable starting point for automated testing. :contentReference[oaicite:3]{index=3}

---

Scope of Work

• Add a test script to package.json using Vitest. :contentReference[oaicite:4]{index=4}
• Identify core website utilities that provide the best initial value for baseline coverage.
• Add initial unit tests for those utilities using the current Vitest setup.
• Ensure tests are easy to run locally with pnpm test.
• Keep the first round of coverage focused and maintainable rather than attempting full repository coverage in one change.

---

Expected Outcome

• Contributors can run tests consistently using pnpm test. :contentReference[oaicite:5]{index=5}
• Core website utilities gain baseline automated coverage.
• Future refactors to shared utility logic can be made with more confidence.
• The repository gets a stronger foundation for expanding test coverage over time.