@mstar-harness/opencode 0.6.9 → 0.6.11

package/harness-agents/architect.md

@@ -1,4 +1,9 @@
 ---
+name: architect
+description: |-
+  技术架构师 - 系统设计、技术决策与技术向文档编写（架构说明、ADR、接口契约等）。
+  Architect - system design, technical decisions, and technical documentation (architecture notes, ADRs, interface contracts).
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -10,10 +15,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: architect
-description: |-
-  技术架构师 - 系统设计、技术决策与技术向文档编写（架构说明、ADR、接口契约等）。
-  Architect - system design, technical decisions, and technical documentation (architecture notes, ADRs, interface contracts).
 ---
 
 ## Morning Star Role Binding

package/harness-agents/frontend-dev.md

@@ -1,4 +1,9 @@
 ---
+name: frontend-dev
+description: |-
+  前端开发工程师 - 页面/组件/交互/a11y/前端性能。全栈功能里默认前端主责（与 `@fullstack-dev` 分轨）；纯 UI 任务首选本角色。
+  Frontend Developer - pages/components/interactions/accessibility/frontend performance. This is the default frontend owner in fullstack work (split with `@fullstack-dev`) and the preferred role for pure UI tasks.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -8,10 +13,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: frontend-dev
-description: |-
-  前端开发工程师 - 页面/组件/交互/a11y/前端性能。全栈功能里默认前端主责（与 `@fullstack-dev` 分轨）；纯 UI 任务首选本角色。
-  Frontend Developer - pages/components/interactions/accessibility/frontend performance. This is the default frontend owner in fullstack work (split with `@fullstack-dev`) and the preferred role for pure UI tasks.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/fullstack-dev-2.md

@@ -1,4 +1,9 @@
 ---
+name: fullstack-dev-2
+description: |-
+  全栈开发工程师 - 与 `@fullstack-dev` 并行的第二实现轨（独立模块/API/页面岛）。PM 在 tasks 可并行或加速时指派；须写明模块边界与分支，勿当作闲置备用。
+  Fullstack Developer (Track 2) - the second implementation track parallel to `@fullstack-dev` (independent modules/APIs/page islands). PM should assign this role when tasks can run in parallel or when acceleration is needed, with explicit module boundaries and branch ownership.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -8,10 +13,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: fullstack-dev-2
-description: |-
-  全栈开发工程师 - 与 `@fullstack-dev` 并行的第二实现轨（独立模块/API/页面岛）。PM 在 tasks 可并行或加速时指派；须写明模块边界与分支，勿当作闲置备用。
-  Fullstack Developer (Track 2) - the second implementation track parallel to `@fullstack-dev` (independent modules/APIs/page islands). PM should assign this role when tasks can run in parallel or when acceleration is needed, with explicit module boundaries and branch ownership.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/fullstack-dev.md

@@ -1,4 +1,9 @@
 ---
+name: fullstack-dev
+description: |-
+  全栈开发工程师 - 后端主导的全栈实现（API/业务/数据层）。UI 重或新页面多时由 PM 拆给 `@frontend-dev`；第二并行实现轨用 `@fullstack-dev-2`。Hotfix/单流小改可一人完成。
+  Fullstack Developer - backend-led fullstack implementation (API/business/data). PM should split UI-heavy or new-page work to `@frontend-dev`, and use `@fullstack-dev-2` for the second parallel track. One developer can handle hotfixes or small single-stream updates.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -8,10 +13,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: fullstack-dev
-description: |-
-  全栈开发工程师 - 后端主导的全栈实现（API/业务/数据层）。UI 重或新页面多时由 PM 拆给 `@frontend-dev`；第二并行实现轨用 `@fullstack-dev-2`。Hotfix/单流小改可一人完成。
-  Fullstack Developer - backend-led fullstack implementation (API/business/data). PM should split UI-heavy or new-page work to `@frontend-dev`, and use `@fullstack-dev-2` for the second parallel track. One developer can handle hotfixes or small single-stream updates.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/ops-engineer.md

@@ -1,4 +1,9 @@
 ---
