@mstar-harness/opencode 0.6.21 → 0.6.22

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

@@ -7,14 +7,17 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 subagent
 
 **首次 Read 本 skill 前：必须先 Read `mstar-harness-core`（SKILL.md）。** 同仓 worktree、QC/QA 检出字段 → **`mstar-branch-worktree`**。冲突时 **以 `mstar-harness-core` 为准**。
 
-## 调度防串扰（强制）
+## 🚨 承接方：如果你是 leaf executor，先读本节！（你的 Assignment 开头 IDENTITY 块已告诉你身份）
 
-- 只有 **`@project-manager`** 可以决定增加/并行 subagent；承接方**默认不得二次分派**。
-- **`Execute as: <role-id>`** = 承接方**亲自**完成本单，**不是**再起同名 subagent 或嵌套同 `subagent_type` 的 Task（禁止**递归误派**）。
-- 额外代理仅以 **`Delegation: allowed (...)`** 为准；未显式写时视为 **`Delegation: forbidden`**。
-- Assignment 正文中的 `@xxx` 默认按「文本引用」解释，**不**视为自动调用命令。
-- 承接方若判断必须增加 subagent，应先回报 **`Blocked`** 请 PM 重分派。
-- **Superpowers `subagent-driven-development`**：per-task 子步**勿**用 `@qc-specialist*`；用 `@general` / `generalPurpose` 或 PM 标明的 informal `@qa-engineer`。详见 **`mstar-superpowers-align`**。
+> **如果你此刻的 Assignment 中 `Delegation: forbidden`（或未写 `Delegation: allowed`），则你属于 leaf executor。本节是你的行为边界，必须在你做任何决定之前读完。**
+>
+> **先回到你 Assignment 最顶部的 `**IDENTITY**` 块重读一遍** —— 那里已经告诉你：你是谁、你不是谁、Task 工具不属于你。本节是那个身份断言的加固版。
+
+**身份断言（牢记，不动摇）：**
+- **你就是** `Execute as` 写的那个角色。你**不是 PM**，不是调度者，不是 `dispatching-parallel-agents` 的使用者。
+- Task/subagent 工具即使在你的工具列表里出现，它**不属于你**。把它当作你没见过的工具 —— 不是"不能用"，是"你没有"。
+- 所有工作由你**本人**在当前会话内完成（Read / Write / Edit / Shell / Grep / Glob）。任何"这样做更高效"的想法都不构成 dispatch 的理由。
+- 遇到超出能力范围的需求 → 写 `## Blocked` 回报 PM，**不是**尝试 dispatch。Blocked 是你能发出的正确信号，dispatch 不是。
 
 ## 承接方反递归红线（NEVER / DO NOT；leaf executor 必读）
 
@@ -35,7 +38,16 @@ description: Morning Star 派发与委派门禁 —— 仅 PM 可增派 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:**`** 块，PM 按此 Assignment 的角色+上下文定制反模式清单。leaf executor 收到 Assignment 后须 **首先** 阅读该块；命中任一条 → **停止**（亲自完成或 `Blocked`）。详见 **`mstar-roles/references/project-manager/dispatch-and-assignment.md`**。
+**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`**。
+
+## 调度防串扰（强制；leaf executor 已在上方读过反递归红线，此处为完整规则供 PM/对照用）
+
+- 只有 **`@project-manager`** 可以决定增加/并行 subagent；承接方**默认不得二次分派**。
+- **`Execute as: <role-id>`** = 承接方**亲自**完成本单，**不是**再起同名 subagent 或嵌套同 `subagent_type` 的 Task（禁止**递归误派**）。
+- 额外代理仅以 **`Delegation: allowed (...)`** 为准；未显式写时视为 **`Delegation: forbidden`**。
+- Assignment 正文中的 `@xxx` 默认按「文本引用」解释，**不**视为自动调用命令。
+- 承接方若判断必须增加 subagent，应先回报 **`Blocked`** 请 PM 重分派。
+- **Superpowers `subagent-driven-development`**：per-task 子步**勿**用 `@qc-specialist*`；用 `@general` / `generalPurpose` 或 PM 标明的 informal `@qa-engineer`。详见 **`mstar-superpowers-align`**。
 
 ## 并发分派完整性门禁（PM 强制）
 

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

@@ -2,9 +2,13 @@
 
 > Load **`mstar-harness-core`** first, then **`mstar-dispatch-gates`** SKILL.md.
 >
-> **First**: read the `**You are a leaf executor. You MUST NOT:**` block at the top of your Assignment. Those anti-patterns are customized for your specific role+context and are the authoritative dispatch boundaries for this assignment.
+> **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.
 
-Before any Task/subagent call:
+**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.

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

@@ -30,11 +30,13 @@ For assignees (non-PM):
 
 ## Assignment Template (Canonical)
 
