Owl login: sad droop, peek glow, tap jump; title in card; docs refreshed

- Wrong password: owl droops its head with a slow blink (replaces the head-shake)
- Show password: the owl's eye rims and lenses glow amber
- Tap the owl and it jumps
- Title "G2Team Potential Updater" and "Sign in" centered inside the card; subtitle hides after sign-in
- Password field autofocuses
- DESIGN.md, design.json, PRODUCT.md and the design brief updated to match the page

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

PRODUCT.md

@@ -18,7 +18,7 @@ Other people involved but not the primary users: the OTS RPA team (builds and ma
 
 ## Product Purpose
 
-Charge Billed Automation produces the **Charge Billed Report**: charges by procedure, pulled from Waystar CMS-1500 claim PDFs into Excel, one workbook per account. It exists because the client keeps asking for charge and payment reports by procedure, and capturing them by hand takes three people a long time.
+The Charge Billed bot, run from the G2Team Potential Updater screen, produces the **Charge Billed Report**: charges by procedure, pulled from Waystar CMS-1500 claim PDFs into Excel, one workbook per account. It exists because the client keeps asking for charge and payment reports by procedure, and capturing them by hand takes three people a long time.
 
 Success means the ops team can start a run, see where it is, and know at the end which claims are saved, which need a person to check, and which failed, without asking the developer.
 
@@ -51,6 +51,10 @@ The bot reads the PDF's text layer directly (`src/cms1500_text.py`) instead of O
   - A screen for reviewing and fixing flagged fields: not chosen for now.
   - Whether a run can be stopped or paused from the UI.
 
+## Brand Commitments
+
+The UI is named **G2Team Potential Updater** (user's choice, 22 Oct 2026); the bot and its report keep the name Charge Billed. Mascot: the orange owl with glasses on a navy night sky.
+
 ## Evidence on Hand
 
 - Real run output from April 2026 in `Output/` (several accounts). It is PHI: never copy it into designs, mockups, demos or screenshots. Use clearly fake sample data instead.