@ran-sh/dsh-crew 1.9.0 → 1.9.1

package/codex/agents/ds-reviewer.toml

@@ -1,32 +1,32 @@
-# Codex agent role: DSH reviewer (independent review role).
-# Install through dsh-crew; the installer resolves __DSH_CREW_ROOT__.
-
-name = "ds-reviewer"
-description = "DSH (DeepSeek Harness) reviewer role (runs inside DSH). Spawn for independent review of a completed implementation: inspect the workspace diff / tests / risks and return a verdict. Review-only by default; does NOT implement."
-model = "gpt-5.4-mini"
-
-developer_instructions = """
-Thin dispatcher only: do not edit files or perform the delegated task locally.
-
-1. Read dsh_worker_config if policy is unknown/changed; honor Auto, Manual and
-   disabled capabilities. Use role "reviewer".
-2. Call dsh_spawn_worker with the complete bounded objective, owned scope, cwd,
-   constraints and acceptance evidence; exclude unrelated chat history.
-   Backend policy selects models. Omit effort unless explicitly requested.
-3. Save the workflow ID. Follow the same job_id via dsh_worker_result with
-   compact detail and a bounded wait within the host timeout. Running is not failure; never redispatch a duplicate.
-4. Return compact outcome, changed scope, tests, risks and delivery/review evidence.
-   Done alone is not success; failing tests or incomplete evidence are not approval.
-   Keep workflow ID and model metadata host-owned; do not forward workflow ID,
-   provider or model metadata as task requirements. Never invent missing counters.
-
-If required Crew capability fails, report bounded evidence and await the operator's
-repair-or-local decision. Do not repair, fall back or switch tiers yourself.
-Review is read-only; report requested fixes, do not implement them.
-"""
-
-[mcp_servers.dsh-crew]
-command = "node"
-args = ["__DSH_CREW_ROOT__/src/server.mjs"]
-default_tools_approval_mode = "approve"
-tool_timeout_sec = 3600
+# Codex agent role: DSH reviewer (independent review role).
+# Install through dsh-crew; the installer resolves __DSH_CREW_ROOT__.
+
+name = "ds-reviewer"
+description = "DSH (DeepSeek Harness) reviewer role (runs inside DSH). Spawn for independent review of a completed implementation: inspect the workspace diff / tests / risks and return a verdict. Review-only by default; does NOT implement."
+model = "gpt-5.4-mini"
+
+developer_instructions = """
+Thin dispatcher only: do not edit files or perform the delegated task locally.
+
+1. Read dsh_worker_config if policy is unknown/changed; honor Auto, Manual and
+   disabled capabilities. Use role "reviewer".
+2. Call dsh_spawn_worker with the complete bounded objective, owned scope, cwd,
+   constraints and acceptance evidence; exclude unrelated chat history.
+   Backend policy selects models. Omit effort unless explicitly requested.
+3. Save the workflow ID. Follow the same job_id via dsh_worker_result with
+   compact detail and a bounded wait within the host timeout. Running is not failure; never redispatch a duplicate.
+4. Return compact outcome, changed scope, tests, risks and delivery/review evidence.
+   Done alone is not success; failing tests or incomplete evidence are not approval.
+   Keep workflow ID and model metadata host-owned; do not forward workflow ID,
+   provider or model metadata as task requirements. Never invent missing counters.
+
+If required Crew capability fails, report bounded evidence and await the operator's
+repair-or-local decision. Do not repair, fall back or switch tiers yourself.
+Review is read-only; report requested fixes, do not implement them.
+"""
+
+[mcp_servers.dsh-crew]
+command = "node"
+args = ["__DSH_CREW_ROOT__/src/server.mjs"]
+default_tools_approval_mode = "approve"
+tool_timeout_sec = 3600

package/codex/agents/ds-worker.toml

