@mstar-harness/opencode 3.2.4 → 3.2.5

package/CHANGELOG.md

@@ -6,6 +6,16 @@ The monorepo root [CHANGELOG.md](../../CHANGELOG.md) summarizes cross-surface re
 
 ## [Unreleased]
 
+## [3.2.5] - 2026-08-24
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- **PR deep-review lists every finding by default**: the `[full]` flag is removed from `/pr-deep-review` — complete findings (all merge classes, nits included) are now always listed in the chat output and GitHub Review; nothing is truncated. README command signature updated.
+
+- Version alignment with harness **3.2.5** (no OpenCode package API change).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **3.2.5**.
+
 ## [3.2.4] - 2026-08-24
 
 ### Bundled harness skills (`harness-skills/` at publish)

package/harness-commands/pr-deep-review.md

@@ -2,7 +2,7 @@
 name: pr-deep-review
 description: Use when asked to deeply review a pull request, branch, or diff before merge — deciding whether a change is safe to ship with evidence-backed findings, rather than a shallow "looks good" pass. Produces a `ship it` / `needs fixes` / `blocked` verdict. Also for a batch of sibling PRs. Do not use for self-checking a change you just authored.
 agent: project-manager
-input: "[pr|branch|scope] [full]"
+input: "[pr|branch|scope]"
 ---
 
 # Deep PR Review

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

@@ -87,7 +87,7 @@ Then open cited code yourself and dispose by-design / mis-attributed / duplicate
 ## Verdict synthesis
 
 - Order findings by impact-if-shipped; no padding, no invented requirements, no style grading.
-- List **every** `must-fix` and `should-fix` finding — the default top 1–3 cut (unless `full`) applies to nits only, and truncated nits are summarized in the display line (§ Output shape / Display contract).
+- List **every** accepted finding — `must-fix`, `should-fix`, and nits alike; nothing is truncated.
 - The verdict is **derived from the tally, not chosen**: classify every accepted finding (§ Merge class) → apply leftover `unmet` AC increments if any (§ Linked-issue hygiene) → apply **Verdict-from-tally** (§ Tally and derived score) → emit that one token. The reviewer does not pick a verdict by vibe.
 - Exactly one verdict:
   - `ship it` — evidence-backed, safe to ship.
@@ -250,7 +250,7 @@ The posted review body is a three-section report. Section order fixed; omit a su
 
 ### Findings
 
-<Ranked findings (§ List cut). Each finding keeps its normal format — title, evidence (`file:line`), impact, **Merge class**, **Confidence**, fix sketch — with its class emoji prefixing the title.>
+<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.>
 
 ### Linked-issue AC
 
@@ -353,6 +353,3 @@ Then ranked findings / leftover AC summary. Do not put `score_pct%` on the `- ve
 
 The GitHub Review `body` no longer uses the two-line header — it follows § Report template, whose Verdict section carries the same facts structured (verdict token + Confidence + four-class emoji tally table).
 
-### List cut
-
-The default "top 1–3 unless `full`" applies to **nits only**: every `must-fix` and `should-fix` finding is listed. If nits are omitted from the narrative list, add one line `nits: <n> omitted from list (counted in tally)` — `tally.nit` stays complete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "3.2.4",
+  "version": "3.2.5",
   "description": "Morning Star harness OpenCode plugin — skills bootstrap + engine-backed runtime hooks (status lint, dispatch validation, Enforcement: hard gates).",
   "license": "MIT",
   "repository": {