@mstar-harness/opencode 1.0.1 → 1.0.3

package/CHANGELOG.md

@@ -0,0 +1,260 @@
+# Changelog
+
+All notable changes to the `@mstar-harness/opencode` package are documented in this file.
+
+The monorepo root [CHANGELOG.md](../../CHANGELOG.md) summarizes cross-surface releases.
+
+## 1.0.3
+
+- Bundled skills/commands: iteration continuous execution (Phase 2–5 HARD push discipline in `iteration-drive` + `mstar-iteration` §2.6); skills command-agnostic cleanup; `pm` Autonomous Execute push rule; routing-eval v15.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **1.0.3**.
+
+## 1.0.2
+
+- Bundled skills/commands: iteration artifact boundaries (`{ITERATION_DIR}/<id>/` workspace, specs-first start, compound workspace promotion at close); new iteration references; corpus hygiene aligned.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **1.0.2**.
+
+## 1.0.1
+
+- Bundled skills/commands: `iteration-drive` + `mstar-iteration` Phase 2 per-task SDD mandate; optional sticky implementer session (`resume` + ledger); thin `pm` skill shim; routing-eval v14.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **1.0.1**.
+
+## 1.0.0
+
+- Bundle `mstar-sdd` skill + scripts; SDD mandatory plan QC tri-review (`Execution mode: sdd`); inline/hotfix single-seat; plan template and SDD metadata fields.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **1.0.0**.
+
+## 0.7.9
+
+- Bundled commands/skills: Assignment plain role ids across PM templates, dispatch gates, branch-worktree, iteration commands, opencode host hygiene, and role NEVER rules — avoids OpenCode `@` auto-dispatch in harness prose.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.9**.
+
+## 0.7.8
+
+- Bundled commands/skills: `mstar-iteration` Phase 4–5 (PR delivery + merge-ready loop); `iteration-drive` sequences through Phase 5 with optional greploop/babysit helpers; core index and anti-patterns updated.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.8**.
+
+## 0.7.7
+
+- Bundled commands/skills: standalone `mstar-*` invariant; bundle `grill-me` for `/iteration-start` only; remove Context7/OpenViking/Open Design from runtime load paths; distill `open-harness-principles.md` into core and plan-conventions references; keep Role → typical topic skills matrix in `mstar-roles`.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.7**.
+
+## 0.7.6
+
+- Bundled commands/skills: commands–skills layering for iteration (`iteration-start` / `iteration-drive` orchestration vs `mstar-iteration` / `mstar-dispatch-gates` SSOT); hardened dispatch gates, Phase 2→3→PR transitions, canonical host dispatch (no Mode A/B/C fallbacks); Phase 1 Review & Edit chain is **sequential** product-manager → architect → writing-specialist.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.6**.
+
+## 0.7.5
+
+- Bundled commands/skills: explicit iteration branch policy — `iteration_base_branch`, `spec_integration_branch`, and `target_branch` required in compass/status metadata; no silent default to `main` for integration branch or PR target. Hardened `iteration-start` / `iteration-drive` gates and QC merge-base rules.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.5**.
+
+## 0.7.4
+
+- Bundled skills/docs: remove Superpowers runtime dependency from Morning Star guidance and host docs; assignments now rely on native mstar dispatch, worktree, plan, review, and evidence contracts.
+- Bundled skills: add `mstar-skill-authoring`, delete `mstar-execution-practices`, and fold review feedback handling into `mstar-coding-behavior`.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.4**.
+
+## 0.7.3
+
+- Bundled commands/skills: `mstar-iteration` Phase 3 close is now an explicit gate after all plans are `Done`; close requires compass normalization when needed, compound Phase 6 knowledge indexing, roadmap update, completed frontmatter, and close checklists before PR.
+- Bundled docs: README command table now includes `/mstar-bootstrap`; workflow and skill overview now match the iteration lifecycle.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.3**.
+
+## 0.7.2
+
+- Docs only at package level: root **0.7.2** documents CLI Cursor install layout (real git checkout at plugin path, not symlink). Re-bundle on publish if CLI dist changed.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.2**.
+
+## 0.7.1
+
+- Bundled commands/skills: `/iteration-start` §5 Review & Edit chain is a hard gate before integration branch commit — Task dispatch for product-manager, architect, writing-specialist; evidence is edited docs + locked compass (no iteration `reports/` artifacts). Synced in `mstar-iteration` §1.6, `pm`, `mstar-dispatch-gates`, `mstar-harness-core`.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.7.1**.
+
+## 0.6.22
+
+- Bundled skills: `mstar-dispatch-gates`, `mstar-roles` (qc-specialist-shared, dispatch-and-assignment) — replace prohibition-based anti-recursion with identity-deprivation framework. Assignment template gains IDENTITY + CAPABILITY BOUNDARY blocks before prohibitions, shifting from "I must not dispatch" (negation) to "I am a leaf executor; Task is not my tool" (capability deprivation).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.22**.
+
+## 0.6.21
+
+- Bundled skills: `mstar-design-md` — add YAML frontmatter as SSOT for token values in templates and spec. Bump template format version to 0.1.0.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.21**.
+
+## 0.6.20
+
+- Bundled commands: `/iteration-start` §5 changed to "Review & Edit Chain" — each reviewer now directly edits documents rather than only flagging issues. PM only does the final lock.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.20**.
+
+## 0.6.19
+
+- Bundled skills: `mstar-coding-behavior` strengthened with distilled Ponytail principles — YAGNI gate, The Ladder (7-level decision hierarchy), "deletion over addition / boring over clever", `simplify:` marker discipline, "bug fix = root cause", and "minimal check for non-trivial logic".
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.19**.
+
+## 0.6.18
+
+- Bundled commands: `/iteration-start` now includes explicit `## 0. Boot` section aligned with `/iteration-drive`, loading core harness entry and PM role identity before research.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.18**.
+
+## 0.6.17
+
+- Bundled commands: `/iteration-drive` PR target now resolved from iteration metadata (`target_branch` in `status.json`), defaulting to `main` when not set.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.17**.
+
+## 0.6.16
+
+- Bundled commands: Add `/iteration-drive` command that invokes the PM Autonomous Execute driver to push all non-`Done` plans to completion (implement → QC → QA → Done loop, then optional PR to `main`).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.16**.
+
+## 0.6.15
+
+- Bundled commands: New `harness-commands/` directory bundle and `loadBundledCommands()` registration in the config hook. Adds `/iteration-start` command that guides PM through iteration bootstrap (research, explore, lock, compass/plans, review chain, integration branch).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.15**.
+
+## 0.6.11
+
+- Bundled agents: Cursor-first frontmatter on all role shells so hosts that share `agents/*.md` parse `name`/`description`/`model` before OpenCode fields.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.11**.
+
+## 0.6.10
+
+- Bundled skills: Profile B `archived/plans-done.json` schema is `{ "plans": [<plan-id>, ...] }` only; add `plans-done.empty.json` template and bootstrap/PM init notes.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.10**.
+
+## 0.6.9
+
+- Bundled skills: universal `pm` orchestration entry (Cursor/Codex `/pm`, OpenCode PM role switch) and Autonomous Execute driver (`status.json` backlog, `spec_integration_branch`, per-plan feature branches, host todos).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.9**.
+
+## 0.6.8
+
+- Bundled skills: targeted QC re-review after fixes (owner seat only, in-place reports), short QC report basenames under `reports/<plan-id>/` (`qc1.md` …).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.8**.
+
+## 0.6.7
+
+- Bundled skills: Codex Plan / Goal Mode bridge for keeping `/plan`, `update_plan`, `/goal`, and goal progress aligned with `.mstar/` SSOT.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.7**.
+
+## 0.6.6
+
+- Bundled skills/agents: Codex custom-agent source files, `.mstar/` harness defaults, and updated host install docs.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.6**.
+
+## 0.6.5
+
+- Bundled skills: Durable Roadmap Gate for staged/partial/temporary work, plus routing-eval v8.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.5**.
+
+## 0.6.4
+
+- Bundled skills: Cursor Plan Build resume contract and routing-eval v7.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.4**.
+
+## 0.6.3
+
+- Bundled skills: slim `/pm` with dispatch-first + `/pm`-only rules; PM shell pointer.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.3**.
+
+## 0.6.2
+
+- Bundled skills: `/pm` Autonomous Execute push (iteration driver, multi-plan); PM shell cross-reference.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.2**.
+
+## 0.6.1
+
+- Bundled skills: `tech-debt-rollup.sh`, PM dual fullstack spread defaults, routing-eval v6.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.1**.
+
+## 0.6.0
+
+- Unified **`mstar-host`** in bundled `harness-skills/`; removed separate package `skills/` host path.
+
+See root [CHANGELOG.md](../../CHANGELOG.md) **0.6.0**.
+
+## 0.5.1
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- Cursor Plan mode dual-write bridge (`mstar-host`, `cursor-plan-mode-bridge`, `pm`, `mstar-harness-core`); `rules/mstar-cursor-plan-mode.mdc`.
+
+See root [CHANGELOG.md](../../CHANGELOG.md).
+
+## 0.5.0
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- Align bundled assets with the 0.5.0 harness release, including Codex plugin validation fixes in shared skill metadata.
+
+See root [CHANGELOG.md](../../CHANGELOG.md).
+
+## 0.4.1
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- **`mstar-plan-artifacts/templates/`**: `status.empty.json` and `notes.empty.json` moved from `mstar-plan-conventions` (paths in skill text updated).
+
+See root [CHANGELOG.md](../../CHANGELOG.md).
+
+## 0.4.0
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- **Topic skill split**: `mstar-phase-gates`, `mstar-dispatch-gates`, `mstar-branch-worktree`, `mstar-plan-artifacts` (status/residual included); slimmer `mstar-harness-core` and `mstar-plan-conventions`.
+- **`mstar-roles`**: Per-role required skill lists; host adapters updated for on-demand topic loading.
+- **`mstar-plan-conventions`**: `{ITERATION_DIR}`, `{KNOWLEDGE_DIR}`, content boundaries; optional `iteration_compass` / `iteration_refs`.
+- **`mstar-phase-gates`**: Prepare **`clarify` core discipline** (shared understanding, explore before asking, recommended answers).
+
+See root [CHANGELOG.md](../../CHANGELOG.md) for full release notes.
+
+## 0.3.2
+
+### Bundled harness skills (`harness-skills/` at publish)
+
+- **`mstar-plan-conventions`**: Formalize `{ITERATION_DIR}` (`{HARNESS_DIR}/iterations/`) and `{KNOWLEDGE_DIR}` (`{HARNESS_DIR}/knowledge/`); add `docs/` vs harness subtree content boundaries; optional `iteration_compass` / `iteration_refs` in `status.json` metadata.
+- **`mstar-harness-core`**: Embed Prepare **`clarify` core discipline** — walk the design decision tree to shared understanding, explore the codebase before asking the user, provide a recommended answer per question.
+
+## 0.3.1
+
+- Align package version with monorepo **0.3.1** (see root `CHANGELOG.md` for harness and host-adapter notes bundled via `harness-skills/` / `harness-agents/`).
+
+## 0.3.0
+
+- Align package version with monorepo **0.3.0** (see root `CHANGELOG.md` for harness and host-adapter notes bundled via `harness-skills/` / `harness-agents/`).
+
+## 0.2.0
+
+- Publish OpenCode plugin with bundled repo `skills/` and `agents/` (`bundle-assets` / root `postinstall`).
+- Remove cwd-based harness path resolution; consume bundled assets only.

