JSON output is not JSON

alan@castle:~$ /staff/alex/sush job output off-because-about-tide-detail-fruit-empty-forward
 » 913-0000019:BRM23230010 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:17,  0 users,  load average: 1.45, 1.54, 1.72
 » 913-0000019:BRM23230018 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:16,  0 users,  load average: 2.75, 3.05, 3.22
 » 913-0000019:BRM27230037 «
✅ Job stdout:
21:53:11    up 3 day(s), 22:15,  0 users,  load average: 1.13, 1.36, 1.63
 » 913-0000023:2F8JEXDK «
✅ Job stdout:
21:53:10    up 2 day(s), 46 min(s),  0 users,  load average: 1.76, 2.10, 2.35
alan@castle:~$ /staff/alex/sush job output off-because-about-tide-detail-fruit-empty-forward -j
{"target":"913-0000019:BRM23230010"}
"21:53:11    up 3 day(s), 22:17,  0 users,  load average: 1.45, 1.54, 1.72\n"
{"target":"913-0000019:BRM23230018"}
"21:53:11    up 3 day(s), 22:16,  0 users,  load average: 2.75, 3.05, 3.22\n"
{"target":"913-0000019:BRM27230037"}
"21:53:11    up 3 day(s), 22:15,  0 users,  load average: 1.13, 1.36, 1.63\n"
{"target":"913-0000023:2F8JEXDK"}
"21:53:10    up 2 day(s), 46 min(s),  0 users,  load average: 1.76, 2.10, 2.35\n"

Reproduce the issue with sush job output <job> -j and trace the command's JSON output path. The fix is done when the output is valid JSON for multiple targets, with the target and stdout represented in one parseable document.