- Ya
- 3 Julai 2026, 21:50 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 7d3e71b
The doc-03 read-router folded into the fleet's MLOS-consumer host (the only Recreate-strategy deployment - durable rebinds die under RollingUpdate), per the doc's explicit 'thin read service or folded' allowance; a greenfield MLOSOrchestrationService stays owner-gated. First production adopters of the shared-lib consumer-reliability core (doc 12 §4.2): every delivery runs through IdempotentEventProcessor - per-consumer dedup marker in the SAME tx as the side effect, RETRY->nak (capped by max-attempts), MlosDeadLetter at the cap, unparseable bodies dead-lettered immediately. - MlosDecisionRoutedConsumer **************** durable daemon-mlos-decision-routed): steward fan-out via StewardNotifier - per-org SMS through VOIP POST /api/bulktext/send (cluster X-Internal-Auth) to configmap- listed numbers; EMPTY default = record-only until the steward-assignment model lands member->contact resolution (the steward UI reads StewardTask directly). - MlosTaskResolvedConsumer **************** durable daemon-mlos-task-resolved): the auto-resume SEAM. DecisionSpine.resolve() already flips task RESOLVED + OrchestrationState GREEN synchronously (discovered in mapping - the spine-side resolve EXISTS; only the HTTP endpoint is the steward-screen unit's); the engine re-run nudge plugs in here when engine resume APIs land. 6 tests.