chore(design): the suite is six apps, and the button radius is a token

EVChargePilot joins the suite, so the generated token files and DESIGN.md say six
where they said five.

The button corner overlay moves into tools/tokens/styles.xml. It existed in
EVSwipe only, inside a file the sync regenerates, so the first sync after the new
app was added deleted it and left Material3 buttons fully rounded against cards
and dialogs at 12dp. One radius across the suite has to live where the suite is
edited.

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

Author: malys

DESIGN.md

@@ -84,8 +84,8 @@ components:
 
 # Design System: EVSuite
 
-Applies to **EVProfile**, **EVTasker**, **EVABRPUploader**, **EVLauncher**,
-**EVSwipe** and the shared **EVHardware** library. This file is the normative
+Applies to **EVProfile**, **EVTasker**, **EVABRPUploader**, **EVChargePilot**,
+**EVLauncher**, **EVSwipe** and the shared **EVHardware** library. This file is the normative
 source; a copy lives at the root of every suite repository and they are kept identical.
 
 ## Overview
@@ -336,6 +336,7 @@ The launcher icon is the suite's signature and the one place it is allowed to ha
 | EVProfile | `MG⁴` lockup — white letters, red superscript 4 |
 | EVTasker | A branch: one input, a condition, two outcomes |
 | EVABRPUploader | An upward arrow leaving two broadcast arcs |
+| EVChargePilot | A battery crossed by a measured energy trace |
 | EVLauncher | A four-tile grid, one tile red |
 | EVSwipe | Two chevrons and a swipe trail |
 
@@ -351,7 +352,7 @@ legible at 48px in greyscale, it is the wrong glyph.
 `app_name` holds and what the driver sees under the icon.
 
 **Repositories, modules and directories** are `EV<Word>` — no space: `EVProfile`,
-`EVTasker`, `EVABRPUploader`, `EVLauncher`, `EVSwipe`, `EVHardware`.
+`EVTasker`, `EVABRPUploader`, `EVChargePilot`, `EVLauncher`, `EVSwipe`, `EVHardware`.
 
 **Package ids** are `com.evsuite.<lowercase>`; a family shares a segment
 (`com.evsuite.launcher`, `com.evsuite.swipe`).

app/src/main/res/values-night/colors.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- EVSuite tokens - DARK theme. See DESIGN.md section Colors.
-     Generated by tools/sync-tokens.mjs and identical in all five apps.
+     Generated by tools/sync-tokens.mjs and identical in all six apps.
 
      Dark remains the mode that matters in a vehicle: a light background filling the
      windscreen at night is glare. The suite moved to DayNight by explicit decision,

app/src/main/res/values/colors.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- EVSuite tokens - LIGHT theme. See DESIGN.md section Colors.
-     Generated by tools/sync-tokens.mjs and identical in all five apps: edit
+     Generated by tools/sync-tokens.mjs and identical in all six apps: edit
      tools/tokens/colors.light.xml, not this copy, and re-check the ratios.
 
      Contrast: this screen is read in daylight, usually through a reflection. Every

app/src/main/res/values/dimens.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- EVSuite tokens - metrics. See DESIGN.md sections Layout and Typography.
-     Generated by tools/sync-tokens.mjs and identical in all five apps. App-specific
+     Generated by tools/sync-tokens.mjs and identical in all six apps. App-specific
      dimensions are declared alongside, in dimens_app.xml, with the reason. -->
 <resources>
     <!-- Vehicle screen: 12.8", ~70 cm from the driver, used while driving, sometimes
@@ -13,7 +13,7 @@
     <dimen name="spacing_md">16dp</dimen>
     <dimen name="spacing_lg">24dp</dimen>
 
-    <!-- One radius across the whole suite: it is what makes five apps written by
+    <!-- One radius across the whole suite: it is what makes six apps written by
          different hands read as one. -->
     <dimen name="ev_corner">12dp</dimen>
 

app/src/main/res/values/styles_ev.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!-- EVSuite - component styles. See DESIGN.md section Components.
-     Generated by tools/sync-tokens.mjs: identical in all five apps, edit only
+     Generated by tools/sync-tokens.mjs: identical in all six apps, edit only
      tools/tokens/styles.xml. The application theme itself stays in values/themes.xml,
      because its name changes from one app to the next.
 
@@ -24,13 +24,15 @@
          away. This is the minimum used everywhere in the suite, including where
          Material offers something much smaller. -->
     <style name="Widget.EV.Button" parent="Widget.Material3.Button">
+        <item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
         <item name="android:minHeight">@dimen/touch_target</item>
         <item name="android:textSize">@dimen/text_body</item>
         <item name="android:paddingStart">@dimen/spacing_lg</item>
         <item name="android:paddingEnd">@dimen/spacing_lg</item>
     </style>
 
     <style name="Widget.EV.Button.Outlined" parent="Widget.Material3.Button.OutlinedButton">
+        <item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
         <item name="android:minHeight">@dimen/touch_target</item>
         <item name="android:textSize">@dimen/text_body</item>
         <item name="android:paddingStart">@dimen/spacing_lg</item>
@@ -40,6 +42,7 @@
     <!-- Dialog buttons are the smallest thing in any app and the easiest to miss:
          pulled up to the same target as the rest. -->
     <style name="Widget.EV.DialogButton" parent="Widget.Material3.Button.TextButton.Dialog">
+        <item name="shapeAppearanceOverlay">@style/ShapeAppearanceOverlay.EV.Button</item>
         <item name="android:minHeight">@dimen/touch_target</item>
         <item name="android:minWidth">140dp</item>
         <item name="android:textSize">@dimen/text_body</item>
@@ -82,4 +85,12 @@
         <item name="android:textSize">@dimen/text_secondary</item>
         <item name="android:textColor">@color/ev_text_secondary</item>
     </style>
+
+    <!-- The suite radius applied to buttons. Material3 buttons are fully rounded by
+         default, which reads as a different design language from every card and dialog
+         around them. This lived in EVSwipe only, in a generated file, so the first sync
+         deleted it — one radius across the suite has to be a token, not a local edit. -->
+    <style name="ShapeAppearanceOverlay.EV.Button" parent="">
+        <item name="cornerSize">@dimen/ev_corner</item>
+    </style>
 </resources>