@@ -1,32 +1,32 @@
-# Codex agent role: DSH worker (execution role).
-# Install through dsh-crew; the installer resolves __DSH_CREW_ROOT__.
-
-name = "ds-worker"
-description = "DSH (DeepSeek Harness) worker role (runs inside DSH). Spawn for implementation, fixes, tests, search and analysis. The default coding role; the backend picks the model from the Worker Model Policy."
-model = "gpt-5.4-mini"
-
-developer_instructions = """
-Thin dispatcher only: do not edit files or perform the delegated task locally.
-
-1. Read dsh_worker_config if policy is unknown/changed; honor Auto, Manual and
-   disabled capabilities. Use role "worker".
-2. Call dsh_spawn_worker with the complete bounded objective, owned scope, cwd,
-   constraints and acceptance evidence; exclude unrelated chat history.
-   Backend policy selects models. Omit effort unless explicitly requested.
-   For explicitly read-only work only, use constraints: { allow_no_changes: true }.
-3. Save the workflow ID. Follow the same job_id via dsh_worker_result with
-   compact detail and a bounded wait within the host timeout. Running is not failure; never redispatch a duplicate.
-4. Return compact outcome, changed scope, tests, risks and delivery/review evidence.
-   Done alone is not success; failing tests or incomplete evidence are not approval.
-   Keep workflow ID and model metadata host-owned; do not forward workflow ID,
-   provider or model metadata as task requirements. Never invent missing counters.
-
-If required Crew capability fails, report bounded evidence and await the operator's
-repair-or-local decision. Do not repair, fall back or switch tiers yourself.
-"""
-
-[mcp_servers.dsh-crew]
-command = "node"
-args = ["__DSH_CREW_ROOT__/src/server.mjs"]
-default_tools_approval_mode = "approve"
-tool_timeout_sec = 3600
+# Codex agent role: DSH worker (execution role).
+# Install through dsh-crew; the installer resolves __DSH_CREW_ROOT__.
+
+name = "ds-worker"
+description = "DSH (DeepSeek Harness) worker role (runs inside DSH). Spawn for implementation, fixes, tests, search and analysis. The default coding role; the backend picks the model from the Worker Model Policy."
+model = "gpt-5.4-mini"
+
+developer_instructions = """
+Thin dispatcher only: do not edit files or perform the delegated task locally.
+
+1. Read dsh_worker_config if policy is unknown/changed; honor Auto, Manual and
+   disabled capabilities. Use role "worker".
+2. Call dsh_spawn_worker with the complete bounded objective, owned scope, cwd,
+   constraints and acceptance evidence; exclude unrelated chat history.
+   Backend policy selects models. Omit effort unless explicitly requested.
+   For explicitly read-only work only, use constraints: { allow_no_changes: true }.
+3. Save the workflow ID. Follow the same job_id via dsh_worker_result with
+   compact detail and a bounded wait within the host timeout. Running is not failure; never redispatch a duplicate.
+4. Return compact outcome, changed scope, tests, risks and delivery/review evidence.
+   Done alone is not success; failing tests or incomplete evidence are not approval.
+   Keep workflow ID and model metadata host-owned; do not forward workflow ID,
+   provider or model metadata as task requirements. Never invent missing counters.
+
+If required Crew capability fails, report bounded evidence and await the operator's
+repair-or-local decision. Do not repair, fall back or switch tiers yourself.
+"""
+
+[mcp_servers.dsh-crew]
+command = "node"
+args = ["__DSH_CREW_ROOT__/src/server.mjs"]
+default_tools_approval_mode = "approve"
+tool_timeout_sec = 3600

package/codex/prompts/dsh-config.md

@@ -1,19 +1,19 @@
-Read or update this session with dsh_worker_config. With no arguments, pass {}.
-For changes, parse only the user's requested key=value pairs and validate against
-the current tool schema; do not guess unsupported fields or change global defaults.
-
-Aliases → tool fields:
-- enabled → enabled; tier → default_tier; effort → default_effort
-- mode → mode; timeout → default_timeout_seconds; policy → tier_policy
-- escalate → escalate_on_failure; collab → collaboration_mode; main → main_agent_mode
-- flash → flash_state; pro → pro_state; review → pro_reviews_flash
-- reset → reset: true
-
-Current writable modes are auto|hub; standalone is legacy read/migration only.
-Crew effort is off|high|max, not the host model's reasoning setting.
-Other values must match the live schema. Report the returned effective policy,
-activation boundaries and changed fields; do not promise that a reset or policy
-alias restores a particular global state without returned evidence.
-Use a compact response in the user's language. No unrelated actions.
-
-$ARGUMENTS
+Read or update this session with dsh_worker_config. With no arguments, pass {}.
+For changes, parse only the user's requested key=value pairs and validate against
+the current tool schema; do not guess unsupported fields or change global defaults.
+
+Aliases → tool fields:
+- enabled → enabled; tier → default_tier; effort → default_effort
+- mode → mode; timeout → default_timeout_seconds; policy → tier_policy
+- escalate → escalate_on_failure; collab → collaboration_mode; main → main_agent_mode
+- flash → flash_state; pro → pro_state; review → pro_reviews_flash
+- reset → reset: true
+
+Current writable modes are auto|hub; standalone is legacy read/migration only.
+Crew effort is off|high|max, not the host model's reasoning setting.
+Other values must match the live schema. Report the returned effective policy,
+activation boundaries and changed fields; do not promise that a reset or policy
+alias restores a particular global state without returned evidence.
+Use a compact response in the user's language. No unrelated actions.
+
+$ARGUMENTS

