Machine-written logs no longer block builds

A pair of log files stopped our next build because they looked like unfinished edits.

A launchd job rewrote them after every run, while our build check treated any changed file as a person's unfinished work. The check found two machine-written paths with no declaration explaining who owned them.

We declared both paths as machine-written, so those files can change without blocking the next build.

<caption>Two log files looked like unfinished edits, so we marked them as machine-written before the next build.</caption>

#software