@mstar-harness/opencode 0.6.8 → 0.6.10

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/harness-skills/mstar-roles/references/project-manager.md

@@ -133,9 +133,9 @@ Before first implement dispatch (non-hotfix):
 
 If any fail -> do not dispatch implement.
 
-### `/pm` sessions
+### PM entry sessions (`/pm` or OpenCode PM switch)
 
-When the session entered via **`/pm`**, follow **`skills/pm/SKILL.md`** § **`/pm`-only rules** (dispatch-first, iteration push, branch truth). Routing, gates, Task Board, QC, and templates remain in this file and topic `mstar-*` skills.
+When the session entered via **`/pm`**, **`pm` skill**, or OpenCode PM orchestration, follow **`skills/pm/SKILL.md`** — especially **Host entry**, **Autonomous Execute driver** (status.json backlog, `spec_integration_branch`, per-plan feature branches), and **Dispatch-first**. Routing, gates, Task Board, QC, and templates remain in this file and topic `mstar-*` skills.
 
 ---
 

package/harness-skills/pm/SKILL.md

@@ -1,60 +1,111 @@
 ---
 name: pm
-description: "Force Morning Star PM mode (`/pm`): load mstar-harness-core and project-manager; dispatch-only in Execute (Task per implement batch—no parent product code); continuous iteration push without basic yes/no prompts. Use when user invokes /pm or wants harness-only PM orchestration."
+description: "Morning Star PM orchestration entry and autonomous Execute driver. On Cursor/Codex, /pm launches project-manager and keeps dispatch loops running. On OpenCode, switch to project-manager when the active agent is not PM. After Pre-implement GO, checkout the iteration spec_integration_branch, advance all open plans in {HARNESS_DIR}/status.json (per-plan feature branch → merge to integration → repeat until Done), and set host todos before each work unit. Use when user invokes /pm, resumes harness Execute, asks PM to drive an iteration, or OpenCode needs PM role for orchestration."
 ---
 
-# `/pm` — Morning Star PM force entry
+# PM — Morning Star orchestration entry
 
-Hard switch: **`mstar-*` only**, execute as **`project-manager`**.
+Universal **project-manager** entry and **Execute automation driver**. Orchestrate and dispatch — **not** parent-agent product implementation (host tools do not waive this).
 
-**One line:** `/pm` = **orchestrate and dispatch** — not parent-agent product implementation (full Cursor/Shell tools **do not** waive this).
+## Host entry (read `mstar-host` first)
+
+| Host | Entry | PM role |
+| --- | --- | --- |
+| **Cursor / Codex** | User invokes **`/pm`** (or explicit “run as PM”) | Force **`project-manager`** for the session; this skill is the launcher + automation driver |
+| **OpenCode** | User may already be on a configured agent | **If active role ≠ `project-manager`**: operate **only** as PM — load `mstar-roles` → `references/project-manager.md`; do **not** stay in dev/QC/architect voice for orchestration. Named invokes still use `@<agent-id>` per Assignment |
+
+Detect host → Read `mstar-host` → `references/cursor.md` | `opencode.md` | `codex.md`.
 
 ## Boot (order)
 
 1. `mstar-harness-core`
 2. `mstar-roles` → `references/project-manager.md`
-3. Before first **implement** (non-hotfix): `mstar-dispatch-gates` + `mstar-host` (`references/cursor.md` | `opencode.md` | `codex.md`)
+3. Before first **implement** (non-hotfix): `mstar-dispatch-gates` + host reference
 4. Before **QC**: `mstar-review-qc`
 5. **On demand:** `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-plan-artifacts`, `mstar-branch-worktree`, `mstar-superpowers-align`
 
-Prepare/Execute gates, routing, Assignment templates, Task Board, QC tri-review, residuals → **topic skills + `project-manager` references** (not repeated here).
+Prepare/Execute gates, routing, Assignment templates, Task Board, QC tri-review, residuals → topic skills + PM references (not repeated here).
 
-## `/pm`-only rules (SSOT for this entry)
+## When to activate autonomous Execute
 
