feat(devices): add battery profiles

A battery profile describes a battery model: the charge and discharge limit
maps over temperature and SoC, the charge and discharge efficiency curves
over C-rate, the technical SoC bounds, the hard temperature cutoffs and,
for a model, its nominal capacity and power limits. EOS packages the
generic profile generic-lfp; users add their own profiles.

A battery or electric vehicle selects its profile by battery_profile and
describes how the installation differs from it in profile_adjustment
(capacity, power limits of the installation, periodic full charge). The
effective values are resolved from both at the measured operating point
(temperature, SoC, power) and shown as effective_* fields.

The GENETIC simulation uses the limits and efficiencies of the profile over
SoC, with precomputed tables as a fast path; GENETIC0 gets the values at the
operating point. Optimization parameters are always valid: a battery whose
profile is missing, unreadable or invalid uses the packaged generic-lfp
profile, and the former defaults only if that is not usable either; each is
logged as error, and an optimization run is never cancelled because of a
battery.

Additional changes
- Add a generic device profile store: user and packaged profiles, atomic
  saves, compiled profiles cached per file and checked again at most once a
  second, plain file names as profile names ('schema' is reserved). On
  Windows, a save or read that collides with the other is retried briefly.
- Add the REST API /v1/profile to list the profile kinds and to list, read
  (document and JSON schema), save and delete profiles.
- Check the hard temperature cutoffs on the exact temperature.
- Resolve inhibited charging or discharging to a power of 0, e.g. for a cold
  battery; give GENETIC0 its own discharge limit for that.
- Limit generic profiles without own power limits to the former 5000 W.
- Accept only the implemented units; current limits need the nominal
  voltage.
- Migrate legacy battery settings into the profile adjustment, keep the
  former charge power limit as discharge limit (also for a Home Assistant
  entity on it) and report dropped efficiencies as errors.
- Limit GENETIC battery discharge by the discharge power.
- Allow battery profile lookups while the configuration is created.
- Resolve a battery once per configuration dump.
- Package the bundled profiles, document battery profiles and regenerate
  the configuration and OpenAPI documentation.
- Ignore the report PDFs written by the visualization tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assisted-by: Claude Code (claude-opus-5-5)

tests/test_measurementbatterycapacity.py

@@ -4,6 +4,7 @@ import pytest_asyncio
 
 # ruff: noqa: S101
 
+import json
 from datetime import datetime, timedelta, timezone
 
 import pytest
@@ -169,9 +170,7 @@ async def database_case(config_eos):
                 "batteries": {
                     "battery": {
                         "device_id": "battery",
-                        "capacity_wh": 12000,
-                        "charging_efficiency": 1,
-                        "discharging_efficiency": 1,
+                        "profile_adjustment": {"nominal_capacity_wh": 12000},
                         "capacity_estimation": {
                             "power_key": "battery_dc",
                             "positive_power": "charging",
@@ -217,29 +216,33 @@ def test_http_reads_database_and_stores_only_explicit_estimate(database_case):
         "start_soc_percentage": 20,
         "soc_reference": "voltage_current_anchor",
     }
+    # The charging efficiency comes from the battery profile; at efficiency 1 the
+    # samples give 10000 Wh.
+    battery = database_case.devices.batteries["battery"]
+    expected_wh = 10000 * battery.effective_charging_efficiency
     response = client.post("/v1/measurement/battery-capacity/battery", json=body)
     assert response.status_code == 200, response.text
-    assert response.json()["estimated_capacity_wh"] == pytest.approx(10000)
-    battery = database_case.devices.batteries["battery"]
+    assert response.json()["estimated_capacity_wh"] == pytest.approx(expected_wh)
     assert battery.capacity_estimate is None
-    assert battery.capacity_wh == 12000
+    assert battery.effective_nominal_capacity_wh == 12000
     body["store_estimate"] = True
     response = client.post("/v1/measurement/battery-capacity/battery", json=body)
     assert response.status_code == 200, response.text
     battery = database_case.devices.batteries["battery"]
     assert battery.capacity_estimate is not None
-    assert battery.capacity_estimate.estimated_capacity_wh == pytest.approx(10000)
-    assert battery.capacity_wh == 12000
+    assert battery.capacity_estimate.estimated_capacity_wh == pytest.approx(expected_wh)
+    assert battery.effective_nominal_capacity_wh == 12000
     database_case.merge_settings_from_dict({"optimization": {"genetic": {"individuals": 100}}})
     battery = database_case.devices.batteries["battery"]
     assert battery.capacity_estimate is not None
-    assert battery.capacity_estimate.estimated_capacity_wh == pytest.approx(10000)
-    assert battery.capacity_wh == 12000
+    assert battery.capacity_estimate.estimated_capacity_wh == pytest.approx(expected_wh)
+    assert battery.effective_nominal_capacity_wh == 12000
 
-    # The estimate survives normal config serialization without becoming capacity_wh.
+    # The estimate survives normal config serialization without replacing the nominal capacity.
     data = database_case.to_config_json()
-    assert '"estimated_capacity_wh": 10000.0' in data
-    assert '"capacity_wh": 12000' in data
+    stored = json.loads(data)["devices"]["batteries"]["battery"]
+    assert stored["capacity_estimate"]["estimated_capacity_wh"] == pytest.approx(expected_wh)
+    assert stored["profile_adjustment"]["nominal_capacity_wh"] == 12000
     previous = battery.capacity_estimate
     body["start_soc_percentage"] = 100
     assert client.post("/v1/measurement/battery-capacity/battery", json=body).status_code == 422