28b2a53c29
Every text line ExecuteR writes now reads [2026-11-16T17:53:40.653Z] - [Category] - [LEVEL] - message key=value: UTC time to the millisecond, a short category (the logging type without its namespace, or Agent/Server), TRACE..FATAL, the rendered message and the properties it did not use as key=value (correlation fields kept, enrichment noise left out). Serilog writes it through LogLineFormatter (console, file and the live views' message text); LOG_JSON keeps compact JSON. The watchdog and its MSI/removal runners write the same format, and the Rust screen host too (a tracing layer), with the agent taking each host line apart and logging it once at the host's level and category, without a second timestamp. LogLineParser reads the format back and the old ones still in device files (services' [yyyy-MM-dd HH:mm:ss.fff LVL] Source: message, the watchdog's ...Z [LVL] message, tracing's default); the watchdog's live view uses it. A warning, error or fatal that repeats (same level, SourceContext and template) is written once, then counted for 60 s; the window's end writes one line with repeated=N window=60s, a quiet window forgets it, at most 1,000 keys are tracked and disposing writes open counts. The screen host does the same. The console's log viewer shows the new level names and categories and copies lines in the file format. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>