For simctl shipped with Xcode 27.0 build 27A266a, is there a supported way to deliver launch stdout/stderr directly to an in-memory consumer without first writing raw output to a regular file, then stop the collector within a bounded time without forwarding a signal to, blocking, terminating, restarting, or changing signal policy in the launched application? Please identify the documented interface and supported OS/runtime scope, or explicitly state that this combination is unsupported.
Do stdout/stderr path options officially accept a FIFO or other nonpersistent sink, and where is that sink resolved? What open/create/truncate/blocking behavior and reader-before-writer order are guaranteed?
Which process owns the output writer after launch returns? Does simctl exit or collector detach close, transfer, or leave that writer alive?
At consumer byte/time limit, EOF, reader closure, collector failure, or backpressure, what happens to App writes and signals, including SIGPIPE/EPIPE? Is there a supported independent detach/drain mechanism that avoids App effects and indefinite background collection?
Can the supported interface guarantee no raw-output file or replay spool before the consumer, and which documented limits can the consumer enforce without affecting App lifecycle?
Please identify the supported interface, applicable tool/runtime versions, and documented lifecycle guarantees, or clarify which requirements are unsupported. This request is limited to the public tool interface contract and contains no application logs, source code, device identifiers, customer data, or diagnostic attachments.
