Use blue landing accent from first paint

[SoundBlaster]

Summary

• What changed?
• • Changed the landing page initial CSS accent tokens from amber/orange hue to the blue hue already used by tweak defaults.
• • Removed the orange accent swatch from the hidden tweak panel and made blue the active swatch.
• Link related issue/task (if any):
• N/A

Motivation

• Why is this change needed?
• • The page briefly painted with an orange accent before JavaScript applied the blue tweak value.
• What problem, gap, or user need does it address?
• • Removes the visible orange-to-blue tint flash during landing page load.

Goals

• What should this PR achieve?
• • Blue accent from first paint, with no orange accent fallback or orange tweak option.
• What is intentionally out of scope?
• • Broader landing page redesign.

Changes

• • Updated --signal and --signal-ink initial CSS values to hue 240.
• • Removed the hue 62 swatch from the tweak panel.

Validation

• Tests added/updated for changed behavior
• Local checks passed

Commands run:

rg -n "oklch\([^\n]* 62\)|amber|data-h=\"62\"|accentHue|--signal" landing/index.html

Results:

• No amber/hue-62 accent token, comment, or swatch remains in landing/index.html.
• Commit hooks ran during commit and skipped non-applicable Python/spec checks.

Risks / Notes

• Backward compatibility impact:
• • Visual-only landing page color adjustment.
• Migration/config changes required:
• • None.
• Known limitations:
• • Browser screenshot QA was not run locally.

Checklist

• PR title clearly describes the change
• Scope is focused and minimal
• Documentation updated (or N/A)
• No secrets or sensitive data added

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.