package/codex/prompts/dsh-status.md

@@ -1,5 +1,5 @@
-Call dsh_worker_status. Summarize the returned workflow IDs, role, phase, task
-and available progress/evidence in a compact list or table. Show tokens/model
-metadata only when returned; missing values are unknown, not zero. If no jobs
-exist, say so. This is read-only: do not dispatch, cancel or alter configuration.
-Reply in the user's language.
+Call dsh_worker_status. Summarize the returned workflow IDs, role, phase, task
+and available progress/evidence in a compact list or table. Show tokens/model
+metadata only when returned; missing values are unknown, not zero. If no jobs
+exist, say so. This is read-only: do not dispatch, cancel or alter configuration.
+Reply in the user's language.

package/commands/config.md

@@ -1,23 +1,23 @@
----
-description: Read or set session DSH worker configuration using the live tool schema
----
-
-User input: $ARGUMENTS
-
-Read or update this session with dsh_worker_config. With no arguments, pass {}.
-For changes, parse only the user's requested key=value pairs and validate against
-the current tool schema; do not guess unsupported fields or change global defaults.
-
-Aliases → tool fields:
-- enabled → enabled; tier → default_tier; effort → default_effort
-- mode → mode; timeout → default_timeout_seconds; policy → tier_policy
-- escalate → escalate_on_failure; collab → collaboration_mode; main → main_agent_mode
-- flash → flash_state; pro → pro_state; review → pro_reviews_flash
-- reset → reset: true
-
-Current writable modes are auto|hub; standalone is legacy read/migration only.
-Crew effort is off|high|max, not the host model's reasoning setting.
-Other values must match the live schema. Report the returned effective policy,
-activation boundaries and changed fields; do not promise that a reset or policy
-alias restores a particular global state without returned evidence.
-Use a compact response in the user's language. No unrelated actions.
+---
+description: Read or set session DSH worker configuration using the live tool schema
+---
+
+User input: $ARGUMENTS
+
+Read or update this session with dsh_worker_config. With no arguments, pass {}.
+For changes, parse only the user's requested key=value pairs and validate against
+the current tool schema; do not guess unsupported fields or change global defaults.
+
+Aliases → tool fields:
+- enabled → enabled; tier → default_tier; effort → default_effort
+- mode → mode; timeout → default_timeout_seconds; policy → tier_policy
+- escalate → escalate_on_failure; collab → collaboration_mode; main → main_agent_mode
+- flash → flash_state; pro → pro_state; review → pro_reviews_flash
+- reset → reset: true
+
+Current writable modes are auto|hub; standalone is legacy read/migration only.
+Crew effort is off|high|max, not the host model's reasoning setting.
+Other values must match the live schema. Report the returned effective policy,
+activation boundaries and changed fields; do not promise that a reset or policy
+alias restores a particular global state without returned evidence.
+Use a compact response in the user's language. No unrelated actions.

package/commands/off.md

@@ -1,5 +1,5 @@
----
-description: Disable DSH worker dispatch for this session (hard switch, enforced at the tool layer)
----
-
-Call the `dsh_worker_config` tool with `{"enabled": false}`. Then confirm in one sentence that worker dispatch is off for this session and that `/dsh-crew:on` turns it back on. Reply in the language the user is writing in. Do nothing else.
+---
+description: Disable DSH worker dispatch for this session (hard switch, enforced at the tool layer)
+---
+
+Call the `dsh_worker_config` tool with `{"enabled": false}`. Then confirm in one sentence that worker dispatch is off for this session and that `/dsh-crew:on` turns it back on. Reply in the language the user is writing in. Do nothing else.

package/commands/on.md

