The owner's rule of 2026-10-12: a cap only where a real constraint asks for
it, never a fixed number out of habit. Three were left that nothing asked for:
- browser_type quoted what the field kept up to 120 characters and then
"...". Those sentences exist to say how the field differs from what was
typed, and a page that reformats a long value makes the difference anywhere
in it. - A turn that failed said the exception's detail up to 200 characters. The
detail is kept because it is the only clue when the cause is real, and a
provider's JSON error names the cause past that point. - The four 503 answers of the panes' routes cut their reason at 200
characters. One function writes that answer now, whole.
Each has a test that turns red when its cap is put back.