chore: remove real identifiers from examples repo-wide

The screenshot fixtures were built by mirroring a live device to get the
JSON field names right, which is how real values got into examples in the
first place. A repo-wide sweep found more of the same predating that work:
the rig's inverter model name in a tigo_web_server.cpp comment, two P4 test
board configs, a curl example in the web-server guide, and a CHANGELOG
example. Also removed the leaked CCA MAC from a comment in the new privacy
test - documenting the leak by quoting it put it straight back in the repo.

Only the boards/test-p4-*.yaml change has any effect: renaming those
inverters changes the generated entity IDs for anyone building from those
files. They are reference configs, not a deployed one.

Claude-Session: https://claude.ai/code/session_01RgSnMCa3JQigphGnPbazdw

Author: RAR

CHANGELOG.md

@@ -159,7 +159,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Panel modal showed "—" for Current in** — the `/api/devices` JSON field is named `"current"` (filled from `device.current_in`), not `"current_in"`; modal now reads the correct key. Duty cycle is already a percent in the JSON, so the suffix is now `%`.
 - **Panel modal card was transparent** because the CSS used `var(--bg-1)`, which isn't defined (`:root` defines `--bg`, `--bg-2`, `--bg-3`, `--bg-4`). Switched to `--bg-2`.
 - **Panel modal showed prior panel's history** during the in-flight fetch when reopening on a different panel — chart polylines now reset to empty + "…" placeholder on every open/range-change.
-- **YAML generator emitted redundant `tigo_mppt_mppt_4`-style IDs** when the user's label already started with the type tag. Generator now skips the type prefix when the slug already begins with it (so "MPPT 4" → `tigo_mppt_4`, "FlexBoss A" → `tigo_inverter_flexboss_a`).
+- **YAML generator emitted redundant `tigo_mppt_mppt_4`-style IDs** when the user's label already started with the type tag. Generator now skips the type prefix when the slug already begins with it (so "MPPT 4" → `tigo_mppt_4`, "South Roof" → `tigo_inverter_south_roof`).
 - **History wiped on every reboot** when using esp_tsdb (only with `feat/handle-based-api` fork). Root cause: `tsdb_open` used `stat()` to detect file existence, but joltwallet's `esp_littlefs` returns `ENOENT` from `stat()` for files that `fopen("rb")` immediately reads bytes back from. Every boot took the create-new path and `fopen("w+b")` truncated the existing file. Fix in the upstream PR (`zakery292/esp_tsdb#1`): try `fopen(..., "r+b")` first; fall through to create-new only on failure. Slot map (panel_map.json) was unaffected because it uses `open(wb)+write+close` per save, which never hits the bad code path.
 - **Nodes view crashed at active-sockets** during R5 diag-view rendering (fixed in `2f14ad8`).
 - **Persistence cleanup on shutdown**: `TigoMonitorComponent::on_shutdown` now drains the TSDB writer queue (best-effort, 800 ms cap), `tsdb_close_h`s every open handle, and unmounts LittleFS so the journal commits cleanly before `esp_restart`.

boards/test-p4-ble-tigomonitor.yaml

@@ -141,11 +141,11 @@ tigo_monitor:
   sync_cca_on_startup: false
   reset_at_midnight: true
   inverters:
-    - name: "FlexBoss A"
+    - name: "Inverter 1"
       mppts:
         - "MPPT 1"
         - "MPPT 2"
-    - name: "FlexBoss B"
+    - name: "Inverter 2"
       mppts:
         - "MPPT 3"
         - "MPPT 4"

boards/test-p4-tigomonitor.yaml

@@ -142,11 +142,11 @@ tigo_monitor:
   sync_cca_on_startup: false
   reset_at_midnight: true
   inverters:
-    - name: "FlexBoss A"
+    - name: "Inverter 1"
       mppts:
         - "MPPT 1"
         - "MPPT 2"
-    - name: "FlexBoss B"
+    - name: "Inverter 2"
       mppts:
         - "MPPT 3"
         - "MPPT 4"

components/tigo_server/tigo_web_server.cpp

@@ -2929,7 +2929,7 @@ void TigoWebServer::build_yaml_json(PSRAMString& json, const std::set<std::strin
 
   // Build "tigo_<type>_<slug>", but skip the <type> tag when the slug
   // already starts with it (e.g. label "MPPT 4" -> "tigo_mppt_4", not
-  // "tigo_mppt_mppt_4"). Inverter "FlexBoss A" stays "tigo_inverter_flexboss_a".
+  // "tigo_mppt_mppt_4"). Inverter "South Roof" stays "tigo_inverter_south_roof".
   auto make_id = [&slugify](const char *type_tag, const std::string &label) -> std::string {
     std::string slug = slugify(label);
     std::string tag(type_tag);

site/src/content/docs/guides/web-server.md

@@ -221,7 +221,7 @@ Renaming an inverter:
 ```bash
 curl -X POST http://192.168.1.100/api/inverters/rename \
   -H 'Content-Type: application/json' \
-  -d '{"name":"FlexBoss A","display_name":"South Roof"}'
+  -d '{"name":"Inverter 1","display_name":"South Roof"}'
 ```
 
 Setting per-panel nameplate watts on a string:

site/test/fixtures-privacy.test.mjs

@@ -37,9 +37,10 @@ test('MACs are inside the RFC 7042 documentation range', () => {
 
 test('bare-hex identifiers use the reserved fake-serial shape', () => {
   // Prefix alone is NOT sufficient. The CCA MAC that leaked into the first
-  // draft of these fixtures was 04C05BA1A94A — it starts with the public Tigo
-  // OUI, so an OUI-only check waves real hardware straight through. Fake
-  // serials must also carry the 0000 block, which no real unit has.
+  // draft of these fixtures began with the public Tigo OUI itself, so an
+  // OUI-only check waves real hardware straight through. Fake serials must
+  // also carry the 0000 block, which no real unit has. (Deliberately not
+  // quoting the leaked value here — that would put it back in the repo.)
   // Scan hex runs inside quoted values only. A bare /[0-9A-F]{10,}/ over the
   // whole blob also matches unquoted epoch timestamps — 1771136965 is ten
   // characters all of which are valid hex digits.