@mstar-harness/dsh 3.8.1 → 3.8.3

package/harness-skills/mstar-sdd/references/implementer-continuation-prompt.md

@@ -26,10 +26,10 @@ Dispatch:
 
     - Control harness root (briefs/reports/diffs live here): [CONTROL_ROOT]
     - Feature worktree — cwd for all source edits, branch [WORKING_BRANCH]: [FEATURE_CWD]
-    - Plan: [PLAN_FILE] — Context file: [CONTEXT_FILE]
+    - Plan: [PLAN_FILE] — PM coordination context: [CONTEXT_FILE] (never use it to select your checkout)
     - Brief: [BRIEF_FILE] — Report: [REPORT_FILE]
     - First step on resume: re-observe `pwd` and the checked-out branch — a sticky session may wake in a different cwd; on mismatch with [FEATURE_CWD]/[WORKING_BRANCH], stop and report BLOCKED — do not write.
-    - These destinations bind the handoff, not the host: a later deliberate `chdir`, absolute-path write outside [FEATURE_CWD], or host-native edit tool (apply_patch) is NOT blocked. CLI-launchable children are started via `mstar sdd exec --context [CONTEXT_FILE] -- <argv>` (starting cwd = feature worktree).
+    - These destinations bind the handoff, not the host: a later deliberate `chdir`, absolute-path write outside [FEATURE_CWD], or host-native edit tool (apply_patch) is NOT blocked. Execute allowed commands directly with the tool workdir fixed to the verified [FEATURE_CWD] / [WORKING_BRANCH]. Hosted leaves must not invoke `mstar sdd exec --context` or resolve cwd from mutable shared context; that entry is reserved for PM serialized CLI launch (file-handoffs.md § Bound child launch).
 
     ## Context not in the brief
 
@@ -39,11 +39,16 @@ Dispatch:
 
     Write your full report to: [REPORT_FILE]
 
+    ## Scope and stop
+
+    Use only the brief's owned files, relevant inputs and named checks. Do not restart global exploration, extend the task, or run local full suites without the user's explicit scoped permission. Reuse unaffected evidence. Stop once the assigned acceptance criteria are evidenced; report concrete missing context instead of over-analyzing settled work.
+
     ## Your job
 
     1. Implement exactly what this brief specifies (prior tasks are done)
-    2. Run tests; commit on Working branch
-    3. Write report file; return short summary only
+    2. Run only assigned affected unit tests or applicable scoped-check evidence; use file-handoffs.md § Verification evidence and retain unaffected prior evidence
+    3. Commit on Working branch
+    4. Write report file with actual evidence; return short summary only
 
     ## When stuck
 

package/harness-skills/mstar-sdd/references/implementer-prompt.md

@@ -26,10 +26,10 @@ Dispatch:
 
     - Control harness root (briefs/reports/diffs live here): [CONTROL_ROOT]
     - Feature worktree — cwd for all source edits, branch [WORKING_BRANCH]: [FEATURE_CWD]
-    - Plan: [PLAN_FILE] — Context file: [CONTEXT_FILE]
+    - Plan: [PLAN_FILE] — PM coordination context: [CONTEXT_FILE] (never use it to select your checkout)
     - Brief: [BRIEF_FILE] — Report: [REPORT_FILE]
     - First step: observe `pwd` and the checked-out branch; on mismatch with [FEATURE_CWD]/[WORKING_BRANCH], stop and report BLOCKED — do not write. A declared-correct assignment does not make a wrong-checkout write safe.
-    - These destinations bind the handoff, not the host: a later deliberate `chdir`, absolute-path write outside [FEATURE_CWD], or host-native edit tool (apply_patch) is NOT blocked. CLI-launchable children are started via `mstar sdd exec --context [CONTEXT_FILE] -- <argv>` (starting cwd = feature worktree).
+    - These destinations bind the handoff, not the host: a later deliberate `chdir`, absolute-path write outside [FEATURE_CWD], or host-native edit tool (apply_patch) is NOT blocked. Execute allowed commands directly with the tool workdir fixed to the verified [FEATURE_CWD] / [WORKING_BRANCH]. Hosted leaves must not invoke `mstar sdd exec --context` or resolve cwd from mutable shared context; that entry is reserved for PM serialized CLI launch (file-handoffs.md § Bound child launch).
 
     ## Context not in the brief
 
@@ -41,14 +41,18 @@ Dispatch:
 
     ## Before you begin
 
-    Ask questions now about requirements, approach, or dependencies.
+    Read the supplied brief and relevant inputs. Ask only about a concrete missing prerequisite that prevents this task; do not reopen settled choices.
+
+    ## Scope and stop
+
+    Use only the brief's owned files, relevant inputs and named checks. Do not restart global exploration, extend the task, or run local full suites without the user's explicit scoped permission. Reuse unaffected evidence. Stop once the assigned acceptance criteria are evidenced; report concrete missing context instead of over-analyzing settled work.
 
     ## Your job
 
     1. Implement exactly what the brief specifies