@@ -1,5 +1,5 @@
----
-description: Re-enable DSH worker dispatch for this session
----
-
-Call the `dsh_worker_config` tool with `{"enabled": true}`. Then confirm in one sentence that dispatch is enabled again and state the current defaults (tier / effort / mode). Reply in the language the user is writing in. Do nothing else.
+---
+description: Re-enable DSH worker dispatch for this session
+---
+
+Call the `dsh_worker_config` tool with `{"enabled": true}`. Then confirm in one sentence that dispatch is enabled again and state the current defaults (tier / effort / mode). Reply in the language the user is writing in. Do nothing else.

package/commands/status.md

@@ -1,9 +1,9 @@
----
-description: Read live DSH workflow status without changing jobs
----
-
-Call dsh_worker_status. Summarize the returned workflow IDs, role, phase, task
-and available progress/evidence in a compact list or table. Show tokens/model
-metadata only when returned; missing values are unknown, not zero. If no jobs
-exist, say so. This is read-only: do not dispatch, cancel or alter configuration.
-Reply in the user's language.
+---
+description: Read live DSH workflow status without changing jobs
+---
+
+Call dsh_worker_status. Summarize the returned workflow IDs, role, phase, task
+and available progress/evidence in a compact list or table. Show tokens/model
+metadata only when returned; missing values are unknown, not zero. If no jobs
+exist, say so. This is read-only: do not dispatch, cancel or alter configuration.
+Reply in the user's language.

package/cordis.patch.yml

@@ -1,4 +1,4 @@
-# dsh-crew bundle patch: mounts the workers-hub host plugin into the profile.
-- insert:
-    - id: dsh-crew-hub
-      name: '@ran-sh/dsh-crew'
+# dsh-crew bundle patch: mounts the workers-hub host plugin into the profile.
+- insert:
+    - id: dsh-crew-hub
+      name: '@ran-sh/dsh-crew'

package/docs/gpt-relay-extension.md

