@mstar-harness/opencode 0.3.1 → 0.4.0

package/harness-skills/mstar-roles/references/ops-engineer.md

@@ -1,12 +1,14 @@
-## Morning Star Skills (Required Reading)
+## Required Skill Dependencies
 
-Before acting as `ops-engineer`, read:
+**Hub matrix:** `mstar-roles` SKILL.md.
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-review-qc` (especially high-risk operations checklist)
-- `mstar-coding-behavior`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Always:** `mstar-harness-core`, `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-review-qc` (high-risk ops checklist), `mstar-branch-worktree` (repo writes, production-touching branches).
+
+**Typically:** `mstar-plan-conventions` (paths); `mstar-superpowers-align` (when plugin on).
+
+**On demand:** `mstar-phase-gates` (hotfix compressed path when assignment says hotfix).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 

package/harness-skills/mstar-roles/references/product-manager.md

@@ -1,12 +1,14 @@
-## Morning Star Skills (Required Reading)
+## Required Skill Dependencies
 
-Before acting as `product-manager`, read:
+**Hub matrix:** `mstar-roles` SKILL.md.
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-coding-behavior`
-- `mstar-superpowers-align`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-plan-conventions` (`{PLAN_DIR}`, `writing-plans` path).
+
+**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
+
+**On demand:** `mstar-branch-worktree` (when committing product docs to the business repo).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 

package/harness-skills/mstar-roles/references/project-manager/qc-and-residuals.md

@@ -19,7 +19,7 @@ Use this reference when PM is dispatching QC, consolidating review verdicts, or
 ## QC / Residual NEVER (PM)
 
 - **NEVER** consolidate tri-review into `Approve` when any QC report’s `plan_id`, `Review range / Diff basis`, `Review cwd / Worktree path`, or `Working branch` **differs** from the PM Assignment text (character-level mismatch).
-- **NEVER** register or rewrite residual `severity` values outside the machine enum in `mstar-plan-conventions`.
+- **NEVER** register or rewrite residual `severity` values outside the machine enum in `mstar-plan-artifacts`.
 - **NEVER** drop residual tracking to chat-only when `Approve with residuals` applies—canonical open list lives under `{HARNESS_DIR}/status.json` `residual_findings[<plan-id>]`.
 - **NEVER** archive or delete open residual rows from `status.json` without the documented close + `{HARNESS_DIR}/archived/residuals/` workflow.
 - **NEVER** treat “two of three QC reports arrived” as sufficient for a parallel tri-review wave—missing reviewer => `Blocked` or explicit PM decision, not silent `Approve`.
@@ -47,7 +47,7 @@ Use this reference when PM is dispatching QC, consolidating review verdicts, or
 When blocking issues are fixed but non-blocking warnings/suggestions remain:
 
 - Must register residual findings (do not leave as chat-only).
-- Severity enum must follow `mstar-plan-conventions` SSOT.
+- Severity enum must follow `mstar-plan-artifacts` SSOT.
 - Canonical store: `{HARNESS_DIR}/status.json` -> root `residual_findings[<plan-id>]`.
 - Optional mirrored index in main plan is allowed, but never replace canonical entry.
 

package/harness-skills/mstar-roles/references/project-manager.md

@@ -2,11 +2,17 @@
 
 Before any non-trivial PM action, read in order:
 
-1. `mstar-harness-core` skill (state machine + phase gates, SSOT)
-2. Current host adapter skill (OpenCode: `mstar-host-opencode`; Cursor: `mstar-host-cursor`)
-3. `mstar-plan-conventions` skill
-4. `mstar-superpowers-align` skill (when Superpowers enabled)
-5. `mstar-review-qc` skill (before QC dispatch)
+1. `mstar-harness-core` (entry, state machine, Task category, skill index)
+2. `mstar-dispatch-gates` + `mstar-phase-gates` (dispatch + Prepare/Execute gates)
+3. Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor)
+4. `mstar-plan-conventions` (path discovery, init, Spec branch summary)
+5. `mstar-superpowers-align` (when Superpowers plugin is enabled)
+6. `mstar-review-qc` (same coordination round, **before** any QC dispatch)
+7. **On demand:** `mstar-branch-worktree` (parallel implement, QC/QA checkout); `mstar-plan-artifacts` (`status.json`, R#); `mstar-plan-artifacts` (InReview waves, reports naming)
+
+**Not required:** `mstar-coding-behavior` (orchestration-only PM work).
+
+Full cross-role matrix: `mstar-roles` SKILL.md.
 
 This file is a compact PM orchestrator shell.
 Detailed procedures are moved to `references/project-manager/*.md`.
@@ -102,10 +108,10 @@ If any item below matches, fix the dispatch/plan state or mark `Blocked`—do **
 - **NEVER** finish a dispatch turn with Assignment Markdown visible but **without** the matching host invokes when assignments were meant to start work (`dispatch incomplete` / paste-only failure).
 - **NEVER** split a required **parallel batch** of `N >= 2` invokes across multiple assistant messages when the host requires a single dispatch turn with all `N` calls.
 - **NEVER** register residuals only inside the plan narrative while skipping root `{HARNESS_DIR}/status.json` `residual_findings[<plan_id>]` when plan conventions require the SSOT field.
-- **NEVER** write non-canonical residual `severity` strings—use only the machine enum from `mstar-plan-conventions`.
+- **NEVER** write non-canonical residual `severity` strings—use only the machine enum from `mstar-plan-artifacts`.
 - **NEVER** use `Task category: quick` to skip mandatory Prepare (`specify → clarify → plan`) for substantive work (`mstar-harness-core` hard rule).
 - **NEVER** omit `Superpowers` hooks when the plugin is enabled and the batch truly requires parallel dev (`dispatching-parallel-agents`) or same-repo multi-writer concurrency (`using-git-worktrees`) per `mstar-superpowers-align`.
-- **NEVER** point QC at a single dev worktree/`Review cwd` that cannot contain **all** claimed changes from parallel tracks until Git integration lands on one `Working branch` `HEAD` (`mstar-harness-core` QC/QA alignment).
+- **NEVER** point QC at a single dev worktree/`Review cwd` that cannot contain **all** claimed changes from parallel tracks until Git integration lands on one `Working branch` `HEAD` (`mstar-branch-worktree` QC/QA alignment).
 - **NEVER** label `QA: skipped` for report-only QA—still dispatch `@qa-engineer` with report-only mode; QC skip rules are separate and explicit.
 - **NEVER** let non-PM/non-QA roles mark plan `Done`.
 

package/harness-skills/mstar-roles/references/prompt-engineer.md

@@ -1,12 +1,14 @@
-## Morning Star Skills (Required Reading)
+## Required Skill Dependencies
 
-Before acting as `prompt-engineer`, read:
+**Hub matrix:** `mstar-roles` SKILL.md.
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-coding-behavior`
-- `mstar-superpowers-align`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Always:** `mstar-harness-core`, `mstar-dispatch-gates`.
+
+**When editing harness text:** read **all** topic skills you touch — at minimum `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-plan-artifacts`, `mstar-branch-worktree`, `mstar-review-qc`, `mstar-coding-behavior`, `mstar-superpowers-align`, plus host adapters — so prompts stay aligned with SSOT and do not re-duplicate rules.
+
+**Typically:** `mstar-plan-conventions` (path symbols in examples).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 

package/harness-skills/mstar-roles/references/qa-engineer.md

@@ -1,13 +1,14 @@
-## Morning Star Skills (Required Reading)
+## Required Skill Dependencies
 
-Before acting as `qa-engineer`, read:
+**Hub matrix:** `mstar-roles` SKILL.md.
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-review-qc`
-- `mstar-coding-behavior`
-- `mstar-superpowers-align`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Always:** `mstar-harness-core`, `mstar-review-qc`, `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (same checkout fields as QC for the feature).
+
+**Typically:** `mstar-plan-conventions` (paths); `mstar-superpowers-align` (when plugin on).
+
+**On demand:** `mstar-plan-artifacts` (closing R# after verified fix); `mstar-phase-gates` (gate checklist when assignment references verification phase).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 
@@ -26,7 +27,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 
 - **NEVER** invoke another `qa-engineer` or dev/QC roles for **this** QA assignment unless `Delegation: allowed (...)` lists them.
 - **NEVER** sign off while `Review cwd` / `Worktree path`, `Working branch`, `plan_id`, and `Review range / Diff basis` disagree with the assignment or (when applicable) differ from the locked QC tri-review pack—**text-identical** metadata is mandatory for the same scope.
-- **NEVER** switch to an unprescribed worktree/branch to “pick up the other half” of parallel development; if the current `HEAD` cannot contain the claimed diff scope, **Blocked** and ask PM for Git integration or a corrected assignment (`mstar-harness-core` multi-worktree ↔ QC/QA section).
+- **NEVER** switch to an unprescribed worktree/branch to “pick up the other half” of parallel development; if the current `HEAD` cannot contain the claimed diff scope, **Blocked** and ask PM for Git integration or a corrected assignment (`mstar-branch-worktree`).
 - **NEVER** treat `Handoff` / template role lists / route arrows as invoke instructions; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer tool exposure implies authorization; **tool availability ≠ delegation**.
 - **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
@@ -90,7 +91,7 @@ Report-only mode may skip QC tri-review only when no test/config/code artifacts
 
 ## Plan & Residual Rules
 
-- Follow `{HARNESS_DIR}` / `{PLAN_DIR}` and residual lifecycle from `mstar-plan-conventions`.
+- Follow `{HARNESS_DIR}` / `{PLAN_DIR}` from `mstar-plan-conventions`; residual lifecycle from `mstar-plan-artifacts`.
 - QA and PM are the only roles allowed to finalize plan `Done`.
 
 ### Git NEVER (repo writes)

package/harness-skills/mstar-roles/references/qc-specialist-shared.md

@@ -12,11 +12,15 @@ Behavior is shared; reviewer identity is parameterized.
 
 ## Required Skill Dependencies
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-review-qc`
-- `mstar-coding-behavior`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Hub matrix:** `mstar-roles` SKILL.md.
+
+**Always:** `mstar-harness-core`, `mstar-review-qc`, `mstar-dispatch-gates`, `mstar-branch-worktree` (checkout alignment before review), `mstar-plan-artifacts` (report paths and naming).
+
+**Typically:** `mstar-plan-conventions` (path symbols only).
+
+**On demand:** `mstar-plan-artifacts` (when PM asks you to cite severity enum for residual registration — QC does not own `status.json` writes).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 
@@ -37,7 +41,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 - **NEVER** ask the user for permission to submit a report, present “notify PM?” choosers, or stall after a completed review—when requirements are met, emit **Completion Report v2** in the **same** assistant turn (with a real **Git** line when commits are required).
 - **NEVER** modify business implementation/tests, `{HARNESS_DIR}/status.json` residual lifecycle fields, `{HARNESS_DIR}/archived/`, or any path outside the host write whitelist for QC (typically `{PLAN_DIR}/reports/**/*.md` only).
 - **NEVER** `git add .` or stage unrelated paths when committing QC reports—stage **only** the report files you changed.
-- **NEVER** close, delete, or archive residual entries in `status.json` from QC; PM/QA own residual lifecycle per `mstar-plan-conventions`.
+- **NEVER** close, delete, or archive residual entries in `status.json` from QC; PM/QA own residual lifecycle per `mstar-plan-artifacts`.
 - **NEVER** treat `Handoff` lines, template role lists, or routing prose as invoke instructions; only `Delegation: allowed` authorizes callees.
 - **NEVER** infer tool exposure implies authorization; **tool availability ≠ delegation**.
 - **NEVER** run Superpowers `dispatching-parallel-agents` yourself; **PM-only** (`mstar-superpowers-align`).
@@ -70,7 +74,7 @@ Still cover shared baseline:
 - High-impact unresolved warning with disagreement => `Needs Discussion`
 - Otherwise => `Approve`
 
-Use severity and formatting standards from `mstar-review-qc` and `mstar-plan-conventions`.
+Use severity and formatting standards from `mstar-review-qc`; machine `severity` enum from `mstar-plan-artifacts`.
 
 ### Verdict NEVER (`{role_id}`)
 

package/harness-skills/mstar-roles/references/writing-specialist.md

@@ -1,12 +1,12 @@
-## Morning Star Skills (Required Reading)
+## Required Skill Dependencies
 
-Before acting as `writing-specialist`, read:
+**Hub matrix:** `mstar-roles` SKILL.md.
 
-- `mstar-harness-core`
-- `mstar-plan-conventions`
-- `mstar-coding-behavior`
-- `mstar-superpowers-align`
-- Host adapter: `mstar-host-opencode` (OpenCode) or `mstar-host-cursor` (Cursor), whichever matches the session
+**Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-coding-behavior` (surgical edits).
+
+**Typically:** `mstar-plan-conventions` (where deliverables land under `{HARNESS_DIR}` / `docs/`); `mstar-plan-artifacts` (when writing under knowledge or plan trees); `mstar-superpowers-align` (when plugin on).
+
+**Host:** `mstar-host-opencode` | `mstar-host-cursor`.
 
 ## Role Mission
 

