@mstar-harness/omp 3.6.0-alpha.4

package/harness-skills/mstar-design-md/templates/DESIGN.md.template

@@ -0,0 +1,474 @@
+---
+version: 0.1.0
+name: "[Design System Name]"
+description: "[Design System Name] is a [adjective — e.g., minimal, high-contrast, playful] design system for [project/product name]. This is the Light theme."
+
+colors:
+  # ── Background surfaces ──
+  # Level 1 — primary page/card surface (REQUIRED)
+  background-100: "[#ffffff]"
+
+  # LEVEL2_PLACEHOLDER: secondary surface, active surface — uncomment and fill when upgrading to Level 2
+  # background-200: "[#f5f5f5]"
+  # background-300: "[#e5e5e5]"
+
+  # ── Gray (solid — text and opaque fills) ──
+  # Level 1 — primary and secondary text (REQUIRED)
+  gray-1000: "[#111111]"
+  gray-900: "[#666666]"
+
+  # LEVEL2_PLACEHOLDER: full 10-step gray scale — uncomment and fill values for steps 100–800
+  # gray-100: "[#f2f2f2]"
+  # gray-200: "[#ebebeb]"
+  # gray-300: "[#e6e6e6]"
+  # gray-400: "[#eaeaea]"
+  # gray-500: "[#c9c9c9]"
+  # gray-600: "[#a8a8a8]"
+  # gray-700: "[#8f8f8f]"
+  # gray-800: "[#7d7d7d]"
+
+  # LEVEL2_PLACEHOLDER: gray alpha (translucent) scale — uncomment and fill
+  # gray-alpha-100: "#0000000d"
+  # gray-alpha-200: "#00000015"
+  # gray-alpha-300: "#0000001a"
+  # gray-alpha-400: "#00000014"
+  # gray-alpha-500: "#00000036"
+  # gray-alpha-600: "#0000003d"
+  # gray-alpha-700: "#00000070"
+  # gray-alpha-800: "#00000082"
+  # gray-alpha-900: "#000000b3"
+  # gray-alpha-1000: "#000000e8"
+
+  # ── Accent — Blue (links, focus, primary actions) ──
+  # Level 1 — at minimum blue-700 for interactive elements (REQUIRED)
+  blue-700: "[#0066ff]"
+
+  # LEVEL2_PLACEHOLDER: full blue scale — uncomment and fill
+  # blue-100: "[#f0f7ff]"
+  # blue-200: "[#e9f4ff]"
+  # blue-300: "[#dfefff]"
+  # blue-400: "[#cae7ff]"
+  # blue-500: "[#94ccff]"
+  # blue-600: "[#48aeff]"
+  # blue-700: "[#006bff]"
+  # blue-800: "[#0059ec]"
+  # blue-900: "[#005ff2]"
+  # blue-1000: "[#002359]"
+
+  # ── Accent — Red (errors, destructive actions) ──
+  # Level 1 — at minimum red-700 for errors (REQUIRED)
+  red-700: "[#e60000]"
+
+  # LEVEL2_PLACEHOLDER: full red scale — uncomment and fill
+  # red-100: "[#ffeeef]"
+  # red-200: "[#ffe8ea]"
+  # red-300: "[#ffe3e4]"
+  # red-400: "[#ffd7d6]"
+  # red-500: "[#ffb1b3]"
+  # red-600: "[#ff676d]"
+  # red-700: "[#fc0035]"
+  # red-800: "[#ea001d]"
+  # red-900: "[#d8001b]"
+  # red-1000: "[#47000c]"
+
+  # ── Accent — Amber (warnings) ──
+  # Level 1 — at minimum amber-700 for warnings (REQUIRED)
+  amber-700: "[#ffaa00]"
+
+  # LEVEL2_PLACEHOLDER: full amber scale — uncomment and fill
+  # amber-100: "[#fff6de]"
+  # amber-200: "[#fff4cf]"
+  # amber-300: "[#fff1c1]"
+  # amber-400: "[#ffdc73]"
+  # amber-500: "[#ffc543]"
+  # amber-600: "[#ffa600]"
+  # amber-700: "[#ffae00]"
+  # amber-800: "[#ff9300]"
+  # amber-900: "[#aa4d00]"
+  # amber-1000: "[#561900]"
+
+  # LEVEL2_PLACEHOLDER: additional accent scales — uncomment and fill
+  # green-100: "[#ecfdec]"
+  # green-200: "[#e5fce7]"
+  # green-300: "[#d3fad1]"
+  # green-400: "[#b9f5bc]"
+  # green-500: "[#82eb8d]"
+  # green-600: "[#4ce15e]"
+  # green-700: "[#28a948]"
+  # green-800: "[#279141]"
+  # green-900: "[#107d32]"
+  # green-1000: "[#003a00]"
+
+  # teal-100: "[#defffb]"
+  # teal-200: "[#ddfef6]"
+  # teal-300: "[#ccf9f1]"
+  # teal-400: "[#b1f7ec]"
+  # teal-500: "[#52f0db]"
+  # teal-600: "[#00e3c4]"
+  # teal-700: "[#00ac96]"
+  # teal-800: "[#00927f]"
+  # teal-900: "[#007f70]"
+  # teal-1000: "[#003f34]"
+
+  # purple-100: "[#faf0ff]"
+  # purple-200: "[#f9f0ff]"
+  # purple-300: "[#f6e8ff]"
+  # purple-400: "[#f2d9ff]"
+  # purple-500: "[#dfa7ff]"
+  # purple-600: "[#c979ff]"
+  # purple-700: "[#a000f8]"
+  # purple-800: "[#8500d1]"
+  # purple-900: "[#7d00cc]"
+  # purple-1000: "[#2f004e]"
+
+  # pink-100: "[#ffe8f6]"
+  # pink-200: "[#ffe8f3]"
+  # pink-300: "[#ffdfeb]"
+  # pink-400: "[#ffd3e1]"
+  # pink-500: "[#fdb3cc]"
+  # pink-600: "[#f97ea7]"
+  # pink-700: "[#f22782]"
+  # pink-800: "[#e4106e]"
+  # pink-900: "[#c41562]"
+  # pink-1000: "[#460523]"
+
+  # LEVEL3_PLACEHOLDER: wide-gamut P3 equivalents — uncomment and fill for Display P3 screens
+  # blue-100-p3: "oklch(…)"
+  # blue-200-p3: "oklch(…)"
+  # …
+
+typography:
+  # ── Body text (multi-line, taller line-height) ──
+  # Level 1 — at minimum one body token (REQUIRED)
+  copy-16:
+    fontFamily: "[font-family]"
+    fontSize: 16px
+    fontWeight: 400
+    lineHeight: 1.6
+    letterSpacing: 0
+
+  # LEVEL2_PLACEHOLDER: additional body sizes — uncomment and fill
+  # copy-24:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 24px
+  #   fontWeight: 400
+  #   lineHeight: 36px
+  #   letterSpacing: 0
+  # copy-20:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 20px
+  #   fontWeight: 400
+  #   lineHeight: 36px
+  #   letterSpacing: 0
+  # copy-14:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 14px
+  #   fontWeight: 400
+  #   lineHeight: 20px
+  #   letterSpacing: 0
+
+  # ── Headings ──
+  # Level 1 — at minimum one heading token (REQUIRED)
+  heading-32:
+    fontFamily: "[font-family]"
+    fontSize: 32px
+    fontWeight: 600
+    lineHeight: 1.2
+    letterSpacing: -0.02em
+
+  # LEVEL2_PLACEHOLDER: full heading scale — uncomment and fill
+  # heading-72:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 72px
+  #   fontWeight: 600
+  #   lineHeight: 72px
+  #   letterSpacing: -0.04em
+  # heading-48:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 48px
+  #   fontWeight: 600
+  #   lineHeight: 56px
+  #   letterSpacing: -0.03em
+  # heading-24:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 24px
+  #   fontWeight: 600
+  #   lineHeight: 32px
+  #   letterSpacing: -0.01em
+  # heading-20:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 20px
+  #   fontWeight: 600
+  #   lineHeight: 26px
+  #   letterSpacing: -0.005em
+
+  # LEVEL2_PLACEHOLDER: label typography (single-line, scannable) — uncomment and fill
+  # label-14:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 14px
+  #   fontWeight: 400
+  #   lineHeight: 20px
+  #   letterSpacing: 0
+
+  # LEVEL2_PLACEHOLDER: button typography — uncomment and fill
+  # button-14:
+  #   fontFamily: "[font-family]"
+  #   fontSize: 14px
+  #   fontWeight: 500
+  #   lineHeight: 20px
+  #   letterSpacing: 0
+
+spacing:
+  base: 4px
+  # Level 1 — at minimum 5 scale steps (REQUIRED)
+  1: 4px
+  2: 8px
+  3: 12px
+  4: 16px
+  6: 24px
+
+  # LEVEL2_PLACEHOLDER: full 9-step scale — uncomment and fill
+  # 8: 32px
+  # 10: 40px
+  # 16: 64px
+  # 24: 96px
+
+rounded:
+  # Level 1 — at minimum one radius for everyday controls (REQUIRED)
+  sm: 6px
+
+  # LEVEL2_PLACEHOLDER: additional radius tokens — uncomment and fill
+  # md: 12px
+  # lg: 16px
+  # full: 9999px
+
+# LEVEL2_PLACEHOLDER: component tokens — uncomment full section when upgrading to Level 2
+# components:
+#   button-primary:
+#     backgroundColor: "{colors.gray-1000}"
+#     textColor: "{colors.background-100}"
+#     typography: "{typography.button-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 10px"
+#     height: 40px
+#   button-secondary:
+#     backgroundColor: "{colors.background-100}"
+#     textColor: "{colors.gray-1000}"
+#     typography: "{typography.button-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 10px"
+#     height: 40px
+#   button-tertiary:
+#     textColor: "{colors.gray-1000}"
+#     typography: "{typography.button-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 10px"
+#     height: 40px
+#   button-error:
+#     backgroundColor: "{colors.red-800}"
+#     textColor: "#ffffff"
+#     typography: "{typography.button-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 10px"
+#     height: 40px
+#   button-small:
+#     typography: "{typography.button-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 6px"
+#     height: 32px
+#   button-large:
+#     typography: "{typography.button-16}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 14px"
+#     height: 48px
+#   input:
+#     backgroundColor: "{colors.background-100}"
+#     textColor: "{colors.gray-1000}"
+#     typography: "{typography.label-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 12px"
+#     height: 40px
+#   input-small:
+#     typography: "{typography.label-14}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 12px"
+#     height: 32px
+#   input-large:
+#     typography: "{typography.label-16}"
+#     rounded: "{rounded.sm}"
+#     padding: "0 12px"
+#     height: 48px
+---
+
+<!-- COMPLETENESS_LEVEL: 1 — last audited [DATE] -->
+
+# [Design System Name]
+
+## Overview
+
+[Design System Name] is a [adjective, e.g., minimal, playful, bold] design system for [project/product name].
+[Aesthetic principles — one sentence describing the visual identity: e.g., "Prioritize readability and clarity with plenty of whitespace and restrained color."]
+
+All concrete token values live in the YAML frontmatter above (colors, typography, spacing, rounded, components). The sections below explain usage rules, design intent, and agent guidance.
+
+This is the Light theme.
+<!-- LEVEL2_PLACEHOLDER: When ready for dark theme, create DESIGN.dark.md with same token names and different values. See references/completeness-checklist.md § Level 3. -->
+<!-- Uncomment when dark theme exists: The Dark theme uses the same token names with different values and lives at /DESIGN.dark.md. -->
+
+## Colors
+
+Token values are defined in the frontmatter `colors:` map. Each non-background scale runs 10 steps (`100`–`1000`), and the step encodes intent, not just lightness:
+
+- `100` default background
+- `200` hover background
+- `300` active background
+- `400` default border
+- `500` hover border
+- `600` active border
+- `700` solid fill, high contrast
+- `800` solid fill, hover
+- `900` secondary text and icons
+- `1000` primary text and icons
+
+`background-100` is the primary page and card surface. The `gray-alpha-*` tokens are translucent, so they layer over any background; use them for borders, dividers, overlays, and hover states. Solid `gray-*` holds its contrast on any surface, so use it for text and opaque fills. Accent scales carry meaning: `blue` for links and focus; `red` for errors; `amber` for warnings; plus `green`, `teal`, `purple`, and `pink`.
+
+<!-- LEVEL2_PLACEHOLDER: Complete the full 10-step gray scale and add all accent scales to the frontmatter. See references/completeness-checklist.md § Level 2/Colors. -->
+<!-- LEVEL2_PLACEHOLDER: Add gray-alpha scale for translucent borders, overlays, and hover states. See references/design-md-spec.md § Colors. -->
+<!-- LEVEL3_PLACEHOLDER: Add wide-gamut P3 equivalents (`*-p3`) in oklch() to the frontmatter. -->
+
+## Typography
+
+Token values are defined in the frontmatter `typography:` map. Token naming: `{role}-{size}` where role is `heading`, `label`, `copy`, or `button` and size is approximate font size in px.
+
+- **Headings** (`heading-72` through `heading-14`): title pages and sections; `letterSpacing` tightens as the size grows.
+- **Labels** (`label-20` through `label-12`): single-line, scannable text — navigation, form labels, table headers, metadata.
+- **Copy** (`copy-24` through `copy-13`): multi-line body text with a taller `lineHeight`.
+- **Buttons** (`button-16` through `button-12`): medium-weight labels for buttons and compact controls.
+- **Mono tokens** (`-mono` suffix): same metrics with a monospace font for code and data; prefer tabular figures when numbers need to align.
+
+<!-- LEVEL2_PLACEHOLDER: Complete the typography scale in the frontmatter. Add at least 3 heading levels, 1 label token, and 1 button typography token. See references/completeness-checklist.md § Level 2/Typography. -->
+
+## Spacing & Layout
+
+Token values are defined in the frontmatter `spacing:` and `rounded:` maps.
+
+### Spacing scale
+
+Keep a three-step rhythm:
+- [small, e.g., 8px] inside a group (label + input, icon + text)
+- [medium, e.g., 16px] between related groups
+- [large, e.g., 32-40px] between sections
+
+Cards use 24px padding, 16px when compact and 32px for hero areas. Center content in a responsive column with side padding that grows at wider breakpoints.
+
+<!-- LEVEL2_PLACEHOLDER: Complete the full 9-step spacing scale in the frontmatter. See references/completeness-checklist.md § Level 2/Spacing. -->
+
+### Breakpoints
+
+<!-- Level 1 — At least 2 breakpoints for responsive layout. -->
+
+| Name | Min Width | Target |
+|------|-----------|--------|
+| sm | 401px | Mobile landscape |
+| lg | 961px | Desktop |
+
+<!-- LEVEL2_PLACEHOLDER: Add intermediate breakpoints (md, xl, 2xl). See references/completeness-checklist.md § Level 2/Breakpoints. -->
+<!--
+| md | 601px | Tablet |
+| xl | 1200px | Large desktop |
+| 2xl | 1400px | Ultra-wide |
+-->
+
+<!-- LEVEL2_PLACEHOLDER: Add Components section — at minimum Button (primary, secondary, tertiary, error) and Input tokens in the frontmatter `components:` map with size variants and all states. See references/design-md-spec.md § Components. -->
+<!--
+## Components
+
+Component tokens are defined in the frontmatter `components:` map. They reference other frontmatter keys via `{colors.*}` and `{typography.*}` syntax.
+
+### Button
+
+**Variants** are defined in frontmatter as `button-primary`, `button-secondary`, `button-tertiary`, `button-error`.
+
+**Size variants** (`button-small`, `button-large`) inherit variant properties and override only typography, padding, and height.
+
+**States:** Fill steps up: 100→200 (hover), 100→300 (active). Border steps up: 400→500→600. Disabled: 100 fill, 700 text, not-allowed cursor. Focus: `0 0 0 2px {colors.background-100}, 0 0 0 4px {colors.blue-700}`.
+
+### Input
+
+**Variants** are defined in frontmatter as `input`.
+
+**Size variants** (`input-small`, `input-large`) same pattern as Button.
+
+**States:** Same state progression as Button. Error: border `red-700`, add error message below.
+-->
+
+<!-- LEVEL3_PLACEHOLDER: Add Elevation & Depth, Motion, Shapes, Voice & Content, and extended Component library. See references/completeness-checklist.md § Level 3. -->
+<!--
+## Elevation & Depth
+
+Hierarchy comes from tonal surfaces and borders first; shadows stay subtle.
+
+### Shadows (light theme)
+
+| Element | Value |
+|---------|-------|
+| Card | 0 2px 2px rgba(0, 0, 0, 0.04) |
+| Popover | 0 1px 1px rgba(0, 0, 0, 0.02), 0 4px 8px -4px rgba(0, 0, 0, 0.04), 0 16px 24px -8px rgba(0, 0, 0, 0.06) |
+| Modal | 0 1px 1px rgba(0, 0, 0, 0.02), 0 8px 16px -4px rgba(0, 0, 0, 0.04), 0 24px 32px -8px rgba(0, 0, 0, 0.06) |
+
+Pair each elevation with the matching radius from `rounded:` frontmatter.
+
+## Motion
+
+Motion clarifies change, never decorates. Default 0ms is often the best choice.
+
+### Easing
+
+Default: cubic-bezier(0.175, 0.885, 0.32, 1.1)
+
+### Durations
+
+| Context | Duration |
+|---------|----------|
+| State change | 150ms |
+| Popover/Tooltip | 200ms |
+| Modal/Overlay | 300ms |
+
+Honor prefers-reduced-motion: drop nonessential motion.
+
+## Shapes
+
+Border radius values are defined in the frontmatter `rounded:` map. Keep one radius family per view; never mix rounded and sharp corners.
+
+## Components — Extended
+
+Add Card, Modal, Tooltip, Menu/Dropdown, Badge tokens to the frontmatter `components:` map following the same structure as Button/Input.
+
+## Voice & Content
+
+Copy is part of the design; keep it precise and free of filler.
+
+- Use Title Case for labels, buttons, titles, and tabs
+- Sentence case for body, helper text, and toasts
+- Name actions with a verb and a noun: [Create Project], [Delete Item]
+- Write errors as what happened + what to do: [Error description. Suggested fix.]
+- Toasts name the specific thing, no trailing period, no "successfully": [Item deleted]
+- Empty states point to the first action: [No items yet. Create one to get started.]
+- In-progress states: present participle + ellipsis: [Saving…], [Loading…]
+- Use numerals, curly quotes, the ellipsis character
+- Skip "please" and marketing superlatives
+-->
+
+## Do's and Don'ts
+
+<!-- Fill in with rules specific to this design system. Examples to customize: -->
+
+- Use `gray-1000` for primary text, `gray-900` for secondary.
+- Keep accent color for state and the single most important action on a view.
+- Hold WCAG AA contrast (4.5:1 for body text).
+- Show focus ring on every interactive element at `:focus-visible`.
+- Use token values from the frontmatter — never set font size, line height, or color by hand.
+- Don't signal state with color alone; pair it with an icon or text label.
+- Don't use more than two font weights in one view.
+- Don't mix rounded and sharp corners in one view.
+- Don't swap `gray-*` for `background-*`; they are separate scales.

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

