refactor: rename MG4Tasker to EVTasker

Rename the app and its package (com.mg4.tasker -> com.evsuite.tasker) as
part of the suite-wide move away from the vehicle-specific MG4 prefix, and
point the vendored library at the consolidated EVHardware.

The catalogue work that had only ever existed in this copy of the library
(ASK_CONFIRM and its localised strings) is now upstream in EVHardware, so
the vendored copy no longer diverges.

Note for release notes: the application ID changes, so an existing install
is not upgraded in place. The new build installs alongside the old one and
does not inherit its rules or permissions.

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

Author: malys

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -97,7 +97,7 @@ body:
         - Firmware: SWI133
         - Android Automotive: v9
         - App Version: 1.0.0
-        - MG4Control: Connected/Version X.Y.Z
+        - EVProfile: Connected/Version X.Y.Z
         - Number of rules: 5
         - Active triggers: speed, time, location
       rows: 5
@@ -173,9 +173,9 @@ body:
       required: true
 
   - type: dropdown
-    id: mg4control_bridge
+    id: evprofile_bridge
     attributes:
-      label: "MG4Control Bridge"
+      label: "EVProfile Bridge"
       description: "Connection status shown in Diagnostic tab"
       options:
         - "Connected"

.github/ISSUE_TEMPLATE/config.yml

@@ -3,6 +3,6 @@ contact_links:
   - name: Security vulnerability
     url: ../../security/advisories/new
     about: Report privately, never in a public issue.
-  - name: MG4Control (the bridge / vehicle layer)
-    url: ../../../MG4Control
+  - name: EVProfile (the bridge / vehicle layer)
+    url: ../../../EVProfile
     about: Anything about how the car is actually read or written belongs there.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -22,7 +22,7 @@ body:
       options:
         - label: I've checked existing issues/discussions and found no duplicate
           required: true
