@ran-sh/dsh-crew 0.3.6 → 0.3.8

package/README.md

@@ -1,180 +1,94 @@
-<p align="center">
-  <img src="./docs/images/dsh-crew-logo.png" alt="DSH Crew" width="120" />
-</p>
-
-<h1 align="center">DSH Crew</h1>
-
-<p align="center">
-  <strong>Use Codex Desktop or Claude Code as the orchestrator, and dispatch coding work to isolated DeepSeek Harness workers and reviewers.</strong>
-</p>
-
-<p align="center">
-  <a href="./README.md"><b>English</b></a> · <a href="./README.zh.md">简体中文</a>
-</p>
-
-## What it does
-
-DSH Crew adds a small orchestration layer between your coding host and DeepSeek Harness:
-
-- **worker** — implements, fixes, tests, searches, and analyzes;
-- **reviewer** — independently reviews the worker result and returns a verdict;
-- **model policy** — resolves provider/model priorities per role and can escalate on evidence;
-- **isolated execution** — coding workers run in temporary git worktrees by default;
-- **live jobs** — Hub sessions expose progress, results, cancellation, routing trace, and readiness data.
-
-```text
-Codex Desktop / Claude Code
-            │
-            ▼
-         DSH Crew
-       ┌────┴────┐
-       │         │
-    worker    reviewer
-       │         │
-       └────┬────┘
-            ▼
-     DeepSeek Harness
-```
-
-## Install
-
-Prerequisites: **Node.js** (Git is needed only for coding-worker isolation).
-
-Recommended: install a stable, package-manager-installed launcher and manage DSH Crew with it:
-
-```bash
-npm install -g @ran-sh/dsh-crew@latest
-dsh-crew install
-```
-
-Manage the installation later with the same CLI:
-
-```bash
-dsh-crew status
-dsh-crew update
-dsh-crew uninstall        # add --purge to also remove config/backups
-```
-
-The globally installed package is only the launcher/manager. The actual Crew runtime/plugin payload is persisted under Crew-owned state (`~/.config/dsh-crew/app`) before Harness registration, so runtime behavior never depends on npm cache paths.
-
-> Known compatibility issue: transient `npx @ran-sh/dsh-crew …` execution is currently unreliable on some npm versions (npm/cli#9870: the npx cache bin is not put on the spawned command PATH). Until that upstream fix reaches your npm, use the global-launcher flow above instead.
-
-An update of the managed payload does not require a clone or rebuild. When the launcher and payload versions match, `dsh-crew update` resolves the newest permitted package from your configured npm registry (or an explicit `--candidate <path>` override). When the running launcher is newer, its validated package payload is used first to converge the older managed payload. Every path stages and validates before switching. If the managed payload is newer than the launcher, it is never downgraded and the CLI prints the exact launcher-refresh command.
-
-> Migration boundary for legacy `<= 0.3.3`: those immutable launchers cannot discover newer registry versions, so their old update behavior cannot be retroactively fixed. Refresh the launcher first, then converge the managed payload—no source checkout is required:
->
-> ```bash
-> npm install -g @ran-sh/dsh-crew@latest
-> dsh-crew update
-> ```
-
-Developer / source setup (alternative path):
-
-```bash
-git clone https://github.com/Ran-sh/dsh-crew.git
-cd dsh-crew
-node scripts/setup.mjs install
-```
-
-Windows source checkouts can use:
-
-```bat
-install.cmd
-```
-
-DSH Crew uses its own Harness home and profile:
-
-```text
-~/.config/dsh-crew/harness
-profile: dsh-crew
-```
-
-Supported Crew tooling does **not** modify the normal `~/.dsh` home, the official `web` profile, or official DSH credential stores.
-
-## Quick start
-
-1. Start DeepSeek Harness normally.
-2. Open **Settings → DSH Crew**.
-3. Install the Codex integration; Claude Code integration is optional.
-4. Refresh Harness models and choose role priorities if needed.
-5. Restart the coding host after integration changes.
-
-Then ask the host naturally, for example:
-
-```text
-Use ds-worker to implement this change.
-Use ds-reviewer to review the implementation.
-```
-
-## Roles and routing
-
-| Role | Purpose |
-|---|---|
-| `worker` | Implementation, fixes, tests, search, analysis |
-| `reviewer` | Independent review and verdict |
-
-Each role resolves its own ordered provider/model candidates. Explicit user priorities remain authoritative; automatic escalation only happens when the workflow has evidence that stronger execution or review is needed.
-
-Legacy `ds-flash` / `ds-pro` aliases remain for compatibility, but new prompts should use `ds-worker` / `ds-reviewer`.
-
-## Isolation
-
-`execution.isolation` defaults to `worktree`.
-
-A coding worker receives a temporary git worktree at the requested revision, so parallel workers do not write into the same working tree. The worker returns an auditable change candidate for the orchestrator to accept, reject, or revise; Crew does not silently merge changes into your primary workspace.
-
-## Update / uninstall
-
-The managed Crew payload updates in place (config, credentials, and backups are preserved; the candidate is staged and validated before switching):
-
-```bash
-dsh-crew update
-```
-
-Uninstall the managed payload and integrations:
-
-```bash
-dsh-crew uninstall
-```
-
-Update a source install instead with:
-
-```bash
-git pull --ff-only
-node scripts/setup.mjs install
-```
-
-Uninstall Crew from a source checkout:
-
-```bash
-node scripts/setup.mjs uninstall
-```
-
-Windows shortcuts:
-
-```bat
-install.cmd
-uninstall.cmd
-```
-
-Crew config and backups under `~/.config/dsh-crew` are preserved unless you remove them yourself.
-
-## Development
-
-```bash
-pnpm install --frozen-lockfile
-node --test test/*.test.mjs
-pnpm run build:client
-pnpm run verify:npm-install
-```
-
-Useful docs:
-
-- [Architecture roadmap](./docs/v0.3-architecture-roadmap.md)
-- [Readiness matrix](./docs/readiness-matrix.md)
-- [Agent Workflow](./docs/agent-workflow.md)
-- [Changelog](./CHANGELOG.md)
-
-## License
-
-MIT
+<p align="center"><img src="./docs/images/dsh-crew-logo.png" alt="DSH Crew" width="120" /></p>
+
+<h1 align="center">DSH Crew</h1>
+
+<p align="center"><strong>Workers and reviewers for Codex Desktop and Claude Code, shown inside the official DeepSeek Harness UI.</strong></p>
+
+<p align="center"><a href="./README.md"><b>English</b></a> · <a href="./README.zh.md">简体中文</a></p>
+
+## Quick start
+
+Requirements: Node.js; Git is required for worktree isolation.
+
+```bash
+npm install -g @ran-sh/dsh-crew@latest
+dsh-crew install
+dsh-crew integrate
+```
+
+Start the official Harness on port 3080 as usual:
+
+```bash
+npx -y @deepseek-ai/dsh web --host 127.0.0.1 --port 3080
+```
+
+Open <http://127.0.0.1:3080> and go to **Settings → DSH Crew**. The official 3080 process displays the UI; Crew work stays in an isolated backend on `127.0.0.1:3210`, which the bridge starts in the background when needed.
+
+## Configure
+
+1. Click **Refresh Harness Models**.
+2. Set the model order for Worker and Reviewer.
+3. Keep Worker on **Auto** for automatic delegation.
+4. Reviewer defaults to **Manual**; enable automatic review only when wanted.
+5. Keep **worktree** isolation for coding tasks.
+
+With one configured model, both roles simply use that model. With several models, each role tries its ordered list and falls back to the next available model. Settings modules are collapsible and show their effective state while closed.
+
+## Use from Codex or Claude
+
+```text
+Use ds-worker to implement this change and run the tests.
+Use ds-reviewer to review the result.
+```
+
+Legacy `ds-flash` and `ds-pro` aliases remain compatible.
+
+## Common commands
+
+```bash
+dsh-crew status       # installation and integration health
+dsh-crew update       # update and repair enabled integrations
+dsh-crew integrate    # connect official 3080 UI to isolated 3210 Crew
+dsh-crew detach       # remove only the 3080 bridge
+dsh-crew uninstall    # remove Crew, keep config and backups
+```
+
+`dsh-crew uninstall --purge` also removes Crew configuration and backups.
+
+If you prefer a completely separate UI, run `dsh-crew detach`, then start the isolated profile directly:
+
+```powershell
+$env:DSH_HOME = "$HOME\.config\dsh-crew\harness"
+& "$env:DSH_HOME\runtime\node_modules\.bin\dsh.cmd" --profile dsh-crew --host 127.0.0.1 --port 3210
+```
+
+The bridge backs up the official `web` profile before its first change and registers only a lightweight proxy/client package. The full Crew Hub, model execution, config, and credentials stay under:
+
+```text
+~/.config/dsh-crew/harness
+profile: dsh-crew
+```
+
+For launchers at `<= 0.3.3`, first refresh the launcher because the old updater cannot discover newer releases and cannot be retroactively fixed:
+
+```bash
+npm install -g @ran-sh/dsh-crew@latest
+dsh-crew update
+```
+
+## Source development
+
+```bash
+git clone https://github.com/Ran-sh/dsh-crew.git
+cd dsh-crew
+node scripts/setup.mjs install
+node --test test/*.test.mjs
+pnpm run build:client
+node scripts/setup.mjs uninstall
+```
+
+More detail: [Changelog](./CHANGELOG.md) · [Readiness matrix](./docs/readiness-matrix.md)
+
+## License
+
+MIT