@@ -0,0 +1,134 @@
+---
+name: mstar-dispatch-gates
+description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent、`Execute as` 与 `Delegation`、承接方反递归 NEVER 红线、SDD implement 串行派发、**SDD 路径 plan QC 强制 tri-review（N=3）**、inline 单席 QC 例外、Assignment 文案≠派发、未齐不发、**invoke 角色字段必填（漏写=静默 generic 回退=派发未完成）**。`project-manager` 派发时必读；leaf 动手前必读反递归。worktree 见 `mstar-branch-worktree`；SDD 见 `mstar-sdd`；宿主见 `mstar-host`。
+---
+
+## Load order（必读顺序）
+
+**首次 Read 本 skill 前：必须先 Read `mstar-harness-core`（SKILL.md）。** 同仓 worktree、QC/QA 检出字段 → **`mstar-branch-worktree`**。冲突时 **以 `mstar-harness-core` 为准**。
+
+## 🚨 承接方：如果你是 leaf executor，先读本节！（你的 Assignment 开头 IDENTITY 块已告诉你身份）
+
+> **如果你此刻的 Assignment 中 `Delegation: forbidden`（或未写 `Delegation: allowed`），则你属于 leaf executor。本节是你的行为边界，必须在你做任何决定之前读完。**
+>
+> **先回到你 Assignment 最顶部的 `**IDENTITY**` 块重读一遍** —— 那里已经告诉你：你是谁、你不是谁、Task 工具不属于你。本节是那个身份断言的加固版。
+
+**身份断言（牢记，不动摇）：**
+- **你就是** `Execute as` 写的那个角色。你**不是 PM**，不是调度者，不是 parallel-agent dispatch 的使用者。
+- Task/subagent 工具即使在你的工具列表里出现，它**不属于你**。把它当作你没见过的工具 —— 不是"不能用"，是"你没有"。
+- 所有工作由你**本人**在当前会话内完成（Read / Write / Edit / Shell / Grep / Glob）。任何"这样做更高效"的想法都不构成 dispatch 的理由。
+- 遇到超出能力范围的需求 → 写 `## Blocked` 回报 PM，**不是**尝试 dispatch。Blocked 是你能发出的正确信号，dispatch 不是。
+
+## 承接方反递归红线（NEVER / DO NOT；leaf executor 必读）
+
+下列行为易触发递归误派；`project-manager` 之外的角色一旦命中，须立即停止并改为本会话内可交付物，或 **`Blocked`** 回报 PM。**禁止**以「更高效」「Assignment 像 PM 编排」等理由绕开：
+
+- **NEVER** 在本会话内调用 Task / subagent，且其 `subagent_type` **等于**你当前的 **`Execute as`** 角色 id。
+- **NEVER** 把 Assignment 里出现的 **任何** plain `role-id` 提及、反引号 `` `<role-id>` ``、**Handoff**、**QA gate**、**Completion Report** 模板里的角色名、路由表下游角色当成「立刻 invoke」的指令；这些是**叙事 / 路由文档 / 后续 PM 编排意图**，不是命令。
+- **NEVER** 把「分解为多个计划 / 多 phase / 多 track」等**设计产物层面**的并行或拆分读成「应 invoke 与子会话数量对应的多个 subagent」。**纸面产物**由本会话写盘完成；并行**调度**由 PM 在后续轮次决定。
+- **NEVER** 因宿主**暴露**了 `Task` 或若干 `subagent_type` 名称就推断可以调用。**工具可用 ≠ 授权使用**；授权只来自 **`Delegation: allowed (...)`**。
+- **NEVER**（非 PM）主动执行 parallel-agent dispatch 来分派子代理；需要并行时回报 PM。
+- **DO NOT** 在 Assignment 缺少 `Execute as` / `Delegation` / `Who runs this turn` 时自行「补齐」为 PM；缺字段时按 **leaf executor** 解释：亲自完成或 **`Blocked`**。
+- **DO NOT** 用「Assignment 太长 / 像编排稿」当作分派依据；先交付本会话任务再回报，分派由 PM 下一轮决定。
+
+**自检（动手前）**：
+
+1. 我此刻的 **`Execute as`** 是什么？
+2. Assignment 是否写了 **`Delegation: allowed (...)`**？没有 → **禁止**任何 Task / subagent。
+3. 下一动作是不是「Task / subagent_type=…」？是 → 停手，改为 Read / Write / Shell / Edit，或 **`Blocked`**。
+4. 命中任一 NEVER → 写 `## Blocked — recursive dispatch refused (<which NEVER>)` 回报 PM，**不**继续 invoke。
+
+**Assignment 顶部反模式块**：每个 PM Assignment 开头均有 **`**You are a leaf executor. You MUST NOT:**`** 块（含 IDENTITY + CAPABILITY BOUNDARY + prohibitions），PM 按此 Assignment 的角色+上下文定制反模式清单。leaf executor 收到 Assignment 后须 **首先** 阅读该块；命中任一条 → **停止**（亲自完成或 `Blocked`）。详见 **`mstar-roles/references/project-manager/dispatch-and-assignment.md`**。
+
+> **Engine 执行范围（caller-scoped，#156）**：engine `antiRecursionPrecheck` 比较的是**派发方自身角色**（caller）与新 Assignment 的 `Execute as`（target）。只有 **dsh**（Config `dispatchBinding`）能观察派发方身份并在 engine 层硬执行（含 `callerRequired` 空绑定 fail-closed）；omp / OpenCode / Cursor 的角色绑定字段是**派发目标**——目标 == `Execute as` 正是 C5 合规派发模式——这些宿主上红线保持 prompt 级约束（本节），engine 不做判定。
+
+## 调度防串扰（强制；leaf executor 已在上方读过反递归红线，此处为完整规则供 PM/对照用）
+
+- 只有 **`project-manager`** 可以决定增加/并行 subagent；承接方**默认不得二次分派**。
+- **`Execute as: <role-id>`** = 承接方**亲自**完成本单，**不是**再起同名 subagent 或嵌套同 `subagent_type` 的 Task（禁止**递归误派**）。
+- 额外代理仅以 **`Delegation: allowed (...)`** 为准；未显式写时视为 **`Delegation: forbidden`**。
+- Assignment 正文中的 role 引用：默认 **plain id**（`product-manager`）；OpenCode 见 **`mstar-host/references/opencode.md`** § Role-mention hygiene。
+- 承接方若判断必须增加 subagent，应先回报 **`Blocked`** 请 PM 重分派。
+- Per-task informal review, when PM explicitly allows it, must not use `qc-specialist*`; use `code-reviewer` (generic fallback only when the role agent is absent on the host) or PM-marked informal `qa-engineer`. Formal QC remains `mstar-review-qc`.
+
+## 并发分派完整性门禁（PM 强制 · Evidence）
+
+当 PM 声明「并发分派」时，须同时满足**文案并发**与**工具并发**：
+
+- **工具并发**：同一调度轮次内，多个 subagent 调用须在**同一条 assistant 消息**里一次性发出（宿主允许时）。
+- **QC tri-review（SDD 强制）**：`Execution mode: sdd` 且全部 task 完成后 → `qc-specialist` / `qc-specialist-2` / `qc-specialist-3` 同条消息 **N=3**（写 `{SDD_DIR}/review/qc1.md`…`qc3.md`；PM 汇总 `qc-consolidated.md` + durable plan summary）。Assignment 须含 branch **review-package** 路径与 report paths。适用于**单 plan 与 iteration**。
+- **QC 单席（例外）**：`Execution mode: inline`（hotfix 等），或 Assignment 显式 `QC mode: single` / `QC mode: single — override: <reason>` → `qc-specialist` ×1，`N=1`，写 `{SDD_DIR}/review/qc.md`。
+- **QC targeted re-review**：Assignment 含 **`QC re-review: targeted — reviewers: …`** 时，**N** = 所列席位数（1–3），同条消息发满 **N**。
+- **先自检再发送**：发送前核对「Assignment 条数 = 本条消息中的实际 **派发** 调用条数」。
+- **先自检字段再发送（与 count 同级门禁）**：核对**每条** invoke 都携带与 **`Execute as`** 匹配的角色绑定字段——omp **`agent`** / Cursor **`subagent_type`** / OpenCode **`subagent`** / Kimi·ZCode **`subagent_type`**；宿主列以 **`mstar-host`** §Detect active host 的 tool-shape 检测为准（禁以 config 路径/仓库内容判定）。**漏写或取默认通用值**（omp 漏 `agent` ⇒ 自动回退 generic `task`，无报错）= **派发未完成**，与 paste-only（零 invoke）**同等级**：当场补齐重发，不得进入下一 gate。**N=1 顺序链（Review & Edit）不豁免**——count 门在 N=1 恒过，**字段门是唯一保护**。
+- **前置步骤与派发回合分离（防串行 rollout）**：为派发准备的 **`bash` / `read` / `glob` / `grep`**（如 `merge-base`、`Review range`、`git rev-parse`）**不计入** `N` 次派发；可在上一条仅含准备的消息完成。准备完成后，**下一条派发消息**须**一次性**含 **`N` 次** Task / subagent invoke。**禁止**先发 `1` 次、等返回再补发其余 `N-1` 次。
+- **未齐不发（emit zero until batch-ready）**：需并发 `N≥2` 而当前只能发 `1` 条时，本条应发 **`0` 条派发 invoke`**（可继续 read/bash 补齐），**禁止**「先发一个顶一下」；`N` 份 payload 就绪后**单次消息发满 `N`**。见 **`mstar-host`** → `references/parallel-dispatch.md`（具备 invoke / Task / subagent 工具的宿主共用）。
+
+### 具名 subagent 宿主：文案分派 ≠ 调度完成
+
+在支持具名角色 / Task 的宿主上，`## Assignment` **正文不会**拉起子会话。PM 须在**同一条 assistant 消息**（或宿主等价机制）发出与 Assignment **条数一致**的 invoke / Task；仅打印 Markdown = **分派未完成**。**几条 Assignment ⇒ 几次 tool 调用**（默认同消息并行）。
+
+> **Engine check (when available):** run `mstar dispatch validate <assignment-file> [--branch <branch>]` (or `import { validateAssignmentFields, assertDefaultBranchProtected } from "@mstar-harness/engine"` in a host hook) to validate the Assignment field contract and the default-branch gate (normative default-branch prose: **`mstar-branch-worktree`** SKILL.md § "Git 功能分支门禁（业务仓库）" — this skill covers dispatch mechanics only). On `fail` -> do not proceed; fix and re-run. Skill text below remains authoritative when the runtime is absent.
+
+## SDD implement 波次（PM only）
+
+When **`Execution mode: sdd`** (`mstar-sdd`):
+
+- **串行**：one implementer at a time; one **fresh** task reviewer after each — **never** parallel implementers (write conflicts).
+- **`SDD implementer session: sticky`**：same implementer subagent may **resume** across tasks when host supports it; **reviewers never resume** — see **`mstar-sdd/references/sticky-implementer-session.md`**.
+- File handoffs only — no pasted plan/diff/history in dispatch prompts.
+- Record per-task BASE SHA; use `review-package` for diffs — **never `HEAD~1`**.
+- After all tasks: branch `review-package` in `{SDD_DIR}/review/` → **mandatory tri-review N=3** when `Execution mode: sdd`; **N=1** only for `inline` / explicit single override.
+
+> **QC seats Engine-check 唯一规范体：** `mstar-review-qc` `SKILL.md`（Engine-check seats 行）。
+
+## 并行规则（摘要）
+
+**两条独立门禁（均须满足，不可互相替代）**：
+
+| 门禁 | SSOT | 常见误满足 |
+|------|------|------------|
+| **工具并发** | 同条消息发满 N 次 invoke | 已发 2 个 Task ⇒ 误以为「并行合规」 |
+| **同仓写隔离** | 派发 **前** 每轨独立 `Worktree path` | 只写了 `Working branch` / `checkout -b` |
+
+- 独立模块可并行 **implement 轨道**（不同 dev Assignment）；**同仓 ≥2 可写并发** → **`mstar-branch-worktree`** **`references/parallel-writable-pre-dispatch.md`**（先于 invoke；同 plan 多轨 = L2）。
+- **SDD 单 plan 内**：task / implementer **仍串行**（`mstar-sdd`）；**禁止**同一 plan 内并行 SDD implementer（写冲突）。
+- **跨 plan（迭代 Phase 2）≠ 单 plan 内并行**：不同 `plan_id` 的 feature implement **允许** lease 门控并行（每 plan 独立 verified snapshot `plans[].execution_lease` + feature worktree，L1）**仅当** coordination 路径 same-host 独占写锁可用且每次协调变更持锁 → **`mstar-iteration`** §2.0 #5 · **`mstar-artifacts`**。**跨主机 / 无共享 flock** → 默认 **`Plan parallelism: serial`** 或 Assignment 仍写并行 → **Blocked**（用户本轮 `Cross-host lease race: accepted` + audit `notes` 除外）。**无 flock 不豁免** control/feature worktree 或 lease。**`Worktree mode: waived` 不豁免**跨 plan 并行安全闸。**禁止**因默认 gitignore 导致 feature 缺 plans 而 waive worktree（harness 经 control 绝对路径）→ **`mstar-branch-worktree`**。**禁止**无 lease 的跨 plan 可写派发（lease 闸未 waive 时）。
+- **`integration_merge_lease`**：`spec_integration_branch` 上的 merge **始终串行**（一次仅一 holder）→ **`mstar-iteration`** · **`mstar-artifacts`**。
+- **`Plan parallelism: serial`**：仅强制跨 plan implement **调度串行**；**不** waive control worktree / `execution_lease` / `integration_merge_lease`（`Worktree mode: waived` 才是 lease/worktree 豁免）→ **`mstar-iteration`** §2.0 #5。
+- **Plan QC tri** after SDD task loop（`Execution mode: sdd`）；**单席**仅 `inline` / hotfix。共用 `Review cwd` / `Working branch` / `plan_id` / `Review range`（**`mstar-branch-worktree`**）。
+- **Tri 同消息规则**：plan QC tri（SDD 或 Assignment 显式 `QC mode: full tri-review`）时三席 **同一条消息**、**同一套** scope 字段。
+
+> **Engine check (when available):** run `mstar worktree check <plan-id> --workflow <id>` (L1) / `mstar worktree check --l2 --tracks <json>` (L2) (or `import { l1PreDispatchCheck, l2PreDispatchCheck } from "@mstar-harness/engine"` in a host hook) to verify the 同仓写隔离 gate above (per-track feature worktree, branch alignment) before parallel dispatch. On `fail` -> do not proceed; fix and re-run. Skill text below remains authoritative when the runtime is absent.
+
+## Specialist review-and-edit dispatch
+
+当 PM 派发**文档编辑类**专业角色（如 product-manager、architect、writing-specialist）直接修订 harness 产物时：
+
+- PM 写初稿；各角色通过宿主 invoke **直接编辑**目标文件（**不**另写仅评论式 `reports/` 替代修订）。
+- **1 Assignment ⇒ 1 invoke**。
+- **Phase 1 Review & Edit chain**（`mstar-iteration` §1.6）：主产出 **`{SPECS_DIR}/`** + **`{ITERATION_DIR}/<iteration-id>/`** package；**禁止** start 链向 `{KNOWLEDGE_DIR}/` 新增。close 时 **`mstar-compound`** 提升 package → 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 分支。
+
+## 反模式（派发）
+
+完整反模式索引见 **`mstar-harness-core`**；lease / worktree / Phase 相关反模式见 **`mstar-branch-worktree`** 与 **`mstar-iteration`**。本节仅列派发机制专属：
+
+- QC 三审拆在多条消息（tri 模式）或单席却未附 review-package 路径。
+- 仅 1 次 invoke 却声称「tri-review 已并行启动」（tri 模式 N=3）。
+- SDD 并行 implementer dispatch（**同一 plan 内**多 task）— **不同于**跨 plan lease 门控并行（后者见上节 L1 / **`mstar-branch-worktree`**）。
+- 递归同角色 subagent；把 Handoff / 多轨编排措辞当 invoke。
+- Review-and-edit 链未完成即 commit integration 分支；PM 代做专业角色编辑而不 invoke。
+- Phase 1 review-and-edit 链三角色并行派发，或未等上一角色返回即派发下一角色。
+- Assignment 已写、invoke 为零（paste-only）却进入下一 gate。
+- Task/subagent item 漏写角色绑定字段（omp 漏 `agent` / Cursor 漏 `subagent_type` / OpenCode 漏 `subagent`）⇒ **静默回退 generic worker**，却因 count=N 通过而误判「派发完成」；属 paste-only 同级的 **dispatch-incomplete**。N=1 顺序 Review-&-Edit 链最易在此漏字段。
+
+## Workflow
+
+派发检查顺序：承接方先读 Assignment 顶部 **IDENTITY / 反模式块**确认 leaf 身份（反递归红线）→ PM 核对字段契约（`Execute as` / `Delegation` / 角色绑定字段；**先自检字段再发送**）→ 同一条消息**一次性发满 N 次** invoke（工具并发；N 按 `Execution mode` 映射）→ 派发前完成同仓写隔离（L1/L2 worktree）→ SDD 波次**串行** implement + fresh reviewer → task 全完成后 `{SDD_DIR}/review/` review-package → **强制 tri-review N=3**（或 inline 单席 N=1）。准备用 read/bash 不计入 N，且与派发回合分离（**未齐不发**）。
+
+## References
+
+- `references/leaf-executor-checklist.md` — 承接方一页自检清单。