package/README.md

@@ -0,0 +1,62 @@
+# @mstar-harness/opencode
+
+Morning Star (启明星) harness plugin for [OpenCode](https://opencode.ai).
+
+Install this package via OpenCode’s `plugin` array — it bundles `mstar-*` skills, role agents, and iteration commands so multi-role workflows (PM routing, SDD implement, QC tri-review, iteration lifecycle) work the same way as in the Cursor and Codex plugins.
+
+## Install
+
+Add to `opencode.json` (global or project):
+
+```json
+{
+  "plugin": ["@mstar-harness/opencode@latest"]
+}
+```
+
+Restart OpenCode.
+
+Or use the installer CLI:
+
+```bash
+npx @mstar-harness/cli init --target opencode
+```
+
+## What you get
+
+| Path in package | Contents |
+|-----------------|----------|
+| `harness-skills/` | `mstar-harness-core`, `mstar-iteration`, `mstar-sdd`, roles, phase/dispatch gates, … |
+| `harness-agents/` | Role shells (`project-manager`, `fullstack-dev`, `qc-specialist`, …) |
+| `harness-commands/` | `/iteration-start`, `/iteration-drive`, `/mstar-bootstrap` |
+
+The plugin resolves **only paths inside this package** — not `process.cwd()/skills`, so your app repo root does not affect harness loading.
+
+## Quick start
+
+1. Install the plugin (above).
+2. In OpenCode, start with the **Project Manager** agent (`project-manager`).
+3. For a full iteration: run **`/iteration-start`**, then **`/iteration-drive`** when plans are ready.
+
+Entry skill: **`mstar-harness-core`** (loaded before other `mstar-*` skills).
+
+## Docs
+
+- [INSTALL.md](./INSTALL.md) — setup, monorepo checkout, migration from legacy git plugin, troubleshooting
+- [Monorepo README](https://github.com/btspoony/mstar-harness#readme) — cross-host overview
+- [CHANGELOG.md](./CHANGELOG.md) — package release notes
+
+## Development (this monorepo)
+
+From the repository root:
+
+```bash
+bun install          # postinstall bundles harness-skills/ + harness-agents/
+bun run opencode:bundle-assets   # if you used --ignore-scripts
+```
+
+Plugin entry: `packages/opencode/src/mstar.ts` → `dist/mstar.js`.
+
+## License
+
+MIT — see [LICENSE](https://github.com/btspoony/mstar-harness/blob/main/LICENSE).

package/harness-commands/iteration-drive.md

@@ -25,11 +25,33 @@ Phase 2: Autonomous Execute  →  Phase 3: iteration-close  →  Phase 4: Create
 
 **Done 定义**：**仅** Phase 5 §5.5 exit checklist 全 `[x]`。**Phase 3 close ≠ Done；Phase 4 开 PR ≠ Done。**
 
+## Continuous execution（HARD — Phase 2–5）
+
+**Autonomous Execute push**：自 Phase 2 进入至 Phase 5 §5.5 exit 全 `[x]` 前，PM **连续编排**，不得把进度汇报、phase 标题或子 agent 返回当作**回合结束**。
+
+| 禁止 | 必须 |
+|------|------|
+| plan / task / phase 边界问用户「是否继续」「要不要现在启动」「是否开 PR」等例行 yes/no | 进度摘要后**下一条动作** = **dispatch**（`Task`）或下一 phase 步骤（打印 checklist → 执行） |
+| 用完整 Phase 2 汇报收束 turn 后等待用户 | 同 plan 内 task 间 → **`mstar-sdd` Continuous execution**；当前 plan Done 后 → **立刻**下一 plan dispatch |
+| 把 `## Phase 3/4/5` 标题当作可停下协商点（除合法 STOP） | Phase 3 checklist `[x]` → **立刻** Phase 4；PR 创建后 → **立刻** Phase 5 loop |
+| 跨 plan **并行** implement dispatch（多 plan 同时跑 implementer） | Per-plan **串行**：plan A implement→QC→QA→Done 后再 plan B（除非用户书面 override） |
+
+**合法 STOP（仅此升级用户）**：
+
+- §2.0 / Phase 4 branch metadata 缺失（`iteration_base_branch` / `target_branch`）
+- **`Blocked`**：真冲突、secrets、不可逆范围缺口、Phase 5 多轮仍无法 merge-ready
+- 用户本轮显式打断
+
+**Turn 收束纪律**：若 host 即将结束本轮，最后一条 assistant 内容必须是 **in-flight 动作**（invoke 已发出、或写明下一 dispatch 的 Assignment 字段），**不得**以对用户的确认问句结尾。
+
+SSOT 细化：`mstar-sdd`（task 级）· `mstar-iteration` §2.6（push 纪律）。
+
 ## PM invariants（Phase 2–5 全程有效）
 
 | 禁止（PM 线程） | 必须 |
 |-----------------|------|
 | Write/Edit/Shell 产品代码、写测试、跑 QC 审查（Phase 2） | 每条 implement/QC/QA Assignment ⇒ **1 次 `Task`** |
+| **进度汇报后问「是否继续」或以 phase 摘要收束 turn** | 汇报后**立刻** dispatch 或进入下一 phase 动作（见上节 Continuous execution） |
 | **多 task plan 用 inline 大包派发**（整份 plan / T1–Tn 贴进一个 dev Assignment） | **SDD**：`mstar-sdd` per-task 循环 — `task-brief` → implementer → `review-package` → task reviewer → `progress.md` |
 | 只写 Assignment 就进入下一 gate | 同轮 dispatch：`Subagent invokes issued: N`（N = Assignment 条数） |
 | 最后一个 plan `Done` 后直接开 PR / 汇报结束 | **Phase 3 → 4 → 5** 顺序执行 |
@@ -60,6 +82,8 @@ Phase 2: Autonomous Execute  →  Phase 3: iteration-close  →  Phase 4: Create
 
 ## Phase 2: Autonomous Execute
 
+**Continuous execution applies** — 本节全程遵守上节 **Continuous execution（HARD）**；Completion Report / 进度同步后不得 check-in，下一条必须是 dispatch 或下一 plan。
+
 **Branch policy first** — before any plan dispatch（`mstar-iteration` §2.3）:
 
 | Field | SSOT | If missing |
@@ -107,7 +131,7 @@ Execute **`mstar-iteration` § Phase 2** exactly. Summary:
 |------|---------|------|
 | 1 | §3.0 / §3.0.5 | Phase 边界；legacy compass 规范化（frontmatter + `## Roadmap Position`） |
 | 2 | §3.1 | 打印 close entry checklist，全部 `[x]` |
-| 3 | §3.2 | Compound；新增 doc 完成 `mstar-compound` Phase 6（`{KNOWLEDGE_DIR}/README.md`） |
+| 3 | §3.2 | Compound + **`<iteration-id>/` workspace promotion**；新增 doc 完成 `mstar-compound` Phase 6（`{KNOWLEDGE_DIR}/README.md`） |
 | 4 | §3.3 | `## Roadmap Position` current iteration → `delivered`；STRATEGY/tracker 按需更新 |
 | 5 | §3.4 | frontmatter `status: completed` + `end_date`；Compound Summary + Retrospective |
 | 6 | §3.5 | 打印 close exit checklist → commit → push |

package/harness-commands/iteration-start.md

@@ -1,6 +1,6 @@
 ---
 name: iteration-start
-description: Start a new harness iteration — research backlog, lock direction with grill-me, produce compass/plans, run mandatory Review & Edit chain via sequential Task dispatch (product-manager → architect → writing-specialist, each review-and-edit, then PM final lock), then create the integration branch from an explicit base. Not Done until review chain completes, compass is locked, and base/target branches are recorded.
+description: Start a new harness iteration — research, grill-me, compass/plans, Review & Edit chain (long-lived {SPECS_DIR}/ + {ITERATION_DIR}/<id>/ workspace; compound promotes workspace at close only), PM lock, integration branch.
 agent: project-manager
 ---
 
@@ -28,7 +28,7 @@ Detailed workflow → **`mstar-iteration` § Phase 1: iteration-start**（含 §
 
 1. `mstar-harness-core`
 2. `mstar-roles` → `references/project-manager.md`
-3. `mstar-iteration` → **§ Phase 1: iteration-start**（迭代范围、compass 模板、§1.6 Review & Edit chain、状态初始化）
+3. `mstar-iteration` → **§ Phase 1: iteration-start**（迭代范围、compass 模板、**§1.5.5 产物边界**、§1.6 Review & Edit chain、状态初始化）
 4. `mstar-dispatch-gates`
 5. `mstar-phase-gates` → Prepare（specify → clarify → plan）
 6. `mstar-plan-conventions`, `mstar-plan-artifacts`
@@ -98,12 +98,12 @@ Each role below **reviews and directly edits** the documents. Do not just flag i
 
 | # | Role | Required action | Gate |
 |---|------|-----------------|------|
-| 5.1 | **product-manager** | invoke: **edit** compass, plans, `{SPECS_DIR}/`; scope, UX, priorities | 完成后方可 5.2 |
-| 5.2 | **architect** | invoke: **edit** compass, plans, specs（含 5.1 修订后版本）; contracts, SQL, module boundaries | 5.1 返回后；完成后方可 5.3 |
-| 5.3 | **writing-specialist** | invoke: **edit** all iteration docs（含 5.1–5.2 修订后版本）; terminology, structure, clarity | 5.2 返回后 |
+| 5.1 | **product-manager** | invoke: **edit** compass, plans, **`{SPECS_DIR}/`**, **`{ITERATION_DIR}/<iteration-id>/`**（`guides/`、`specs/` 按需）— **禁止** `{KNOWLEDGE_DIR}/` 新增 | 完成后方可 5.2 |
+| 5.2 | **architect** | invoke: **edit** compass, plans, **`{SPECS_DIR}/`**, workspace `specs/`（含 5.1 后版本）— **禁止** `{KNOWLEDGE_DIR}/` 新增 | 5.1 返回后；完成后方可 5.3 |
+| 5.3 | **writing-specialist** | invoke: **edit** compass / plans / specs / iteration 文档; **specs corpus hygiene**（全库 `{SPECS_DIR}/` + 既有 `{KNOWLEDGE_DIR}/` 卫生与错放纠正，**不**新增 knowledge）— `mstar-iteration/references/iteration-artifact-boundaries.md` + `iteration-corpus-hygiene.md` | 5.2 返回后 |
 | 5.4 | **project-manager** | Merge subagent edits; resolve conflicts; **lock** compass (`status: locked`); confirm Prepare gates | 5.3 返回后 |
 
-**Evidence of done** = edited compass / plans / specs on disk + compass `status: locked`. **No** separate iteration review reports under `reports/` — unlike per-plan QC, there is no downstream audit chain to preserve.
+**Evidence of done** = edited compass / plans / **specs** / iteration docs on disk + specs corpus hygiene（及既有 knowledge 归档/错放纠正，如有）+ compass `status: locked`. **No** new `{KNOWLEDGE_DIR}/` from this chain — knowledge → **`mstar-compound`** @ iteration-close. **No** separate iteration review reports under `reports/`.
 
 **Tool rule (hosts with invoke)** — per **`mstar-dispatch-gates`** · specialist review-and-edit dispatch（**顺序链**，非 parallel batch）：
 
@@ -128,9 +128,9 @@ PM must print this block before §6; all `[ ]` must be `[x]`:
 
 - [ ] grill-me decisions recorded in compass
 - [ ] Draft compass + plans + `status.json` registered
-- [ ] product-manager invoke completed — compass / plans / specs edited
-- [ ] architect invoke completed — compass / specs edited
-- [ ] writing-specialist invoke completed — iteration docs edited
+- [ ] product-manager invoke completed — compass / plans / specs / **`<iteration-id>/` workspace**（按需）；**未**向 `{KNOWLEDGE_DIR}/` 新增
+- [ ] architect invoke completed — compass / **specs** edited；**未**向 `{KNOWLEDGE_DIR}/` 新增
+- [ ] writing-specialist invoke completed — specs + iteration docs edited；**specs corpus hygiene** done（全库 `{SPECS_DIR}/`；既有 knowledge 仅卫生/归档；错放已迁回 `iterations/` 或 archive）
 - [ ] PM final lock: compass `status: locked`; Prepare gates pass (blocked plans documented)
 - [ ] Branch policy locked: `iteration_base_branch`, `spec_integration_branch`, and `target_branch` recorded in compass / `status.json`
 - [ ] **THEN**: git commit + push `iteration/<iteration-id>`

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-compound
-description: Morning Star 知识结晶 —— 将已解决问题的经验沉淀为结构化知识文档，存入 `{KNOWLEDGE_DIR}`。支持 Bug track（症状/失败尝试/解决方案）与 Knowledge track（上下文/指南/适用场景）双轨。含重叠检测（更新已有文档）、可发现性检查（AGENTS.md 索引）、CONCEPTS.md 领域词汇协同。触发：迭代收口时（`mstar-iteration` § iteration-close）批量执行；也可独立触发。产出：`{KNOWLEDGE_DIR}/<category>/<slug>.md` + 可选 AGENTS.md 更新。
+description: Morning Star 知识结晶 —— 将已解决问题的经验沉淀为结构化知识文档，存入 `{KNOWLEDGE_DIR}`；迭代收口时从 `{ITERATION_DIR}/<iteration-id>/` 工作区提升 specs/guides。支持 Bug track 与 Knowledge track 双轨。含重叠检测、可发现性检查、CONCEPTS.md 协同。触发：iteration-close（`mstar-iteration` §3.2）或独立触发。产出：`{KNOWLEDGE_DIR}/<category>/<slug>.md`。
 ---
 
 # mstar-compound（知识结晶）
@@ -79,6 +79,26 @@ iteration-start → [plan lifecycle × N: specify→...→Done] → iteration-cl
 
 迭代内所有 plan Done 后，PM 回顾整轮迭代中产生的可结晶知识，批量 compound。per-plan Done 是 per-plan 的闭环终点；compound 是迭代级收口活动。
 
+### Iteration workspace promotion（iteration-close 强制盘点）
+
+正式迭代收口时，compound **除** plan 实现/debug/review 素材外，**必须**盘点当前迭代的 workspace：
+
+**路径**：`{ITERATION_DIR}/<iteration-id>/**`（含 `guides/`、`specs/`、扁平 `.md`；不含根目录 `*-delivery-compass.md` 除非 PM 显式纳入）。
+
+| 步骤 | 动作 |
+|------|------|
+| 1. Inventory | 列出 workspace 下全部 `.md`；读各文件 + workspace `README.md`（若有） |
+| 2. Triage | 每篇：**Promote** / **Keep snapshot** / **Skip**（理由写入 compound 摘要） |
+| 3. Promote | 值得跨迭代复用 → 走 Q1–Q8（或轻量判定）→ Phase 2 重叠检测 → Phase 3–6 **结构化重写**进 `{KNOWLEDGE_DIR}/`（**禁止**无改写整文件复制） |
+| 4. Trace | 源文件顶栏或 workspace README：`Promoted to: <knowledge-path>`；`{KNOWLEDGE_DIR}/README.md` 的 Source 可记 `iteration:<iteration-id>/<relpath>` |
+| 5. Summary | PM 写入 compass `## Compound Round Summary`：提升篇数、保留快照、跳过及原因 |
+
+**Promote 典型**：迭代 spec 已验证且指导未来实现；guide 含非显而易见的过程知识或失败尝试。
+
+**Keep snapshot**：仅迭代史、已被 `{SPECS_DIR}/` 取代的草案、或自检 ≤2 Yes 的琐碎笔记。
+
+边界 SSOT → **`mstar-iteration/references/iteration-artifact-boundaries.md`**。
+
 ## When to use (trigger)
 
 - **迭代收口时**（`mstar-iteration` § iteration-close）：PM 批量回顾所有 plan 的产物
@@ -114,7 +134,9 @@ In Cursor, Full mode dispatches subagents via Task tool. PM selects mode.
 
 ## Phase 1: Gather context
 
-Read the conversation history to understand:
+Read the conversation history **and**, when `iteration_id` is known, scan **`{ITERATION_DIR}/<iteration-id>/`** workspace per **Iteration workspace promotion** above.
+
+Understand:
 - What problem was solved (the concrete issue)
 - What was tried and didn't work
 - What the working solution was

package/harness-skills/mstar-compound-refresh/SKILL.md

@@ -45,7 +45,7 @@ For each candidate document, classify into one of five outcomes:
 3. **Match docs to reality.** When code differs from doc, update the doc — not ask whether the code change was "intentional."
 4. **Be decisive.** When evidence is clear (file renamed, class moved), apply. Only ask PM when genuinely ambiguous.
 5. **Avoid low-value churn.** Don't edit for typos, polish, or cosmetic changes that don't improve accuracy.
-6. **Delete, don't archive.** No `_archived/` directory. Git history is the archive. `git log --diff-filter=D -- <path>` finds deleted docs.
+6. **Delete, don't archive** — **except** formal **iteration-start** §1.6 corpus hygiene (`mstar-iteration/references/iteration-corpus-hygiene.md`), which **moves** superseded/redundant knowledge/specs to `{HARNESS_DIR}/archived/knowledge|specs/`. Outside that gate, git history is the archive; `git log --diff-filter=D -- <path>` finds deleted docs.
 7. **Evaluate document-set design.** Check whether two+ docs overlap and should be consolidated. Redundant docs silently drift apart.
 
 ## Scope selection

package/harness-skills/mstar-dispatch-gates/SKILL.md

@@ -87,7 +87,7 @@ When **`Execution mode: sdd`** (`mstar-sdd`):
 
 - PM 写初稿；各角色通过宿主 invoke **直接编辑**目标文件（**不**另写仅评论式 `reports/` 替代修订）。
 - **1 Assignment ⇒ 1 invoke**。
-- **Phase 1 Review & Edit chain**（`mstar-iteration` §1.6）：**顺序** `product-manager` → `architect` → `writing-specialist`；上一角色落盘修订完成后再派发下一角色。**禁止**本链并行 batch（与 QC 三审不同）。
+- **Phase 1 Review & Edit chain**（`mstar-iteration` §1.6）：主产出 **`{SPECS_DIR}/`** + **`{ITERATION_DIR}/<iteration-id>/`** workspace；**禁止** start 链向 `{KNOWLEDGE_DIR}/` 新增。close 时 **`mstar-compound`** 提升 workspace → knowledge。
 - 其他彼此独立、无先后依赖的文档编辑任务：可并行（同条消息发满 N），见 **`parallel-dispatch.md`**。
 - PM 线程代做全部专业编辑 = **反模式**（`mstar-iteration` §1.6、`mstar-harness-core` 反模式索引）。
 - PM merge / lock（如 compass `status: locked`）在链末 subagent 返回后于 PM 线程完成。**不得**在 review-and-edit 链完成前 commit integration 分支。

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

@@ -6,7 +6,7 @@ Parallel PM dispatch: **`parallel-dispatch.md`** (Task tool uses same turn model
 
 ## Cursor-only context
 
-- Role prompts: `mstar-roles`; **`/pm`** or **`pm` skill** → general PM orchestration (per-plan dispatch, gates, QC) without an iteration command. **`commands/`** (`iteration-start`, `iteration-drive`, `mstar-bootstrap`) only when running formal iteration Phase 1–5.
+- Role prompts: `mstar-roles`; **`/pm`** or **`pm` skill** → general PM orchestration (per-plan dispatch, gates, QC) without an iteration command. Host **`commands/`** for formal iteration Phase 1–5 (semantics → **`mstar-iteration`**).
 - Routing-eval: `.cursor/skills/mstar-routing-eval/` — regression tooling only; not runtime load order.
 
 ## Plan mode × harness dual-write

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

@@ -6,7 +6,7 @@ Parallel PM dispatch: **`parallel-dispatch.md`** (read in dispatch rounds).
 
 ## Role loading
 
-- **PM entry**: **`/pm`** or **`pm` skill** → `project-manager` for general orchestration; **`commands/`** (`iteration-start`, `iteration-drive`, `mstar-bootstrap`) for formal iteration only.
+- **PM entry**: **`/pm`** or **`pm` skill** → `project-manager` for general orchestration; host **`commands/`** for formal iteration Phase 1–5 (semantics → **`mstar-iteration`**).
 - **Role shell**: `agents/<id>.md` referenced by `opencode.json` `agent.<id>` (frontmatter + role binding only).
 - **Role body**: `mstar-roles` `references/<id>.md` (or shared references + parameters).
 - Implementation evidence and RCA behavior: `mstar-coding-behavior`.

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-iteration
-description: Morning Star 迭代管理 —— iteration-start、Autonomous Execute（per-plan SDD + plan QC tri）、iteration-close、PR 交付（Phase 4）、PR merge-ready loop（Phase 5）。显式分支策略；compass `{ITERATION_DIR}/`；分支 SSOT：`status.json` metadata + compass frontmatter。**必须**在 iteration-start / iteration-drive / 多 plan 编排、integration 分支、iteration-close 或 PR merge-ready 时 Read；`@project-manager` 迭代编排必读。
+description: Morning Star 迭代管理 —— iteration-start（specs + `<iteration-id>/` workspace；禁止直写 knowledge）、Autonomous Execute、iteration-close（compound 提升 workspace → knowledge）、PR 交付、PR merge-ready loop。分支 SSOT：`status.json` + compass frontmatter。
 ---
 
 # mstar-iteration（迭代管理）
@@ -43,7 +43,7 @@ Phase 5: PR merge-ready loop —— 至 mergeable + CI 全绿 + reviews resolved
 | **→ Phase 4** | §3.5 exit checklist 全 `[x]`；frontmatter `status: completed` + `end_date` | 打印 `## Phase 4: PR delivery`；开 PR 到 `metadata.target_branch`（§4） | 跳过 §3.1 entry checklist 或 compound Phase 6 |
 | **→ Phase 5** | Phase 4 PR 已创建 | 打印 `## Phase 5: PR merge-ready`；执行 §5 loop 至 §5.5 exit | 开 PR 后停止；跳过 review resolve / CI loop |
 | **→ 迭代交付完成** | §5.5 exit checklist 全 `[x]` | PR mergeable；required CI 全绿；reviews resolved | Phase 4 开 PR 即宣称完成 |
-| **iteration-start → integration branch** | §1.6 Review & Edit chain | 三角色 **按序** invoke 完成 + compass `status: locked` | PM 线程代做三角色编辑；并行三角色；review 前 commit |
+| **iteration-start → integration branch** | §1.6 Review & Edit chain | 三角色按序 invoke；**specs** 为主产出；**禁止** start 链向 `{KNOWLEDGE_DIR}/` 新增；writing-specialist corpus hygiene + compass `status: locked` | PM 代做专业编辑；并行三角色；product/architect 写 knowledge；临时笔记进 specs |
 
 **误判信号**：对话里出现 compound 摘要、roadmap 更新、或「所有 plan 已完成」但 **未** 打印 §3.1 / §3.5 checklist → 视为 **Phase 3 未执行**，回到 §3.0。
 
@@ -153,18 +153,31 @@ iteration 正式全流程**必须**写入 `{HARNESS_DIR}/status.json`：
 
 compass frontmatter 的 `iteration_base_branch` / `target_branch` **必须与** `status.json` 一致；若仅写在 compass 而 status 缺失，§2.3 同轮 backfill。
 
+### 1.5.5 产物边界（specs · iterations · knowledge）
+
+Phase 1 与 §1.6 须遵守 **`references/iteration-artifact-boundaries.md`**（HARD）：
+
+| 树 | iteration-start 主责 | 说明 |
+|----|---------------------|------|
+| **`{SPECS_DIR}/`** | product-manager、architect | **长期**规范性产出：锁定规格、ADR、契约；plan `primary_spec` / `spec_refs` 主要挂此处 |
+| **`{ITERATION_DIR}/`** | product-manager、architect、PM | compass（根）+ **`<iteration-id>/` workspace**（迭代级 specs & guides） |
+| **`{KNOWLEDGE_DIR}/`** | **非** start/execute 直写；**`mstar-compound`** @ iteration-close（含 workspace **提升**） | 可复用实施 SSOT |
+
+**禁止**：product/architect 在 §1.6 向 `{KNOWLEDGE_DIR}/` **新增**；把迭代级草案写入 `{SPECS_DIR}/`（应进 `<iteration-id>/specs/` 或 guides）。
+
 ### 1.6 Review & Edit chain（integration 分支前强制）
 
 **Phase 1 在 PM lock 前不算完成**——compass/plans 初稿落盘 ≠ Done。
 
 派发机制 → **`mstar-dispatch-gates`**（specialist review-and-edit dispatch，**顺序链**）。PM **不得**将迭代 harness 文档 commit 到 `spec_integration_branch`，直到：
 
-1. **product-manager** → **architect** → **writing-specialist** 已按序通过宿主 invoke **直接编辑**（非仅评论）compass、plans 及受影响 specs；每一环基于上一环落盘修订
-2. PM 将 compass `status` 设为 `locked`，并确认各 plan 的 Prepare gate（specify / clarify / plan）
+1. **product-manager** → **architect** → **writing-specialist** 已按序 invoke 编辑 compass、plans、`{SPECS_DIR}/` 与 **`{ITERATION_DIR}/<iteration-id>/`** workspace（guides/specs，按需）；**不得**在 start 链向 `{KNOWLEDGE_DIR}/` 新增
+2. **writing-specialist** 完成 **corpus hygiene**：全库 `{SPECS_DIR}/` + 既有 `{KNOWLEDGE_DIR}/` 卫生；错放迁回 **`<iteration-id>/`** workspace；细则 → **`iteration-corpus-hygiene.md`**、**`iteration-artifact-boundaries.md`**
+3. PM 将 compass `status` 设为 `locked`，并确认各 plan 的 Prepare gate（specify / clarify / plan）
 
-**顺序理由**：产品范围与优先级 → 架构与契约 → 术语与行文；并行会导致后手重复劳动或覆盖前手未定稿内容。OpenCode：plain role id — **`mstar-host/references/opencode.md`** § Role-mention hygiene。
+**顺序理由**：产品范围与优先级 → 架构与长期契约（specs）→ 行文、规格库卫生与错放纠正（须在 PM/architect 定稿后扫全库 specs）。并行会导致后手重复劳动或覆盖前手未定稿内容。OpenCode：plain role id — **`mstar-host/references/opencode.md`** § Role-mention hygiene。
 
-**完成证据** = 磁盘上的 compass / plans / specs 修订 + compass `status: locked`。**不**要求 `reports/<iteration-id>/` 审查报告——迭代审查的 SSOT 是被编辑的文档本身，无 per-plan QC 式审计链。
+**完成证据** = 磁盘上的 compass / plans / specs / iteration 文档修订 + specs（与既有 knowledge）卫生/归档（如有）+ 索引与 metadata 更新 + compass `status: locked`。**不**要求 `reports/<iteration-id>/` 审查报告——迭代审查的 SSOT 是被编辑的文档本身，无 per-plan QC 式审计链。
 
 **反模式**：PM 线程代替三角色完成全部编辑而不 invoke；或将本链三角色并行派发 —— 见 **`mstar-harness-core`** 反模式索引。
 
@@ -270,11 +283,15 @@ Iteration Phase 2 附加：
 - `Subagent invokes issued: 0` 而 Assignment 已写出 → **`dispatch incomplete`**；下一条补发 invoke，禁止 PM 顶替
 - QC 初轮：**SDD → N=3**；**inline → N=1**；双轨 implement → **N=2**（同条消息发满 N）
 
-### 2.6 Push 纪律
+### 2.6 Push 纪律（Autonomous Execute）
+
+**Continuous execution（HARD）**：Phase 2 Autonomous Execute 经 Phase 5 merge-ready exit 全程 — 不向用户做例行 yes/no check-in。
 
-- 不因 harness 基础问题常问"是否继续"—— 决策、记录、**dispatch**
-- 未知 → 读 `mstar-*`；**`Blocked`** 或仅对 stop/secrets/不可逆范围缺口/冲突后升级
+- 不因 harness 流程问题常问「是否继续」「要不要现在启动」—— **决策、记录、dispatch**
+- 进度汇报 / subagent Completion Report 后，下一条必须是 **dispatch 或下一 gate 动作**，不得以确认问句收束 turn
+- 未知 → 读 `mstar-*`；仅 **`Blocked`**、secrets、不可逆范围缺口、branch metadata 缺失、或 Phase 5 多轮仍 blocked 时升级用户
 - 实际 Git ≠ `working_branch` → **同轮**更新 plan + status
+- Per-plan loop **串行**（plan A Done 后再 plan B）；plan 内 SDD task **串行** — 见 §2.4、§2.5、`mstar-sdd` Continuous execution
 
 ---
 
@@ -322,11 +339,12 @@ PM **必须**在对话中打印本 checklist；不得默认同过。
 PM 批量触发后须：
 
 1. 收集本迭代 plan 实现 / debug / review 素材，筛候选知识
-2. 逐条过 `mstar-compound` 自检；跳过项记入 compass `## Compound Round Summary`
-3. 写入或更新 `{KNOWLEDGE_DIR}/<category>/<slug>.md`；新领域词更新 `CONCEPTS.md`
-4. **每篇**新 doc 完成 Phase 6（`{KNOWLEDGE_DIR}/README.md` 登记）
+2. **盘点** `{ITERATION_DIR}/<iteration-id>/**` workspace（`guides/`、`specs/`）— **`mstar-compound`**「Iteration workspace promotion」；提升值得保留者进 `{KNOWLEDGE_DIR}/`
+3. 逐条过 `mstar-compound` 自检；跳过项记入 compass `## Compound Round Summary`
+4. 写入或更新 `{KNOWLEDGE_DIR}/<category>/<slug>.md`；新领域词更新 `CONCEPTS.md`
+5. **每篇**新 doc 完成 Phase 6（`{KNOWLEDGE_DIR}/README.md` 登记）
 
-若无结晶，仍在 `## Compound Round Summary` 写明 `无可结晶知识` 及原因。
+若无结晶且无 workspace 提升，仍在 `## Compound Round Summary` 写明 `无可结晶知识` / workspace 盘点结论及原因。
 
 ### 3.3 更新 roadmap
 
@@ -350,7 +368,7 @@ PM 批量触发后须：
 PM 打印 **iteration-close exit checklist**；全部为 `[x]` 后方可 `git commit`；然后进入 **Phase 4**（§4）：
 
 - [ ] §3.1 前置 gate 已打印并满足
-- [ ] §3.2 compound 完成；新增 knowledge doc 均已登记 `{KNOWLEDGE_DIR}/README.md`（或已记录无可结晶原因）
+- [ ] §3.2 compound 完成；**`<iteration-id>/` workspace 已盘点**（提升 / 保留 / 跳过已记入 Compound Summary）；新增 knowledge doc 均已登记 `{KNOWLEDGE_DIR}/README.md`（或已记录无可结晶原因）
 - [ ] §3.3 `## Roadmap Position` current iteration 已标 `delivered`；tracker / STRATEGY 已按需更新
 - [ ] §3.4 frontmatter `status: completed` + `end_date`；Compound Summary + Retrospective 已填
 - [ ] 当前分支是 `spec_integration_branch`
@@ -436,8 +454,11 @@ PR **merge** 本身可仍由用户手动执行，除非 Assignment 明确授权
 | `mstar-sdd` | SDD implement 波次 — per-plan loop |
 | `mstar-review-qc` | SDD 强制 plan QC tri — per-plan loop |
 | `mstar-branch-worktree` | 分支/merge/worktree 隔离 |
-| `mstar-compound` | iteration-close 中触发知识结晶 |
+| `mstar-compound` | iteration-close 中触发知识结晶（**唯一**默认 knowledge 新增路径） |
 | `mstar-compound-refresh` | iteration-close 后可触发知识维护 |
+| `references/iteration-artifact-boundaries.md` | Phase 1 specs / iterations workspace / knowledge 分工 |
+| `references/iteration-workspace-readme-template.md` | `<iteration-id>/README.md` 可选模板 |
+| `references/iteration-corpus-hygiene.md` | §1.6 writing-specialist specs 卫生细则 |
 | `mstar-strategy` | iteration-start 时读 `STRATEGY.md` 对齐方向 |
 
 ## NOT to do
@@ -453,5 +474,8 @@ PR **merge** 本身可仍由用户手动执行，除非 Assignment 明确授权
 - 不要跳过 compound Phase 6（`{KNOWLEDGE_DIR}/README.md` 索引）——即使只结晶一篇文档
 - 不要跳过 compound——如果本迭代确实没有可结晶的知识，在 compass `## Compound Round Summary` 写 `无可结晶知识（原因：<简述>）`
 - 不要将 **Phase 4 开 PR** 等同于 **迭代交付完成** — 必须完成 **Phase 5** §5.5 merge-ready loop
-- 不要在 Phase 5 跳过 review comment + resolve 纪律（§5.1 step 5）
+- **不要在 iteration-start §1.6 由 product/architect 向 `{KNOWLEDGE_DIR}/` 新增文档**（知识 → iteration-close **`mstar-compound`**）
+- **不要把迭代级草案写入 `{SPECS_DIR}/`**（应进 `{ITERATION_DIR}/<iteration-id>/specs/` 或 `guides/`）
+- **不要在 iteration-close 跳过 `<iteration-id>/` workspace 盘点**（compound 提升 SSOT → **`mstar-compound`**）
+- **不要在 iteration-start §1.6 跳过 writing-specialist 全库 specs corpus hygiene**（仅改当轮 compass/plans 而不扫 `{SPECS_DIR}/`）
 - **不要在 SDD plan 上以单席 `qc.md` 收尾**（除非用户书面 `QC mode: single — override`）

package/harness-skills/mstar-iteration/references/iteration-artifact-boundaries.md

@@ -0,0 +1,94 @@
+# iteration-start 产物边界（specs · iterations · knowledge）
+
+> **When**: Phase 1 — PM 初稿落盘、§1.6 Review & Edit chain；Phase 2 迭代执行期可继续写入 iteration workspace；Phase 3 iteration-close 经 **`mstar-compound`** 提升。
+> **Conflict**: 与 `mstar-plan-artifacts/references/knowledge-and-designs.md` 一致；冲突以 **`mstar-harness-core`** 为准。
+
+## 三棵树分工（HARD）
+
+| 树 | 路径 | 长期价值 | 谁写（何时） | 典型内容 |
+|----|------|----------|--------------|----------|
+| **Specs（仓库级）** | `{SPECS_DIR}/` | **是** — 跨迭代规范性权威 | product / architect @ **iteration-start** | 已锁定产品/API 规格、ADR、契约 |
+| **Iterations** | `{ITERATION_DIR}/` | **迭代级** — 历史快照；可提升 | product / architect / PM @ start & execute | compass + **`<iteration-id>/` workspace** |
+| **Knowledge** | `{KNOWLEDGE_DIR}/` | **是** — 可复用实施 SSOT | **`mstar-compound`** @ **iteration-close**（含 workspace 提升） | 结晶、提升后的长期实施知识 |
+
+```text
+iteration-start / execute
+  product / architect  ──►  {SPECS_DIR}/              已锁定的长期规格
+                         ──►  {ITERATION_DIR}/<id>/   迭代级 specs + guides（工作区）
+                         ✗   {KNOWLEDGE_DIR}/          不直接新增
+
+iteration-close (§3.2)
+  mstar-compound       ──►  读 plan 素材 + {ITERATION_DIR}/<id>/**
+                         ──►  {KNOWLEDGE_DIR}/          提升值得保留的 specs/guides
+```
+
+## `{ITERATION_DIR}/<iteration-id>/` 工作区（迭代级 specs & guides）
+
+compass 仍在根目录：`**{ITERATION_DIR}/<iteration-id>-delivery-compass.md**`（现有约定）。**迭代级** specs / guides 放入同名子目录工作区：
+
+```text
+{ITERATION_DIR}/
+  README.md
+  <iteration-id>-delivery-compass.md
+  <iteration-id>/
+    README.md              # 可选：本迭代工作区索引
+    guides/                # 探索笔记、过程指南、未锁定权衡
+    specs/                 # 迭代级规格草案（尚未升格到 {SPECS_DIR}/ 或 knowledge）
+    <flat-files>.md        # 允许；大迭代可再分子目录
+```
+
+| 子路径 | 放什么 | 不放什么 |
+|--------|--------|----------|
+| **`<iteration-id>/guides/`** | 候选方案、调研、会议记录、实施过程说明 | 已锁定的仓库级规范 |
+| **`<iteration-id>/specs/`** | 本迭代演进中的规格、迭代内契约草稿 | 已锁定、跨迭代 `{SPECS_DIR}/` 级权威（应升格或已在 `{SPECS_DIR}/`） |
+| **compass（根）** | 范围、plans 表、验收、分支策略 | 长文探索正文（链到 workspace） |
+
+**何时用 workspace 而非单文件 working guide**：一篇 guide 不够时，**默认**用 `<iteration-id>/` 目录；单文件 `<iteration-id>-working-guide.md` 仍允许作轻量入口（可链接进 workspace）。
+
+**索引**：`{ITERATION_DIR}/README.md` 登记 compass 行 + workspace 目录行；workspace 内 `README.md` 列出 `guides/`、`specs/` 下文档。
+
+## `{SPECS_DIR}/` 准入（仓库级长期）
+
+写入 `{SPECS_DIR}/` 前须满足 **至少一条**（与 iteration workspace 区分）：
+
+- 决策**已锁定**，变更需显式评审
+- 跨 plan、跨迭代仍成立
+- 本迭代及后续 plan 的 **`primary_spec` / `spec_refs`** 权威来源
+
+**不应**进 `{SPECS_DIR}/`：
+
+- 仍在迭代内演进的草案 → **`<iteration-id>/specs/`**
+- 探索 scratch → **`<iteration-id>/guides/`**
+- 实施踩坑（未整理）→ 留 workspace 或 plan 素材，**close 时 compound 提升**
+
+## Knowledge 与 compound 提升
+
+- **`{KNOWLEDGE_DIR}/` 新增**：默认仅在 **iteration-close** §3.2 **`mstar-compound`**。
+- **提升来源（iteration-close）**：除 plan 实现/debug/review 素材外，**必须盘点** `{ITERATION_DIR}/<iteration-id>/**`（`guides/`、`specs/`、扁平文件）。值得跨迭代复用的内容 → 按 compound 双轨模板**重写**进 `{KNOWLEDGE_DIR}/`（非整文件复制）；细则 → **`mstar-compound`**「Iteration workspace promotion」。
+- **提升后**：在源文件顶部或 workspace `README.md` 标注 `Promoted to: {KNOWLEDGE_DIR}/...`；源文件**保留**为迭代历史（或迁入 `<iteration-id>/archived/` 若团队约定）。
+- **iteration-start §1.6**：product / architect **不得**向 `{KNOWLEDGE_DIR}/` **新增**；误写由 writing-specialist 迁回 **workspace**。
+
+## §1.6 各角色编辑范围
+
+| 角色 | 必须编辑 | 禁止 |
+|------|----------|------|
+| **product-manager** | compass、plans、`{SPECS_DIR}/`、`{ITERATION_DIR}/<iteration-id>/`（guides/specs） | `{KNOWLEDGE_DIR}/` **新增**；迭代草案写入 `{SPECS_DIR}/` |
+| **architect** | 同上 + workspace `specs/` 技术向 | 同上；在 `{SPECS_DIR}/` 堆实施踩坑 |
+| **writing-specialist** | 当轮文档 + `{SPECS_DIR}/` corpus hygiene + 既有 knowledge 卫生 | 代替 compound **提升**；跳过 specs 全库审查 |
+
+Phase 2 执行期：各角色可继续向 **`<iteration-id>/`** 追加 guides/specs；**仍不**直写 `{KNOWLEDGE_DIR}/`。
+
+## plans[].metadata 挂接
+
+| 内容 | 挂接键 | 路径 |
+|------|--------|------|
+| 仓库级锁定规格 | `primary_spec` / `spec_refs` | `{SPECS_DIR}/` |
+| 迭代上下文 | `iteration_compass` / `iteration_refs` | compass + `{ITERATION_DIR}/<iteration-id>/...` |
+| 知识库（已有） | 仅历史链接 | `{KNOWLEDGE_DIR}/` — **start 不新增** |
+
+## 反模式
+
+- 用 `{KNOWLEDGE_DIR}/` 存迭代探索（应进 `<iteration-id>/guides/`）
+- 把迭代 workspace 草案直接复制进 `{SPECS_DIR}/` 而不锁定评审
+- iteration-close **只做** plan 素材 compound、**不**盘点 `<iteration-id>/` workspace
+- 提升时整文件复制到 knowledge（应 compound 结构化重写）

package/harness-skills/mstar-iteration/references/iteration-compass-template.md

@@ -71,6 +71,20 @@ Status values: `Todo` | `InProgress` | `InReview` | `Done` | `Blocked`
 |------|-----------|--------|------------|
 | <risk> | Low/Med/High | Low/Med/High | <mitigation> |
 
+## Iteration workspace (optional)
+
+> Iteration-level **specs** and **guides** live under `{ITERATION_DIR}/<iteration-id>/` — not in `{SPECS_DIR}/` or `{KNOWLEDGE_DIR}/`. Promoted to knowledge at iteration-close via **`mstar-compound`**.
+
+| Path | Purpose |
+|------|---------|
+| `<iteration-id>/guides/` | Exploration, process notes |
+| `<iteration-id>/specs/` | Iteration-scoped spec drafts |
+| `<iteration-id>/README.md` | Workspace index (recommended when non-trivial) |
+
+Link from compass when used:
+
+- Workspace: `<iteration-id>/` | <one-line purpose>
+
 ## Compound Round Summary
 
 > Filled at iteration-close.
@@ -105,6 +119,7 @@ Status values: `Todo` | `InProgress` | `InReview` | `Done` | `Blocked`
 | `## Non-Goals` | Yes | Phase 1 |
 | `## Roadmap Position` | **Yes** | Phase 1（必填节，非散落于 general context prose）；Phase 3 §3.3（current iteration → `delivered`） |
 | `## Risk Register` | Optional | Phase 1, Phase 2 (update) |
+| Iteration workspace (`<iteration-id>/`) | Optional | Phase 1 §1.5.5 — `guides/` + `specs/`; index in `{ITERATION_DIR}/README.md` |
 | `## Compound Round Summary` | Yes | Phase 3 §3.4 |
 | `## Iteration Retrospective` | Recommended | Phase 3 §3.4 |
 

package/harness-skills/mstar-iteration/references/iteration-corpus-hygiene.md

@@ -0,0 +1,51 @@
+# iteration-start corpus hygiene（specs primary · knowledge read-only）
+
+> **When**: Phase 1 §1.6 — **writing-specialist** only, after product/architect landed compass / plans / `{SPECS_DIR}/` / **`{ITERATION_DIR}/<iteration-id>/`** workspace.
+> **Boundaries**: **`iteration-artifact-boundaries.md`** — no `{KNOWLEDGE_DIR}/` adds @ start; iteration drafts → **`<iteration-id>/guides/`** or **`specs/`**.
+
+## Scope (HARD)
+
+| Priority | Tree | Action |
+|----------|------|--------|
+| **Primary** | `{SPECS_DIR}/**` | Full active corpus review |
+| **Included** | `{ITERATION_DIR}/<iteration-id>/**` | Workspace guides/specs + compass cross-links |
+| **Secondary** | `{KNOWLEDGE_DIR}/**` (existing) | Archive / relocate only — **no** new docs |
+| **Included** | `{PLAN_DIR}/` plans touched this iteration | Spec refs, terminology |
+
+**Out of scope**: compound promotion (iteration-close); `{PLAN_DIR}/reports/`; code.
+
+## Misplaced content (relocate)
+
+| Found in | Target |
+|----------|--------|
+| `{SPECS_DIR}/` | Iteration-only draft → `{ITERATION_DIR}/<iteration-id>/specs/` or `guides/` |
+| `{SPECS_DIR}/` | Implementation/debug notes → workspace `guides/` (compound @ close) |
+| `{KNOWLEDGE_DIR}/` | New exploration from start chain → `<iteration-id>/guides/` or archive |
+| Flat `{ITERATION_DIR}/*-working-guide.md` | OK as entry; or merge into `<iteration-id>/guides/` when workspace exists |
+
+## Classification
+
+Same as before for specs + existing knowledge: Active / Superseded / Redundant / Obsolete / Unclear → archive under `archived/specs/` or `archived/knowledge/` with relative path preserved.
+
+## Index and metadata
+
+1. `{SPECS_DIR}/README.md` — update as needed
+2. `{KNOWLEDGE_DIR}/README.md` — archive rows only; no new iteration exploration rows
+3. `{ITERATION_DIR}/README.md` — compass + **`<iteration-id>/` workspace** directory row
+4. `{ITERATION_DIR}/<iteration-id>/README.md` — list guides/specs (create if non-trivial)
+5. `plans[].metadata` — `primary_spec` / `spec_refs` → `{SPECS_DIR}/`; `iteration_refs` → workspace paths
+
+## Evidence of done
+
+- No iteration scratch left in `{SPECS_DIR}/`
+- Workspace used for iteration-level drafts (`<iteration-id>/guides|specs/`)
+- No new `{KNOWLEDGE_DIR}/` from §1.6 chain
+- Completion Report lists workspace paths + spec hygiene moves
+
+## Distinction from compound @ iteration-close
+
+| | §1.6 hygiene | compound workspace promotion |
+|--|--------------|------------------------------|
+| When | iteration-start | iteration-close §3.2 |
+| `{ITERATION_DIR}/<id>/` | Create/edit drafts | **Inventory → promote** to `{KNOWLEDGE_DIR}/` |
+| `{KNOWLEDGE_DIR}/` | No new writes | Structured new docs |

package/harness-skills/mstar-iteration/references/iteration-workspace-readme-template.md

@@ -0,0 +1,29 @@
+# Iteration workspace README (template)
+
+Optional index inside `{ITERATION_DIR}/<iteration-id>/`. Copy when the workspace has more than a few files.
+
+```markdown
+# <iteration-id> workspace
+
+Iteration-scoped **specs** and **guides** — not `{KNOWLEDGE_DIR}/`. Worthy content is **promoted** at iteration-close via `mstar-compound`.
+
+## Guides
+
+| Document | Description | Status |
+|----------|-------------|--------|
+| [guides/<name>.md](guides/<name>.md) | <purpose> | draft / active / promoted |
+
+## Specs (iteration-level)
+
+| Document | Description | Status |
+|----------|-------------|--------|
+| [specs/<name>.md](specs/<name>.md) | <purpose> | draft / locked-in-{SPECS_DIR} / promoted |
+
+## Promotion log (filled at iteration-close)
+
+| Source | Promoted to | Date | Notes |
+|--------|-------------|------|-------|
+| | | | |
+```
+
+**Status values**: `draft` | `active` | `promoted` (link knowledge path) | `superseded` | `snapshot-only`

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

@@ -12,9 +12,9 @@
 | 区域 | 典型内容 | 受众 / 权威 |
 |------|----------|-------------|
 | **`docs/`**（或项目约定的用户文档根） | 安装/quickstart、稳定架构概览、贡献指南、对外 API 说明 | 人类贡献者与终端用户；clone 后应可读 |
-| **`{SPECS_DIR}`**（可选） | 冻结 v1-spec、ADR、program roadmap | 产品/API 规范性最高权威；变更须显式流程 |
-| **`{ITERATION_DIR}`**（可选） | `*-delivery-compass-*`、`*-program-compass-*`、版本范围/验收/风险、遗留 `v1.*` 规划快照 | Agent handoff；**不**替代 `{SPECS_DIR}` |
-| **`{KNOWLEDGE_DIR}`**（可选） | 实现细节 SSOT、架构细则、契约说明、跨版本 tracker、性能基线 | Agent handoff；**不**覆盖 `{SPECS_DIR}` 中的规范性条款 |
+| **`{SPECS_DIR}`**（可选） | 冻结 v1-spec、ADR、program roadmap — **跨迭代长期权威** | 产品/API 规范性最高权威；**iteration-start** 由 product/architect 主写 |
+| **`{ITERATION_DIR}`**（可选） | delivery compass + **`<iteration-id>/` workspace**（`guides/`、`specs/`） | Agent handoff；迭代级草稿；close 时 compound **提升** → knowledge |
+| **`{KNOWLEDGE_DIR}`**（可选） | 实现细节 SSOT、架构细则、契约说明、跨版本 tracker — **经 `mstar-compound` 结晶** | Agent handoff；**不**在 iteration-start 由 product/architect 新增 |
 | **`{PLAN_DIR}/`** | 单 plan 主文件、`reports/`、可选 `residuals/` | 计划执行与审查留档 |
 
 
@@ -23,15 +23,21 @@
 ## `{ITERATION_DIR}`（可选·迭代/版本级 compass）
 
 - **物理路径**：`**{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」分表。
-- **与 plan 的链接**：在 `**plans[].metadata**` 中可用 `**iteration_compass**`（单文件）或 `**iteration_refs**`（`string[]`）登记仓库内相对路径；PM 在 Assignment 点名本轮须读的 compass。
-- **维护**：`@product-manager` / `@architect` 起草；`**@project-manager**` 维护 README 与 metadata 挂接；compass 定稿后**少改多版本**（新版本优先新文件名 `v<N>` 或新 compass 文件）。
+- **放什么**：delivery compass（根目录 `*-delivery-compass*.md`）；**`<iteration-id>/` 工作区** — `guides/`（探索、过程）、`specs/`（迭代级规格草案）；遗留规划快照。
+- **不放什么**：已锁定的仓库级规范（→ **`{SPECS_DIR}/`**）；已提升的跨迭代实施 SSOT（→ **`{KNOWLEDGE_DIR}/`**，经 compound）；单 plan QC（→ `reports/`）。
+- **索引**：`**{ITERATION_DIR}/README.md**` 登记 compass + workspace 目录；`<iteration-id>/README.md` 登记工作区内文档。
+- **维护**：`@product-manager` / `@architect` 起草 workspace；`**@project-manager**` 维护索引与 metadata；**iteration-close** 时 **`mstar-compound`** 盘点 workspace 并**提升**至 `{KNOWLEDGE_DIR}/`。
+
+## `{SPECS_DIR}`（可选·长期规格）
+
+- `{SPECS_DIR}` 解析：优先 `{HARNESS_DIR}/specs/`，否则 `{HARNESS_DIR}/designs/`；皆无则建议新建 `specs/`。
+- **放什么**：跨迭代有效、已锁定或待锁定的产品/API 规范、ADR、契约 — **iteration-start 主产出**（product/architect）。
+- **不放什么**：本迭代-only 探索（→ `<iteration-id>/guides/`）；迭代级 spec 草案（→ `<iteration-id>/specs/`）；实施踩坑原文（→ workspace 或 plan 素材，**close 时 compound 提升**）。
+- **索引**：非 trivial 树建议 `{SPECS_DIR}/README.md`；plan **`primary_spec` / `spec_refs`** 主要指向此处。
 
 ## `{KNOWLEDGE_DIR}`（可选·实施知识库）
 
-- `{SPECS_DIR}` 定义：优先 `{HARNESS_DIR}/specs/`，否则 `{HARNESS_DIR}/designs/`；若两者都不存在，建议新建 `{HARNESS_DIR}/specs/`。
+- **新增 SSOT 默认路径**：**iteration-close** 时经 **`mstar-compound`** 写入；**iteration-start §1.6 禁止** product/architect 新增（见 **`mstar-iteration/references/iteration-artifact-boundaries.md`**）。
 - **必须**维护 `**{KNOWLEDGE_DIR}/README.md**` 作为**目录索引**：至少包含表格列 **Document（链接）**、**Source Plan（`plans[].id`）**、**Description**、**Status**（如 `Active` / `Superseded by implementation (<plan-id>)` / `Archived`）。
 - 可选：目录级 `**{KNOWLEDGE_DIR}/AGENTS.md**` 承载命名、维护节奏、与 `{SPECS_DIR}` 的权威边界（Nexus 模式）；harness 宽规则仍以 `mstar-plan-conventions` 与本 reference 为准。
 - 初始化启用知识库时：创建空表头的 `README.md`，随文档递增行。
@@ -44,16 +50,21 @@
 
 ## 与 `status.json` 的链接
 
-- 某 plan 的**权威设计输入**在知识库、迭代 compass 或规格目录中时，在 `**plans[].metadata**` 中登记路径，推荐使用已列标准键：`**primary_spec**`（单文件）、`**spec_refs**`（`string[]`）、`**iteration_compass**` / `**iteration_refs**`（迭代级，可选）。路径为**仓库内相对路径**（推荐布局下常写作 `**.mstar/knowledge/....md**`、`**.mstar/iterations/....md**` 或 `**.mstar/specs/....md**`；兼容旧目录时也可为 `.agents/...`）。
+- 某 plan 的**权威设计输入**在规格、迭代 compass 或（已有）知识库中时，在 `**plans[].metadata**` 中登记路径：`**primary_spec**` / `**spec_refs**` → 优先 **`{SPECS_DIR}/`**；`**iteration_compass**` / `**iteration_refs**` → **`{ITERATION_DIR}/`**；已有 **`{KNOWLEDGE_DIR}/`** 链接保留，但 **iteration-start 不得新增** knowledge 路径。
 - 执行方在 **implement 前**须按 metadata 读取这些文件，并与主 plan 核对；不得在未读链接文档的情况下**静默偏离**其中已写明的决策（若需偏离，先回写 knowledge 或 plan 并走 PM/architect 门禁）。
 
 ## 维护规则
 
-1. **新增**：按命名规则添加 `.md` → 在 `{KNOWLEDGE_DIR}/README.md` 或 `{ITERATION_DIR}/README.md` 索引表增加一行 → 在相关 `plans[].metadata` 更新 `primary_spec` / `spec_refs` / `iteration_*`（若该文档为本 plan 输入/输出）。
+1. **新增**：
+   - **Specs（长期）**：`{SPECS_DIR}/` → spec 索引（若有）→ `plans[].metadata` 的 `primary_spec` / `spec_refs`
+   - **迭代 workspace**：`{ITERATION_DIR}/<iteration-id>/guides|specs/` → `{ITERATION_DIR}/README.md` + workspace README → `iteration_refs`
+   - **Knowledge**：**`mstar-compound`** @ iteration-close（含 workspace **提升**）→ `{KNOWLEDGE_DIR}/README.md`
 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/`**（该处用于**计划行**冷快照）；知识库用索引状态表达生命周期即可。
-5. **结晶（Compound）**：PM 在迭代收口时（`mstar-iteration` § iteration-close）批量触发 `mstar-compound`，将整轮迭代的经验沉淀为结构化知识文档（`{KNOWLEDGE_DIR}/<category>/<slug>.md`，YAML frontmatter + 双轨模板）。compound 是迭代级活动，不在 per-plan Done 后单独执行。定期维护由 `mstar-compound-refresh` 执行。详见 **`mstar-compound`**、**`mstar-iteration`** 与 **`mstar-compound-refresh`**。
+4. **归档**：
+   - **iteration-start（强制）**：`writing-specialist` §1.6 以 **`{SPECS_DIR}/` 全库卫生为主**；对**既有** `{KNOWLEDGE_DIR}/` 仅归档/错放纠正，**不**新增 knowledge。细则 → **`mstar-iteration/references/iteration-corpus-hygiene.md`**。
+   - **其它时机**：当文档内容已完全反映到已合并代码中、且非 iteration-start 扫库时：可将索引 **Status** 标为 `Superseded by implementation (...)` 或 `Archived`；可保留原位或迁入 `archived/knowledge/`。**不要**把知识库产物搬进 `{HARNESS_DIR}/archived/plans/`（该处用于**计划行**冷快照）。
+5. **结晶（Compound）**：PM 在 **iteration-close** 触发 **`mstar-compound`**：plan 素材 + **`{ITERATION_DIR}/<iteration-id>/` workspace 提升** → `{KNOWLEDGE_DIR}/`。不在 per-plan Done 后单独执行。维护 → **`mstar-compound-refresh`**。
 
 ## 与 `reports/`、`{PLAN_DIR}/residuals/` 的区分
 

package/harness-skills/mstar-plan-conventions/references/artifact-storage-paths.md

@@ -17,9 +17,12 @@
 | **SDD scratch** | `{HARNESS_DIR}/sdd/<plan-id>/`（gitignored） | `mstar-sdd` |
 | **status.json** | `.mstar/status.json` | `mstar-plan-artifacts` |
 | **迭代 compass** | `.mstar/iterations/<iteration-id>-delivery-compass.md` | `mstar-iteration`（读写） |
+| **迭代工作区** | `.mstar/iterations/<iteration-id>/`（`guides/`、`specs/` 等） | `mstar-iteration`（读写）；close 时 `mstar-compound`（提升读） |
 | **迭代索引** | `.mstar/iterations/README.md` | `mstar-iteration`（读写） |
 | **规格** | `specs/`（优先），否则 `designs/` | `mstar-plan-artifacts` |
 | **archived residuals** | `.mstar/archived/residuals/<plan-id>.json` | `mstar-plan-artifacts` |
+| **archived knowledge** | `.mstar/archived/knowledge/`（保留原 `{KNOWLEDGE_DIR}` 相对路径） | `mstar-iteration` §1.6 corpus hygiene、`mstar-plan-artifacts` |
+| **archived specs** | `.mstar/archived/specs/`（保留原 `{SPECS_DIR}` 相对路径） | `mstar-iteration` §1.6 corpus hygiene、`mstar-plan-artifacts` |
 
 ## 仓库根目录（`<repo-root>/`，与 `.git/` 同级）
 

package/harness-skills/mstar-roles/references/architect.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare: specify/clarify/plan), `mstar-plan-conventions` (`{PLAN_DIR}`, plan-writing path).
 
-**Typically:** `mstar-plan-artifacts` (knowledge/specs/ADR placement); `mstar-design-md` (DESIGN.md design system spec — architect is primary creator); `mstar-coding-behavior` (surgical doc edits).
+**Typically:** `mstar-plan-artifacts` (specs, **`{ITERATION_DIR}/<id>/` workspace**); `mstar-design-md`; `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**.
 
 **On demand:** `mstar-branch-worktree` (when committing architecture docs to the business repo).
 

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

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-plan-conventions` (`{PLAN_DIR}`, plan-writing path).
 
-**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-design-md` (DESIGN.md design intent and requirements for UI planning); `mstar-coding-behavior` (surgical doc edits).
+**Typically:** `mstar-plan-artifacts` (specs, **`{ITERATION_DIR}/<id>/` workspace** — not knowledge @ start); `mstar-design-md`; `mstar-coding-behavior`. Boundaries → **`mstar-iteration/references/iteration-artifact-boundaries.md`**.
 
 **On demand:** `mstar-branch-worktree` (when committing product docs to the business repo).
 

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

@@ -177,4 +177,4 @@ read `mstar-host` → the active host reference and `references/parallel-dispatc
 
 - 把整份 plan 或 T1–Tn 全文贴进 **一个** `fullstack-dev` leaf Assignment。
 - 省略 `Execution mode` / `SDD dir` / `Model tier` 却期望 SDD 产物（`progress.md`、per-task review）。
-- 期望 leaf `fullstack-dev` 载入 `mstar-sdd` 并自编排 per-task 循环 — **编排仅 PM**（`iteration-drive` / `mstar-iteration` §2.4–2.5）。
+- 期望 leaf `fullstack-dev` 载入 `mstar-sdd` 并自编排 per-task 循环 — **编排仅 PM**（`mstar-iteration` §2.4–2.5）。

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

@@ -143,7 +143,7 @@ If any fail -> do not dispatch implement.
 | Entry | Next reads |
 |-------|------------|
 | **`/pm`** or **`pm` skill** (Codex, Cursor; OpenCode when no command) | This shim → **`project-manager.md`** § Required Reading + topic skills on demand |
-| **Cursor / OpenCode** **`commands/`** (`iteration-start`, `iteration-drive`, `mstar-bootstrap`) | Command **Boot** + **`project-manager.md`** — iteration lifecycle only; **not** required for ordinary per-plan PM |
+| **Cursor / OpenCode** host iteration `commands/` | Command Boot + **`project-manager.md`** — iteration lifecycle only; **not** required for ordinary per-plan PM |
 | **OpenCode** (no command, not `/pm`) | `project-manager` + `mstar-host` → `opencode.md` |
 
 **Dispatch-first**, iteration branch policy（`iteration_base_branch` / `spec_integration_branch` / `target_branch`）, Autonomous Execute → **`mstar-iteration`** §2. Routing, gates, Task Board, QC, templates → this file + topic `mstar-*` skills.

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

@@ -36,6 +36,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 3. Marketing/copy writing
 4. Script writing
 5. Tone/style adaptation by audience
+6. **iteration-start corpus hygiene** (§1.6 step 3): specs-first hygiene; misplaced drafts → **`{ITERATION_DIR}/<iteration-id>/`** workspace — **`iteration-artifact-boundaries.md`** + **`iteration-corpus-hygiene.md`**. **Promotion** workspace → knowledge is **`mstar-compound`** @ iteration-close only.
 
 ## Scope Boundaries
 

package/harness-skills/mstar-sdd/references/sticky-implementer-session.md

@@ -11,7 +11,7 @@ SSOT for mode selection and host resume → this file. Per-task artifacts → **
 | **`fresh`** (default) | Independent tasks, module boundaries, different dev tracks, or first task on a plan |
 | **`sticky`** | Same `fullstack-dev` (or same role id), sequential tasks on one branch, strong file/context continuity (e.g. T3+T4 daemon stderr + DB reset) |
 
-**Prefer `sticky`** on iteration-drive Phase 2 when PM will dispatch many tasks to the same dev on one plan feature branch.
+**Prefer `sticky`** on iteration Phase 2 Autonomous Execute when PM will dispatch many tasks to the same dev on one plan feature branch.
 
 ## Assignment fields (implement dispatch)
 

package/harness-skills/pm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pm
-description: "PM entry shim — force project-manager orchestration when user invokes /pm or this skill (Codex and Cursor). General per-plan PM work: this skill + project-manager.md. Formal iteration lifecycle on Cursor/OpenCode: commands (iteration-start, iteration-drive, mstar-bootstrap). Boot, routing, dispatch SSOT → mstar-roles/references/project-manager.md and topic mstar-* skills — not here."
+description: "PM entry shim — force project-manager orchestration when user invokes /pm or this skill (Codex and Cursor). General per-plan PM work: this skill + project-manager.md. Formal iteration lifecycle: mstar-iteration (host commands/ may orchestrate Phase 1–5). Boot, routing, dispatch SSOT → mstar-roles/references/project-manager.md and topic mstar-* skills — not here."
 ---
 
 # PM (entry shim)
@@ -12,10 +12,10 @@ description: "PM entry shim — force project-manager orchestration when user in
 | Host | Use |
 |------|-----|
 | **Codex** | **`/pm`** or this skill → **`project-manager`** for the session |
-| **Cursor** | **`/pm`** or this skill → general PM orchestration (single-plan, hotfix, QC waves, dispatch) **without** starting an iteration. Formal iteration → **`commands/`** below |
+| **Cursor** | **`/pm`** or this skill → general PM orchestration (single-plan, hotfix, QC waves, dispatch) **without** starting an iteration. Formal iteration → host **`commands/`** + **`mstar-iteration`** |
 | **OpenCode** | Same as Cursor when no command: **`project-manager`** via `mstar-roles` → `references/project-manager.md` |
 
-**Iteration commands** (optional; carry their own Boot): `iteration-start`, `iteration-drive`, `mstar-bootstrap` — use when running Phase 1–5 iteration lifecycle, not required for ordinary PM work.
+**Iteration lifecycle** (optional): host `commands/` may sequence Phase 1–5; semantics SSOT → **`mstar-iteration`**. Not required for ordinary PM work.
 
 Detect host → **`mstar-host`** → `references/codex.md` | `cursor.md` | `opencode.md`.
 
@@ -25,10 +25,11 @@ Detect host → **`mstar-host`** → `references/codex.md` | `cursor.md` | `open
 2. `mstar-roles` → **`references/project-manager.md`** — required reading list, routing, dispatch-first, iteration branch policy
 3. Topic skills **on demand** per that file and the active workflow (`mstar-dispatch-gates`, `mstar-iteration`, `mstar-sdd`, `mstar-review-qc`, …)
 
-## Three rules (everything else is a pointer)
+## Four rules (everything else is a pointer)
 
 1. **Delegate** — PM does not implement, QC, or QA in-thread (`project-manager.md` Execution Boundary; hotfix → `mstar-phase-gates`).
 2. **Dispatch** — when host has invoke/Task tools: **1 Assignment ⇒ 1 invoke** (`mstar-dispatch-gates`). Markdown alone is not dispatch.
-3. **SSOT** — iteration lifecycle → **`mstar-iteration`** (or **`commands/`** on Cursor/OpenCode); Cursor Plan mode → **`mstar-host/references/cursor-plan-mode-bridge.md`**.
+3. **SSOT** — iteration lifecycle → **`mstar-iteration`**; Cursor Plan mode → **`mstar-host/references/cursor-plan-mode-bridge.md`**.
+4. **Autonomous Execute push** — multi-plan iteration Phase 2–5: continuously dispatch implement → QC → QA → Done through merge-ready exit without routine yes/no prompts; **Blocked** only on true conflicts or metadata gaps → **`mstar-iteration` §2.6**.
 
 Conflict: user instructions → project `AGENTS.md` / `CLAUDE.md` → `mstar-harness-core` → this file.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "Morning Star harness OpenCode plugin (skills bootstrap and agent loading).",
   "license": "MIT",
   "repository": {
@@ -16,7 +16,9 @@
     "harness-agents",
     "harness-commands",
     "AGENTS.md",
-    "INSTALL.md"
+    "INSTALL.md",
+    "README.md",
+    "CHANGELOG.md"
   ],
   "scripts": {
     "bundle-assets": "bun run scripts/bundle-harness-assets.ts",