tommy-orchestrator v0.1.6 — critical dispatch-delivery fix

tommy-orchestrator bumped 0.1.5 -> 0.1.6 (memnos/memnos-sdk unchanged, still 0.1.30).

Critical fix — fix(tommy): claude harness never received a real prompt, dispatch never ran (#132, #133)

tommy_dispatch could never deliver a real prompt to the claude harness: claude auto-enters
non-interactive print mode whenever its own stdout isn't a TTY (true for every dispatch), and print
mode hard-requires a prompt via stdin or a positional argument. Neither launch path
(cli.py's _launch_harness, mcp_server.py's tommy_dispatch) provided one, and neither pinned
stdin= explicitly, so the child could also inherit a live, never-closing host stdin pipe under
tommy --mcp. Net effect: no dispatched work using the claude harness — the only harness
installed on this machine — ever actually ran.

Fixed by appending a minimal trailing trigger prompt (preserving --append-system-prompt-file's
system-level framing) and pinning stdin= explicitly on every launch path. Regression-guarded by
agents/tommy/tests/test_dispatch_stdin_isolation.py, which runs unconditionally in the
tommy-tests CI job.

Upgrade ASAP if you use tommy_dispatch against the claude harness — this was a 100% failure
rate on every real dispatch.