# Delta for Frontend Admin Visual Language

## ADDED Requirements

### Requirement: Admin Phase 2 Visual Alignment

The Admin frontend SHALL adopt OmniOil dark/orange visual language after the Console phase, focusing on shell, login/auth surfaces, and primitive UI usage while preserving existing Admin workflows.

#### Scenario: Admin shell aligns with OmniOil brand

- GIVEN an authenticated Admin user
- WHEN the Admin shell renders
- THEN it SHALL use near-black backgrounds, dark cards, subtle light borders, and orange accents
- AND existing navigation, routing, and permissions behavior SHALL remain unchanged

#### Scenario: Admin auth surface preserves behavior

- GIVEN an unauthenticated Admin user
- WHEN the Admin login or auth surface renders
- THEN it SHALL present the OmniOil dark/orange visual language
- AND authentication fields, errors, and submission behavior SHALL remain unchanged

### Requirement: Admin Local Token Consistency

Admin styling SHALL use local app tokens or local style conventions for repeated colors, surfaces, borders, and accents without depending on a shared package.

#### Scenario: Repeated Admin styling uses local tokens

- GIVEN multiple Admin screens use dark surfaces and orange actions
- WHEN their styles are reviewed
- THEN repeated visual values SHALL be represented through local Admin tokens or local reusable styles
- AND no cross-app design-system package SHALL be required

#### Scenario: Hardcoded divergent colors are audited

- GIVEN an Admin screen contains legacy blue, teal, or incompatible accent colors
- WHEN the Phase 2 visual pass reaches that surface
- THEN those colors SHALL be replaced or explicitly justified as semantic exceptions
- AND semantic status colors MAY remain when they communicate state

### Requirement: Admin Phase Boundary

Admin visual alignment SHALL be reviewable independently from PWA visual alignment.

#### Scenario: Admin phase does not require PWA changes

- GIVEN Console has been aligned and Admin is being aligned
- WHEN Phase 2 is reviewed
- THEN PWA changes SHALL NOT be required for Admin acceptance
- AND Admin SHALL remain independently buildable and testable