Add SCSS token output to build pipeline

[OJBoon]

What

Adds dist/web/_lotus-tokens.scss as a generated output from build-platforms.mjs, alongside the existing CSS, Swift, and Android files.

Why

justpark-ui currently hand-maintains _colorPrimitives.scss — a static SCSS file that duplicates the values in DESIGN.md. This means token changes require a manual update in two places, and the values have already drifted (e.g. grey-500 is different between the two files).

This generated SCSS file is the concrete step that allows parkhub/frontend to consume Lotus token values and names from a single automated source, rather than keeping them in sync by hand.

Output

_lotus-tokens.scss contains four sections, all derived directly from tokens.json:

• Primitive colors — $grey-500, $green-500 etc.
• Semantic colors — $text-primary, $action-primary etc.
• Spacing — $spacing-xs, $spacing-s etc.
• Border radius — $rounded-sm, $rounded-md etc.
• Typography — $typography-h1-font-size etc.

Variable names match DESIGN.md token names exactly — the same names used in the Swift and Android outputs — establishing shared language across all three platforms.

Migration path (next step, separate PR in parkhub/frontend)

Once @justpark/lotus is published, justpark-ui/_colors.scss swaps:

// Before
@use "colorPrimitives";

// After
@use '@justpark/lotus/dist/web/lotus-tokens' as lotus;

Test plan

• node scripts/build-platforms.mjs runs without errors
• dist/web/_lotus-tokens.scss generated with correct values
• All existing outputs (CSS, Swift, Android XML) unaffected

[gitstream-cm]

🚨 gitStream Monthly Automation Limit Reached 🚨

Your organization has exceeded the number of pull requests allowed for automation with gitStream.
Monthly PRs automated: 250/250

To continue automating your PR workflows and unlock additional features, please contact LinearB.