feat(components): ActionButton stopAlert + typography type fixes

.impeccable.md

@@ -0,0 +1,26 @@
+# FightRate Design Context
+
+## Design Context
+
+### Users
+FightRate is for combat-sport athletes and coaches during boxing, Muay Thai, jiu-jitsu, MMA, conditioning, pad work, sparring, and heavy bag sessions. The athlete starts the app before training, leaves the phone aside, and expects heart-rate monitoring to keep running while the screen is locked. During training they cannot babysit the interface.
+
+### Use Cases
+- Monitor heart rate continuously all day/session-long from a BLE chest strap such as Magene H003.
+- Mark a training window by pressing start and stop; that window is highlighted later in history while the underlying heart-rate stream continues to be stored.
+- Open saved history items and inspect the exact training window with real timestamped BPM data.
+- Extract as much useful training information as possible from captured data: max/min/avg BPM, zones, load, effort spikes, recovery patterns, density, and session notes.
+- Diagnose sensor state clearly without fake statuses or fake data.
+
+### Brand Personality
+Industrial, precise, uncompromising. The product should feel like a physical corner instrument used by a fight team: durable, technical, serious, and immediately legible under pressure.
+
+### Aesthetic Direction
+Corner Instrument. Dark, physical, rugged surfaces; high-contrast numbers; technical strips; timeline/window metaphors; no generic SaaS cards, no nested cards, no decorative fake analytics, no soft consumer wellness look. The interface should look like training equipment, not a dashboard template.
+
+### Design Principles
+1. Continuous capture is the core product. A workout is a marked window inside the continuous stream, not the whole lifetime of monitoring.
+2. Every metric must come from real timestamped samples. Empty states must explain what data is missing.
+3. Replace generic cards with instrument surfaces, rails, strips, separators, and timeline details.
+4. History must be inspectable: saved windows open into detailed, timestamped training evidence.
+5. UI copy stays PT-BR; code identifiers stay English.