@mstar-harness/dsh 3.2.5 → 3.2.6

package/harness-skills/mstar-audit/references/pr-review.md

@@ -230,7 +230,7 @@ Posting the GitHub Review is a **mandatory deliverable** of the `pr` variant —
 
 ### Report template (GitHub Review `body`)
 
-The posted review body is a three-section report. Section order fixed; omit a subsection only when its content is genuinely empty (write `none`, never delete the heading).
+The posted review body is a three-section report. Section order fixed; omit a subsection only when its content is genuinely empty (write `none`, never delete the heading). The block below shows only **fill-in slots**: a `<...>` that wraps descriptive text (`<verdict>`, `<n>`, `<finding title>`, …) is a slot — replace the whole bracket pair with real content and never render those brackets. The literal HTML tags in the template (`<details>`, `<summary>`, `<br>`) are **structural** — keep them verbatim so the collapsible block survives. The Slot rules below the template are guidance — never copy them into the posted body.
 
 **Section emoji map** — verdict: `ship it` ✅ · `needs fixes` ⚠️ · `blocked` ⛔. Finding classes: 🔴 must-fix · 🟠 should-fix · 🔵 nit · ❓ unverified.
 
@@ -246,36 +246,52 @@ The posted review body is a three-section report. Section order fixed; omit a su
 
 ## 📋 Review
 
-**What this PR does**: <2–3 sentences summarizing the diff's intent and surface — from the PR description plus your own read of the changed files, not copied marketing text.>
+**What this PR does**: <2–3 sentence summary of the diff's intent and surface>
 
 ### Findings
 
-<Ranked findings. Each finding keeps its normal format — title, evidence (`file:line`), impact, **Merge class**, **Confidence**, fix sketch — with its class emoji prefixing the title.>
+#### <class-emoji> <finding title>
+
+- **Evidence**: `file:line` — what the code does
+- **Impact**: why it matters
+- **Merge class**: must-fix | should-fix | nit
+- **Confidence**: HIGH | MEDIUM | LOW
+- **Fix sketch**: one-line suggestion
 
 ### Linked-issue AC
 
-<When § Linked-issue hygiene applied: per-criterion met / unmet / cut with one-line reasoning. Otherwise `none`.>
+<per-criterion: met / unmet / cut — one-line reasoning, or `none`>
 
 ### ✅ Verified
 
-<Concise what-checks-proved summary — the smallest runtime checks actually run and what they showed. Residual unverified leads go here as `- ❓ <lead>` lines, not into the findings table.>
+- <check or command> → <what it showed>
+- ❓ <unverified lead, if any>
 
 ### 🗑️ Considered & rejected
 
-<- <finding>: rejected because <one line>. Otherwise `none` — rejections come from the three-way attack / vet pass (§ Attack and vet), so the next reviewer does not re-chase them.>
+- **<short finding title>**: rejected — <one-line reason>
 
 ## 🛠️ Plan to fix
 
-<details><summary>展开修复计划 / Expand fix plan</summary>
+<details><summary>Expand fix plan</summary>
 <br>
 
 ```md
-<Fix plan in markdown when the audit produced one: ordered steps per finding, files touched, verification gates. Omit the block entirely only when no fix is proposed.>
+<fix plan in markdown>
 ```
 
 </details>
 ````
 
+**Slot rules (guidance — not part of the posted body):**
+
+- **What this PR does**: from the PR description plus your own read of the changed files, not copied marketing text.
+- **Findings**: ranked by impact-if-shipped (§ Verdict synthesis); every accepted finding listed, nothing truncated; repeat the `#### <class-emoji> <title>` block per finding.
+- **Linked-issue AC**: fill only when § Linked-issue hygiene applied; otherwise a bare `none`.
+- **Verified**: the smallest runtime checks actually run and what they showed; unverified leads as `❓` lines here, never in the findings table.
+- **Considered & rejected**: one bullet per rejected candidate from the three-way attack / vet pass (§ Attack and vet), so the next reviewer does not re-chase it; bare `none` when nothing was rejected.
+- **Plan to fix**: fix plan in markdown (ordered steps per finding, files touched, verification gates); follow-up plan index folds in above the ```md block (§ Folding plans); when there is no fix plan, replace the whole `<details>` block with a single line `none`.
+
 - The Verdict section replaces the old two-line tally header on GitHub: same facts (verdict token + `score_pct` as Confidence + four-class tally), structured. The chat display contract (§ Display contract) is unchanged.
 - When the fix plan itself contains fenced code blocks, open the outer fence with four backticks so the inner fences survive.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/dsh",
-  "version": "3.2.5",
+  "version": "3.2.6",
   "description": "Morning Star harness dsh (DeepSeek Harness) cordis function plugin — in-process engine gates (status/dispatch/lease) with hard refusal channels.",
   "keywords": [
     "dsh",