1.31.3 — Fleet sync convergence and sensitive request-body controls

2026-09-29

Fleet sync now finishes promptly when nodes already run the current configuration, and host apps can opt sensitive request paths out of body and exception capture.

Fixed

• fleet sync now accepts a healthy node whose running app already loaded the current configuration, checks the sync service and pending restart for the resolved systemd unit, and gives an exact restore command for timers left held after a real failure.

Security

• The new opt-in MOJO_SENSITIVE_BODY_PATHS setting keeps request bodies, query strings and exception messages for listed path prefixes out of error events, incidents, tickets, LLM triage and logs. Nothing changes unless an app lists a path; invalid configuration fails closed.