/*!
 * LEGACY ANGULAR OVERRIDES — emergency / extreme cases only.
 *
 * What this is:
 *   Tiny CSS escape hatch for AngularJS UI that still loads `app.build.css`.
 *   That global sheet is frozen (compiled once from Sass, then Sass removed).
 *
 * Why it exists:
 *   Angular-only SCSS sources that fed the bundle are gone.
 *   We still get occasional visual fixes on Angular screens (~a handful of
 *   commits/month historically). Editing the frozen ~1MB `app.build.css` by
 *   hand is unsafe (no nesting, no tokens, hard review, easy regressions).
 *
 * When you MAY add rules here:
 *   - Production / staging breakage or severe UX bug on Angular-only UI
 *   - No React replacement ready in time
 *   - Fix is a few scoped selectors (prefer a feature/root class, not globals)
 *
 * When you MUST NOT touch this file:
 *   - New features, refactors, or “while I’m here” polish
 *   - Anything that can wait for a React migration of that screen
 *   - Design-system / shared token work (use FE-522 CSS variables / src modules)
 *   - Expanding this into a second stylesheet of record
 *
 * Prefer instead:
 *   1. Migrate the screen to React + `.module.css` in `/src`
 *   2. Or fix upstream if the bug is in React / vendor CSS
 *
 * If you add a rule: keep it scoped, comment the ticket, delete it when the
 * Angular surface dies.
 */