-    2. Run tests (TDD if brief requires)
+    2. Run only the assigned affected unit tests; for non-executable docs/policy, use real scoped-check evidence per file-handoffs.md § Verification evidence
     3. Commit on Working branch
-    4. Self-review
+    4. Self-review only the task diff and directly affected contracts
     5. Write report file; return short summary only
 
     ## When stuck
@@ -59,7 +63,8 @@ Dispatch:
 
     - Status: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
     - Implemented / attempted
-    - Tests: command, output, red/green evidence if TDD
+    - Verification: affected test files, command, actual output (red/green for executable bug fixes), OR the complete scoped-check block from file-handoffs.md for non-executable docs/policy
+    - Reused evidence: original range and reason it remains applicable
     - Files changed
     - Self-review notes
 ```

package/harness-skills/mstar-sdd/references/sticky-implementer-session.md

@@ -4,14 +4,16 @@ Reuse the **same implementer subagent** across multiple tasks in one plan when t
 
 SSOT for mode selection and host resume → this file. Per-task artifacts → **`file-handoffs.md`**.
 
+**Parallel ready tasks use fresh sessions and task-specific artifact paths inside one canonical per-plan SDD root** (`mstar-sdd` § Ready-task scheduling). Never resume the same session concurrently or share its ledger between tracks; PM alone updates shared context/progress; parallel leaves consume immutable absolute artifact paths, not shared-context helpers.
+
 ## When to use
 
 | `SDD implementer session` | Use |
 |---------------------------|-----|
 | **`fresh`** (default) | Independent tasks, module boundaries, different dev tracks, or first task on a plan |
-| **`sticky`** | Same `fullstack-dev` (or same role id), sequential tasks on one branch, strong file/context continuity (e.g. T3+T4 daemon stderr + DB reset) |
+| **`sticky`** | One sequential dependency chain on one owner track; same `fullstack-dev` (or same role id), sequential tasks on one branch, strong file/context continuity (e.g. T3+T4 daemon stderr + DB reset) |
 
-**Prefer `sticky`** on iteration Phase 2 Autonomous Execute when PM will dispatch many tasks to the same dev on one plan feature branch.
+**Prefer `sticky`** only within a sequential dependency chain with strong context continuity; independent ready tasks remain fresh and concurrent.
 
 ## Assignment fields (implement dispatch)
 

package/harness-skills/mstar-sdd/references/task-reviewer-prompt.md

@@ -12,7 +12,7 @@ Dispatch:
     <SUBAGENT-STOP> Skip PM orchestration. Read-only review.</SUBAGENT-STOP>
 
     Review one task implementation: spec compliance first, then quality.
-    Task-scoped gate — plan-level QC comes later on the whole branch.
+    Task-scoped gate — later plan QC checks changed interfaces across tasks, reusing this report.
 
     ## What was requested
 
@@ -39,8 +39,12 @@ Dispatch:
     Diff file: [DIFF_FILE]
 
     Read the diff file once. Do not re-run git. Do not mutate checkout.
-    Do not re-run full test suite — trust implementer evidence unless a
-    specific doubt needs one focused test.
+    Review only the assigned task diff and directly affected interfaces.
+    No repository-wide exploration or full test suite. Reuse relevant
+    implementer evidence; a specific doubt permits only the assigned focused
+    unit check. Non-executable docs/policy may use scoped-check evidence;
+    verify its applicability against the diff, never invent a test obligation.
+    Stop once the assigned acceptance questions are answered.
 
     ## Output
 
@@ -57,4 +61,4 @@ Dispatch:
     **Task quality:** Approved | Needs fixes
 ```
 
-Re-review after fixes covers both verdicts. PM resolves all ⚠️ items before marking task complete.
+Re-review after fixes checks both verdicts only for the raised findings and fix delta; unchanged evidence remains reusable. PM resolves all ⚠️ items before marking task complete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/dsh",
-  "version": "3.8.1",
+  "version": "3.8.3",
   "description": "Morning Star harness dsh (DeepSeek Harness) cordis function plugin — in-process engine gates (status/dispatch/lease) with hard refusal channels.",
   "keywords": [
     "dsh",
@@ -145,7 +145,7 @@
     "anser": "^2.3.5",
     "bun-types": "^1.2.17",
     "clsx": "^2.0.0",
-    "dsh-llm-fallbacks": "0.4.1",
+    "dsh-llm-fallbacks": "0.5.2",
     "immer": "^10.1.1",
     "js-yaml": "^4.1.0",
     "katex": "^0.16.47",