orchestrator-present-approvallisted

# Present Approval — Orchestrator Branch Present trusted contract data exactly. Do not execute, derive, shorten, reorder, or silently expand it. ## The surface is rendered, never composed WHAT the user sees is produced Gaia-side from the sealed payload by one function -- `hooks/adapters/consent_presentation.py::render_native_text`, over that module's `VISIBLE_FIELDS` table -- and it comes out identical on every host. Its exact shape, field set, render order and absence semantics are stated in `template.md`. Show that text verbatim. Compose nothing, summarise nothing, reorder nothing, translate no label. ## Present the surface as text, then ask a minimal decision A presentation is two pieces. Print the rendered surface verbatim as console text -- the MESSAGE. Then ask a binary decision -- the QUESTION -- carrying one line of operation, the command count, and the approval id, and nothing else. `template.md` states both shapes literally, together with the four rules that make the split safe: the id on both ends, adjacency with a reprint duty, the minimum the question carries, and a binary control set with no `always`. That order is deliberate and the reason is narrow. When the surface travels *inside* a host's decision payload, whether the host's renderer displays every line of it is unverifiable from outside that host: nothing you can read back confirms the user saw the `ROLLBACK` line, or the eighth command's fingerprint, or anything past a truncation the renderer applie