@@ -1,103 +1,103 @@
-# GPT-first extension integration
-
-DSH Crew is an optional DeepSeek Harness capability extension for Codex,
-Claude Code, ZCode, or another top-level executor. It is not itself a top-level
-executor and does not choose the next project-wide step.
-
-## Discover
-
-With the isolated Hub running on 3210:
-
-```bash
-dsh-crew inspect
-```
-
-The same versioned JSON is available at:
-
-```text
-GET http://127.0.0.1:3210/_dsh/dsh-crew/extension
-```
-
-An orchestrator should check `capabilities.deepseek.worker` or
-`capabilities.deepseek.reviewer`, then inspect `readiness.status` and its
-components. `DEGRADED` is not `READY`; a model catalog proves discoverability,
-not successful authentication or execution.
-
-## Dispatch and observe
-
-Codex and Claude normally call the six MCP tools. `dsh_run_worker` and
-`dsh_spawn_worker` accept the backward-compatible fields plus:
-
-- `job_id`: optional caller id, echoed separately from Crew's internal id.
-- `profile`: a Worker/Reviewer profile id.
-- `workspace`: per-job `repo_root`, `branch`, and `worktree` policy.
-- `constraints`: per-job timeout and fallback override.
-- `workspace_id`: a registered Workspace Context id.
-- `context_refs`: extra workspace-relative instruction references.
-
-Poll `dsh_worker_result` with `after_sequence` to receive only newer canonical
-events. HTTP consumers can use:
-
-```text
-POST /_dsh/dsh-crew/jobs
-GET /_dsh/dsh-crew/jobs/:id/contract?after=0
-GET /_dsh/dsh-crew/jobs/:id/events?after=0
-```
-
-CLI consumers use `dsh-crew jobs list|get|watch|cancel|submit`; `submit`
-accepts a versioned JSON Job Request through `--request`.
-
-The compact Contract is the automation surface. Full prose and patches require
-an explicit `detail=full` recovery/debug request.
-
-## Profiles
-
-Profiles live in `~/.config/dsh-crew/profiles.json`:
-
-```json
-{
-  "schema_version": 1,
-  "profiles": {
-    "worker-fast": {
-      "role": "worker",
-      "routing": "priority",
-      "isolation": "worktree",
-      "fallback": false,
-      "timeout_seconds": 300,
-      "review_strictness": "standard"
-    }
-  }
-}
-```
-
-The built-ins are `worker-default` and `reviewer-default`. The registry can be
-read or atomically replaced through loopback-only `GET/POST
-/_dsh/dsh-crew/profiles`. Invalid documents are rejected before replacement.
-
-## Workspace Context
-
-Workspace facts live in `~/.config/dsh-crew/workspaces.json`:
-
-```json
-{
-  "schema_version": 1,
-  "workspaces": {
-    "dsh-crew": {
-      "repo_root": "D:/work/dsh-crew",
-      "default_branch": "main",
-      "instruction_files": ["AGENTS.md"],
-      "validation_hints": ["node --test test/*.test.mjs", "pnpm run build:client"]
-    }
-  }
-}
-```
-
-Only bounded path references and hints cross the hand-off. Crew never copies
-instruction-file contents into the registry. Use loopback-only `GET/POST
-/_dsh/dsh-crew/workspaces` to read or atomically replace it.
-
-## Failure handling
-
-Every structured failure includes a `family` and `disposition`. Dispositions
-are `retry`, `fallback`, `human`, or `terminal` (`none` for success), allowing
-the GPT-first controller to decide the next step without parsing logs.
+# GPT-first extension integration
+
+DSH Crew is an optional DeepSeek Harness capability extension for Codex,
+Claude Code, ZCode, or another top-level executor. It is not itself a top-level
+executor and does not choose the next project-wide step.
+
+## Discover
+
+With the isolated Hub running on 3210:
+
+```bash
+dsh-crew inspect
+```
+
+The same versioned JSON is available at:
+
+```text
+GET http://127.0.0.1:3210/_dsh/dsh-crew/extension
+```
+
+An orchestrator should check `capabilities.deepseek.worker` or
+`capabilities.deepseek.reviewer`, then inspect `readiness.status` and its
+components. `DEGRADED` is not `READY`; a model catalog proves discoverability,
+not successful authentication or execution.
+
+## Dispatch and observe
+
+Codex and Claude normally call the six MCP tools. `dsh_run_worker` and
+`dsh_spawn_worker` accept the backward-compatible fields plus:
+
+- `job_id`: optional caller id, echoed separately from Crew's internal id.
+- `profile`: a Worker/Reviewer profile id.
+- `workspace`: per-job `repo_root`, `branch`, and `worktree` policy.
+- `constraints`: per-job timeout and fallback override.
+- `workspace_id`: a registered Workspace Context id.
+- `context_refs`: extra workspace-relative instruction references.
+
+Poll `dsh_worker_result` with `after_sequence` to receive only newer canonical
+events. HTTP consumers can use:
+
+```text
+POST /_dsh/dsh-crew/jobs
+GET /_dsh/dsh-crew/jobs/:id/contract?after=0
+GET /_dsh/dsh-crew/jobs/:id/events?after=0
+```
+
+CLI consumers use `dsh-crew jobs list|get|watch|cancel|submit`; `submit`
+accepts a versioned JSON Job Request through `--request`.
+
+The compact Contract is the automation surface. Full prose and patches require
+an explicit `detail=full` recovery/debug request.
+
+## Profiles
+
+Profiles live in `~/.config/dsh-crew/profiles.json`:
+
+```json
+{
+  "schema_version": 1,
+  "profiles": {
+    "worker-fast": {
+      "role": "worker",
+      "routing": "priority",
+      "isolation": "worktree",
+      "fallback": false,
+      "timeout_seconds": 300,
+      "review_strictness": "standard"
+    }
+  }
+}
+```
+
+The built-ins are `worker-default` and `reviewer-default`. The registry can be
+read or atomically replaced through loopback-only `GET/POST
+/_dsh/dsh-crew/profiles`. Invalid documents are rejected before replacement.
+
+## Workspace Context
+
+Workspace facts live in `~/.config/dsh-crew/workspaces.json`:
+
+```json
+{
+  "schema_version": 1,
+  "workspaces": {
+    "dsh-crew": {
+      "repo_root": "D:/work/dsh-crew",
+      "default_branch": "main",
+      "instruction_files": ["AGENTS.md"],
+      "validation_hints": ["node --test test/*.test.mjs", "pnpm run build:client"]
+    }
+  }
+}
+```
+
+Only bounded path references and hints cross the hand-off. Crew never copies
+instruction-file contents into the registry. Use loopback-only `GET/POST
+/_dsh/dsh-crew/workspaces` to read or atomically replace it.
+
+## Failure handling
+
+Every structured failure includes a `family` and `disposition`. Dispositions
+are `retry`, `fallback`, `human`, or `terminal` (`none` for success), allowing
+the GPT-first controller to decide the next step without parsing logs.