LICENSE.md: EVProfile's upstream licence is settled

EVHardware's notes call the licence of EVProfile's upstream unresolved.
Checked: malys/EVProfile is MIT, forked from SliDeeN/MG4Control and last
merged from it on 2026-08-02. MG4Control is MIT up to 2.6.5
(2026-08-05) and GPL v3 from 2.6.6 (2026-09-02), with the earlier
versions staying MIT, so the code EVProfile took is from the MIT
period. Recorded with links; not an audit of every EVHardware line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki

LICENSE.md

@@ -27,9 +27,21 @@ software. `LICENSE` names all of them; keep every line.
 
 The car app links EVHardware into its APK, so the **built app** may only be used and passed on
 non-commercially, whatever the MIT parts would allow on their own. The server, the Kubernetes
-manifests and the docs do not contain EVHardware and are plain MIT. EVHardware's own notes say
-that parts of it come from EVProfile, whose upstream licence situation it calls unresolved;
-that caveat is EVHardware's and stays with it.
+manifests and the docs do not contain EVHardware and are plain MIT.
+
+EVHardware's own notes say parts of it come from EVProfile, "itself a fork whose upstream
+licence situation is unresolved". Checked on 2026-10-18, that is settled for the code in
+question:
+
+- [malys/EVProfile](https://github.com/malys/EVProfile) is MIT. It is a fork of
+  [SliDeeN/MG4Control](https://github.com/SliDeeN/MG4Control), and its last merge from
+  MG4Control is a commit of 2026-08-02.
+- MG4Control is MIT up to and including 2.6.5 (released 2026-08-05; its licence file dates
+  from 2026-06-24) and GPL v3 or later from 2.6.6 (2026-09-02). Its `LICENCE.md` states that
+  the earlier versions stay MIT for good.
+
+So what EVProfile took from MG4Control dates from MG4Control's MIT period. This covers the
+lineage EVHardware names; it is not an audit of every line in EVHardware.
 
 ## No warranty