@mstar-harness/opencode 0.6.5 → 0.6.7

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

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

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

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

package/harness-agents/qc-specialist.md

@@ -5,13 +5,17 @@ tools:
   edit: true
   bash: true
 permission:
-  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (three possible roots — match project layout).
+  # `edit` covers write/patch/multiedit. Only `.md` under resolved `{PLAN_DIR}/reports/` (default + legacy roots).
   edit:
     "*": deny
+    ".mstar/plans/reports/*.md": allow
+    ".mstar/plans/reports/**/*.md": allow
     ".agents/plans/reports/*.md": allow
     ".agents/plans/reports/**/*.md": allow
     ".plans/reports/*.md": allow
     ".plans/reports/**/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/*.md": allow
+    ".worktrees/**/.mstar/plans/reports/**/*.md": allow
     ".worktrees/**/.agents/plans/reports/*.md": allow
     ".worktrees/**/.agents/plans/reports/**/*.md": allow
     ".worktrees/**/.plans/reports/*.md": allow

package/harness-skills/mstar-harness-core/SKILL.md

@@ -129,7 +129,7 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 | residual 只写 plan 不写 SSOT | `mstar-plan-artifacts` |
 | 角色文件塞流程长文 | 用专题 skill |
 | 无证据宣称完成 | `mstar-coding-behavior` / verification |
-| CreatePlan 不落盘 / 无 `.agents` mirror | `mstar-host` · `cursor-plan-mode-bridge` |
+| CreatePlan 不落盘 / 无 `{HARNESS_DIR}` mirror | `mstar-host` · `cursor-plan-mode-bridge` |
 | 临时方案 / 后续计划只写在对话里 | `mstar-phase-gates` · Durable Roadmap Gate |
 
 ## 可选：OpenViking Memory

package/harness-skills/mstar-host/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mstar-host
-description: Morning Star host adapter (OpenCode, Cursor, Codex). Use after mstar-harness-core whenever host entry, clarify, dispatch, or plan UX differs by platform - OpenCode question/@agent-id invoke, Cursor /pm and CreatePlan/SwitchMode dual-write and Task parallel QC, Codex plugin skills plus sandboxed tools/tool discovery. Auto-detect host from session tools; then Read references/<host>.md. Always load after mstar-harness-core.
+description: Morning Star host adapter (OpenCode, Cursor, Codex). Use after mstar-harness-core whenever host entry, clarify, dispatch, or plan UX differs by platform - OpenCode question/@agent-id invoke, Cursor /pm and CreatePlan/SwitchMode dual-write and Task parallel QC, Codex plugin skills plus Plan/Goal Mode, sandboxed tools, and tool discovery. Auto-detect host from session tools; then Read references/<host>.md. Always load after mstar-harness-core.
 ---
 
 # Morning Star Host Adapter
@@ -30,7 +30,7 @@ Use **capability signals** (not filesystem paths):
 | **CreatePlan** / **SwitchMode** available | `cursor` | `references/cursor.md`; Plan mode also `references/cursor-plan-mode-bridge.md` |
 | **`question`** tool or PM **`@<agent-id>`** subagent invoke | `opencode` | `references/opencode.md` |
 | **Task** + `subagent_type`, no CreatePlan | `cursor` | `references/cursor.md` |
-| **Codex app/CLI/plugin context**, `functions.*`, `codex_app.*`, `tool_search`, Browser plugin tools | `codex` | `references/codex.md` |
+| **Codex app/CLI/plugin context**, `/plan`, `/goal`, Goal tools, `functions.*`, `codex_app.*`, `tool_search`, Browser plugin tools | `codex` | `references/codex.md`; Plan/Goal mode also `references/codex-plan-goal-mode-bridge.md` |
 | Still ambiguous | - | Read sections in **`cursor.md`**, **`opencode.md`**, and **`codex.md`** that match tools you have; **`mstar-harness-core` wins** on conflict |
 
 ## Parallel dispatch (invoke-capable hosts)

package/harness-skills/mstar-host/references/codex-plan-goal-mode-bridge.md