package/harness-skills/mstar-dispatch-gates/references/leaf-executor-checklist.md

@@ -0,0 +1,23 @@
+# Leaf executor dispatch checklist
+
+> Load **`mstar-harness-core`** first, then **`mstar-dispatch-gates`** SKILL.md.
+>
+> **First**: read the `**IDENTITY**` and `**CAPABILITY BOUNDARY**` blocks at the top of your Assignment. Those tell you who you ARE and what tools are NOT yours. Then read the `**You are a leaf executor. You MUST NOT:**` prohibitions. Those anti-patterns are customized for your specific role+context and are the authoritative dispatch boundaries for this assignment.
+
+**Preamble — internalize before any action:**
+
+I am a leaf executor. I personally complete all work. Task/subagent is NOT my tool. If I think about dispatching, I stop and return to my direct work or write `Blocked`.
+
+Before any Task/subagent call (if I somehow forget the preamble):
+
+1. What is my **`Execute as`**?
+2. Does the Assignment include **`Delegation: allowed (...)`**? If no → **no** Task/subagent.
+3. Is my next step a Task/subagent invoke? If yes without (2) → **stop**; use Read/Write/Shell/Edit in-session or **`Blocked`**.
+4. Is `subagent_type` equal to my `Execute as`? If yes → **forbidden** (recursive dispatch).
+5. Am I treating plain `role-id` mentions, Handoff, QA gate, Completion Report roles, or multi-plan/multi-track **design text** as invoke commands? If yes → **stop**; deliver in-session.
+6. Am I invoking because the tool exists? **Available ≠ authorized.**
+7. Need parallel work or PM-only dispatch? → **`Blocked`**; PM dispatches on the next round.
+
+If blocked, report: `## Blocked — recursive dispatch refused (<which NEVER or reason>)`
+
+Full NEVER/DO NOT list → **`mstar-dispatch-gates` SKILL.md**「承接方反递归红线」.