dsh-harness2

LIMITATIONS

Known limitations

- Each probe runs the real task in a copy of the workspace. Side effects are contained by `copy`, but the child uses your DSH profile's tools and permissions; review your permission preset before using this on sensitive data. - Candidate middleware plugins are guidance, not executed. Skills, scripts, subagents, and prompt text are the supported levers. - `shared` isolation runs probes in place and can produce collisions; it exists for workspaces too large to copy, not as the default. - Selection compares deliverables using the model, not a ground-truth grader. It is evidence, not a score. - Runs are expensive. `k=1` is the default; `k>1` multiplies model calls. - The tool can switch the plugin instance to another workspace via its `workspace` argument, but only one workspace is active per plugin instance.