package/harness-skills/mstar-superpowers-align/SKILL.md

@@ -119,7 +119,7 @@ Superpowers:
 Superpowers 插件内该技能附带 **`implementer-prompt.md`**、**`spec-reviewer-prompt.md`**、**`code-quality-reviewer-prompt.md`** 等模板（部分宿主以 `/implementer-prompt` 等名称暴露）。正文还描述「每任务后 spec 审 + code quality 审」与示例路径 **`docs/superpowers/plans/`**。在本仓库中须按下述方式 **降权为可选技巧**，**不得覆盖 harness**。
 
 - **权威上下文**：实现与审查的 **分支、检出路径、plan、状态机** 以 **`mstar-harness-core`**、**`mstar-plan-conventions`**、**`mstar-review-qc`** 及 **`@project-manager` 的 Assignment** 为准；**不要用上游模板替代 Assignment 结构**（`Execute as` / `Delegation` 写法见 `agents/project-manager.md` §1.3；另含 `Working branch`、`Review cwd` / `Worktree path`、`plan_id`、`Review range` / `Diff basis` 等）。
-- **谁可以派 subagent**：仅 `@project-manager` 可增加或并行 subagent；Assignment 未写 **`Delegation: allowed (...)`** 时，承接方 **不得** 依该技能自行连续派发「implementer / reviewer」子代理（见 `mstar-harness-core` SKILL.md「调度防串扰」）。
+- **谁可以派 subagent**：仅 `@project-manager` 可增加或并行 subagent；Assignment 未写 **`Delegation: allowed (...)`** 时，承接方 **不得** 依该技能自行连续派发「implementer / reviewer」子代理（见 **`mstar-dispatch-gates`** SKILL.md「调度防串扰」）。
 - **per-task 双审（spec + code quality）用谁**：这是**任务级、会话内快速自检**，**禁止**把 `@qc-specialist` / `@qc-specialist-2` / `@qc-specialist-3` 当作这两步子代理的承接方——QC 角色绑定 **`mstar-review-qc`** 与 **`{PLAN_DIR}/reports/<plan-id>/`** 正式产出，与「每任务后快速过一遍」冲突，易造成误派与多余文档。**推荐**用 **`@general`**（OpenCode 等宿主内置）或宿主并行 Task 的 **`generalPurpose`** subagent，仅借用上游 `spec-reviewer-prompt` / `code-quality-reviewer-prompt` 的检查思路；回报限本会话内简短结论（要点 / 阻塞项），不写 QC Completion Report、不落 `reports/<plan-id>/`。可选用 **`@qa-engineer`** 做同一类 informal pass（侧重可测性、验收对齐、smoke 建议）时，PM 须在 Assignment 写明 **`Informal per-task review only`**（本轮**不**套用正式 QC/QA 的 `plan_id` + `Review range` 三审门禁、**不向** `reports/` 落盘）；**feature 完成后的正式验证**仍按 harness 另派，字段与 QC 对齐。
 - **正式审查门禁**：**QC 三审 + @qa-engineer 验证** 在 **feature / 整 plan 开发完成后**按默认节奏执行（多 batch 默认不每 batch 全套三审）；上游技能的 **per-task 双 reviewer 子代理** 若使用，**最多视为作者侧或会话内自检**，**不可替代** `{PLAN_DIR}/reports/<plan-id>/` 下按 **`mstar-review-qc`** 产出的 QC 报告，也不得绕过 **`plan_id` / `Review range` 三份逐字相同** 的约定。
 - **完成态**：实现方将工作置 **`InReview`**；**`Done`** 仅 `@project-manager` 或 `@qa-engineer` 设定（`mstar-harness-core`）。上游模板中的「任务完成」**不等于** harness 的 **Done / sign-off**。
