@mstar-harness/omp 3.6.0-alpha.4

package/harness-skills/mstar-iteration/references/command-shared-invariants.md

@@ -0,0 +1,62 @@
+# Iteration 命令共享 invariants + preflight
+
+本文件是 `commands/iteration-*.md`（`iteration-start` / `iteration-drive` / `iteration-loop`）**重叠内容**的单一共享副本（SSOT）。**只收录出现在 ≥2 个命令中的行**；命令专属内容保留在命令正文，**不**复制进本文件：
+
+- `iteration-start` Phase 1 review-chain 表（§5.1→§5.2→§5.3 顺序 invoke、三角色冒充禁止、`{KNOWLEDGE_DIR}/` 新增禁止）— start 专属
+- `iteration-loop`「Do not Read `skills/grill-me/SKILL.md`」— loop 专属
+- `iteration-loop` session todo `phase-1-autonomous-start`（Boot → compass `locked` + integration committed）— loop 专属
+
+命令正文经一行指针引用本文件，不重复定义以下 invariants / preflight / todos / STOP。
+
+## PM invariants（重叠行）
+
+Phase 2–5 全程有效（drive + loop 共有的行）：
+
+| 禁止（PM 线程） | 必须 |
+|-----------------|------|
+| Write/Edit/Shell 产品代码、写测试、跑 QC（Phase 2） | 每条 implement/QC/QA Assignment ⇒ **1 次 `Task`** |
+| **多 task plan 用 inline 大包派发**（整份 plan / T1–Tn 贴进一个 dev Assignment） | **SDD**：`mstar-sdd` per-task 循环 — `mstar sdd task-brief` → implementer → `mstar sdd review-package` → task reviewer → `progress.md` |
+| 只写 Assignment 就进入下一 gate | 同轮 dispatch：每条 Assignment ⇒ **1 次 invoke**（`Subagent invokes issued: N`，N = Assignment 条数） |
+| 最后一个 plan `Done` 后直接开 PR / 汇报结束 | **Phase 3 → 4 → 5** 顺序执行 |
+| Phase 5 自己改产品代码 | 需改产品代码时 **dispatch** `fullstack-dev` / `ops-engineer` |
+
+派发细则 → **`mstar-dispatch-gates`** + **`mstar-host`**。Phase 3 细则 → **`mstar-iteration` §3** + **`mstar-compound`**。
+
+## Assignment preflight（bash 块 — byte-identical 共享副本）
+
+`mstar-harness` bin 未安装时静默跳过；在每次 implement/QC/QA 派发前（**SDD** 下为最新 `{SDD_DIR}/task-N-brief.md` 或临时写盘的 Assignment）校验。模式由迭代 compass frontmatter 的 `enforcement` 键决定（Slice 5）：
+
+- **默认（compass 无 `enforcement: hard`）— 可选 warn-only**：exit 1 仅提示，不阻断派发（Slice 3 行为不变）：
+
+```bash
+command -v mstar-harness >/dev/null 2>&1 && mstar-harness dispatch validate "<latest-assignment-file>"
+```
+
+- **`enforcement: hard`（迭代 compass frontmatter 声明）— fail-fast**：校验失败即 `exit 1` 阻断派发（bin 缺失仍静默跳过）：
+
+```bash
+if command -v mstar-harness >/dev/null 2>&1; then mstar-harness dispatch validate "<latest-assignment-file>" || exit 1; fi
+```
+
+> 路径必须加引号且替换为具体文件（如最新 `{SDD_DIR}/task-N-brief.md`，勿留尖括号）——agent 代入的路径不得进入 shell 无引号展开。
+
+## Session todos（重叠行；drive + loop 共有）
+
+| Todo id | 何时追加 | 何时可勾掉 |
+|---------|----------|------------|
+| plan-wave todos | 进入 Phase 2 | 各 plan `Done` |
+| `phase-3-iteration-close` | 仅剩 1 个非 `Done` plan | Phase 3 §3.5 exit 全 `[x]` |
+| `phase-4-create-pr` | Phase 3 完成后 | PR 已创建并记录 URL/number |
+| `phase-5-pr-merge-ready` | Phase 4 完成后 | Phase 5 §5.5 exit 全 `[x]` |
+
+## Continuous execution STOP list（重叠行；start / drive / loop 共有）
+
+Execute **`mstar-iteration` §2.6**（Continuous execution SSOT：自 Phase 2 进入至 Phase 5 §5.5 exit 前 PM **连续编排**，进度汇报后下一条必须是 dispatch 或下一 phase 步骤，不向用户例行 yes/no check-in）。
+
+**合法 STOP（仅此升级用户）**：
+
+- 迭代 branch metadata 缺失（`iteration_base_branch` / `target_branch`）
+- **`Blocked`**：真冲突、secrets、不可逆范围缺口、Phase 5 多轮仍无法 merge-ready
+- 用户本轮显式打断
+
+**Turn 收束纪律**：最后一条 assistant 内容必须是 **in-flight 动作**（invoke 已发出、或写明下一 dispatch 的 Assignment 字段），**不得**以对用户的确认问句收束 turn。

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