@@ -0,0 +1,103 @@
+# Codex Plan / Goal Mode x Harness Bridge
+
+> **Load order**: Read **`mstar-harness-core`** first, then **`mstar-host`** and **`references/codex.md`**. When plan management is required, also read **`mstar-plan-conventions`** and **`mstar-plan-artifacts`** before creating or claiming any durable plan state. On conflict, **`mstar-harness-core`** wins.
+
+## Purpose
+
+Codex **Plan Mode** (`/plan`) and **Goal Mode** (`/goal`) are host collaboration surfaces:
+
+- **Plan Mode** helps shape a plan inside the active Codex conversation.
+- **Goal Mode** attaches a persistent objective and success criteria to the active thread.
+
+Morning Star durable state still lives under **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`). This reference prevents Codex session plans, UI todos, goal text, or goal completion from replacing the harness SSOT.
+
+## Priority (hard)
+
+1. User explicit instructions (this turn)
+2. Project `AGENTS.md` / `CLAUDE.md`
+3. **`{HARNESS_DIR}` / `{PLAN_DIR}` / `status.json`** (harness SSOT)
+4. Codex Goal Mode objective / progress controls
+5. Codex Plan Mode output, `update_plan`, UI todos, chat summaries
+
+**NEVER** cite only a Codex goal, session plan, UI todo, or chat summary in Assignment **Plan Path**, **Context Loaded**, or Completion Report when `{PLAN_DIR}/<plan-id>-<name>.md` should exist.
+
+## When this applies
+
+- Codex Plan Mode is active (`/plan`, Plan collaboration mode, or host guidance says planning-only).
+- Codex Goal Mode is active (`/goal`, host goal controls, or goal tools such as `create_goal`, `get_goal`, `update_goal`).
+- Morning Star plugin or `/pm` is in use under Codex.
+
+## Codex Plan Mode
+
+Use Plan Mode to clarify, inspect, compare approaches, and draft the harness plan. Do **not** treat Plan Mode output as a durable artifact.
+
+Before implementation or PM dispatch:
+
+1. Discover `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions`.
+2. Ensure `{HARNESS_DIR}/status.json` exists or initialize it via `mstar-plan-artifacts` templates.
+3. Register a `plans[]` row in `status.json` when a Morning Star plan is needed.
+4. Write `{PLAN_DIR}/<plan-id>-<name>.md` with task checkboxes, branch policy, verification, and roadmap / deferred scope when applicable.
+5. Use the SSOT plan path in Assignment and Completion Report evidence.
+
+Allowed in Plan Mode: exploration, clarify questions, spec/plan drafting, `.mstar/` initialization, SSOT plan/status edits, PM routing decisions.
+
+Not allowed by default in Plan Mode: product implementation, test implementation, QC execution, QA execution, deployment, or ops changes. Switch to normal execution or dispatch through an actual callable subagent/multi-agent tool first.
+
+## Codex Goal Mode
+
+Goal text is useful as the top-level objective and success criteria, but it is **not** a Morning Star plan, status ledger, PM Assignment, QC report, or QA Done authority.
+
+When starting or receiving a Goal Mode objective:
+
+1. If the goal is implementation-sized or long-running, create or update the harness SSOT (`status.json` + `{PLAN_DIR}` plan) before implementation.
+2. Mirror the goal's success criteria into the SSOT plan as acceptance / verification criteria.
+3. If the goal changes, update both Goal Mode text/progress and the SSOT plan/status in the same coordination round.
+4. If the goal conflicts with the SSOT, pause or report **Blocked** until PM/user resolves scope.
+
+### Goal completion gate
+
+Only mark a Codex goal complete when all applicable harness gates are satisfied:
+
+- Required plan checkboxes are complete in `{PLAN_DIR}`.
+- `status.json` reflects the current lifecycle state.
+- Required commits exist on the authorized branch.
+- Verification evidence is recorded.
+- QC/QA authority has passed when the plan requires InReview / Done gates.
+
+If the host asks to complete a goal but harness Done authority is missing, report **Blocked** and list the missing artifacts or gate decisions. Do not call a goal-completion tool as a substitute for PM/QC/QA evidence.
+
+## Resume / compaction
+
+Codex can resume threads and compact context. On resume, before editing product code:
+
+1. Reload `mstar-harness-core` -> `mstar-host` -> `references/codex.md` -> this bridge.
+2. If Goal Mode is active, read the current goal and compare it with `{HARNESS_DIR}/status.json` and the active SSOT plan.
+3. Treat `.mstar/` as durable truth over chat summaries or UI todos.
+4. If the active role or Assignment is missing, resume as PM for coordination and dispatch only.
+
+## `/pm` under Codex Plan / Goal Mode
+
+When `/pm` runs under Plan or Goal Mode:
+
+- `/pm` is still the force entry into Morning Star PM behavior.
+- Prepare phase (`specify -> clarify -> plan`) still applies unless the task qualifies for a documented hotfix path.
+- Goal Mode can hold the high-level objective, but PM must still write Assignment with `Execute as`, `Delegation`, branch policy, SSOT `Plan Path`, and evidence requirements.
+- Without an actual callable subagent/multi-agent tool, Assignment Markdown is coordination text only; execute serially in-session or report Blocked for rerouting.
+
+## Anti-patterns
+
+| Anti-pattern | Fix |
+|--------------|-----|
+| `/plan` output only, no `{HARNESS_DIR}` files | Write SSOT plan + `status.json` entry before implementation |
+| `update_plan` todo done, no commit/evidence | Commit or record required evidence before completion |
+| Goal objective treated as Done authority | Check harness plan/status/QC/QA gates first |
+| Goal changed but `.mstar/` still has old scope | Update Goal Mode and SSOT in the same round |
+| Resume starts coding from chat summary | Reload harness context and SSOT plan/status first |
+| Assignment Plan Path points at Codex transcript/goal | Use `{PLAN_DIR}/...` path |
+
+## Related skills
+
+- `mstar-plan-conventions` - discover `{HARNESS_DIR}`, `{PLAN_DIR}`, legacy layouts
+- `mstar-plan-artifacts` - `status.json`, plan checkboxes, reports, residuals
+- `mstar-phase-gates` - Prepare / Execute and Done authority
+- `mstar-dispatch-gates` - Assignment, Delegation, anti-recursion

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

@@ -1,6 +1,8 @@
 # Codex host reference
 
-Load when **`mstar-host`** detection resolves **codex** (Codex app/CLI session, Codex plugin installed from `.codex-plugin/plugin.json`, or Codex tool namespaces such as `functions.*`, `codex_app.*`, `tool_search`, `image_gen`, or Browser plugin tools).
+Load when **`mstar-host`** detection resolves **codex** (Codex app/CLI session, Codex plugin installed from `.codex-plugin/plugin.json`, Codex custom agents linked from `codex/agents/*.toml`, or Codex tool namespaces such as `functions.*`, `codex_app.*`, `tool_search`, `image_gen`, or Browser plugin tools).
+
+Plan / Goal Mode: read **`codex-plan-goal-mode-bridge.md`** when Codex Plan Mode (`/plan`) or Goal Mode (`/goal`, goal tools, or goal progress controls) is active. Codex session plans, UI todos, and goal text are not durable harness SSOT.
 
 Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an actual multi-agent / Task-style invocation tool. If no callable invoke tool exists, Assignment Markdown is coordination text only; do **not** claim subagent dispatch.
 
@@ -8,16 +10,18 @@ Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an
 
 - Plugin source: `.codex-plugin/plugin.json`.
 - Runtime skills: repo `skills/` mounted by the Codex plugin (`"skills": "./skills/"`).
+- Custom agent source: repo `codex/agents/*.toml`; CLI/manual install links these into `~/.codex/agents/` or project `.codex/agents/`.
 - `/pm`: shared force entry via the `pm` skill; after that, role behavior comes from `mstar-roles`.
-- Role files under `agents/` are for hosts that load agent shells; Codex role execution should load `mstar-roles` references directly.
+- Role files under root `agents/` are for hosts that load OpenCode/Cursor-style agent shells; Codex uses `codex/agents/*.toml` and still loads `mstar-roles` references directly.
 - Tool and plugin availability can be lazy-loaded or session-dependent. Use the tools actually present in the current session; do not infer capability from documentation alone.
 
 ## Skill loading
 
 1. Read `mstar-harness-core`.
 2. Read `mstar-host` and this Codex reference.
-3. Load `mstar-roles` and the active role reference.
-4. Load topic skills on demand per the role reference.
+3. If Plan Mode or Goal Mode is active, read `codex-plan-goal-mode-bridge.md`.
+4. Load `mstar-roles` and the active role reference.
+5. Load topic skills on demand per the role reference.
 
 Use skill names in prompts and references. Avoid absolute local paths unless the user is maintaining this repository or the skill is not installed and must be read from the checkout.
 
@@ -27,11 +31,12 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 - If a structured user-input tool is available in the active mode, use it for concise 1-3 choice decisions.
 - Otherwise ask one concise Markdown question only after codebase exploration cannot answer it.
 - `update_plan` / local todo UI is session progress only; it does not replace `{PLAN_DIR}` plans or `{HARNESS_DIR}/status.json`.
+- Codex Goal Mode objective is completion criteria for the host thread, not Morning Star Done authority; mirror it into the SSOT plan when the work is implementation-sized.
 
 ## Dispatch and role execution
 
-- **No invoke tool = no dispatch**: printing `## Assignment` does not start another Codex worker.
-- If Codex exposes multi-agent tools, PM may dispatch through those tools and must follow `parallel-dispatch.md`.
+- **No invoke tool / no linked custom agent = no dispatch**: printing `## Assignment` does not start another Codex worker.
+- If Codex exposes custom-agent / multi-agent tools and matching Morning Star agents are linked, PM may dispatch through those tools and must follow `parallel-dispatch.md`.
 - If no invoke tool is present, use single-session role execution: state the active role, load that role reference, complete the assignment, and return Completion Report v2.
 - QC tri-review is only "parallel" when three distinct callable reviewer sessions are actually launched in one dispatch turn. Without that, run a clearly labeled serial/manual review path or return `Blocked` for PM rerouting.
 - Leaf executors still follow `mstar-dispatch-gates`: no recursive Task/subagent calls unless Assignment says `Delegation: allowed (...)`.
@@ -51,6 +56,6 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 
 ## Gotchas
 
-- Codex plugin install gives skills, not automatic OpenCode-style named role invocations.
+- Codex plugin install gives skills; Morning Star role subagents require custom agent TOML files linked from `codex/agents/`.
 - Tool discovery (`tool_search`) can reveal capabilities, but availability is not authorization; Assignment `Delegation` still controls use.
-- Session plans, chat summaries, and UI todos are not durable harness SSOT unless mirrored to `{HARNESS_DIR}`.
+- Session plans, Goal Mode text, chat summaries, and UI todos are not durable harness SSOT unless mirrored to `{HARNESS_DIR}`.

package/harness-skills/mstar-host/references/cursor-plan-mode-bridge.md

@@ -4,7 +4,7 @@
 
 ## Purpose
 
-Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX. Morning Star **SSOT** lives on disk under **`{HARNESS_DIR}`** (default `.agents/`). This reference defines **dual-write**: mirror every durable plan artifact to the repo; never treat the Cursor plan URI alone as the handoff surface.
+Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX. Morning Star **SSOT** lives on disk under **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`). This reference defines **dual-write**: mirror every durable plan artifact to the repo; never treat the Cursor plan URI alone as the handoff surface.
 
 ## Priority (hard)
 
@@ -23,7 +23,7 @@ Cursor **Plan mode** uses **CreatePlan** and built-in plan todos for session UX.
 ## Before the first CreatePlan
 
 1. **Read** (minimum): `mstar-plan-conventions`, `mstar-plan-artifacts` (SKILL.md); Prepare gates from `mstar-phase-gates` if not hotfix.
-2. **Discover** `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions` (prefer `.agents/` + `.agents/plans/`).
+2. **Discover** `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions` (prefer `.mstar/` + `.mstar/plans/`; reuse legacy `.agents/` only when already present and `.mstar/` is absent).
 3. **Initialize** if absent (see checklist below).
 
 ### Harness initialization checklist
@@ -58,7 +58,7 @@ Add one object to `status.json` → `plans[]`:
 {
   "id": "<plan-id>",
   "status": "Todo",
-  "file": ".agents/plans/<plan-id>-<short-name>.md",
+        "file": ".mstar/plans/<plan-id>-<short-name>.md",
   "metadata": {
     "primary_spec": "<spec-id or path if known>",
     "description": "<one-line summary>"
@@ -66,7 +66,7 @@ Add one object to `status.json` → `plans[]`:
 }
 ```
 
-Set `updated_at` on `status.json` to today (`YYYY-MM-DD`). Commit harness files in the **business repo** when the project tracks `.agents/` (default).
+Set `updated_at` on `status.json` to today (`YYYY-MM-DD`). Commit harness files in the **business repo** when the project tracks `{HARNESS_DIR}` (default).
 
 ### `mirror-plan` minimum content
 
@@ -85,9 +85,9 @@ Use this structure in CreatePlan `plan` markdown; mirror the same sections into
 # Plan: <title>
 
 **plan_id**: <plan-id>
-**HARNESS_DIR**: .agents/
-**Plan file (SSOT)**: .agents/plans/<plan-id>-<short-name>.md
-**status.json**: .agents/status.json
+**HARNESS_DIR**: .mstar/
+**Plan file (SSOT)**: .mstar/plans/<plan-id>-<short-name>.md
+**status.json**: .mstar/status.json
 
 ## Prepare gates
 
@@ -107,9 +107,9 @@ Use this structure in CreatePlan `plan` markdown; mirror the same sections into
 
 ### Bootstrap (fixed prefix — complete before implement)
 
-1. harness-init — init .agents/, status.json, reports/, archived/residuals/
+1. harness-init — init .mstar/, status.json, reports/, archived/residuals/
 2. spec-register — register plan_id in status.json; spec stub if applicable
-3. mirror-plan — write .agents/plans/<plan-id>-<short-name>.md
+3. mirror-plan — write .mstar/plans/<plan-id>-<short-name>.md
 
 ### Implement
 
@@ -187,7 +187,7 @@ When `/pm` runs under Plan mode:
 
 | Anti-pattern | Fix |
 |--------------|-----|
-| CreatePlan only, no `.agents/` files | Run bootstrap todos; Write mirror plan + status.json |
+| CreatePlan only, no `{HARNESS_DIR}` files | Run bootstrap todos; Write mirror plan + status.json |
 | Todo done, no commit | Commit per task; paste `git log -1` evidence |
 | Drift between CreatePlan and SSOT plan | Update both in same round |
 | Cursor plan URI as Plan Path | Use `{PLAN_DIR}/...` path |

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

@@ -11,7 +11,7 @@ Parallel PM dispatch: **`parallel-dispatch.md`** (Task tool uses same turn model
 
 ## Plan mode × harness dual-write
 
-When **Plan mode** is active, **CreatePlan is session UX**; SSOT is **`{HARNESS_DIR}`** (default `.agents/`) — `{PLAN_DIR}/<plan-id>-<name>.md`, `{HARNESS_DIR}/status.json`.
+When **Plan mode** is active, **CreatePlan is session UX**; SSOT is **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`) — `{PLAN_DIR}/<plan-id>-<name>.md`, `{HARNESS_DIR}/status.json`.
 
 Before first **CreatePlan**: Read `mstar-plan-conventions`, `mstar-plan-artifacts`, Prepare gates from `mstar-phase-gates` when not hotfix. Full procedure: **`cursor-plan-mode-bridge.md`**.
 

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

@@ -22,10 +22,10 @@
 
 ## `{ITERATION_DIR}`（可选·迭代/版本级 compass）
 
-- **物理路径**：`**{ITERATION_DIR}/**`（推荐布局下常为 `**.agents/iterations/**`，与 `{KNOWLEDGE_DIR}`、`{PLAN_DIR}` 并列）。
+- **物理路径**：`**{ITERATION_DIR}/**`（推荐布局下常为 `**.mstar/iterations/**`，与 `{KNOWLEDGE_DIR}`、`{PLAN_DIR}` 并列；legacy 项目可继续为 `.agents/iterations/`）。
 - **放什么**：某一**交付版本或迭代**的范围、里程碑、验收、风险、program 备注；命名示例 `v1.15-delivery-compass-v1.md`、`*-program-compass-*.md`；遗留非标准 `v1.*` 规划快照可保留于此并列入索引。
 - **不放什么**：可跨版本复用的实现 SSOT（进 `{KNOWLEDGE_DIR}`）；冻结产品/API 规范（进 `{SPECS_DIR}`）；单 plan 的 QC 留档（进 `{PLAN_DIR}/reports/`）。
-- **索引**：**必须**维护 `**{ITERATION_DIR}/README.md**`：至少 **Document**、**Version / iteration**、**Description**；可按「Delivery compasses」与「Legacy artifacts」分表（参考 Nexus `.agents/iterations/README.md`）。
+- **索引**：**必须**维护 `**{ITERATION_DIR}/README.md**`：至少 **Document**、**Version / iteration**、**Description**；可按「Delivery compasses」与「Legacy artifacts」分表。
 - **与 plan 的链接**：在 `**plans[].metadata**` 中可用 `**iteration_compass**`（单文件）或 `**iteration_refs**`（`string[]`）登记仓库内相对路径；PM 在 Assignment 点名本轮须读的 compass。
 - **维护**：`@product-manager` / `@architect` 起草；`**@project-manager**` 维护 README 与 metadata 挂接；compass 定稿后**少改多版本**（新版本优先新文件名 `v<N>` 或新 compass 文件）。
 
@@ -44,7 +44,7 @@
 
 ## 与 `status.json` 的链接
 
-- 某 plan 的**权威设计输入**在知识库、迭代 compass 或规格目录中时，在 `**plans[].metadata**` 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）、`**spec_refs**`（`string[]`）、`**iteration_compass**` / `**iteration_refs**`（迭代级，可选）。路径为**仓库内相对路径**（推荐布局下常写作 `**.agents/knowledge/....md**`、`**.agents/iterations/....md**` 或 `**.agents/specs/....md**`；兼容旧目录时也可为 `**.agents/designs/....md**`）。
+- 某 plan 的**权威设计输入**在知识库、迭代 compass 或规格目录中时，在 `**plans[].metadata**` 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）、`**spec_refs**`（`string[]`）、`**iteration_compass**` / `**iteration_refs**`（迭代级，可选）。路径为**仓库内相对路径**（推荐布局下常写作 `**.mstar/knowledge/....md**`、`**.mstar/iterations/....md**` 或 `**.mstar/specs/....md**`；兼容旧目录时也可为 `.agents/...`）。
 - 执行方在 **implement 前**须按 metadata 读取这些文件，并与主 plan 核对；不得在未读链接文档的情况下**静默偏离**其中已写明的决策（若需偏离，先回写 knowledge 或 plan 并走 PM/architect 门禁）。
 
 ## 维护规则
@@ -83,4 +83,4 @@
 
 **维护**：`**@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」的状态。
+**关闭与归档**：当该条从 **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」的状态。

package/harness-skills/mstar-plan-artifacts/references/plan-files-and-reports.md

@@ -44,7 +44,7 @@
 - **并行 vs 串行**：不同 `plan_id` **相互独立**时，可 **并行**派发多组三审（每组各自的 Assignment 与 `reports/<plan-id>/`）；若 PM 选择串行，须在 Status Update 写明顺序——**每组仍须完整三审 + QA**，不是「一个大 QC」混审。
 - **读 skill**：书写或派发 QC 相关 Assignment 前，PM **必须** Read **`mstar-review-qc`** skill（`mstar-plan-conventions` 不重复 QC 清单与 verdict 规则）。见 `mstar-plan-conventions` SKILL.md **QC pre-dispatch gate** 与 **InReview 与 QC+QA** 小节。
 
-**QC 落盘与宿主权限**：`@qc-specialist` / `@qc-specialist-2` / `@qc-specialist-3` 在支持路径白名单的宿主上（如 OpenCode 的 **`permission.edit`**），**仅可** Write/Edit **`{PLAN_DIR}/reports/`** 下 **`.md`**（全局 agent 提示词中已配置 `.agents/plans/reports/**`、`.plans/reports/**`、`plans/reports/**` 相对路径）。报告文件**必须**以 YAML **frontmatter** 开头（键见各 QC agent 提示词）。**若** 项目的 `{PLAN_DIR}` 不落在上述三种根下，须在**项目级**宿主配置（如 OpenCode）中为 QC 角色追加对应的 `edit` allow 规则。
+**QC 落盘与宿主权限**：`@qc-specialist` / `@qc-specialist-2` / `@qc-specialist-3` 在支持路径白名单的宿主上（如 OpenCode 的 **`permission.edit`**），**仅可** Write/Edit **`{PLAN_DIR}/reports/`** 下 **`.md`**（全局 agent 提示词中已配置 `.mstar/plans/reports/**`、`.agents/plans/reports/**`、`.plans/reports/**`、`plans/reports/**` 相对路径）。报告文件**必须**以 YAML **frontmatter** 开头（键见各 QC agent 提示词）。**若** 项目的 `{PLAN_DIR}` 不落在上述根下，须在**项目级**宿主配置（如 OpenCode）中为 QC 角色追加对应的 `edit` allow 规则。
 
 **QC 报告与 Git**：报告落盘后，各 QC 角色须在业务仓内对**本次报告文件**执行 **`git add` + `git commit`**（细则与 bash 权限见 `agents/qc-specialist*.md`）；**禁止**仅落盘不提交导致 `clone` 后不可见。**PM / architect / product-manager** 对 **`{HARNESS_DIR}`** / **`{PLAN_DIR}`** 与主 plan 的创建与更新亦须在业务仓内 **commit**（见 `agents/project-manager.md` Plan 初始化与 PM 职责、`agents/architect.md` / `agents/product-manager.md` Git 小节）。
 

package/harness-skills/mstar-plan-artifacts/references/status-and-residuals.md

@@ -241,10 +241,10 @@ Prefer **`archived/residuals/`**; migrate and delete history key when possible.
 ### Query open and archived (examples)
 
 ```bash
-# Replace .agents with your resolved {HARNESS_DIR}.
-jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .agents/status.json
-jq '.entries[] | select(.id == "R1")' .agents/archived/residuals/01-data-infrastructure.json
-bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .agents/status.json
+# Replace .mstar with your resolved {HARNESS_DIR}; legacy projects may use .agents.
+jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .mstar/status.json
+jq '.entries[] | select(.id == "R1")' .mstar/archived/residuals/01-data-infrastructure.json
+bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .mstar/status.json
 ```
 
 (`//` right-hand side = legacy read path.)
@@ -277,8 +277,8 @@ Append-only log for merge closure, batch archive, `tech_debt_summary` refresh, e
 **Compute (canonical):** run the read-only script (do **not** hand-count):
 
 ```bash
-# From repo root; pass path to status.json if not .agents/status.json
-bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .agents/status.json
+# From repo root; pass path to status.json if not .mstar/status.json
+bash skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh .mstar/status.json
 ```
 
 - Prints computed `total_open`, `by_severity`, `by_target`, `by_plan`.
@@ -328,11 +328,11 @@ Before merge/PR, **`@project-manager`** (or delegate) should verify: `plans[].st
 
 - Read: accept `id` or `plan_id`.
 - Write: one canonical key (prefer `id`).
-- Document canonical key in `.agents/AGENTS.md` if migrating.
+- Document canonical key in `{HARNESS_DIR}/AGENTS.md` if migrating.
 
 ## Common queries
 
 ```bash
-jq '.plans[] | select(.id == "01-data-infrastructure")' .agents/status.json
-jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .agents/status.json
+jq '.plans[] | select(.id == "01-data-infrastructure")' .mstar/status.json
+jq '.residual_findings["01-data-infrastructure"] // .metadata.residual_findings["01-data-infrastructure"]' .mstar/status.json
 ```

package/harness-skills/mstar-plan-artifacts/scripts/tech-debt-rollup.sh

@@ -3,7 +3,7 @@
 # Does not write status.json — PM applies output manually.
 set -euo pipefail
 
-STATUS_FILE="${1:-.agents/status.json}"
+STATUS_FILE="${1:-.mstar/status.json}"
 
 if [[ ! -f "$STATUS_FILE" ]]; then
   echo "error: status file not found: $STATUS_FILE" >&2

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-plan-conventions
-description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Superpowers `writing-plans` 落盘门限、工期预估（agent-oriented）。**必须**在读写 `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
+description: Morning Star (启明星) harness 计划目录约定 —— `{HARNESS_DIR}` / `{PLAN_DIR}` / `{ITERATION_DIR}` / `{KNOWLEDGE_DIR}` / `{SPECS_DIR}` 发现与初始化（默认 `.mstar/`，兼容 `.agents/`）、`docs/` 与 harness 子树边界、未启用 plan 时的工作方式、Spec 集成分支与多 Plan 实现分支（merge 靶与 PR 合 main）、Superpowers `writing-plans` 落盘门限、工期预估（agent-oriented）。**必须**在读写 `.mstar/` / `.agents/`、初始化 harness、编排含 plan 的任务、或对齐 `metadata.primary_spec` 时 Read；`@project-manager` 开 plan 任务前必读。plan 文件 / status / residual / reports / knowledge → **`mstar-plan-artifacts`**；分支与 QC 检出 → **`mstar-branch-worktree`**。
 ---
 
 ## Load order（必读顺序）
@@ -17,7 +17,7 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 | 符号 | 默认 |
 |------|------|
-| `{HARNESS_DIR}` | `.agents/` |
+| `{HARNESS_DIR}` | `.mstar/` |
 | `{PLAN_DIR}` | `{HARNESS_DIR}/plans/` |
 | `{ITERATION_DIR}` | `{HARNESS_DIR}/iterations/` |
 | `{KNOWLEDGE_DIR}` | `{HARNESS_DIR}/knowledge/` |
@@ -25,11 +25,12 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 ### 解析顺序（找到即停）
 
-1. `.agents/` → `{HARNESS_DIR}=.agents/`, `{PLAN_DIR}=.agents/plans/`
-2. 否则 `.plans/` 或 `plans/` → 遗留同目录 `{HARNESS_DIR}={PLAN_DIR}`
-3. 皆无 → 未启用 plan；进度走对话与 Completion Report
+1. `.mstar/` → `{HARNESS_DIR}=.mstar/`, `{PLAN_DIR}=.mstar/plans/`
+2. 否则 `.agents/` → legacy `{HARNESS_DIR}=.agents/`, `{PLAN_DIR}=.agents/plans/`
+3. 否则 `.plans/` 或 `plans/` → 遗留同目录 `{HARNESS_DIR}={PLAN_DIR}`
+4. 皆无 → 未启用 plan；进度走对话与 Completion Report
 
-并存时 **`.agents/` 优先**。
+并存时 **`.mstar/` 优先**；仅当项目已有 `.agents/` 且无 `.mstar/` 时继续沿用 `.agents/`。
 
 `{SPECS_DIR}`：有 `specs/` 用之；否则 `designs/`；皆无则建议新建 `specs/`。
 
@@ -49,11 +50,11 @@ description: Morning Star (启明星) harness 计划目录约定 —— `{HARNES
 
 PM 在需要持久化追踪时：
 
-1. 建 `.agents/`、`plans/`、`status.json`（空模板见 **`mstar-plan-artifacts/templates/status.empty.json`**）
+1. 建 `.mstar/`、`plans/`、`status.json`（空模板见 **`mstar-plan-artifacts/templates/status.empty.json`**）
 2. 可选 `notes.json`（模板 **`mstar-plan-artifacts/templates/notes.empty.json`**）、`reports/README.md`、`knowledge/`、`iterations/`、`specs/`
 3. Git：团队交付 **勿** ignore 整个 `{HARNESS_DIR}`（handoff 需 clone 可达）
 
-步骤与 `.agents/AGENTS.md` 分层 → **`references/harness-bootstrap-and-agents-layering.md`**。
+步骤与 `{HARNESS_DIR}/AGENTS.md` 分层 → **`references/harness-bootstrap-and-agents-layering.md`**。
 
 ## Spec 驱动的分支模型（多 Plan · 同一 Spec）
 

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

@@ -12,12 +12,12 @@
 
 ## Bootstrap 最小步骤
 
-1. 创建 `{HARNESS_DIR}`（推荐 `.agents/`）与 `{PLAN_DIR}`（推荐 `.agents/plans/`）。
+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. 创建 `.agents/AGENTS.md`（harness 子树规则）：符号表可复述 `{HARNESS_DIR}`、`{PLAN_DIR}`、`{ITERATION_DIR}`、`{KNOWLEDGE_DIR}`、`{SPECS_DIR}` 与 `docs/` 分工（参考 Nexus `.agents/AGENTS.md`）。
-6. 校准根 `AGENTS.md`：只保留仓库级长期约束，显式引用 `.agents/AGENTS.md` 作为 harness SSOT。
+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/`）。
 
 ## 三层 `AGENTS.md` 职责切分
@@ -27,7 +27,7 @@
 - 放：仓库身份、技术边界、构建/测试接口、安全与分支策略、规格路由表。
 - 不放：动态状态、当前批次进展、R# 明细、QC 单次结论。
 
-### `.agents/AGENTS.md`（harness 层）
+### `{HARNESS_DIR}/AGENTS.md`（harness 层）
 
 - 放：`{HARNESS_DIR}`/`{PLAN_DIR}`/`{ITERATION_DIR}`/`{KNOWLEDGE_DIR}`/`{SPECS_DIR}` 契约、`docs/` 与 harness 子树内容边界、状态推进门禁、QC/QA 对齐规则、residual 生命周期、Done compaction profile。
 - 不放：语言/框架编码细节、业务模块实现约束。
@@ -56,7 +56,7 @@
 1. Current user instruction
 2. Root `AGENTS.md`
 3. This file
-4. `.agents/AGENTS.md`
+4. `{HARNESS_DIR}/AGENTS.md`
 
 ## Boundary Rules
 - ...
@@ -74,7 +74,7 @@
   修正：迁移到 `status.json` 的 `plans[].metadata` 与 `notes.json`。
 
 - 反模式：每个子目录复制一份完整 harness 规则。  
-  修正：保留一行引用 `.agents/AGENTS.md`，仅写本目录增量约束。
+  修正：保留一行引用 `{HARNESS_DIR}/AGENTS.md`，仅写本目录增量约束。
 
 - 反模式：目录级规则未声明 Source Priority，冲突时不可裁决。  
   修正：统一四级优先级模板并在每个目录级文件开头声明。

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

@@ -7,8 +7,8 @@ Use this reference for `{HARNESS_DIR}` / `{PLAN_DIR}` initialization, status syn
 Follow `mstar-plan-conventions` for canonical discovery.
 Preferred layout:
 
-- `{HARNESS_DIR}`: `.agents/`
-- `{PLAN_DIR}`: `.agents/plans/`
+- `{HARNESS_DIR}`: `.mstar/` by default; existing `.agents/` projects remain valid.
+- `{PLAN_DIR}`: `.mstar/plans/` by default; existing `.agents/plans/` projects remain valid.
 
 Legacy fallbacks:
 

package/package.json

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