[burinc]

Fixes #13.

run-eval called the two-argument jolt.nrepl/evaluate, which captures *out* and returns it whole. So a long eval's output reached the client only when the eval finished, and anything it printed to *err* went to the server's terminal instead. It now passes evaluate's {:out f :err f} argument (jolt-lang/jolt#1157), so each flushed chunk goes out as an out or err message while the eval runs, the way upstream's session writers and jolt's built-in eval op do.

• :jolt/min-version moves from 0.8.0 to 0.8.13, the first Jolt with that arity.
• (when (seq out) ...) stays: :out comes back empty when streaming.
• evaluate binds *capturing-thread* in both arities, so out-subscribe still doesn't echo an eval's own output a second time.
• The README says output streams and why the floor is 0.8.13.

Tests

Two new tests in session_test.clj:

• eval-output-streams-as-it-is-flushed: two printlns with a sleep between come back as two out messages, before the value.
• eval-err-output-reaches-the-client: a println to *err* comes back as an err message.

Both fail on main and pass here. jolt -M:test on Jolt v0.8.22: 80 tests, 173 assertions, 0 failures (78 and 169 on main).

Timed against a real jolt nrepl-server using this branch, evaluating (dotimes [i 3] (println "tick" i) (Thread/sleep 1000)): the ticks arrive at 1, 1031 and 2036 ms and the value at 3041 ms. On main all three ticks arrive together at about 3010 ms.