Run several genuinely different strategies for the same task, each in its own forked machine (real repo + uncommitted edits + seeded DB + running services), all at once, and return the finished outcome of each: diff, test result, wall-clock, cost.

Call this instead of picking one approach yourself whenever a task has more than one plausible strategy (e.g. a perf fix: add-index vs cache vs query-rewrite). Pass 2-8 approaches, each a short strategy label + one sentence of instruction.

If benchmark_cmd is given, it runs in each fork after the tests pass and should print a line SUPERPOSE_METRIC=<number> (lower is better, e.g. p95 latency in ms). The winner is then chosen by the best measured metric — so you pick the approach that is actually fastest, not just one that happens to pass. Land it with apply_winner.

Run several DIFFERENT tasks on the same repo AT ONCE — each becomes its own parallel Superpose session, all running together. Use this when you have multiple independent changes queued for one codebase and want them worked in parallel from a single call.

tasks is a list of objects, each: {task, approaches, test_cmd?, benchmark_cmd?} — the same fields as try_all. Returns every session's finished result. They appear live and concurrently on the Monitor at http://localhost:8787/ as separate branch trees.

Land one fork's diff on the local tree. First re-verifies it on a fresh clean fork (the receipt), so what lands is proven to pass somewhere other than where it was written. Returns {ok, receipt_ok}.

List superpose sessions and their forks (status, timing, cost) for review.