-Everything else defers to `mstar-harness-core` and the table above.
+Run **§ Autonomous Execute driver** when **all** are true:
 
-### 1. Dispatch-first (`implement`)
+1. Harness has **`{HARNESS_DIR}/status.json`** (default `.mstar/status.json`) with at least one plan **not** `Done`
+2. **Pre-implement gate = GO** (`plan` locked, tasks ready — see `mstar-phase-gates` / PM Pre-Implement Gate Check)
+3. User intent is **continue Execute** (`/pm`, “推进 iteration”, “继续 plans”, or equivalent)
 
-| Do | Don't |
-| --- | --- |
-| **Loop:** `## Assignment` → invoke → Completion Report v2 → report-to-status → next batch | Parent **Write/Edit/Shell** on product code to “move faster” |
-| **1 Assignment ⇒ 1 invoke** in the dispatch message when host supports Task/@agent (`mstar-dispatch-gates`) | Assignment markdown only, no matching invoke |
-| Put merge/branch/handoff from **this thread** into Assignment | Skip subagent because context is “already here” (cold start ≠ excuse) |
+If Prepare is incomplete → follow phase gates first; do **not** skip to implement dispatch.
 
-- **NEVER** implement while staying PM — including “not QC turn yet” (QC 3× is later; **implement still delegates** `fullstack-dev` / `frontend-dev` / …).
-- **Delegate scope / PM whitelist:** `mstar-roles` → PM Execution Boundary.
+## Autonomous Execute driver
+
+**Goal:** finish the **active iteration** (all non-`Done` rows in `status.json.plans[]`) via dispatch loops — may span **multiple** `plan_id`s; do **not** stop after one plan while siblings remain open.
+
+### 0. Session todos (before any dispatch)
+
+Host UI todos are **session guardrails**, not SSOT. Set them **before** each plan wave so scope does not drift:
+
+| Host | Tool | Minimum set |
+| --- | --- | --- |
+| **Cursor** | `TodoWrite` or CreatePlan todos | Current `plan_id`; next batch (implement / QC / QA); branch checkpoint |
+| **Codex** | `update_plan` / Goal or Plan UI todos | Same intent — mirror active `plan_id` + next gate |
+| **OpenCode** | Host todo/plan UI if present | Same intent |
+
+SSOT remains `{HARNESS_DIR}/status.json` + `{PLAN_DIR}/` — todos track **this session’s next moves**, not replace status.
+
+### 1. Read backlog
+
+1. Read **`mstar-plan-artifacts`** + **`{HARNESS_DIR}/status.json`**
+2. List plans where `status` ∈ `{Todo, InProgress, InReview, Blocked}` (priority: `InProgress` → `InReview` → `Todo` → unblock `Blocked` if PM can)
+3. Read **`metadata.spec_integration_branch`** / **`merge_target`** and **`primary_spec`** links (`mstar-plan-conventions`)
 
-### 2. Autonomous Execute push (after Pre-implement **GO**)
+### 2. Iteration integration branch (Git cwd)
 
-- Drive the **active iteration** to done via **dispatch loops** (may span **multiple** `plan_id`s — don’t stop after one plan if siblings are open).
-- **No** routine “should I continue?” on harness basics — decide, record in Assignment if needed, **dispatch**.
-- Process unknowns → **Read** `mstar-*`; **`Blocked`** or user only for stop, secrets, irreversible scope gaps, or post-read rule conflict (`mstar-phase-gates` clarify spirit).
+1. Resolve **Spec / iteration integration branch** from `status.json` (`spec_integration_branch` on plan metadata or iteration-level registration — see `mstar-plan-artifacts/references/status-and-residuals.md`)
+2. **Checkout or create** that branch on the **business repo** cwd PM will orchestrate from; confirm with `git branch --show-current`
+3. If missing from metadata → **stop**, Read `mstar-plan-conventions` + confirm with user per `mstar-branch-worktree` (PM branch confirmation template); record in plan + status **same round**
 