-        - label: This is an automation/rule feature (not vehicle control — that's MG4Control)
+        - label: This is an automation/rule feature (not vehicle control — that's EVProfile)
           required: true
         - label: I understand this feature must have no safety issues
           required: true

.github/ISSUE_TEMPLATE/security.yml

@@ -31,7 +31,7 @@ body:
         - label: "State corruption (rule state becomes inconsistent)"
         - label: "Condition bypass (gate condition ignored)"
         - label: "Unauthorized vehicle action (unintended profile/setting change)"
-        - label: "MG4Control bridge exploitation (improper IPC validation)"
+        - label: "EVProfile bridge exploitation (improper IPC validation)"
         - label: "Data exfiltration (personal data leaked via rule log/export)"
         - label: "Privilege escalation or permission abuse"
         - label: "Code execution vulnerability"
@@ -83,7 +83,7 @@ body:
     attributes:
       label: "Affected Versions"
       description: "Which versions are affected?"
-      placeholder: "MG4Tasker < 1.0.0 (all builds)"
+      placeholder: "EVTasker < 1.0.0 (all builds)"
     validations:
       required: true
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,4 +1,4 @@
-# Pull Request: MG4Tasker
+# Pull Request: EVTasker
 
 ## 📝 What and Why
 
@@ -25,8 +25,8 @@
 - [ ] No race conditions when two rules fire simultaneously
 - [ ] State transitions correctly (e.g., entry/exit geofence)
 
-**Vehicle Safety (if any MG4Control interaction added):**
-- [ ] All vehicle writes go through MG4Control (never direct access)
+**Vehicle Safety (if any EVProfile interaction added):**
+- [ ] All vehicle writes go through EVProfile (never direct access)
 - [ ] Speed gate enforced before any vehicle write (0 km/h only)
 - [ ] ADAS/safety-critical actions require explicit user confirmation
 - [ ] Unreadable conditions make rule **not evaluable** (fail closed, not default-fire)
@@ -51,8 +51,8 @@
 - [ ] State corruption impossible (consistent before/after rule execution)
 
 **Permissions & IPC:**
-- [ ] MG4Tasker holds no vehicle privileges (no `android.car.*`, no `sharedUserId`)
-- [ ] MG4Control bridge properly authenticated (calls validated)
+- [ ] EVTasker holds no vehicle privileges (no `android.car.*`, no `sharedUserId`)
+- [ ] EVProfile bridge properly authenticated (calls validated)
 - [ ] No new `uses-permission` (or added to allowlist with justification)
 - [ ] App does NOT self-grant permissions at runtime
 
@@ -73,7 +73,7 @@ If you'd like Claude AI to help review this PR, include this checklist:
 ```
 Please review this automation PR for:
 1. Task sequencing correctness (atomicity, no race conditions)
-2. Vehicle safety (MG4Control interaction, speed gate, ADAS handling)
+2. Vehicle safety (EVProfile interaction, speed gate, ADAS handling)
 3. Input validation (prompt injection, task injection, bounds)
 4. State machine consistency (no corruption)
 5. Offline operation verification

.github/security/permission-allowlist.txt

@@ -1,22 +1,22 @@
-# Allowed permissions for MG4Tasker.
+# Allowed permissions for EVTasker.
 # Any uses-permission in a manifest NOT listed here FAILS the CI.
 # Why: this app decides when settings get written to a car, and now writes them directly
 # (system app). Every new permission widens what a rule can reach and must be reviewed here.
 #
 # One line = one full permission name. '#' = comment.
 
 # --- Vehicle access (system app) ---
-# MG4Tasker reads and writes the vehicle directly through MG4Hardware. These car
+# EVTasker reads and writes the vehicle directly through EVHardware. These car
 # permissions are signature|privileged and are granted because the app is signed with the
-# ROM platform key and declares sharedUserId="android.uid.system" (same as MG4Control).
+# ROM platform key and declares sharedUserId="android.uid.system" (same as EVProfile).
 android.car.permission.CAR_ENERGY
 android.car.permission.CAR_POWERTRAIN
 android.car.permission.CAR_VENDOR_EXTENSION
 android.car.permission.CONTROL_CAR_CLIMATE
 android.permission.WRITE_SETTINGS
 
 # --- Own vehicle service ---
-# A persistent foreground service inits MG4Hardware and listens for ignition; it starts at
+# A persistent foreground service inits EVHardware and listens for ignition; it starts at
 # boot to catch the first ignition without the app being opened.
 android.permission.FOREGROUND_SERVICE
 android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE
@@ -37,13 +37,13 @@ android.permission.BLUETOOTH_PRIVILEGED
 # publishes the paired phone's explicitly shared phone book through ContactsContract.
 android.permission.READ_CONTACTS
 
-# Signature permission defined by MG4Tasker to reject forged OEM hard-key broadcasts.
-com.mg4.tasker.permission.RECEIVE_HARDKEY
+# Signature permission defined by EVTasker to reject forged OEM hard-key broadcasts.
+com.evsuite.tasker.permission.RECEIVE_HARDKEY
 
-# --- Optional MG4Control bridge (profile action only) ---
+# --- Optional EVProfile bridge (profile action only) ---
 # Signature-level, obtained solely because both APKs share the platform key. Used only to
-# apply an MG4Control profile when MG4Control is installed.
-com.mg4.control.permission.CONTROL_PROFILES
+# apply an EVProfile profile when EVProfile is installed.
+com.evsuite.profile.permission.CONTROL_PROFILES
 
 # --- Position ---
 # The "near a place" condition, and nothing else. Last known fix only (no live request), read

.github/workflows/release.yml

@@ -2,9 +2,9 @@ name: Release
 
 # Tag push only — publishing an APK that automates a car is a human decision.
 #
-# La signature utilise la MÊME clé plateforme que MG4Control, et ce n'est pas un détail
+# La signature utilise la MÊME clé plateforme que EVProfile, et ce n'est pas un détail
 # d'organisation : la permission signature qui protège le pont n'est accordée que si les
-# deux APK partagent la clé. Un MG4Tasker signé autrement s'installe et ne fait rien.
+# deux APK partagent la clé. Un EVTasker signé autrement s'installe et ne fait rien.
 on:
   push:
     tags:
@@ -19,7 +19,7 @@ jobs:
     name: Build and publish APK
     runs-on: ubuntu-latest
     env:
-      MG4_KEYSTORE_BASE64: ${{ secrets.MG4_KEYSTORE_BASE64 }}
+      EV_KEYSTORE_BASE64: ${{ secrets.EV_KEYSTORE_BASE64 }}
     steps:
       - uses: actions/checkout@v4
         with:
@@ -34,16 +34,16 @@ jobs:
         uses: gradle/actions/setup-gradle@v4
 
       - name: Decode platform keystore
-        if: ${{ env.MG4_KEYSTORE_BASE64 != '' }}
+        if: ${{ env.EV_KEYSTORE_BASE64 != '' }}
         run: |
           # Tolerate newlines/spaces in the secret; printf avoids a stray trailing newline.
-          printf '%s' "$MG4_KEYSTORE_BASE64" | tr -d '[:space:]' | base64 -d > "$RUNNER_TEMP/platform.keystore"
+          printf '%s' "$EV_KEYSTORE_BASE64" | tr -d '[:space:]' | base64 -d > "$RUNNER_TEMP/platform.keystore"
           # A PKCS12/JKS keystore starts with 0x30 (DER SEQUENCE); anything else is corrupt.
           if [ "$(head -c1 "$RUNNER_TEMP/platform.keystore" | od -An -tx1 | tr -d ' ')" != "30" ]; then
-            echo "::error::MG4_KEYSTORE_BASE64 is invalid. Recreate the secret with: base64 -w0 platform.keystore"
+            echo "::error::EV_KEYSTORE_BASE64 is invalid. Recreate the secret with: base64 -w0 platform.keystore"
             exit 1
           fi
-          echo "MG4_KEYSTORE=$RUNNER_TEMP/platform.keystore" >> "$GITHUB_ENV"
+          echo "EV_KEYSTORE=$RUNNER_TEMP/platform.keystore" >> "$GITHUB_ENV"
 
       - name: Run checks before publishing
         run: |
@@ -53,22 +53,22 @@ jobs:
 
       - name: Build release APK
         env:
-          MG4_KEYSTORE_PASSWORD: ${{ secrets.MG4_KEYSTORE_PASSWORD }}
-          MG4_KEY_ALIAS: ${{ secrets.MG4_KEY_ALIAS }}
-          MG4_KEY_PASSWORD: ${{ secrets.MG4_KEY_PASSWORD }}
+          EV_KEYSTORE_PASSWORD: ${{ secrets.EV_KEYSTORE_PASSWORD }}
+          EV_KEY_ALIAS: ${{ secrets.EV_KEY_ALIAS }}
+          EV_KEY_PASSWORD: ${{ secrets.EV_KEY_PASSWORD }}
         run: ./gradlew assembleStableRelease --no-daemon
 
       - name: Collect APK
         run: |
           mkdir -p dist
           # AGP 9 emits app-release.apk; rename to the published convention.
           ver=$(grep -oE 'versionName = "[^"]+"' app/build.gradle.kts | head -1 | sed -E 's/.*"([^"]+)"/\1/')
-          find app/build/outputs/apk -name "app-stable-release.apk" -exec cp {} "dist/MG4Tasker-stable-${ver}.apk" \;
+          find app/build/outputs/apk -name "app-stable-release.apk" -exec cp {} "dist/EVTasker-stable-${ver}.apk" \;
           ls -la dist/
 
       - uses: actions/upload-artifact@v4
         with:
-          name: mg4tasker-apk
+          name: evtasker-apk
           path: dist/*.apk
 
       - name: Publish GitHub Release
@@ -79,15 +79,15 @@ jobs:
           prerelease: false
           files: dist/*.apk
           body: |
-            ## MG4Tasker ${{ github.ref_name }}
+            ## EVTasker ${{ github.ref_name }}
 
             Installation manuelle. Cette application n'embarque **aucun auto-updater** et
             ne contacte aucun serveur.
 
             ### Prérequis
-            - **MG4Control installé**, signé avec la même clé plateforme. Sans lui,
-              MG4Tasker démarre mais n'a accès à rien : l'onglet Diagnostic affichera
-              « Pont MG4Control : injoignable ».
+            - **EVProfile installé**, signé avec la même clé plateforme. Sans lui,
+              EVTasker démarre mais n'a accès à rien : l'onglet Diagnostic affichera
+              « Pont EVProfile : injoignable ».
             - R8 est activé sur cette build. **Vérifiez sur véhicule** avant de vous y
               fier : le code du pont est résolu par nom au moment de la liaison.
 

.github/workflows/security.yml

@@ -73,7 +73,7 @@ jobs:
         if: always()
         run: |
           {
-            echo "# MG4Tasker security report"
+            echo "# EVTasker security report"
             echo "_$(date -u)_"
             echo
             echo "## mobsfscan"
@@ -106,7 +106,7 @@ jobs:
         if: ${{ env.NVD_API_KEY != '' }}
         uses: dependency-check/Dependency-Check_Action@main
         with:
-          project: MG4Tasker
+          project: EVTasker
           path: "."
           format: "SARIF"
           args: --nvdApiKey ${{ env.NVD_API_KEY }}

.github/workflows/unstable.yml

@@ -15,7 +15,7 @@ jobs:
     name: Build and publish unstable APK
     runs-on: ubuntu-latest
     env:
-      MG4_KEYSTORE_BASE64: ${{ secrets.MG4_KEYSTORE_BASE64 }}
+      EV_KEYSTORE_BASE64: ${{ secrets.EV_KEYSTORE_BASE64 }}
     steps:
       - uses: actions/checkout@v4
         with: { fetch-depth: 1, submodules: recursive }
@@ -29,14 +29,14 @@ jobs:
         uses: gradle/actions/setup-gradle@v4
 
       - name: Decode platform keystore
-        if: ${{ env.MG4_KEYSTORE_BASE64 != '' }}
+        if: ${{ env.EV_KEYSTORE_BASE64 != '' }}
         run: |
-          printf '%s' "$MG4_KEYSTORE_BASE64" | tr -d '[:space:]' | base64 -d > "$RUNNER_TEMP/platform.keystore"
+          printf '%s' "$EV_KEYSTORE_BASE64" | tr -d '[:space:]' | base64 -d > "$RUNNER_TEMP/platform.keystore"
           if [ "$(head -c1 "$RUNNER_TEMP/platform.keystore" | od -An -tx1 | tr -d ' ')" != "30" ]; then
-            echo "::error::MG4_KEYSTORE_BASE64 is invalid. Recreate the secret with: base64 -w0 platform.keystore"
+            echo "::error::EV_KEYSTORE_BASE64 is invalid. Recreate the secret with: base64 -w0 platform.keystore"
             exit 1
           fi
-          echo "MG4_KEYSTORE=$RUNNER_TEMP/platform.keystore" >> "$GITHUB_ENV"
+          echo "EV_KEYSTORE=$RUNNER_TEMP/platform.keystore" >> "$GITHUB_ENV"
 
       - name: Run checks
         run: |
@@ -52,9 +52,9 @@ jobs:
 
       - name: Build unstable release APK
         env:
-          MG4_KEYSTORE_PASSWORD: ${{ secrets.MG4_KEYSTORE_PASSWORD }}
-          MG4_KEY_ALIAS: ${{ secrets.MG4_KEY_ALIAS }}
-          MG4_KEY_PASSWORD: ${{ secrets.MG4_KEY_PASSWORD }}
+          EV_KEYSTORE_PASSWORD: ${{ secrets.EV_KEYSTORE_PASSWORD }}
+          EV_KEY_ALIAS: ${{ secrets.EV_KEY_ALIAS }}
+          EV_KEY_PASSWORD: ${{ secrets.EV_KEY_PASSWORD }}
         run: ./gradlew assembleUnstableRelease -PunstableBuild=${{ github.run_number }} --no-daemon
 
       - name: Collect APK
@@ -63,7 +63,7 @@ jobs:
           # The release tag is the fixed string "unstable", so the version lives in the asset
           # name: the updater matches ".apk" + "unstable" and reads the version from it.
           find app/build/outputs/apk -name "app-unstable-release.apk" \
-            -exec cp {} "dist/MG4Tasker-unstable-${{ steps.version.outputs.value }}.apk" \;
+            -exec cp {} "dist/EVTasker-unstable-${{ steps.version.outputs.value }}.apk" \;
           ls -la dist/
 
       - name: Build timestamp
@@ -99,8 +99,8 @@ jobs:
             the same certificate as the running app — otherwise it deletes the file. Install
             is still a manual tap.
 
-            Requires MG4Control installed and signed with the same platform key. The unstable
-            id is `com.mg4.tasker.unstable` (installs beside stable); it does not receive the
+            Requires EVProfile installed and signed with the same platform key. The unstable
+            id is `com.evsuite.tasker.unstable` (installs beside stable); it does not receive the
             auto ignition trigger — use "Test now" to run rules.
 
             Commit: ${{ github.sha }}

.gitmodules

@@ -1,3 +1,3 @@
-[submodule "MG4Hardware"]
-	path = MG4Hardware
-	url = https://github.com/malys/MG4Hardware
+[submodule "EVHardware"]
+	path = EVHardware
+	url = https://github.com/malys/EVHardware