@@ -0,0 +1,103 @@
+# iteration-start 产物边界（specs · iterations · knowledge）
+
+> **When**: Phase 1 — PM 初稿落盘、§1.6 Review & Edit chain；Phase 2 迭代执行期可继续写入 iteration package；Phase 3 iteration-close 经 **`mstar-compound`** 提升。
+> **Conflict**: 与 `mstar-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 | **`<iteration-id>/` package**（compass + specs/guides） |
+| **Knowledge** | `{KNOWLEDGE_DIR}/` | **是** — 可复用实施 SSOT | **`mstar-compound`** @ **iteration-close**（含 package 提升） | 结晶、提升后的长期实施知识 |
+
+```text
+iteration-start / execute
+  product / architect  ──►  {SPECS_DIR}/                    已锁定的长期规格
+                         ──►  {ITERATION_DIR}/<id>/         迭代 package（compass + specs + guides）
+                         ✗   {KNOWLEDGE_DIR}/                不直接新增
+
+iteration-close (§3.2)
+  mstar-compound       ──►  读 plan 素材 + {ITERATION_DIR}/<id>/**
+                         ──►  {KNOWLEDGE_DIR}/                提升值得保留的 specs/guides
+```
+
+## `{ITERATION_DIR}/<iteration-id>/` 迭代 package（目录优先）
+
+**Canonical layout**（新 iteration-start **只写**此形态）：
+
+```text
+{ITERATION_DIR}/
+  README.md                         # 根索引：每迭代一行 → 指向 <iteration-id>/
+  <iteration-id>/
+    delivery-compass.md             # 迭代状态 SSOT（frontmatter status）
+    README.md                       # 本迭代文档索引（有 guides/specs 时推荐）
+    guides/                         # 探索笔记、过程指南、未锁定权衡
+    specs/                          # 迭代级规格草案
+```
+
+| 子路径 | 放什么 | 不放什么 |
+|--------|--------|----------|
+| **`delivery-compass.md`** | 范围、plans 表、验收、分支策略、close 摘要 | 长文探索正文（链到 `guides/` / `specs/`） |
+| **`guides/`** | 候选方案、调研、会议记录、实施过程说明 | 已锁定的仓库级规范 |
+| **`specs/`** | 本迭代演进中的规格、迭代内契约草稿 | 已锁定、跨迭代 `{SPECS_DIR}/` 级权威（应升格或已在 `{SPECS_DIR}/`） |
+| **`README.md`** | 本 package 内 documents 索引（单表即可） | 替代根 `{ITERATION_DIR}/README.md` |
+
+**索引**：
+
+- **`{ITERATION_DIR}/README.md`**：**一行 = 一次迭代**（指向 `<iteration-id>/` 目录，**不**再拆 compass 行 + workspace 行）。
+- **`<iteration-id>/README.md`**：列出本目录下 `guides/`、`specs/`（及其它文档）；模板 → **`iteration-workspace-readme-template.md`**。
+
+**Compass 解析顺序**（读）：
+
+1. `{ITERATION_DIR}/<iteration-id>/delivery-compass.md`（canonical）
+2. Legacy flat：`{ITERATION_DIR}/<iteration-id>-delivery-compass.md`（仅兼容读；新写禁止）
+
+**禁止（新写）**：根目录 `<iteration-id>-delivery-compass.md`、根目录 `<iteration-id>-working-guide.md`。轻量入口一律进 `<iteration-id>/guides/`。
+
+## `{SPECS_DIR}/` 准入（仓库级长期）
+
+写入 `{SPECS_DIR}/` 前须满足 **至少一条**（与 iteration package 区分）：
+
+- 决策**已锁定**，变更需显式评审
+- 跨 plan、跨迭代仍成立
+- 本迭代及后续 plan 的 **`primary_spec` / `spec_refs`** 权威来源
+
+**不应**进 `{SPECS_DIR}/`：
+
+- 仍在迭代内演进的草案 → **`<iteration-id>/specs/`**
+- 探索 scratch → **`<iteration-id>/guides/`**
+- 实施踩坑（未整理）→ 留 package 或 plan 素材，**close 时 compound 提升**
+
+## Knowledge 与 compound 提升
+
+- **`{KNOWLEDGE_DIR}/` 新增**：默认仅在 **iteration-close** §3.2 **`mstar-compound`**。
+- **提升来源（iteration-close）**：除 plan 实现/debug/review 素材外，**必须盘点** `{ITERATION_DIR}/<iteration-id>/**`（`guides/`、`specs/`、扁平文件；**默认排除** `delivery-compass.md` 除非 PM 显式纳入）。值得跨迭代复用的内容 → 按 compound 双轨模板**重写**进 `{KNOWLEDGE_DIR}/`（非整文件复制）；细则 → **`mstar-compound`**「Iteration package promotion」。
+- **提升后**：在源文件顶部或 package `README.md` 标注 `Promoted to: {KNOWLEDGE_DIR}/...`；源文件**保留**为迭代历史（或迁入 `<iteration-id>/archived/` 若团队约定）。
+- **iteration-start §1.6**：product / architect **不得**向 `{KNOWLEDGE_DIR}/` **新增**；误写由 writing-specialist 迁回 **package**。
+
+## §1.6 各角色编辑范围
+
+| 角色 | 必须编辑 | 禁止 |
+|------|----------|------|
+| **product-manager** | compass、plans、`{SPECS_DIR}/`、`{ITERATION_DIR}/<iteration-id>/`（guides/specs） | `{KNOWLEDGE_DIR}/` **新增**；迭代草案写入 `{SPECS_DIR}/` |
+| **architect** | 同上 + package `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` | `{ITERATION_DIR}/<iteration-id>/delivery-compass.md` + 同目录下 docs |
+| 知识库（已有） | 仅历史链接 | `{KNOWLEDGE_DIR}/` — **start 不新增** |
+
+## 反模式
+
+- 用 `{KNOWLEDGE_DIR}/` 存迭代探索（应进 `<iteration-id>/guides/`）
+- 把迭代 package 草案直接复制进 `{SPECS_DIR}/` 而不锁定评审
+- iteration-close **只做** plan 素材 compound、**不**盘点 `<iteration-id>/` package
+- 提升时整文件复制到 knowledge（应 compound 结构化重写）
+- 新写仍把 compass 放在 `{ITERATION_DIR}/` 根目录（应用 `<iteration-id>/delivery-compass.md`）

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

@@ -0,0 +1,142 @@
+# Iteration Compass Template
+
+Copy this template when creating `{ITERATION_DIR}/<iteration-id>/delivery-compass.md`.
+
+```markdown
+---
+iteration_id: <id>
+start_date: YYYY-MM-DD
+status: active
+iteration_base_branch: <branch-or-ref>
+target_branch: <branch>
+plans: []
+---
+
+# <iteration-id> Delivery Compass
+
+## Scope
+
+本迭代锁定的 spec 点：
+
+- <spec point 1>
+- <spec point 2>
+
+## Plans
+
+| plan_id | Name | Status | Notes |
+|---------|------|--------|-------|
+| <plan-id-1> | <plan name> | Todo | |
+| <plan-id-2> | <plan name> | Todo | |
+
+Status values: `Todo` | `InProgress` | `InReview` | `Done` | `Blocked`
+
+## Milestones
+
+| Milestone | Target date | Status |
+|-----------|-------------|--------|
+| Spec freeze | YYYY-MM-DD | pending |
+| Dev complete | YYYY-MM-DD | pending |
+| QC complete | YYYY-MM-DD | pending |
+| Iteration close | YYYY-MM-DD | pending |
+
+## Acceptance Criteria
+
+- <迭代级验收项 1>
+- <迭代级验收项 2>
+
+## Non-Goals
+
+- <明确排除项 1>
+- <明确排除项 2>
+
+## Roadmap Position
+
+- **Current iteration（<iteration-id>）**：<what this iteration delivers>
+- **Next iteration**：<what comes next>，触发条件：<condition>，owner：<who>
+- **最终目标**：<the long-term Done definition this iteration contributes to>
+
+## Delivery Branch Policy
+
+> Mirror of frontmatter; keep in sync with workflow snapshot `{WORKFLOW_DIR}/<id>/snapshot.json` `branch` anchors.
+
+| Field | Value |
+|-------|-------|
+| `iteration_base_branch` | <branch-or-ref integration branch is cut from> |
+| `spec_integration_branch` | <e.g. iteration/<iteration-id>> |
+| `target_branch` | <PR target after iteration-close> |
+
+## Risk Register
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|-----------|--------|------------|
+| <risk> | Low/Med/High | Low/Med/High | <mitigation> |
+
+## Iteration package
+
+> Sibling paths under `{ITERATION_DIR}/<iteration-id>/` — not in `{SPECS_DIR}/` or `{KNOWLEDGE_DIR}/`. Promoted to knowledge at iteration-close via **`mstar-compound`**.
+
+| Path | Purpose |
+|------|---------|
+| `guides/` | Exploration, process notes |
+| `specs/` | Iteration-scoped spec drafts |
+| `README.md` | Package document index (recommended when non-trivial) |
+
+## Quality Gate Summary
+
+> Filled at iteration-close. Human summary only; per-plan gate details stay in each main plan, and open residual SSOT stays in `{PROJECT_DIR}/<id>/residuals.json`.
+
+| plan_id | QC decision | QA gate | Residuals | Durable summary |
+|---------|-------------|---------|-----------|-----------------|
+| <plan-id-1> | Approve / Approve with residuals / Request Changes / N/A | mandatory / pm-acceptance / report-only / N/A | none / R1,R2 / accepted | `{PLAN_DIR}/<plan>.md#review-gate-summary` |
+
+Notes:
+
+- Raw review bundle: `{SDD_DIR}/review/` (ephemeral; do not rely on it after Done).
+- Open residual SSOT: `{PROJECT_DIR}/<id>/residuals.json` `entries[<plan-id>]` (default `{HARNESS_DIR}/projects/<id>/`).
+
+## Compound Round Summary
+
+> Filled at iteration-close.
+
+- 结晶文档数：<N>
+- 新增 CONCEPTS.md 条目：<N>
+- 触发 compound-refresh：<是/否>
+
+## Iteration Retrospective (minimal)
+
+> Filled at iteration-close.
+
+- 做得好的：
+- 可改进的：
+- 下迭代建议：
+```
+
+## Fields guide
+
+| Field | Required | When to fill |
+|-------|----------|-------------|
+| `iteration_id` | Yes | Phase 1 |
+| `start_date` | Yes | Phase 1 |
+| `end_date` | No | Phase 3 §3.4 only |
+| `status` | Yes | Phase 1 → `active` / `locked`（§1.6 PM lock）；Phase 3 §3.4 → **`completed`**（YAML frontmatter，非 prose completion status） |
+| `iteration_base_branch` | Yes | Phase 1; integration branch must be created from this ref |
+| `target_branch` | Yes | Phase 1; final PR target after Phase 3 |
+| `plans` (frontmatter) | Recommended | Phase 1 (initial), Phase 2 (add new) |
+| `## Plans` table | Yes | Phase 2 (sync status), Phase 3 (final) |
+| `## Milestones` | Recommended | Phase 1, Phase 2 (update) |
+| `## Acceptance Criteria` | Yes | Phase 1 |
+| `## 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 package (`guides/` / `specs/`) | Optional | Phase 1 §1.5.5; root index one row → `{ITERATION_DIR}/README.md` |
+| `## Quality Gate Summary` | Yes | Phase 3 §3.4 |
+| `## Compound Round Summary` | Yes | Phase 3 §3.4 |
+| `## Iteration Retrospective` | Recommended | Phase 3 §3.4 |
+
+## Legacy compass drift
+
+若仓库中已有 compass **无** YAML frontmatter、**无** `## Roadmap Position`，或只有 prose completion status：
+
+- **新迭代**：Phase 1 必须按本模板写入 **`{ITERATION_DIR}/<iteration-id>/delivery-compass.md`**，不延续 prose-only 或根目录 flat 文件惯例。
+- **收口时**：`mstar-iteration` §3.0.5 在 Phase 3 入口规范化，再执行 §3.3–§3.4。
+- **Legacy path**：若仍存在 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md`，读时兼容；本轮若改写该迭代，迁入 `<iteration-id>/delivery-compass.md`。

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

@@ -0,0 +1,45 @@
+# Iteration corpus hygiene（writing-specialist · §1.6）
+
+> **When**: Phase 1 §1.6 — **writing-specialist** only, after product/architect landed compass / plans / `{SPECS_DIR}/` / **`{ITERATION_DIR}/<iteration-id>/`** package.
+> **Boundaries**: **`iteration-artifact-boundaries.md`** — no `{KNOWLEDGE_DIR}/` adds @ start; iteration drafts → **`<iteration-id>/guides/`** or **`specs/`**.
+
+## Scope
+
+| | Path | Notes |
+|--|------|-------|
+| **Primary** | `{SPECS_DIR}/**` | Full-tree hygiene (lock vs draft, naming, index) |
+| **Included** | `{ITERATION_DIR}/<iteration-id>/**` | Package guides/specs + compass cross-links |
+| **Existing only** | `{KNOWLEDGE_DIR}/**` | Archive / misplaced correction — **no** new knowledge docs |
+| **Out of scope** | New `{KNOWLEDGE_DIR}/` writes | → **`mstar-compound`** @ iteration-close |
+
+## Placement corrections
+
+| Found in | Misplaced as | Move to |
+|----------|--------------|---------|
+| `{SPECS_DIR}/` | Iteration-only draft → `{ITERATION_DIR}/<iteration-id>/specs/` or `guides/` |
+| `{SPECS_DIR}/` | Implementation pitfall prose → package `guides/` or leave for compound |
+| `{KNOWLEDGE_DIR}/` | New exploration from start chain → `<iteration-id>/guides/` or archive |
+| Flat `{ITERATION_DIR}/*-working-guide.md`（legacy） | → `<iteration-id>/guides/` |
+| Flat `{ITERATION_DIR}/*-delivery-compass.md`（legacy） | Prefer migrate to `<iteration-id>/delivery-compass.md` when touching that iteration |
+
+## Index updates（after edits）
+
+1. `{SPECS_DIR}/README.md`（若存在）— 规格索引
+2. `{KNOWLEDGE_DIR}/README.md` — Status / archive only（无新增行来自 start 链）
+3. `{ITERATION_DIR}/README.md` — **一行 = 一次迭代**（目录链接，非 compass+workspace 双行）
+4. `{ITERATION_DIR}/<iteration-id>/README.md` — Documents 单表列出 guides/specs（非 trivial 时创建）
+
+## Done signals
+
+- Specs tree hygiene complete（draft vs locked clear）
+- Package used for iteration-level drafts (`<iteration-id>/guides|specs/`)
+- Misplaced knowledge / specs moved or archived with index Status updated
+- No new `{KNOWLEDGE_DIR}/` documents from this chain
+
+## Close vs start
+
+| Tree | Start (§1.6) | Close (§3.2 compound） |
+|------|--------------|------------------------|
+| `{SPECS_DIR}/` | Hygiene + lock clarity | Usually unchanged |
+| `{ITERATION_DIR}/<id>/` | Create/edit drafts | **Inventory → promote** to `{KNOWLEDGE_DIR}/` |
+| `{KNOWLEDGE_DIR}/` | Hygiene / archive only | **Primary write path** |

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

@@ -0,0 +1,27 @@
+# Iteration package README (template)
+
+Optional index inside `{ITERATION_DIR}/<iteration-id>/`. Copy when the package has more than a few files beyond `delivery-compass.md`.
+
+```markdown
+# <iteration-id>
+
+Iteration package — `delivery-compass.md` + specs/guides. Not `{KNOWLEDGE_DIR}/`. Worthy content is **promoted** at iteration-close via `mstar-compound`.
+
+## Documents
+
+| Document | Kind | Description | Status |
+|----------|------|-------------|--------|
+| [delivery-compass.md](delivery-compass.md) | compass | Scope, plans, branch policy | active / locked / completed |
+| [guides/<name>.md](guides/<name>.md) | guide | <purpose> | draft / active / promoted |
+| [specs/<name>.md](specs/<name>.md) | spec | <purpose> | draft / locked-in-{SPECS_DIR} / promoted |
+
+## Promotion log (filled at iteration-close)
+
+| Source | Promoted to | Date | Notes |
+|--------|-------------|------|-------|
+| | | | |
+```
+
+**Kind**: `compass` | `guide` | `spec` | `other`
+
+**Status values**: `draft` | `active` | `locked` | `completed` | `promoted` (link knowledge path) | `superseded` | `snapshot-only`

package/harness-skills/mstar-iteration/references/phase-2-worktree-lease.md

@@ -0,0 +1,205 @@
+# Phase 2 control worktree + execution lease
+
+Normative field names → field SSOT
+`mstar-artifacts/references/status-and-residuals.md`; the **full lease
+protocol prose** (single canonical copy) → `mstar-engine-legacy/references/lease-protocol.md`
+(engine-absent fallback). This reference is the **iteration-command execution
+checklist** — do not invent alternate lease field names; do not re-state the
+full protocol here.
+
+## When it applies
+
+**Phase 2+ command-layer only**（`iteration-start` ends before this; `iteration-drive`
+/ `iteration-loop` are Phase 2+ command layer）. Defaults are **hard** unless the current turn
+explicitly waives via Assignment `Worktree mode: waived` (or equivalent user
+instruction). `Plan parallelism: serial` is **not** a waiver — it only forces
+serial cross-plan **implement** scheduling while control worktree + leases remain
+required.
+
+Phase 1 Review & Edit may stay on the primary checkout. The control-worktree gate
+starts at **Phase 2 entry**.
+
+**Phase scope**：本参考仅约束 **Phase 2**（含 serial integration merge 与「control 禁止产品编辑 / 每 plan feature worktree」）。**Phase 5** PR merge-ready 修复 **不**沿用该产品编辑隔离——直接在 control / `spec_integration_branch` 上改，**禁止**另开 Phase 5 fix worktree → **`phase-4-5-pr-delivery.md`** §5.0。
+
+## Control worktree (Phase 2 entry)
+
+1. Resolve all active plans' `metadata.spec_integration_branch` to the **same**
+   integration branch (STOP if mismatch).
+2. Resolve or create the **control worktree** (usually primary checkout or
+   PM-designated path) checked out to that `spec_integration_branch`.
+3. Verify `git branch --show-current` equals `spec_integration_branch`; working
+   tree clean before merge operations.
+4. Record canonical absolute repository-root path in the workflow
+   snapshot top-level `control_worktree_path` (not `{HARNESS_DIR}`; canonicalize symlinks).
+5. Resolve coordination paths from that root (default-gitignored process artifacts live on the **control filesystem**, not as Git blobs):
+   - status register: `<control_worktree_path>/{HARNESS_DIR}/status.json` (v2 root — active workflow entries)
+   - snapshot SSOT: `<control_worktree_path>/{WORKFLOW_DIR}/<id>/snapshot.json` (plan rows + leases + branch anchors)
+   - project register: `<control_worktree_path>/{PROJECT_DIR}/<id>/residuals.json`
+   - plans SSOT: `<control_worktree_path>/{PLAN_DIR}/` (or `<control>/{HARNESS_DIR}/plans/`)
+   - iterations SSOT: `<control_worktree_path>/{ITERATION_DIR}/`
+   - SDD tree: `<control_worktree_path>/{HARNESS_DIR}/sdd/<plan-id>/`
+
+All sessions MUST reread the **control copy** of the workflow snapshot immediately before
+claim, release, transfer, plan-status transition, or merge-lease mutation.
+
+**Do not** set `Worktree mode: waived` because a feature worktree lacks
+`plans/` under default gitignore — keep feature worktrees and pass absolute
+control **`Plan Path`** / **`SDD dir`** in Assignments
+(`mstar-branch-worktree` 「Harness path SSOT under default gitignore」).
+
+### Same-host exclusive write lock
+
+All control-path lease mutations (claim, release, transfer, merge-lease
+claim/release) **MUST** run inside a same-host exclusive write lock for the full
+read-check-replace-verify sequence. Engine writers acquire the lock
+automatically (`writeWorkflowSnapshot` / `registerWorkflow` use
+`<status-file dir>/.status-write.lockdir/` — for snapshots the lockdir lands
+inside `workflows/<id>/`); for manual edits prefer the engine-check commands
+(`mstar lease verify --workflow <id>`, `mstar worktree check`) over hand-rolled
+`flock`. The atomic-mkdir alternative (`.status-write.lockdir/` in the same
+directory as the file) remains the documented fallback. Do **not** invent a
+distributed CAS CLI.
+
+**Cross-plan parallel hard gate:** Applies **whether or not** `Worktree mode: waived`.
+Lease-gated **cross-plan parallel** writable implement is allowed **only when**
+this same-host lock is **available on the coordination snapshot path and
+used for every coordination mutation** in that Phase 2 session (control path
+when lease gate active; primary checkout `{HARNESS_DIR}/status.json` + snapshot
+when waived). Agents on **different hosts** or with **no shared flock/lockdir** →
+default **`Plan parallelism: serial`** (preferred when waived). **No flock
+does not waive** control worktree / feature worktree / leases — serial
+scheduling only. Assignment still
+claiming cross-plan parallel without lock availability → **Blocked** until PM
+sets serial scheduling or the user gives current-turn override
+`Cross-host lease race: accepted` (or equivalent) + audit on snapshot plan
+`notes` / `notes.jsonl`.
+**`Worktree mode: waived` alone is not** this override.
+
+Immediately before **any** writable implement dispatch, re-read the control
+snapshot and re-verify `execution_lease` holder + paths match this session;
+mismatch → **STOP**.
+
+> **Lease Engine-check:** canonical callout lives in `mstar-artifacts` `SKILL.md`（Engine-check lease 行）— this file carries the execution checklist only.
+
+## Feature worktree (per plan)
+
+- Each concurrently active plan uses a **distinct** absolute feature-worktree
+  path and dedicated feature branch from `spec_integration_branch`.
+- `execution_lease.worktree_path` MUST differ from
+  `control_worktree_path` (never reuse the control checkout for product
+  edits).
+- `Worktree path` MUST appear in the writable Assignment and in the snapshot
+  plan row's `execution_lease.worktree_path` before first writable implement dispatch.
+- Product/source edits run from the feature worktree; plans, iterations,
+  status, and SDD coordination reads/writes run through **absolute control
+  paths** (never relative `.mstar/...` from the feature cwd when L1 is active).
+- Assignment MUST include absolute feature **`Worktree path`** and absolute
+  control **`Plan Path`** / **`SDD dir`** before writable implement dispatch.
+- Default **L1**: one writable track per plan. Within-plan multi-writable tracks
+  still follow L2 `parallel-writable-pre-dispatch` (`mstar-branch-worktree`).
+
+## Execution lease (`plans[].execution_lease` in the workflow snapshot)
+
+Required shape (v1): `holder`, `claimed_at` (RFC 3339 UTC with `Z`),
+`worktree_path`, `working_branch`; optional `session_label` (display only).
+Lives on the snapshot plan row — `{WORKFLOW_DIR}/<id>/snapshot.json` → `plans[]`.
+
+### Claim (before `InProgress` or writable dispatch)
+
+1. Read the control snapshot; locate exactly one plan row (`id` read compatibility).
+2. If `execution_lease` exists:
+   - **Same `holder` as this session** → **resume**: verify `worktree_path` and
+     `working_branch` match the Assignment; continue (not steal/block).
+   - **Different `holder`** → **Blocked** (no timestamp makes it stealable).
+3. Create or verify dedicated feature worktree + branch (default `<repoRoot>/.worktrees/<plan-id>-<slug>`).
+4. Re-read the snapshot under write lock; if row/status/lease changed, restart claim.
+5. One complete-file update (still under lock): `status: "InProgress"` + full `execution_lease`.
+   Use temp file + atomic replace; never expose partial JSON.
+6. Re-read and verify `holder`, `worktree_path`, `working_branch` match before
+   any writable dispatch.
+
+### Hold, release, override
+
+- Lease stays active across `InProgress` and `InReview` (including post-QC/QA
+  ready-to-merge) unless released or transferred.
+- Normal release: re-read the control snapshot under write lock; confirm stored `holder` matches
+  this session — mismatch → **Blocked**; then **delete** `execution_lease`
+  (never `null` or tombstone).
+- `Done` authority deletes `execution_lease` in the same update as `status: "Done"`
+  — **only after** successful integration merge (when lease gate not waived).
+- Override of another holder requires **explicit user instruction this turn** +
+  audit note on snapshot plan `notes` / `notes.jsonl` (prior holder, new holder/release, user authorized).
+- V1: **manual release only** — no `expires_at`, TTL, or heartbeat authority.
+
+### Orphan `InProgress` without lease
+
+If a plan row is `InProgress` but has **no** `execution_lease` in the snapshot, STOP and
+escalate — do not invent a lease or writable-dispatch. Unattended "Recover with
+claim" is permitted **only** for the **same** stable `holder`; different holder
+requires verified quiescence + handoff or current-turn user override + audit.
+Recovery semantics → `mstar-artifacts` (not iteration skill).
+
+## Multi-plan parallelism
+
+**Cross-plan parallel safety gate** applies **whether or not** `Worktree mode:
+waived` is in effect — waiver does **not** authorize lockless cross-host parallel.
+
+- **Feature implementation** MAY proceed in parallel across **different plan IDs**
+  only when **one** of:
+  1. Same-host exclusive write lock is available on the coordination
+     snapshot path (control path when lease gate active; primary checkout
+     `{HARNESS_DIR}/status.json` + snapshot when waived) and used for every coordination
+     mutation in that session; **and** when lease gate is not waived, each plan
+     holds a verified, distinct `execution_lease` and feature worktree.
+  2. **`Plan parallelism: serial`** (default when waived; preferred default under
+     waiver).
+  3. Current-turn `Cross-host lease race: accepted` (or equivalent) + audit
+     snapshot plan `notes` / `notes.jsonl`.
+  Cross-host / no shared lock without (2) or (3) → **Blocked** if Assignment still
+  claims cross-plan parallel writable implement.
+- **Integration merge** into `spec_integration_branch` is **serial** (one at a time),
+  with or without lease gate.
+
+## Integration merge lease (snapshot top-level `integration_merge_lease`)
+
+Required shape (v1): `holder`, `claimed_at`, `plan_id`, `source_branch`,
+`target_branch` (= resolved `spec_integration_branch`); optional `session_label`.
+Lives top-level on the snapshot — `{WORKFLOW_DIR}/<id>/snapshot.json`.
+
+1. From control worktree: clean tree; branch = `spec_integration_branch`.
+2. Under write lock, re-read the snapshot. If `integration_merge_lease` exists:
+   - **Same `holder` as this session** → **resume**: verify `plan_id`,
+     `source_branch`, `target_branch` match intended merge; confirm control
+     worktree state; continue (not steal/block).
+   - **Different `holder`** → **Blocked** (cannot expire or steal).
+3. If unclaimed, claim merge lease (same read-check-replace-verify as execution claim).
+4. Only merge-lease holder runs integration from `control_worktree_path`.
+5. On success: record merge commit/evidence; delete merge lease; set plan
+   **`Done`** and delete `execution_lease` in the same locked update.
+6. On conflict/failure: retain leases; plan stays **`InReview`** — do not set
+   `Done`. Release merge lease only after control worktree is clean and known state.
+
+Execution and merge leases may coexist; merge lease does not grant execution
+ownership for the source plan.
+
+## Waiver
+
+Explicit `Worktree mode: waived` (or equivalent user instruction) this turn
+waives **only**:
+
+- Control worktree establishment and control-path SSOT routing
+- Per-plan feature worktree defaults
+- Snapshot lease claim/hold/release defaults (`plans[].execution_lease` and top-level `integration_merge_lease`)
+
+It does **not** waive the **cross-plan parallel safety gate**. Under waiver,
+cross-plan **parallel writable** implement still requires same-host exclusive
+write lock on the coordination snapshot path, default **`Plan parallelism:
+serial`**, or current-turn `Cross-host lease race: accepted` + audit
+snapshot plan `notes` / `notes.jsonl`. **Prefer serial scheduling when waived**; parallel under waiver
+only with the race-accepted override (or same-host lock when mutating shared
+state).
+
+`Plan parallelism: serial` does **not** waive control worktree or leases.
+
+Iteration commands MUST NOT infer waiver from missing worktrees or single-session
+starts. Explicit override this turn only.