@@ -142,7 +142,7 @@ PM 在 Assignment 的 `Superpowers` 中引用 `subagent-driven-development` 时
 - `QC: skipped` 只用于已定义例外（product-docs only / tech-spec only）；否则默认进入 QC 路径。
 - **`Delegation: forbidden`** 与 Superpowers 里的 `subagent-driven-development` **互斥**（除非已 `allowed` 且范围覆盖）——见上文专节。
 - `Working branch` 与 `Branch policy` 只能二选一；两者同写时，以 PM 明确改写为准后再执行。
-- **`QC 三审`**：三份 Assignment 的 **`plan_id`** 与 **`Review range` / `Diff basis`** 必须 **完全一致**（可复制粘贴）；缺一项则 **不得**将 gate 汇总为 `Approve`，须 `Blocked` 后补 Assignment 或补报告（见 `mstar-harness-core` `references/branch-and-worktree.md`）。
+- **`QC 三审`**：三份 Assignment 的 **`plan_id`** 与 **`Review range` / `Diff basis`** 必须 **完全一致**（可复制粘贴）；缺一项则 **不得**将 gate 汇总为 `Approve`，须 `Blocked` 后补 Assignment 或补报告（见 `mstar-branch-worktree`）。
 
 ## References
 

package/harness-skills/mstar-superpowers-align/references/per-role-matrix.md

