stabilize esp8266 mqtt path

Author: ZeroBitsTech

CHANGELOG.md

@@ -12,6 +12,7 @@
 - Added optional offline queue gating in `ZeroHttpPump` and `ZeroMqttPump` so constrained boards can refuse backlog when link or transport is down.
 - Reduced scheduler contention in the ESP8266 preset by staggering network task start offsets and lowering idle network task cadence.
 - Updated the ESP8266 preset to recommend `kIdleYield` instead of `kIdleSleep`, which materially reduces live timing jitter in the official Wemos validation node.
+- Tuned the ESP8266 preset toward MQTT-first delivery with lighter MQTT dispatch pressure, producing a repeatable Wemos run where MQTT delivery stays live while timing remains at or better than baseline.
 - Added generic compare workloads for `EnvMonitor`, `TelemetryGateway`, and `IndustrialLoop`.
 - Added repeatable ESP32 compare runners plus a cross-target workload compile matrix.
 - Improved telemetry gateway tuning so module throughput rises without queue buildup.

README.md

@@ -117,7 +117,7 @@ Current target maturity:
 Recommended board-specific path:
 
 - **ESP32:** use the default network module configs first, then validate against your real endpoint.
-- **ESP8266 / Wemos:** start with `ZeroNetProfileEsp8266`. It is a BETA, MQTT-first constrained preset that disables periodic HTTP dispatch by default, prevents offline queue buildup, staggers slower network task cadence, and recommends a lighter idle strategy so constrained boards do not need heavy manual tuning just to stay responsive.
+- **ESP8266 / Wemos:** start with `ZeroNetProfileEsp8266`. It is a constrained MQTT-first preset that disables periodic HTTP dispatch by default, prevents offline queue buildup, staggers lighter network task cadence, and recommends a lighter idle strategy. In current validation it is the preferred path for Wemos MQTT delivery, while HTTP remains degraded/off by default.
 
 Current best module tradeoff reference (ESP32, `LEAN_NET`, manual pattern vs module pattern):
 

docs/wiki/Beta-Modules.md

@@ -18,7 +18,7 @@ They are already useful and validated on desktop plus ESP32 smoke tests, but the
 
 Recommended default:
 
-- For constrained ESP8266 boards, start with `ZeroNetProfileEsp8266`. It is a BETA, MQTT-first constrained preset that keeps HTTP degraded by default, rejects offline queueing, and uses a lighter recommended idle strategy plus staggered network task starts so the board stays more predictable without hand-tuning every interval.
+- For constrained ESP8266 boards, start with `ZeroNetProfileEsp8266`. It is the recommended MQTT-first constrained preset: HTTP stays degraded/off by default, offline queueing is rejected, and the preset uses a lighter recommended idle strategy plus staggered network task starts so the board stays more predictable without hand-tuning every interval.
 
 ## What BETA Means Here
 

src/modules/net/ZeroNetProfileEsp8266.h

@@ -16,7 +16,7 @@ struct ZeroNetProfileEsp8266 {
   static const unsigned long kSampleTaskIntervalMs = 100UL;
   static const unsigned long kWiFiTaskIntervalMs = 250UL;
   static const unsigned long kHttpTaskIntervalMs = 250UL;
-  static const unsigned long kMqttTaskIntervalMs = 500UL;
+  static const unsigned long kMqttTaskIntervalMs = 250UL;
   static const unsigned long kDispatchTaskIntervalMs = 250UL;
   static const unsigned long kReportTaskIntervalMs = 250UL;
 
@@ -54,11 +54,11 @@ struct ZeroNetProfileEsp8266 {
 
   static ZeroMqttPump::Config mqttConfig() {
     ZeroMqttPump::Config config;
-    config.pollIntervalMs = 150UL;
+    config.pollIntervalMs = 100UL;
     config.retryBaseMs = 600UL;
     config.retryMaxMs = 3000UL;
     config.retryJitterMs = 180UL;
-    config.idleLoopIntervalMs = 300UL;
+    config.idleLoopIntervalMs = 150UL;
     config.maxRetries = 2;
     config.queueWhenTransportDown = false;
     return config;