Background process management for Pi. Start long-running commands without blocking the conversation.

docs(evals): explain which eval code is ours and which is vendored master

Anything under tests/evals/vendor is destroyed by the next sync, so the distinction matters when something breaks. Also records why the harness is patched and how to tell a real pass from a trivial one.


+112
1 changed file