🎨 feat: Subtle APRÓ Theme and Logos

[TomasPalsson]

What

A subtle APRÓ look for LibreChat. The stock neutral palette stays. Only the accents change.

• client/src/apro.css overrides accent tokens only. It is imported after style.css.
  • Light: navy #092B3F for primary controls, switches and the focus ring. Green-deep #268465 for links and accents.
  • Dark: Aurora green #50C19B for links, accents and the focus ring. Bright Mist for inverted controls.
• High-contrast mode and user custom themes still win. High-contrast rules are more specific, and ThemeProvider sets inline styles.
• Login page shows the APRÓ wordmark, with a white variant in dark mode (AuthLayout.tsx).
• Favicons and PWA icons are the white APRÓ mark on navy. The manifest name is "APRÓ Spjallið".

⚠️ Do not merge into aproorg/0.8.8

Every tenant's image is built from aproorg/0.8.8. Merging would rebrand all customers. Build this branch only for an APRÓ tenant:

custom-image-build.yml with service=librechat, revision=feat/apro-theme, target=<apro tenant>

If we keep it, the next step is to gate it behind a build arg, so one branch can serve every tenant.

Tested locally

• Ran the production build against a local MongoDB.
• Checked the login page, chat page and Settings in light and dark mode.
• Ran the touched client tests: 7 suites and 29 tests pass.
• An adversarial review found two dark-mode contrast issues: an invisible focus ring and an unreadable purple badge. Both are fixed.

Not covered:

• The send button uses bg-text-primary. Stock text is already #212121, which is APRÓ's body-text color, so it is unchanged.
• No brand fonts. Source Sans 3 is an easy follow-up.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[TomasPalsson]

Closing: looking into a config-based approach instead.