Update Mesh America catalogs to 1.17.1.5 USA Cascade

mesh-america/README.md

@@ -1,17 +1,18 @@
 # Mesh America provider catalogs
 
-**Legacy catalog snapshot:** these checked-in catalogs still reference
-1.17.1.1/1.17.1.2. They are not the 1.17.1.5 release inventory. Use the
-[current firmware picker](../docs/firmware_picker.md) and
-[1.17.1.5 release guide](../docs/releases/1.17.1.5.md) for current downloads.
-The commands below document maintenance of the older catalogs; publishing a
-release does not update these JSON files automatically.
+Both active provider catalogs now use **1.17.1.5 USA Cascade**, published from
+firmware commit `26303793`. They cover **94 device cards, 540 selectable
+entries, 539 unique firmware profiles, and 1,078 unique firmware files**.
+One Full Companion image is listed under two compatible device/accessory cards.
+The MQTT simulation environment is a laboratory target and is not a device
+choice. Entries without a qualified replacement in this OTA-required release
+are omitted; no download silently points to an older firmware release.
 
-Generated provider catalogs for the Keymind Cascade MeshCore release assets.
-The provider URLs stay stable when a new firmware release is published.
+## Stable provider URLs
 
-Use these catalog URLs after this directory is committed and pushed to
-`keymindCascade`:
+The `v1.16.0` text in these filenames is part of the existing provider URL,
+not the firmware version. Keep these URLs in Mesh America; they now load
+1.17.1.5 choices.
 
 ```text
 Provider name: Keymind Cascade
@@ -23,56 +24,46 @@ Provider name: Keymind Cascade Logging
 Catalog URL:   https://raw.githubusercontent.com/mikecarper/MeshCore/keymindCascade/mesh-america/keymind-cascade-logging-v1.16.0-provider.json
 ```
 
-The standard catalog currently keeps unaffected infrastructure on v1.17.1.1
-and tracks the corrective v1.17.1.2 release for every Companion role. Update
-only those Companion choices from the completed corrective matrix with:
+## Logging and former variants
 
-```text
-python3 mesh-america/update-provider-release.py \
-  --release-dir /path/to/release \
-  --artifact-version v1.17.1.2-c9652754 \
-  --main-tag v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --advanced-tag lora-ota-v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --full-tag full-profiles-v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --utility-tag kiss-v1.17.1.1-halo-keymind-cascade-759a35fc \
-  --companion-only
-```
+Both catalogs now select from the same canonical firmware set. Logging,
+power-saving, and controllable gain variants are runtime settings; selecting
+the logging provider does not itself change the device's saved settings.
+Each entry includes the appropriate commands, update methods, hardware
+requirements, and its actual GitHub release page.
 
-The updater preserves the catalog's curated device names, role choices, and
-hardware guidance; validates every referenced artifact; routes URLs to the
-correct GitHub release page; and replaces legacy portable MQTT choices with the
-matching expanded-partition unified FULL USB + Wi-Fi observer builds.
+- **Full Companion:** ESP32 uses `set usb.logging on` / `set usb.logging off`;
+  nRF52 uses `set usb.logging on reboot` / `set usb.logging off reboot` for its
+  optional second USB port. MQTT-capable Full Companions use WebConfig broker
+  cards, not infrastructure MQTT commands.
+- **Infrastructure:** `set usb.logging on` / `set usb.logging off` controls live
+  USB logs. MQTT-capable unified Full images use `set logging.output off`,
+  `usb`, `wifi`, or `both`; `set bridge.enabled on` / `off` toggles the bridge.
+- Open the [USB web console](https://flasher.meshcore.io/console) at 115200 baud.
+  Full Companion and infrastructure start in ASCII mode. Download-only board
+  entries retain their external programming requirements.
 
-The logging catalog likewise keeps unaffected roles on v1.17.1.1 while its
-Companion, Full Companion, and expanded Companion logging profiles track the
-v1.17.1.2 correction. Ordinary logging builds are for a USB-connected
-MQTT/logging host. Unified FULL ESP32 builds can instead select USB, the direct
-on-device Wi-Fi MQTT bridge, both, or neither at runtime. Update only the
-Companion choices from the same completed matrix with:
+See [feature switches by role](../docs/role_feature_switches.md), the
+[release guide](../docs/releases/1.17.1.5.md), and the
+[old-variant map](../docs/releases/1.17.1.5-variant-map.tsv).
+For nRF52 OTAFIX installations use the exact board/storage profile from
+[OTAFIX 2.4.6](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6).
 
-```text
-python3 mesh-america/update-logging-provider-release.py \
-  --release-dir /path/to/release \
-  --artifact-version v1.17.1.2-c9652754 \
-  --logging-main-tag logging-v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --logging-utility-tag logging-utility-v1.17.1.1-halo-keymind-cascade-759a35fc \
-  --full-tag full-profiles-v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --main-tag v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --advanced-tag lora-ota-v1.17.1.2-halo-keymind-cascade-c9652754 \
-  --utility-tag kiss-v1.17.1.1-halo-keymind-cascade-759a35fc \
-  --companion-only
-```
+## Catalog maintenance
 
-In Companion-only mode, each updater preserves every unaffected catalog entry,
-validates every selected replacement artifact, and adds the one-time
-power-saving migration guidance. Without `--companion-only`, the existing
-all-role behavior remains available for a future complete matrix release; the
-logging updater then validates all curated entries while allowing consolidated
-FULL USB + Wi-Fi artifacts to replace their former duplicate identities.
+The 1.17.1.5 catalog download URLs were reconciled with `release-plan.json`
+and each group's qualified `TARGET-MANIFEST.json`, then verified against the
+published GitHub assets. Preserve the exact tag for each file: Companion,
+Repeater/Room Server, Sensor, LoRa OTA, and expanded Full profiles are on
+separate release pages. Do not update these catalogs by replacing version
+strings alone.
 
-The older PowerShell generator remains available for the historical standard
-and logging source folders:
+The older `update-provider-release.py`, `update-logging-provider-release.py`,
+and PowerShell generator target earlier flat release directories and tag
+layouts. Their default routing is not sufficient for the five-page 1.17.1.5
+staging layout. Before using them for another release, reconcile canonical
+aliases, omitted targets, runtime feature descriptions, and release-group
+routing against that release's manifests.
 
-```powershell
-powershell -ExecutionPolicy Bypass -File mesh-america\generate-mesh-america-catalogs.ps1
-```
+Files ending in `provider-backup.json` are historical backups and intentionally
+retain their original versions. They are not the active provider URLs above.