Keep the line breaks in a stored FOS report

[mastacontrola]

Port of #1223.

Widening MAX_TEXT to 8192 bytes (#1218) bought less than it looked like: _sanitize() stripped every control character including the newline, so 8K of trace arrived as one unbroken line — barely more readable than the 500 characters it replaced.

Where the flattening belongs

It was there for a real reason, just not for the row. An embedded newline lets a caller forge a second entry — true of a chat notification, and of fosreports.log, whose entries are one timestamped line each and which gets read with tail. Not true of a database row.

destination	line breaks
taskLog.logText	kept
Slack / pushbullet Reason	flattened, then cut to MAX_REASON
fosreports.log	flattened

Two details that are easy to get wrong and are pinned by tests:

• \r\n and lone \r are normalised to \n first. Without that the CR is merely replaced by a space, so every line of a DOS-ended report — which is most of them — stores with trailing whitespace.
• The invalid-UTF-8 fallback is an explicit byte range, not [[:cntrl:]]. That class includes the newline, so a machine with the wrong locale would silently lose the shape of its report while every other machine kept it.

_flatten() is applied before the MAX_REASON cut, so the 500 characters are spent on text rather than on indentation.

Narrower than #1223, by fact rather than choice

That branch also had to escape the logs grid's Message column — DataTables writes cell content with innerHTML and that column had no render, which made an unauthenticated endpoint an HTML sink — and to replace the modal's .text-wrap, whose white-space: normal !important was overriding its <pre>.

This branch has no logs tab, no js/fog/task/, and no taskLog viewer at all, so there is nothing here to escape or to wrap, and no FOG_BCACHE_VER bump to make. The row is stored faithfully either way, which is what a future viewer would want to find.

Verification

The code is identical to 1.6's, where it was run against a copy of the live database — a CRLF report carrying terminal escapes and a NUL:

stored:    3 line breaks, no CR, no NUL, no ESC byte
flattened: 0 line breaks

Six mutations, all killed. Two survived the first pass, both because no test case carried a newline through the path they guarded.

Full suite: 14 passed, 0 failed.

🤖 Generated with Claude Code

https://claude.ai/code/session_013mJVe4CpK3rRbi9H5GubXd