@@ -22,14 +22,14 @@
 - 当任务进入 **gate / sign-off / merge decision**，若未出现 `verification-before-completion` 或等价证据要求，视为门禁不完整。
 - 当任务声明 **并行分派**，`Superpowers` 中应显式包含 `dispatching-parallel-agents`（或同义触发短语），并为每个可写承接方写清 `Working branch`。
 - 当 **并行分派** 且 **≥2 个可写承接方** 针对 **同一 Git 仓库** 可能并发落盘时，`Superpowers` 中还 **必须** 显式包含 **`using-git-worktrees`**（或同义触发短语），并在 Assignment 中写清各流 **检出路径约定**（或要求 Completion Report 回报实际 worktree 路径）；**禁止**依赖「多 subagent 共享同一工作目录」完成并发写入。
-- **QC 三审**：三份 Assignment 除 `Review cwd`、`Working branch` 外，**必须**含 **相同**的 **`plan_id`** 与 **`Review range` / `Diff basis`**（可复制粘贴）；**@qa-engineer** 同 feature 验证时 **照抄**同一组字符串。缺任一项视为 PM 分派不完整（`mstar-harness-core` `references/branch-and-worktree.md`）。**同仓、同一 plan、多 worktree 并行**：PM **推荐**先建 **plan 集成分支** 再挂各轨 worktree，QC 前再归并到单一 `HEAD`（见同 reference **「推荐默认编排：先建 plan 集成分支，再挂各 worktree」**）。**同一 plan 多 batch**：**默认仅在整 plan dev 完成后**派一轮完整三审；复验波次用新文件名；增量例外须 Assignment 写明（`mstar-plan-conventions`）。
+- **QC 三审**：三份 Assignment 除 `Review cwd`、`Working branch` 外，**必须**含 **相同**的 **`plan_id`** 与 **`Review range` / `Diff basis`**（可复制粘贴）；**@qa-engineer** 同 feature 验证时 **照抄**同一组字符串。缺任一项视为 PM 分派不完整（`mstar-branch-worktree`）。**同仓、同一 plan、多 worktree 并行**：PM **推荐**先建 **plan 集成分支** 再挂各轨 worktree，QC 前再归并到单一 `HEAD`（见同 reference **「推荐默认编排：先建 plan 集成分支，再挂各 worktree」**）。**同一 plan 多 batch**：**默认仅在整 plan dev 完成后**派一轮完整三审；复验波次用新文件名；增量例外须 Assignment 写明（`mstar-plan-conventions`）。
 
 ## @product-manager
 
 | 场景 | 技能 |
 |------|------|
 | 必用 | `brainstorming`（新产品/大范围需求澄清） |
-| 必用（与同仓其他可写 subagent 并发落盘项目仓库时） | `using-git-worktrees`（独立 worktree + Assignment 已批准分支；见 `mstar-harness-core`） |
+| 必用（与同仓其他可写 subagent 并发落盘项目仓库时） | `using-git-worktrees`（独立 worktree + Assignment 已批准分支；见 **`mstar-branch-worktree`**） |
 | 宜用 | `writing-plans`（把 PRD/验收拆成可执行里程碑，与 `mstar-plan-conventions` 对齐） |
 
 ## @architect
@@ -37,7 +37,7 @@
 | 场景 | 技能 |
 |------|------|
 | 必用 | `brainstorming`（重大架构取舍、多方案比选） |
-| 必用（与同仓其他可写 subagent 并发落盘项目仓库时） | `using-git-worktrees`（见 `mstar-harness-core`） |
+| 必用（与同仓其他可写 subagent 并发落盘项目仓库时） | `using-git-worktrees`（见 **`mstar-branch-worktree`**） |
 | 宜用 | `writing-plans`（技术方案、迁移、分阶段落地计划） |
 
 ## @fullstack-dev / @fullstack-dev-2 / @frontend-dev
@@ -57,7 +57,7 @@
 | 场景 | 技能 |
 |------|------|
 | 必用 | `verification-before-completion`（报告通过/阻塞、Done sign-off 前须有可复现命令与输出） |
-| 必用（验证 feature / 跑业务仓测试或提交测试工件时） | 在 PM 写明的 **`Review cwd` / `Worktree path`**、**`Working branch`**、**`plan_id`**、**`Review range` / `Diff basis`** 下执行（与 QC **逐字相同**）；先核对路径、分支与审查范围（见 `mstar-harness-core` `references/branch-and-worktree.md`「QC 三审、QA 验证与 feature 检出上下文」） |
+| 必用（验证 feature / 跑业务仓测试或提交测试工件时） | 在 PM 写明的 **`Review cwd` / `Worktree path`**、**`Working branch`**、**`plan_id`**、**`Review range` / `Diff basis`** 下执行（与 QC **逐字相同**）；先核对路径、分支与审查范围（见 `mstar-branch-worktree`「QC 三审、QA 验证与 feature 检出上下文」） |
 | 必用（与同仓其他可写 subagent 并发写仓库时） | `using-git-worktrees` |
 | 宜用 | `using-git-worktrees`（需与既有目录分离、但在**同一 `Working branch`** 上另开检出专供 QA 写入时） |
 | 宜用 | `systematic-debugging`（flaky、环境、不可稳定复现） |
@@ -68,7 +68,7 @@
 | 场景 | 技能 |
 |------|------|
 | 必用 | `verification-before-completion`（审查结论须指向证据：diff、lint、日志） |
-| 必用（审查 feature 实现时） | 在 PM 写明的 **`Review cwd` / `Worktree path`**、**`Working branch`**、**`plan_id`**、**`Review range` / `Diff basis`** 下执行审查（**`plan_id` 与 `Review range` 三份 QC Assignment 须一致**）；先核对再按 **`Review range` / `Diff basis`** 跑 diff/lint（见 `mstar-harness-core` `references/branch-and-worktree.md`、`mstar-review-qc`） |
+| 必用（审查 feature 实现时） | 在 PM 写明的 **`Review cwd` / `Worktree path`**、**`Working branch`**、**`plan_id`**、**`Review range` / `Diff basis`** 下执行审查（**`plan_id` 与 `Review range` 三份 QC Assignment 须一致**）；先核对再按 **`Review range` / `Diff basis`** 跑 diff/lint（见 `mstar-branch-worktree`、`mstar-review-qc`） |
 | 宜用 | `using-git-worktrees`（需与开发目录分离、但在**同一待审分支**上另开检出专供审查时） |
 | 宜用 | `systematic-debugging`（对"疑似缺陷但证据不足"的条目追根） |
 