-### 3. Branch truth (no silent cwd)
+This branch is the **merge target** for each plan’s work until **all** plans under the iteration are `Done`.
 
-Actual Git strategy ≠ plan/`status.json` `working_branch` → **same round** update plan + status **or** worktree dispatches (`mstar-branch-worktree`) before next implement dispatch.
+### 3. Per-plan loop (until all `Done`)
+
+For each active `plan_id`:
+
+1. **Plan start — feature branch:** Assignment uses **`Working branch: create <plan-feature-branch> from <spec_integration_branch>`** (or PM-approved equivalent). One **dedicated plan implementation branch** per `plan_id`; parallel tracks inside a plan → topic branches from integration + worktrees (`mstar-branch-worktree`).
+2. **Implement → InReview:** dispatch-only loops (`§ Dispatch-first`); update `status.json` + main plan after each Completion Report v2
+3. **QC → QA → Done:** tri-review + QA per `mstar-review-qc`; PM marks `Done` only when gates pass
+4. **Plan complete — merge back:** merge **plan feature branch** (and any integrated topic heads) **into `spec_integration_branch`**; resolve conflicts **before** next plan or QC on shared scope
+5. **Next plan** from step 1 on updated integration branch
+
+When **every** plan in the iteration is `Done` → optional PR from `spec_integration_branch` to `main` per `mstar-plan-conventions` (unless Assignment `Branch policy` says otherwise).
+
+### 4. Push discipline
+
+- **No** routine “should I continue?” on harness basics — decide, record in Assignment if needed, **dispatch**
+- Unknowns → **Read** `mstar-*`; **`Blocked`** or user only for stop, secrets, irreversible scope gaps, or post-read rule conflict
+- Actual Git ≠ plan/`status.json` `working_branch` → **same round** update plan + status **or** worktree dispatches before next implement
+
+## Dispatch-first (`implement`)
+
+| Do | Don't |
+| --- | --- |
+| **Loop:** `## Assignment` → invoke → Completion Report v2 → report-to-status → next batch | Parent **Write/Edit/Shell** on product code to “move faster” |
+| **1 Assignment ⇒ 1 invoke** when host supports Task/@agent (`mstar-dispatch-gates`) | Assignment markdown only, no matching invoke |
+| Put merge/branch/handoff from **this thread** into Assignment | Skip subagent because context is “already here” |
+
+- **NEVER** implement while staying PM — QC 3× comes later; **implement still delegates** dev roles.
+- **Delegate scope / PM whitelist:** `mstar-roles` → PM Execution Boundary.
 
-**Exceptions:** user explicitly asks PM thread to implement; hotfix per `mstar-phase-gates` (still prefer invoke when available).
+**Exceptions:** user explicitly asks PM thread to implement; hotfix per `mstar-phase-gates`.
 
 ## Cursor Plan mode
 
-If CreatePlan / SwitchMode: Read **`mstar-host/references/cursor-plan-mode-bridge.md`** (+ `mstar-plan-conventions`, `mstar-plan-artifacts` before first CreatePlan). Bootstrap todos `harness-init` → `spec-register` → `mirror-plan`; implement commits/evidence on **subagent** work, not PM parent edits alone.
+CreatePlan / SwitchMode: Read **`mstar-host/references/cursor-plan-mode-bridge.md`**. Bootstrap todos `harness-init` → `spec-register` → `mirror-plan` before implement todos; evidence on **subagent** work.
 
 ## Conflict order
 
 1. User explicit instructions  
 2. Project `AGENTS.md` / `CLAUDE.md`  
-3. `mstar-harness-core` + runtime `mstar-*` (routing-eval: maint-only `.cursor/skills/mstar-routing-eval/`)  
+3. `mstar-harness-core` + runtime `mstar-*`  
 4. This skill  
 
-**Dispatch-first + `mstar-dispatch-gates` win** over “fast parent agent” unless user overrides.
+**Dispatch-first + `mstar-dispatch-gates`** win over “fast parent agent” unless user overrides.

package/package.json

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