fix(ui): align compact indicators and launcher styling with the design system

[kev1n77]

Summary

• Expand NumberBadge's visible background to the full 24px height.
• Align keyboard hints to 14px and status pills to 18px at default typography.
• Add opt-in StatusPill emphasis for short labels such as Ask.
• Adjust the standard launcher to a 72px minimum width, 11px monospace text, and 12px icons.
• Align light-theme badge, hint, switch, scrollbar, and launcher colors.
• Add an inline-controls composition to Design Lab and preserve legacy Appearance overrides.

Type and Areas

Type: Bug fix / UI/UX

Areas: Shared UI components, design tokens, themes, Appearance compatibility, Design Lab, generated theme assets.

Motivation / Impact

Compact controls previously had inconsistent visible sizes, spacing, and color intensity. This change improves their alignment and visual hierarchy while preserving existing product interactions and custom Appearance backgrounds.

Verification

Recorded validation for this patch:

• pnpm run design-system:check — passed, including component, token, and theme contract tests.
• pnpm run check:web — passed, including theme audits and TypeScript checks.
• Focused Appearance regression tests — 19 tests passed, including legacy payload round trips and override precedence.

Checks were not rerun while drafting this description. Native visual verification across themes, density settings, long labels, and interaction states remains pending. Remote scenarios were not exercised.

Reviewer Notes

• StatusPill emphasis is opt-in; ordinary status labels retain their semantic colors.
• The product's compact Hi-to-Hello launcher interaction remains unchanged. The 72px minimum applies to the standard public component.
• Switch dimensions and scrollbar width remain unchanged.
• Legacy Appearance overrides remain supported, with defaults for the new tokens.
• No backend protocols or persisted data shapes change.

Checklist

• This PR is focused and does not include secrets, temporary prompts, generated scratch files, or unrelated artifacts.
• Relevant verification is recorded above, or skipped checks are explained.
• User-facing strings, docs, and locales are updated where applicable.