package/harness-skills/mstar-superpowers-align/references/tension-table.md

@@ -10,10 +10,10 @@
 | 热修 | 热修以恢复服务为先，可事后补 RCA；Assignment 须标明 Hotfix / `Branch policy` | `systematic-debugging` 可能强调「查透再改」 | **消解**：热修路径以 **Assignment + `mstar-harness-core`** 为准；技能用于**最小变更**与**事后根因**，不要求在长调查完成前强行停改。 |
 | 完成与证据 | `mstar-harness-core` 反模式：无测试或行为证据即宣称完成 | `verification-before-completion` | **一致**：表述不同，目标相同（gate 前可核对证据）。 |
 | Plan 形态 | `mstar-plan-conventions`：**`{PLAN_DIR}`**、**`{HARNESS_DIR}/status.json`**（open residual）、**`{HARNESS_DIR}/archived/residuals/<plan-id>.json`**、`{PLAN_DIR}/reports/<plan-id>/` | `writing-plans` | **互补**：convention 管**存放位置与结构**；writing-plans 管**多步任务如何写成可执行计划**；PM 维护时两者同时满足。**路径门限**：提示词 + `mstar-plan-conventions` 约束 **`{PLAN_DIR}`** 优先于技能默认的 `docs/superpowers/plans/`（无本地同名技能覆盖）。 |
-| 并行开发 | `mstar-harness-core`：独立模块可并行；**先锁接口契约**再并行编码；**同仓多可写并发须 `git worktree` 隔离检出目录** | `dispatching-parallel-agents`、`subagent-driven-development`、**`using-git-worktrees`**（同仓并发写入时） | **叠加约束**：并行**不免除** `mstar-harness-core` `references/branch-and-worktree.md` 分支门禁——每个**可写**承接方 Assignment 仍须含 PM 批准的 **`Working branch`** / **`Branch policy`**，禁止多人各自假设 base；**且** ≥2 可写流同仓并发时 **禁止**共用同一 cwd，**必须** worktree（或等价独立检出）+ Assignment 写明检出约定。 |
+| 并行开发 | `mstar-harness-core`：独立模块可并行；**先锁接口契约**再并行编码；**同仓多可写并发须 `git worktree` 隔离检出目录** | `dispatching-parallel-agents`、`subagent-driven-development`、**`using-git-worktrees`**（同仓并发写入时） | **叠加约束**：并行**不免除** `mstar-branch-worktree` 分支门禁——每个**可写**承接方 Assignment 仍须含 PM 批准的 **`Working branch`** / **`Branch policy`**，禁止多人各自假设 base；**且** ≥2 可写流同仓并发时 **禁止**共用同一 cwd，**必须** worktree（或等价独立检出）+ Assignment 写明检出约定。 |
 | `subagent-driven-development` 与 `implementer-prompt` | **PM Assignment**、具名角色 **`Execute as: role-id`**（无 `@`）、仅 PM 可派 subagent；QC 三审 + QA 在 feature / plan 完成后，**`plan_id` + `Review range` 三审与 QA 逐字对齐**；**`{PLAN_DIR}`**；**`InReview` / `Done` 权限** | 上游：**每任务**后 **spec + code-quality 子代理审**；**泛化 implementer** 模板；示例 **`docs/superpowers/plans/`**；默认不并行多个 implementer | **以 harness 为准**：上游模板与 per-task 双审**不替代** Assignment 与 **QC/`mstar-review-qc`**；per-task 双审用 **`@general` / `generalPurpose` 或 informal `@qa-engineer`**，**勿**用 **`@qc-specialist*`**；per-task 审查**仅可作非正式自检**（若 PM 未另授权 `Delegation`）；并行以 **PM + worktree** 为准。细则见 SKILL.md **「`subagent-driven-development` 与上游 implementer-prompt / reviewer 模板」**。 |
 | TDD | 全局流程**未**强制 TDD | `test-driven-development` | **项目/用户优先**：项目或用户禁止 TDD 时，不得因技能强行 TDD。 |
