dsh-taskwatch

LIMITATIONS

已知限制

Development regression tests use DSH `0.1.1-rc.2`. An isolated installation of the exported bundle on DSH `0.1.5-rc.3` with Node.js `26.0.0` passed startup, sidebar state, language switching and model-settings smoke checks with zero model calls. This verifies installation and these UI paths, not live supervision or coach behavior on the newer host. Peer declarations name these two versions only. TaskWatch does not make benchmark or quality claims. On the newer host, TaskWatch uses the public authenticated Fetch-route API because the legacy channel registration fails across plugin scopes. It retains a loopback-only Host/Origin check and a 64 KiB request limit; the older host keeps its loopback RPC channel. The web client accepts only the transport announced by the server. Remote access to TaskWatch endpoints is not supported. The plugin needs a DSH installation with a web client and Node.js `>=22.23.2`. It supervises only the task explicitly bound through its consent flow. It cannot recover evidence that DSH did not expose, and coach cannot deliver to a main Agent that is no longer running.