Function render_order_detail_text 

pub fn render_order_detail_text(
    detail: &OrderDetail,
    palette: Palette,
) -> String

order show, one field per line, then the authorization tree.

Tracks acme_proxy_admin::admin::render::render_order_detail_json member for member, omitting every field that was not recorded rather than rendering it empty — the shape render_account_detail_text and render_audit_detail_text already have. It printed six fields until now, while its own --json carried the serial, the leaf’s expiry and the revocation state, and the book documented the JSON spelling of the last two as something order show surfaced.

Four JSON members are deliberately not here:

• authorizations and finalize are URLs. The indented tree below answers the same question for a terminal, and carries the ids.
• certificate is the ACME URL, reachable only by signed POST-as-GET, so printing it is a dead string — the reason the order card refuses it too.
• certificatePem is the chain itself, several KB of it, and this is a command an operator runs to orient themselves. --json and the panel’s chain.pem download are where the bytes live; cli.md says so.