+name: ops-engineer
+description: |-
+  运维工程师 - 部署、监控和基础设施。
+  Ops Engineer - deployment, monitoring, and infrastructure operations, including CI/CD and observability.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -8,10 +13,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: ops-engineer
-description: |-
-  运维工程师 - 部署、监控和基础设施。
-  Ops Engineer - deployment, monitoring, and infrastructure operations, including CI/CD and observability.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/product-manager.md

@@ -1,4 +1,9 @@
 ---
+name: product-manager
+description: |-
+  产品经理 - 需求分析、产品规划、市场/用户研究与产品向文档编写。
+  Product Manager - requirements analysis, product planning, market/user research, and product-facing documentation.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -10,10 +15,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: product-manager
-description: |-
-  产品经理 - 需求分析、产品规划、市场/用户研究与产品向文档编写。
-  Product Manager - requirements analysis, product planning, market/user research, and product-facing documentation.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/project-manager.md

@@ -1,4 +1,9 @@
 ---
+name: project-manager
+description: |-
+  项目经理 - 协调开发团队，管理项目进度。
+  Project Manager - coordinate the team, track progress, and orchestrate execution across roles.
+model: inherit
 mode: primary
 tools:
   write: true
@@ -7,10 +12,6 @@ tools:
 permission:
   task:
     "*": allow
-name: project-manager
-description: |-
-  项目经理 - 协调开发团队，管理项目进度。
-  Project Manager - coordinate the team, track progress, and orchestrate execution across roles.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/prompt-engineer.md

@@ -1,4 +1,9 @@
 ---
+name: prompt-engineer
+description: |-
+  提示词工程师 - 设计与优化 Agent 提示词与技能。
+  Prompt Engineer - design and optimize prompts and skills for agents, including refactoring and debugging prompt systems.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -8,10 +13,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: prompt-engineer
-description: |-
-  提示词工程师 - 设计与优化 Agent 提示词与技能。
-  Prompt Engineer - design and optimize prompts and skills for agents, including refactoring and debugging prompt systems.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/qa-engineer.md

@@ -1,4 +1,9 @@
 ---
+name: qa-engineer
+description: |-
+  测试工程师 - 编写测试用例和自动化测试。
+  QA Engineer - test planning, automated tests, coverage improvements, and regression protection.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -10,10 +15,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: qa-engineer
-description: |-
-  测试工程师 - 编写测试用例和自动化测试。
-  QA Engineer - test planning, automated tests, coverage improvements, and regression protection.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/qc-specialist-2.md

@@ -1,4 +1,9 @@
 ---