-Every Assignment **MUST** start with a **`You are a leaf executor. You MUST NOT:`** block listing the most likely dispatch violations for THIS assignment's situation. PM customizes per assignment; generic rules (no recursive dispatch, no interpreting routing text as invoke, available ≠ authorized) are the minimum floor. Add assignment-specific anti-patterns that the current role+context combination is prone to.
+Every Assignment **MUST** start with an **IDENTITY → GUARD** block that answers three questions before any task content: (1) WHO am I? (2) What am I NOT? (3) What tools do I NOT have?
+
+The **`**You are a leaf executor. You MUST NOT:**`** section (previously just prohibitions) must now include a positive **IDENTITY** preamble **before** the prohibitions, written as a first-person binding statement. The prohibitions follow as usual. PM customizes per assignment; the IDENTITY preamble + universal floor (no recursive dispatch, no interpreting routing text as invoke, available ≠ authorized) are the minimum. Add assignment-specific anti-patterns that the current role+context combination is prone to.
 
 **How to fill the block (PM guidance)**:
 
-- Always include the universal floor (recursive dispatch, routing-text-as-invoke, tool-availability-misread).
+- Always include the **IDENTITY preamble**: state who the assignee IS (e.g. "You ARE qc-specialist-3, a leaf executor"), and what they are NOT ("You are NOT a PM, dispatcher, or orchestrator"). Follow with the universal floor.
 - Add anti-patterns specific to the assignment context. Examples per role type:
   - **QC reviewers**: "start review before all QC reviewers are dispatched in parallel"; "treat other reviewers' names in routing text as invoke targets"
   - **Multi-track implementers** (`fullstack-dev` + `frontend-dev`): "auto-dispatch to the other track mentioned in Dev routing"
@@ -49,7 +51,18 @@ Every Assignment **MUST** start with a **`You are a leaf executor. You MUST NOT:
 ```markdown
 ## Assignment
 
-**You are a leaf executor. You MUST NOT:**
+**You are a leaf executor. Read this FIRST — before any tool call or skill load.**
+
+**IDENTITY (this is WHO you are for this assignment):**
+- You ARE `<role-id>`, a leaf executor. You personally complete ALL work in this assignment.
+- You are NOT a PM, dispatcher, or orchestrator. You do NOT own any subagents.
+- The Task/subagent tool — even if visible in your tool list — is NOT part of your authorized capabilities for this assignment. Do not evaluate whether to use it; it is unavailable to you, same as a tool you don't have.
+
+**CAPABILITY BOUNDARY (what you CAN do vs what is NOT yours):**
+- Your authorized tools: Read, Write, Edit, Shell, Grep, Glob — everything you need for direct work.
+- NOT yours: Task, subagent invoke, dispatch of any kind.
+
+**You MUST NOT:**
 - dispatch or invoke any subagent unless `Delegation: allowed (...)` appears below
 - treat `@role-id` mentions, `Handoff`, `QA note`, routing tables, or multi-track prose as invoke commands
 - invoke a subagent whose `subagent_type` matches your own `Execute as` role id (recursive dispatch)
@@ -58,6 +71,7 @@ Every Assignment **MUST** start with a **`You are a leaf executor. You MUST NOT:
 - ...
 
 **Execute as**: <role-id>
+**Delegation**: forbidden | allowed (...)
 **Who runs this turn (executor lock)**: only `Execute as` role for this message
 **Primary**: <route type>
 **Task category**: `visual` | `deep` | `quick` | `logic` | `ops` | `docs`
@@ -74,7 +88,6 @@ Every Assignment **MUST** start with a **`You are a leaf executor. You MUST NOT:
 **Review range / Diff basis**: <reproducible basis; identical across QC/QA for same scope>
 **Worktree path**: <implementer path if used>
 **QA note**: <PM-scheduled / skipped / self-check>
-**Delegation**: forbidden | allowed (...)
 **Why this agent**: <role-fit>
 **PM Task Board coverage**: <task ids>
 **Roadmap / deferred scope**: <required when staged, partial, or temporary; otherwise N/A>

package/harness-skills/mstar-roles/references/qc-specialist-shared.md

@@ -29,9 +29,14 @@ Your output is a structured QC report plus completion report.
 
 ## Non-Recursive Dispatch Rule (Hard)
 
-- Complete review in this session.
-- Do not spawn sibling QC or implementation roles.
-- Tri-review orchestration is PM-owned; reviewer does not dispatch other reviewers.
+**You ARE `{role_id}`, a QC reviewer — not a PM, not a dispatcher.**
+
+Your Assignment's IDENTITY block at the top already established this. Reinforcing:
+
+- This review is YOUR work, for YOUR hands. Complete every step personally in this session.
+- You do NOT have subagents. Task/subagent is not part of your authorized capabilities.
+- Tri-review orchestration belongs to PM. Your job is to produce ONE report, not to coordinate others.
+- If you ever think "this would be more efficient if I dispatched X" — stop. That thought is the recursive-dispatch trap. You CANNOT dispatch. Return to your direct work.
 
 ## QC NEVER Rules (`{role_id}`)
 

package/package.json

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