-| `git worktree` / 多工作目录 | `mstar-harness-core` `references/branch-and-worktree.md`：**开发**阶段同仓多可写 **并发**须独立 worktree；**QC / QA** 须在 **该 feature 的检出上下文**（通常 `Review cwd` = 开发所用 worktree，或同分支另开检出）上审查与验证，且 **三份 QC + QA** 共用 **`plan_id`** 与 **`Review range` / `Diff basis`**（逐字相同）；仅 `@project-manager` 决定分支策略、`Assignment` 须写明 **`Working branch`** / **`Branch policy`** 与 **检出路径约定**（含 **`Review cwd` / `Worktree path`**） | `using-git-worktrees` | **不冲突，但须叠同一门禁**：worktree 是「同一仓库多个检出目录」；**分支授权**仍须与 PM 一致。开发并发写入若不用 worktree 易导致互相覆盖；QC/QA 若错用 cwd/分支/**diff 范围**会审错、验错对象——见 `mstar-harness-core` `references/branch-and-worktree.md` **「QC 三审、QA 验证与 feature 检出上下文」**。若在 worktree 里擅自 `checkout -b` 或未授权切换分支，即违规。 |
+| `git worktree` / 多工作目录 | `mstar-branch-worktree`：**开发**阶段同仓多可写 **并发**须独立 worktree；**QC / QA** 须在 **该 feature 的检出上下文**（通常 `Review cwd` = 开发所用 worktree，或同分支另开检出）上审查与验证，且 **三份 QC + QA** 共用 **`plan_id`** 与 **`Review range` / `Diff basis`**（逐字相同）；仅 `@project-manager` 决定分支策略、`Assignment` 须写明 **`Working branch`** / **`Branch policy`** 与 **检出路径约定**（含 **`Review cwd` / `Worktree path`**） | `using-git-worktrees` | **不冲突，但须叠同一门禁**：worktree 是「同一仓库多个检出目录」；**分支授权**仍须与 PM 一致。开发并发写入若不用 worktree 易导致互相覆盖；QC/QA 若错用 cwd/分支/**diff 范围**会审错、验错对象——见 `mstar-branch-worktree` **「QC 三审、QA 验证与 feature 检出上下文」**。若在 worktree 里擅自 `checkout -b` 或未授权切换分支，即违规。 |
 | 升级与重复失败 | `mstar-harness-core` skill：多次失败升级人工等 | `systematic-debugging`、`verification-before-completion` | **一致**：技能减少「无根因重复改」；**达不到 harness 升级条件**时仍以文档为准。 |
 
 **小结**：Superpowers 主要填充各阶段**如何做**的细节；**阶段顺序、Done 权限、QC/QA 路由、分支唯一决策人**仍以 `mstar-*` skills 与 `@project-manager` 路由表为准。

package/harness-skills/pm/SKILL.md

@@ -17,7 +17,7 @@ Use `/pm` as a hard switch for the current session: enter Morning Star PM mode u
 
 ## Operating baseline
 
-- Prefer **`specify → clarify → plan → tasks → delegate`** (align with `mstar-harness-core` / `references/phase-gate-playbook.md`; do not skip `specify`).
+- Prefer **`specify → clarify → plan → tasks → delegate`** (align with `mstar-phase-gates`; do not skip `specify`).
 - Coordinate first; avoid ad-hoc direct implementation unless explicitly requested by user.
 - Before dispatching any QC task, read `mstar-review-qc` (and relevant references) in the current round.
 - Require evidence before completion claims.
@@ -27,5 +27,5 @@ Use `/pm` as a hard switch for the current session: enter Morning Star PM mode u
 
 1. User explicit instructions
 2. Project `AGENTS.md` / `CLAUDE.md`
-3. `mstar-harness-core` and related runtime `mstar-*` skills under `skills/` (`mstar-roles`, `mstar-plan-conventions`, `mstar-review-qc`, `mstar-coding-behavior`, `mstar-superpowers-align`). Routing regression is **maint-only**: `.cursor/skills/mstar-routing-eval/` (not part of `/pm` runtime load).
+3. `mstar-harness-core` and related runtime `mstar-*` skills under `skills/` (`mstar-roles`, `mstar-phase-gates`, `mstar-dispatch-gates`, `mstar-plan-conventions`, `mstar-review-qc`, `mstar-superpowers-align`; plus `mstar-branch-worktree`, `mstar-plan-artifacts` when the round needs them). Routing regression is **maint-only**: `.cursor/skills/mstar-routing-eval/` (not part of `/pm` runtime load).
 4. This `/pm` command skill

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "0.3.1",
+  "version": "0.4.0",
   "description": "Morning Star harness OpenCode plugin (skills bootstrap and agent loading).",
   "license": "MIT",
   "repository": {

package/skills/mstar-host/SKILL.md

@@ -87,7 +87,8 @@ Routing in `mstar-roles` **project-manager** may read `@explore → @product-man
 - `question` availability is host-config dependent; if unavailable, fall back to structured Markdown clarify flow.
 - Printing an Assignment in the main thread is not dispatch; PM must actually invoke the target role.
 - Built-in `@explore` remains read-only orientation, not a substitute for role-owned implementation or review deliverables.
-- More MCPs does not fix process gaps; follow phase-gate and evidence rules first.
+- More MCPs does not fix process gaps; follow `mstar-phase-gates` and evidence rules first.
+- Topic skills load **on demand** per `mstar-roles` (see hub matrix): `mstar-dispatch-gates`, `mstar-phase-gates`, `mstar-branch-worktree`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-plan-artifacts`, etc.
 
 ## Shared protocol: library documentation retrieval (Context7)
 

package/harness-skills/mstar-harness-core/references/phase-gate-playbook.md

@@ -1,87 +0,0 @@
-# Phase Gate Playbook（Morning Star）
-
-本手册将 `specify -> clarify -> plan -> tasks -> implement` 变成可执行动作，供 `@project-manager`、开发与 QA 在日常交付中快速对齐。
-
-## 适用范围
-
-- 非热修（non-hotfix）任务默认强制执行全链路门禁。
-- 热修可走压缩路径，但必须补事后 `clarify/RCA` 记录。
-
-## 两阶段门禁
-
-### A. Prepare
-
-顺序：`specify -> clarify -> plan`
-
-- `specify`
-  - 目标：定义问题、范围、验收。
-  - 最小产物：问题陈述、目标用户价值、非目标、DoD 草案。
-- `clarify`
-  - 目标：收敛会影响方案或验收的歧义。
-  - 最小产物：歧义清单 + 结论；若未收敛则 `blocked`。
-  - **意图**：区分字面请求与真实目标；手段/目标混淆须在此收敛（见本 skill `SKILL.md` Intent gate）。
-  - **结构化澄清**：与用户核对歧义或决策时，`@project-manager`（及直接与用户对话的角色）在**宿主支持**时优先用 `question` 类能力拉齐输入；否则用等价结构化正文。宿主差异细则见当前宿主的 `mstar-host` skill。
-- `plan`
-  - 目标：给出可执行技术方案与风险控制。
-  - 最小产物：方案、模块边界/接口契约、风险与回滚、验证计划。
-  - **准入**：能书面写出真实目标、成功判据、非目标后再锁 plan（同 `SKILL.md`）。
-
-### B. Execute
-
-顺序：`plan locked -> tasks -> implement`
-
-- `plan locked`
-  - 目标：冻结本轮基线，防止边做边漂移。
-  - 最小动作：在 plan 或 notes 记录当前锁定版本（日期或 hash）。
-- `tasks`
-  - 目标：把 plan 拆成可执行任务与依赖顺序。
-  - 最小产物：任务列表、并行标记、完成判据、映射到验收标准。
-  - **PM**：若并行标记对应「多轨同时 implement」，在对外 **Status Update** 与实现 Assignment 的 **`Superpowers`** 中写入 **`dispatching-parallel-agents`**（或同义短语）；同仓多可写并发时叠 **`using-git-worktrees`**（见 `mstar-superpowers-align`）。
-- `implement`
-  - 目标：按任务执行并提交证据，进入审查。
-  - 最小产物：实现 diff、自检证据、回报与 handoff。
-  - **行为准则**：执行中遵循 `mstar-coding-behavior`（不静默假设、优先简单方案、只做与任务直接相关的手术式改动、按 `Step -> verify` 推进）。
-  - **编辑纪律**：改文件前以磁盘为准重读；Patch 失败则重读、缩小步长，禁止盲试（见 `SKILL.md`「可验证编辑与上下文纪律」）。
-  - **知识库**：若项目启用 `{HARNESS_DIR}/knowledge/` 且当前计划在 `{HARNESS_DIR}/status.json` 的 `plans[].metadata` 中登记了 `primary_spec` / `spec_refs`，**开工前**须阅读并在回报中说明已对齐；规则见 `mstar-plan-conventions`「`{HARNESS_DIR}/knowledge/` 开发过程知识库」。
-
-## 角色职责
-
-- `@project-manager`
-  - 负责门禁判定与 Assignment 中的 `Phase Gate Checklist`。
-  - 在 `Status Update` 汇报当前 gate 状态。
-- 开发角色（`@frontend-dev` / `@fullstack-dev` / `@fullstack-dev-2`）
-  - 仅在 Execute gate 放行后开始实现。
-  - 发现新约束时先回报并请求回写 plan。
-- `@qa-engineer`
-  - 在 `InReview` 阶段验证实现与验收映射是否一致。
-
-## Plan 目录与审查报告（启用 `{PLAN_DIR}` 时）
-
-- 进入 `InReview` 后，QC 书面产出按 `mstar-plan-conventions` 落入 `{PLAN_DIR}/reports/<plan-id>/`（如 `*-qc1.md` … `*-qc-consolidated.md`）；勿与主 plan 文件混写为「唯一草稿」后又删，保留可追溯历史。**多 batch 的同一 plan**：完整 QC 三审**默认在整 plan dev 完成后一次**（非每 batch），见 `mstar-plan-conventions`「QC 三审触发时机」。
-- 非阻断项与后续技术债：PM 汇总后写入 `{HARNESS_DIR}/status.json` 根级 `residual_findings[<plan-id>]`（**open**，与 `plans` 平级；canonical 见 `mstar-plan-conventions` **SKILL.md** 开篇）；关闭后迁入 `{HARNESS_DIR}/archived/residuals/<plan-id>.json`，与 `mstar-review-qc` 一致。每条 **`severity`** 遵守 `mstar-plan-conventions`「Residual findings：severity（SSOT，机器字段）」。
-
-## 快速判定（PM）
-
-1. `specify` 是否完成？
-2. `clarify` 是否完成（高影响歧义是否收敛）？
-3. 意图门禁是否满足（真实目标 / 成功判据 / 非目标已写明）？
-4. `plan` 是否完成并可引用？
-5. `tasks` 是否完成？
-6. Assignment 是否含 **`Task category`**（实现类任务）并与 Owner 一致？
-7. 若中途出现 plan drift，是否先回写再继续？
-8. 实现说明中是否体现"最小解法 + 手术式改动 + 可验证检查"？
-
-任一项为「否」时，`Gate decision` 必须是 `blocked`。
-
-## Hotfix 例外
-
-- 允许路径：`specify(min) -> plan(min) -> implement`
-- 必须补记：
-  - 事后 `clarify/RCA`
-  - 触发条件、影响范围、修复与回滚摘要
-
-## 最小证据要求
-
-- Prepare 阶段证据：问题定义、歧义结论、plan 链接。
-- Execute 阶段证据：tasks 清单、实现自检、审查/验证证据。
-- 结论证据：不得仅写"done"，必须可复核（命令、输出、截图或复现步骤）。

package/harness-skills/mstar-plan-conventions/references/knowledge-and-designs.md

@@ -1,70 +0,0 @@
-# `{HARNESS_DIR}/knowledge/` 开发过程知识库与 `{SPECS_DIR}` / `residuals/` 散文（Morning Star）
-
-> **Load order（与其它 `mstar-*` skill 一致）**：依赖本 reference 维护知识库 / 规格挂接前，须已 Read **`mstar-harness-core`** skill（SKILL.md；仓库写操作与分支门禁见 `mstar-harness-core/references/branch-and-worktree.md`）。冲突以 **`mstar-harness-core`** 为准。
-
-本节将「用户文档」与「agent / 实施用知识」分开，**与具体业务仓库无关**；项目可在根目录 `AGENTS.md` 用一小段指向本 reference 或复述分界关键词，避免重复维护长文。
-
-## 与公开文档目录的分工（典型为 `docs/`）
-
-
-| 区域                               | 典型内容                                            | 受众                                       |
-| -------------------------------- | ----------------------------------------------- | ---------------------------------------- |
-| `**docs/`**（或项目约定的用户文档根）         | 安装/quickstart、稳定架构概览、贡献指南、对外 API 说明             | 人类贡献者与终端用户；clone 后应可读                    |
-| `**{HARNESS_DIR}/knowledge/**`   | 架构评审报告、规格修订稿、gap 分析、约束清单、**某一 plan 的输入/输出设计材料** | Agent handoff、跨会话连续；**不**默认当作对外产品文档      |
-| `**{SPECS_DIR}`**（可选）             | 规格主目录（支持 `{HARNESS_DIR}/specs/` 或 `{HARNESS_DIR}/designs/`） | 与 `knowledge/` 分工由团队定义；**不**默认替代 `docs/` |
-
-
-**不应**放入用户文档树的内容（宜放 `knowledge/`、`{SPECS_DIR}` 或主 plan）：作为**特定 plan 的输入/输出**的评审结论、实施笔记、未稳定的规格草案。
-
-## 目录与索引
-
-- `{SPECS_DIR}` 定义：优先 `{HARNESS_DIR}/specs/`，否则 `{HARNESS_DIR}/designs/`；若两者都不存在，建议新建 `{HARNESS_DIR}/specs/`。
-
-- 知识库物理路径：`**{HARNESS_DIR}/knowledge/`**（推荐布局下常为 `**.agents/knowledge/**`，与 `**{PLAN_DIR}**` 并列）。
-- **必须**维护 `**{HARNESS_DIR}/knowledge/README.md`** 作为**目录索引**：至少包含表格列 **Document（链接）**、**Source Plan（`plans[].id`）**、**Description**、**Status**（如 `Active` / `Superseded by implementation (<plan-id>)` / `Archived`）。
-- 初始化启用知识库时：创建空表头的 `README.md`，随文档递增行。
-
-## 文件命名
-
-- 推荐：`<topic>-<qualifier>-v<N>.md`（例：`sync-contract-gap-analysis-v1.md`），便于同主题多版共存。
-- 避免与主 plan 文件名混淆：主 plan 仍建议 `<plan-id>-<plan-name>.md` 且放在 `{PLAN_DIR}/` 根下，而非塞进 `knowledge/` 根（除非团队明确约定）。
-
-## 与 `status.json` 的链接
-
-- 某 plan 的**权威设计输入**在知识库或规格目录中时，在 `**plans[].metadata`** 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）或 `**spec_refs**`（`string[]`）。路径为**仓库内相对路径**（推荐布局下常写作 `**.agents/knowledge/....md`** 或 `**.agents/specs/....md`**；兼容旧目录时也可为 `**.agents/designs/....md**`）。
-- 执行方在 **implement 前**须按 metadata 读取这些文件，并与主 plan 核对；不得在未读链接文档的情况下**静默偏离**其中已写明的决策（若需偏离，先回写 knowledge 或 plan 并走 PM/architect 门禁）。
-
-## 维护规则
-
-1. **新增**：按命名规则添加 `.md` → 在 `knowledge/README.md` 索引表增加一行 → 在相关 `plans[].metadata` 更新 `primary_spec` / `spec_refs`（若该文档为本 plan 输入/输出）。
-2. **阅读**：开发类 agent 在开始编码前，**必须**阅读当前 plan 在 `metadata` 中指向的 knowledge 文档（若存在）；`@project-manager` 在 Assignment 中可再次点名路径。
-3. **修订**：评审或规格变更若改动了 knowledge 文件，同步更新 README 中 **Status** 或 Description；版本迭代优先新文件名 `v<N+1>` 或保留旧版并标明 Superseded。
-4. **归档**：当文档内容已完全反映到已合并代码中时：**保留文件不删除**（保留设计考据）；将索引 **Status** 标为 `Superseded by implementation (...)` 或 `Archived`。**不要**把知识库产物搬进 `**{HARNESS_DIR}/archived/plans/`**（该处用于**计划行**冷快照）；知识库用索引状态表达生命周期即可。
-
-## 与 `reports/`、`{PLAN_DIR}/residuals/` 的区分
-
-- `**reports/<plan-id>/`**：偏 **审查流程留档**（review、QC1/2/3、consolidated），只读历史。
-- `**{PLAN_DIR}/residuals/<plan-id>/`**：偏 **仍 open 的 R# 长文补充**（与根级 `**residual_findings**` 配套，canonical 见 `mstar-plan-conventions` **SKILL.md** 开篇）；见下文「open residual 散文详情」。
-- `**knowledge/**`：偏 **可复用的设计上下文**（规格、决策、分析），可被后续 plan 或多会话反复引用；三者可互链，但职责不混写。
-
----
-
-## `{PLAN_DIR}/residuals/<plan-id>/`（可选·open residual 散文详情）
-
-当某条 open residual 需要**多于** open 列表（根级 `residual_findings[<plan-id>][]`；若仅存 legacy 侧则同口径）里结构化字段所能承载的叙述时，可在本目录增加 **Markdown 散文**，作为 **SSOT 的补充**（**不替代** JSON；**权威仍以** `**{HARNESS_DIR}/status.json`** 中的 open 条目为准）。
-
-
-| 与相邻目录的分工                                  | 典型内容                                                                  |
-| ----------------------------------------- | --------------------------------------------------------------------- |
-| `**{PLAN_DIR}/reports/<plan-id>/**`       | QC / review **流程留档**（`-qc*.md`、consolidated 等），只读历史链                  |
-| **本目录 `{PLAN_DIR}/residuals/<plan-id>/`** | 针对**仍 open** 的某一 R#：defer 背景、遗留原因、代码锚点、后续接手提示等**长文**                  |
-| `**{HARNESS_DIR}/knowledge/`**            | 可跨 plan 复用的**设计**上下文、规格修订、gap 分析（若文中顺带提到 residual，仍以 JSON + 本目录为跟踪权威） |
-
-
-**文件命名（推荐）**：`<finding-id>-<short-label>.md`，其中 `**finding-id`** 与该条在 **open 列表**（根级 `**residual_findings**`，见 `mstar-plan-conventions` **SKILL.md** 开篇）中的 `**id**`（如 `R1`）或团队约定的 `**td-*` 等技术债编号**一致，便于 `detail_doc` 与目录互查。
-
-**登记**：在对应 open 条目中填写可选 `**detail_doc`**（仓库内相对路径，常形如 `**{PLAN_DIR}/residuals/<plan-id>/R1-….md**`）。**禁止**只写散文、不在 SSOT 中登记 open 行。
-
-**维护**：`**@project-manager`**（或与 Assignment 一致的可写角色）；`**@qc-specialist***` 宿主白名单通常**不含**本目录——审查结论仍以 `**reports/`** 为准，散文由 PM/实现方据结论整理。
-
-**关闭与归档**：当该条从 **open 列表**（根级 **`residual_findings[<plan-id>]`**；若仅存 legacy 侧则从该处）移除并**追加**至 `**{HARNESS_DIR}/archived/residuals/<plan-id>.json`** 时，应将对应 `**.md**` 一并收口：可迁入 `**{HARNESS_DIR}/archived/knowledge/**`（若视为历史考据）、或团队约定的 `**{HARNESS_DIR}/archived/residuals/**` 子路径（与 `**.json**` 同批变更可追溯）；并在归档条目的 `**closure_evidence` / `closure_note**`（或团队约定字段）中**写明散文最终路径**。勿长期保留「JSON 已关闭而散文仍留在 `residuals/` 且声称仍 open」的状态。