dsh-file-explorer-kit

LIMITATIONS

已知限制

- Target dsh: `@deepseek-ai/dsh` v0.1.1-rc.2 (`dsh web`, profile `web`). The browser face targets that release's `conversation.view` view-ring contract (tabs are auto-listed from the entries; the body renders only the active view per `only: <active id>`) and `ctx.workspaces.openPath`; re-validate against the upstream contract on version upgrades. - The "Files" tab only appears **inside a session** (the no-session hero state has no tabs) — an inherent boundary of session-level views. - Styling is inline (light theme) and does not follow the system theme — the same tradeoff as dsh-workspace-kit v1. - Security boundary: the endpoints are read-only; `/dsh-files` keeps the official trust posture (it is not an authentication layer). If you deploy behind a container/proxy where the Host header is not loopback, keep the dsh web service on a loopback binding or extend the `trusted()` allowlist in `src/host/index.ts`. - Integration with the LoopDSH platform's per-user instances is the same as for dsh-workspace-kit: see "Option A: idempotent pre-provisioning at harness startup" in `docs/plugins/loopdsh-integration.md` inside the LoopDSH repository.