+name: qc-specialist-2
+description: |-
+  质量控制专家（Reviewer #2）- 代码审查和质量保证。
+  Quality Control Specialist (Reviewer #2) - code review and quality assurance after significant changes.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -90,10 +95,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: qc-specialist-2
-description: |-
-  质量控制专家（Reviewer #2）- 代码审查和质量保证。
-  Quality Control Specialist (Reviewer #2) - code review and quality assurance after significant changes.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/qc-specialist-3.md

@@ -1,4 +1,9 @@
 ---
+name: qc-specialist-3
+description: |-
+  质量控制专家（Reviewer #3）- 代码审查和质量保证。
+  Quality Control Specialist (Reviewer #3) - code review and quality assurance after significant changes.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -90,10 +95,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: qc-specialist-3
-description: |-
-  质量控制专家（Reviewer #3）- 代码审查和质量保证。
-  Quality Control Specialist (Reviewer #3) - code review and quality assurance after significant changes.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/qc-specialist.md

@@ -1,4 +1,9 @@
 ---
+name: qc-specialist
+description: |-
+  质量控制专家（Reviewer #1）- 代码审查和质量保证。
+  Quality Control Specialist (Reviewer #1) - code review and quality assurance after significant changes.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -90,10 +95,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: qc-specialist
-description: |-
-  质量控制专家（Reviewer #1）- 代码审查和质量保证。
-  Quality Control Specialist (Reviewer #1) - code review and quality assurance after significant changes.
 ---
 
 ## Morning Star Role Binding

package/harness-agents/writing-specialist.md

@@ -1,4 +1,9 @@
 ---
+name: writing-specialist
+description: |-
+  写作专家 - 文档写作、小说写作、文案写作与脚本写作。
+  Writing Specialist - documentation, fiction, copywriting, and script writing.
+model: inherit
 mode: subagent
 tools:
   write: true
@@ -10,10 +15,6 @@ permission:
   task:
     "*": deny
     explore: allow
-name: writing-specialist
-description: |-
-  写作专家 - 文档写作、小说写作、文案写作与脚本写作。
-  Writing Specialist - documentation, fiction, copywriting, and script writing.
 ---
 
 ## Morning Star Role Binding

package/harness-skills/mstar-host/references/cursor.md

@@ -41,7 +41,7 @@ Enforcement: `rules/mstar-cursor-plan-mode.mdc` when plugin active.
 ## Task tool (QC tri-review)
 
 - Apply **`parallel-dispatch.md`**: prerequisite message may prep only; dispatch message emits **all `N`** Tasks (**3** for tri-review) in **one** message when parallel is required.
-- `subagent_type`: `qc-specialist`, `qc-specialist-2`, `qc-specialist-3`.
+- `subagent_type`: bare role ids — `qc-specialist`, `qc-specialist-2`, `qc-specialist-3` (same for implement roles: `fullstack-dev`, `frontend-dev`, etc.).
 - Identical across three Tasks: **`plan_id`**, **`Review cwd`**, **`Review range` / Diff basis** (`mstar-branch-worktree`, `mstar-dispatch-gates`, `mstar-review-qc`).
 - Parallel QC ≠ different review cwd per reviewer; one integrated HEAD for scope.
 - Status Update may note QC ran via parallel Task subagents.

package/harness-skills/mstar-plan-artifacts/SKILL.md

@@ -15,7 +15,7 @@ description: Morning Star plan harness artifacts — `{PLAN_DIR}` main plans and
 | knowledge / iterations / specs boundaries and indexes | `references/knowledge-and-designs.md` |
 | Done row compaction Profile A/B | `references/done-compaction.md` |
 | `status.json`, residual severity, lifecycle, `jq` | `references/status-and-residuals.md` |
-| Empty-repo `status.json` / `notes.json` templates | `templates/status.empty.json`, `templates/notes.empty.json` (`templates/README.md`) |
+| Empty-repo `status.json` / `notes.json` / Profile B `plans-done.json` templates | `templates/status.empty.json`, `templates/notes.empty.json`, `templates/plans-done.empty.json` (`templates/README.md`) |
 | Tech-debt rollup (read-only) | `scripts/tech-debt-rollup.sh` |
 
 **Out of scope:** branch and QC/QA checkout alignment → **`mstar-branch-worktree`**; QC checklist and verdict → **`mstar-review-qc`**; `{HARNESS_DIR}` discovery and init → **`mstar-plan-conventions`**.

package/harness-skills/mstar-plan-artifacts/references/done-compaction.md

@@ -22,32 +22,42 @@
 - **可选**（人类扫表友好，非必须）：**`title`** 一行、**`done_at`**；勿把长叙述塞回热行——放进 **`{HARNESS_DIR}/notes.json`** 或依赖冷快照 / `reports/`。
 - 一旦快照已写入，热行**不得**再承载完整 `gates`、`qc_status`、`tests`、`commits`、长 `description`/`scope` 等；**以 `archived_record` 指向文件为准**。
 - 单条 **`plans[].notes`** 字符串若仍在用，保持**极短**（如指向 `reports/<plan-id>/`）；**不要**重复 QC 报告大段原文。
+- **可选索引**：`{HARNESS_DIR}/archived/plans/_index.json` — `plan-id` → 相对路径，便于不依赖 glob 的工具。
+- **可选滚动保留**：进一步缩小 `plans[]` 时，可只在热文件中保留**最近窗口**的瘦 `Done` 行，更旧 id 仅出现在 `_index.json` 与快照文件中；若采用，须在项目 `AGENTS.md` 中写明，并检查依赖「热文件中必有全部历史 id」的脚本。
 
 ## Profile B（可选）— 热文件不保留任何 `Done` 行（统一压缩）
 
-- **Done 快照路径**：`{HARNESS_DIR}/archived/plans/<plan-id>.json`（保存完整 `plans[]` 行快照）。
-- **Done 目录路径**：`{HARNESS_DIR}/archived/plans-done.json`（最小索引，便于统一发现已完成计划）。
-- **`plans-done.json` 推荐最小字段**：`id`、`title`、`done_at`、`plan_file`、`archived_record`。
-- **热文件行为**：`status.json.plans[]` 只保留非 `Done`（`Todo` / `InProgress` / `InReview` / `Blocked`）；计划变为 `Done` 后，从热文件移除该行。
-- **读取约定**：当前执行状态读取 `status.json`；历史 `Done` 列表读取 `archived/plans-done.json`，详情读取 `archived/plans/<plan-id>.json`。
+- **Done 快照路径**：`{HARNESS_DIR}/archived/plans/<plan-id>.json` — 单个 **`plans[]` 行对象**（含当时全部 `metadata`）；**不是**包装层，勿再套 `plan_id` / `snapshot` 外壳。
+- **Done 目录路径**：`{HARNESS_DIR}/archived/plans-done.json` — **仅** plan id 列表（见下）；**勿**使用 `_index.json`、对象数组目录或其它并行索引。
+- **`plans-done.json` schema（唯一权威；不得扩展）**：
+
+```json
+{
+  "plans": ["01-data-infrastructure", "02-auth-refactor"]
+}
+```
+
+  - 根对象**只允许**键 **`plans`**（字符串数组）。
+  - 数组元素为 **`plans[].id`**（= `archived/plans/<plan-id>.json` 的 basename；通常亦为主 plan `.md` 去扩展名）。
+  - 标题、`done_at`、主 plan 路径、`archived_record` 等**只**存在于 `archived/plans/<plan-id>.json` 快照内。
+  - 初始化：`mstar-plan-artifacts/templates/plans-done.empty.json` → `{ "plans": [] }`。
+- **热文件行为**：`status.json.plans[]` 只保留非 `Done`；`Done` 后从热文件**删除**该行。
+- **读取约定**：活跃计划 → `status.json`；历史 Done id 列表 → `plans-done.json`.`plans`；单条详情 → `archived/plans/<plan-id>.json`（路径由 id 拼接，**不**读目录内嵌路径字段）。
 
 ## 原子更新约束（Profile A / B 通用）
 
 - 将计划标记为 `Done` 时，冷快照写入与 `status.json` 更新应在**同一变更集**完成（或紧随合并后一次性完成）。
 - 采用 **Profile B** 时，必须在同一变更集中同时完成：  
   1) 写入/更新 `archived/plans/<plan-id>.json`，  
-  2) 写入/更新 `archived/plans-done.json`，  
+  2) 将 `<plan-id>` 追加进 `archived/plans-done.json` 的 **`plans`** 数组（去重；勿写额外字段），  
   3) 从 `status.json.plans[]` 删除该 `Done` 行。  
 - 若无法满足以上三步，视为未完成 `Done` 收口，不应宣称已完成压缩迁移。
 
-**可选索引**：`{HARNESS_DIR}/archived/plans/_index.json` — `plan-id` → 相对路径，便于不依赖 glob 的工具。
-
-**可选滚动保留**：进一步缩小 `plans[]` 时，可只在热文件中保留**最近窗口**的瘦 `Done` 行，更旧 id 仅出现在 `_index.json` 与快照文件中；若采用，须在项目 `AGENTS.md` 中写明，并检查依赖「热文件中必有全部历史 id」的脚本。
-
 ## 采纳说明
 
 - 未写快照、热文件中仍保留完整 `Done` 行在历史仓库里依然可读；但新落地时建议先确定并固定使用 **Profile A** 或 **Profile B**，避免同仓混跑。
-- 从 Profile A 迁到 Profile B 前，先检查依赖 `status.json.plans[]` 扫描全部历史 `Done` 的脚本与流程，必要时先切换读取源到 `archived/plans-done.json`。
+- 从 Profile A 迁到 Profile B 前，先检查依赖 `status.json.plans[]` 扫描全部历史 `Done` 的脚本与流程，并改为读取 `archived/plans-done.json`.`plans`。
+- 若仓库 `plans-done.json` 仍为非 `{ "plans": [...] }` 形态（例如对象数组、顶层 `entries`/`catalog`），**整文件改写**为仅 id 列表；勿保留兼容层或双写富字段。
 
 ## 仓库级采用声明模板（贴到项目 `AGENTS.md`）
 
@@ -56,7 +66,7 @@
 ```markdown
 ### Plan compaction profile (this repository)
 
-This repository uses **Profile A** from the Morning Star `mstar-plan-conventions` skill (`references/done-compaction.md`).
+This repository uses **Profile A** from the Morning Star `mstar-plan-artifacts` skill (`references/done-compaction.md`).
 
 - `status.json.plans[]` keeps active plans and may keep **slim `Done` rows**.
 - `archived/plans/<plan-id>.json` is used as cold snapshot when available.
@@ -68,11 +78,11 @@ This repository uses **Profile A** from the Morning Star `mstar-plan-conventions
 ```markdown
 ### Plan compaction profile (this repository)
 
-This repository uses **Profile B** from the Morning Star `mstar-plan-conventions` skill (`references/done-compaction.md`).
+This repository uses **Profile B** from the Morning Star `mstar-plan-artifacts` skill (`references/done-compaction.md`).
 
 - `status.json.plans[]` keeps **non-`Done`** plans only.
 - Every `Done` plan MUST be represented in:
   - `archived/plans/<plan-id>.json` (full snapshot), and
-  - `archived/plans-done.json` (minimal catalog).
-- Historical `Done` discovery MUST read `archived/plans-done.json`, not `status.json.plans[]`.
+  - `archived/plans-done.json` (`{ "plans": ["<plan-id>", ...] }` only).
+- Historical `Done` discovery MUST read `archived/plans-done.json` **`plans`**, not `status.json.plans[]`; per-plan detail from `archived/plans/<plan-id>.json`.
 ```

package/harness-skills/mstar-plan-artifacts/templates/README.md

@@ -6,3 +6,4 @@ Copy these into `{HARNESS_DIR}` when bootstrapping a project. Path symbols (`{HA
 |------|---------|--------|
 | `status.empty.json` | `{HARNESS_DIR}/status.json` | Root `residual_findings` only (see **`mstar-plan-artifacts` SKILL.md**). Replace `updated_at` with the real date. |
 | `notes.empty.json` | `{HARNESS_DIR}/notes.json` | Optional program timeline. Replace `updated_at` when first edited. |
+| `plans-done.empty.json` | `{HARNESS_DIR}/archived/plans-done.json` | **Profile B only** — `{ "plans": [<plan-id>, ...] }` **only** (`references/done-compaction.md`). Append id on each `Done` compaction; no other keys or object elements. |

package/harness-skills/mstar-plan-artifacts/templates/plans-done.empty.json

@@ -0,0 +1,3 @@
+{
+  "plans": []
+}

package/harness-skills/mstar-plan-conventions/references/harness-bootstrap-and-agents-layering.md

@@ -15,10 +15,11 @@
 1. 创建 `{HARNESS_DIR}`（推荐 `.mstar/`）与 `{PLAN_DIR}`（推荐 `.mstar/plans/`）。
 2. 初始化 `status.json`：从 **`mstar-plan-artifacts/templates/status.empty.json`** 复制；residual canonical 见 **`mstar-plan-artifacts` SKILL.md**；字段与生命周期见 **`mstar-plan-artifacts/references/status-and-residuals.md`**。
 3. 初始化可选 `notes.json`（**`mstar-plan-artifacts/templates/notes.empty.json`**）与 `plans/reports/README.md`。
-4. 可选：创建 `{ITERATION_DIR}`（`iterations/` + `README.md`）与 `{KNOWLEDGE_DIR}`（`knowledge/` + `README.md`）；内容边界见 `mstar-plan-conventions` SKILL.md 与 `references/knowledge-and-designs.md`。
-5. 创建 `{HARNESS_DIR}/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工；新项目推荐 `.mstar/AGENTS.md`，已有项目可继续使用 `.agents/AGENTS.md`。
-6. 校准根 `AGENTS.md`：只保留仓库级长期约束，显式引用 `{HARNESS_DIR}/AGENTS.md` 作为 harness SSOT。
-7. 仅在确有稳定边界时新增目录级 `AGENTS.md`（如 `contracts/`、`gateway/`、`sdk/`）。
+4. **Profile B**（统一 Done 压缩）时另建 `{HARNESS_DIR}/archived/plans/` 与 `archived/plans-done.json`（自 **`mstar-plan-artifacts/templates/plans-done.empty.json`** 复制；schema 仅 `{ "plans": [] }`，见 **`mstar-plan-artifacts/references/done-compaction.md`**）。
+5. 可选：创建 `{ITERATION_DIR}`（`iterations/` + `README.md`）与 `{KNOWLEDGE_DIR}`（`knowledge/` + `README.md`）；内容边界见 `mstar-plan-conventions` SKILL.md 与 `references/knowledge-and-designs.md`。
+6. 创建 `{HARNESS_DIR}/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工；新项目推荐 `.mstar/AGENTS.md`，已有项目可继续使用 `.agents/AGENTS.md`。
+7. 校准根 `AGENTS.md`：只保留仓库级长期约束，显式引用 `{HARNESS_DIR}/AGENTS.md` 作为 harness SSOT。
+8. 仅在确有稳定边界时新增目录级 `AGENTS.md`（如 `contracts/`、`gateway/`、`sdk/`）。
 
 ## 三层 `AGENTS.md` 职责切分
 
@@ -29,7 +30,7 @@
 
 ### `{HARNESS_DIR}/AGENTS.md`（harness 层）
 
-- 放：`{HARNESS_DIR}`/`{PLAN_DIR}`/`{ITERATION_DIR}`/`{KNOWLEDGE_DIR}`/`{SPECS_DIR}` 契约、`docs/` 与 harness 子树内容边界、状态推进门禁、QC/QA 对齐规则、residual 生命周期、Done compaction profile。
+- 放：`{HARNESS_DIR}`/`{PLAN_DIR}`/`{ITERATION_DIR}`/`{KNOWLEDGE_DIR}`/`{SPECS_DIR}` 契约、`docs/` 与 harness 子树内容边界、状态推进门禁、QC/QA 对齐规则、residual 生命周期、Done compaction profile（Profile B 时声明 `archived/plans-done.json` 仅为 `{ "plans": [<plan-id>, ...] }`，细则见 **`mstar-plan-artifacts/references/done-compaction.md`**）。
 - 不放：语言/框架编码细节、业务模块实现约束。
 
 ### `<subdir>/AGENTS.md`（边界层）

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

@@ -21,7 +21,8 @@ Legacy fallbacks:
 2. Initialize `{HARNESS_DIR}/status.json` from template if available.
 3. Initialize reports path: `{PLAN_DIR}/reports/`.
 4. Initialize residual archive path: `{HARNESS_DIR}/archived/residuals/`.
-5. Optional: `{HARNESS_DIR}/notes.json`, `{HARNESS_DIR}/knowledge/README.md`.
+5. **Profile B** only: `{HARNESS_DIR}/archived/plans/` and `archived/plans-done.json` from `mstar-plan-artifacts/templates/plans-done.empty.json` (`{ "plans": [] }` only; see `done-compaction.md`).
+6. Optional: `{HARNESS_DIR}/notes.json`, `{HARNESS_DIR}/knowledge/README.md`.
 
 If legacy plan directories already exist, reuse them; avoid dual-structure duplication.
 

package/package.json

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