mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
ef089ed6ec
`code` still carried `bash-env` behind its own `isolate` realm and its own `tool-subagent-report` row — the two the other three presets had already given back to the host. It was added a layer above the fix, so the rebase carried it forward untouched, and the shipped deployment ran a preset whose sessions get no `DSH_WEB_URL` in their shell and hand every subagent a second `report` registration on the host registry. Nothing caught it. A tool-catalog assertion cannot: neither row contributes a tool. The web lane cannot: no scenario composes `code` beside another preset, which is when the second `report` throws. The presets are near-copies of one another, so "fixed in three of four" is the shape this failure takes, and it will take it again. So the invariant is checked rather than described. `verify-cordis-config` now rejects any shipped preset row that is also active on the host plane, which is the property both defects violated: a row active on both planes is mounted once per process and once per session, and what that costs depends on the row — a provider behind an `isolate` realm shadows the host's for its own consumers, so a host contributor reaches nobody; a row registering into a host singleton registers once per live session, so the second collides.