v0.5.8

Two fixes found after 0.5.7 shipped. No behaviour change to consultations, reviews or workflows.

A killed child hands its pipes back while there is still a loop. A subprocess transport finishes only when the child has exited and every pipe has reached EOF, and the paths through _terminate are the ones where no EOF is coming: a StreamReader over its limit has paused the transport, or the readers were cancelled. The transport was left to the garbage collector, and if the loop had closed by then, __del__ raised RuntimeError: Event loop is closed where nothing could catch it. _terminate now closes it in a finally. Verified not to cost any output: run_streaming's stop path returns the same stderr it did before, byte for byte.

The console script reads its arguments and its config errors. orchestrator-mcp-server --help used to print a five-frame traceback, because main read no arguments and went straight into a server booting against the caller's config. Now -h/--help and -V/--version answer, an unrecognised argument is refused with exit 2 instead of ignored, and a ConfigError leaves as one line naming the key to set rather than our own stack.

Full diff: v0.5.7...v0.5.8