The owned launch view works in Standard mode. It removes terminal control codes from displayed text, colors errors and warnings itself, and identifies the first error and failed child process lines with local patterns. These are reading aids, not a diagnosis or readiness verdict. Parent process state and declared readiness remain separate. The original retained log bytes are not recolored or rewritten for presentation.
Press L in the terminal UI for the log. / searches the available retained history. e, w, and a select errors, warnings, or all lines; c shows two surrounding lines; f returns to the full retained view. Page Up and Page Down stop at the first and last matching lines. Use j and k to scroll within the current page and its declared readiness-check results. Left and Right reveal long lines. Check observations do not prove which process produced a node or message. The view shows its search coverage, retained source path, SHA-256 digest, and byte count.
The writer retains at most 1 MiB per launch log. Once output exceeds that bound, it keeps the first 128 KiB, a bounded window around the first identified error if that error fell outside the prefix, and the most recent output. Gap markers mark missing middle history. Search covers all retained sections. Lines outside them cannot be recovered from this log. The first error context window uses up to 20 preceding and 20 following lines within a 64 KiB bound; an exceptionally long error line is clipped in that retained context. The live summary is written to the launch record on normal close. A sudden kill before close can lose that metadata, though the retained log sections remain.
flightops evidence read RECEIPT_ID --kind lines --start 1 --end 20 prints readable text first. Add --json for the exact base64 bytes and full retrieval metadata. A receipt requires an explicitly selected source and checks its hash again at retrieval; a changed file is refused.
Jev is the optional paid TypeSafe AI service that ranks already selected evidence receipts for a question. It does not summarize launch logs, does not run in this log view, and no Jev request is needed for these controls.