@mstar-harness/opencode 1.5.2 → 1.5.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,12 @@ All notable changes to the `@mstar-harness/opencode` package are documented in t
4
4
 
5
5
  The monorepo root [CHANGELOG.md](../../CHANGELOG.md) summarizes cross-surface releases.
6
6
 
7
+ ## 1.5.3
8
+
9
+ - Version alignment with harness **1.5.3** (bundled skills/commands: frontmatter YAML quotes + `/iteration-loop` scale `XL`).
10
+
11
+ See root [CHANGELOG.md](../../CHANGELOG.md) **1.5.3**.
12
+
7
13
  ## 1.5.2
8
14
 
9
15
  - Version alignment with harness **1.5.2** (bundled skills/commands: process-vs-results git policy + `{SPECS_DIR}` resolve order).
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: iteration-loop
3
- description: Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no grill-me.
3
+ description: "Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no grill-me."
4
4
  agent: project-manager
5
5
  ---
6
6
 
@@ -27,17 +27,18 @@ Phase gate SSOT → **`mstar-iteration`** §1–§5. This command is a **consume
27
27
  | Arg | Meaning | Default |
28
28
  |-----|---------|---------|
29
29
  | `direction` | Iteration direction / feedback constraint (free text) | Code-first research → **auto-lock recommended** |
30
- | `scale` | `S` \| `M` \| `L` | **`M`** |
30
+ | `scale` | `S` \| `M` \| `L` \| `XL` | **`M`** |
31
31
 
32
32
  **Scale budget**(写入 compass;约束 **业务** plan 数量)→ **`mstar-iteration`** §1.2 + `references/autonomous-direction-lock.md`:
33
33
 
34
34
  - **S** → 1 business plan
35
35
  - **M** → 2–3 business plans
36
- - **L** → 3–4 business plans(默认上限 4,除非 `direction` 显式要求更大)
36
+ - **L** → 3–4 business plans(上限 4
37
+ - **XL** → **>4** business plans(5+;适合大范围 autonomous 迭代)
37
38
 
38
- **HARD**:budget **只计**实际业务交付 plan;**不计** harness 流程(Review 链、QC/QA、compound、close、PR、merge-ready、compass/`status.json` 维护等)。流程门禁仍须执行,但不占 S/M/L 名额,也不得写成独立 process plan 来“凑数/占坑”。
39
+ **HARD**:budget **只计**实际业务交付 plan;**不计** harness 流程(Review 链、QC/QA、compound、close、PR、merge-ready、compass/`status.json` 维护等)。流程门禁仍须执行,但不占 S/M/L/XL 名额,也不得写成独立 process plan 来“凑数/占坑”。
39
40
 
40
- Parse: if the last token is exactly `S`/`M`/`L` (case-insensitive), treat it as `scale`; remaining text is `direction`. If only one token and it is `S`/`M`/`L`, that is `scale` with empty `direction`.
41
+ Parse: if the last token is exactly `S`/`M`/`L`/`XL` (case-insensitive), treat it as `scale`; remaining text is `direction`. If only one token and it is `S`/`M`/`L`/`XL`, that is `scale` with empty `direction`.
41
42
 
42
43
  ## Phase state machine(禁止跳步)
43
44
 
@@ -190,7 +191,7 @@ Tool rule → **`mstar-dispatch-gates`** specialist review-and-edit(顺序链
190
191
  Print before §6; all must be `[x]`:
191
192
 
192
193
  - [ ] Autonomous direction lock rationale recorded in compass(not grill-me)
193
- - [ ] Scale budget applied; **business** plan count within S/M/L(harness process not counted)
194
+ - [ ] Scale budget applied; **business** plan count within S/M/L/XL(harness process not counted)
194
195
  - [ ] Draft compass + plans + `status.json` registered
195
196
  - [ ] product-manager invoke completed;**未**向 `{KNOWLEDGE_DIR}/` 新增
196
197
  - [ ] architect invoke completed;**未**向 `{KNOWLEDGE_DIR}/` 新增
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mstar-branch-worktree
3
- description: Morning Star business-repo Git feature branches, worktree isolation layers **L1** (iteration cross-plan — control worktree + per-plan feature worktrees + `execution_lease`) and **L2** (within-plan — `references/parallel-writable-pre-dispatch.md`; N parallel Task invokes do NOT satisfy isolation), plan/Spec integration branches, and QC/QA checkout alignment (`Review cwd`, `Working branch`, `plan_id`, `Review range` / `Diff basis` must match verbatim across three QC reviewers and QA). Read when PM writes `Working branch` / `Branch policy`, iteration Phase 2 control vs feature worktree paths, dispatches ≥2 concurrent writable implement tracks on one repo, `Worktree isolation: required`, two or more writable streams touch one repo, dispatching QC tri-review or QA after merging to a single `HEAD`, dev/QA/ops before first `git commit`, or explaining worktree paths. Required for `project-manager` parallel implement or pre-QC orchestration; `fullstack-dev*` / `frontend-dev` / `qa-engineer` / `ops-engineer` on repo writes; `qc-specialist*` before review. Does not replace the state machine (`mstar-harness-core`).
3
+ description: "Morning Star business-repo Git feature branches, worktree isolation layers **L1** (iteration cross-plan — control worktree + per-plan feature worktrees + `execution_lease`) and **L2** (within-plan — `references/parallel-writable-pre-dispatch.md`; N parallel Task invokes do NOT satisfy isolation), plan/Spec integration branches, and QC/QA checkout alignment (`Review cwd`, `Working branch`, `plan_id`, `Review range` / `Diff basis` must match verbatim across three QC reviewers and QA). Read when PM writes `Working branch` / `Branch policy`, iteration Phase 2 control vs feature worktree paths, dispatches ≥2 concurrent writable implement tracks on one repo, `Worktree isolation: required`, two or more writable streams touch one repo, dispatching QC tri-review or QA after merging to a single `HEAD`, dev/QA/ops before first `git commit`, or explaining worktree paths. Required for `project-manager` parallel implement or pre-QC orchestration; `fullstack-dev*` / `frontend-dev` / `qa-engineer` / `ops-engineer` on repo writes; `qc-specialist*` before review. Does not replace the state machine (`mstar-harness-core`)."
4
4
  ---
5
5
 
6
6
  ## Load order(必读顺序)
@@ -81,7 +81,7 @@ PM 在新迭代启动时执行。
81
81
  | **非目标** | 明确排除在本次迭代外的事项 |
82
82
  | **Roadmap 上下文** | 本迭代在整体 roadmap 中的位置(current iteration / next iteration) |
83
83
  | **Delivery branch policy** | `iteration_base_branch`(integration 分支从何处分出)、`spec_integration_branch`、`target_branch`(最终 PR 目标) |
84
- | **Scale budget**(可选) | 仅当 caller **显式**给出或选用 **autonomous** 时适用:`S` = 1 **业务** plan;`M` = 2–3;`L` = 3–4(默认上限 4)。**只计实际业务交付 plan**,不计 harness 流程性工作(Review 链 / QC / QA / compound / close / PR 等)。**interactive 默认不强制** S/M/L。计数细则 → **`references/autonomous-direction-lock.md`** § Scale budget |
84
+ | **Scale budget**(可选) | 仅当 caller **显式**给出或选用 **autonomous** 时适用:`S` = 1 **业务** plan;`M` = 2–3;`L` = 3–4(上限 4);`XL` = **>4**(5+)。**只计实际业务交付 plan**,不计 harness 流程性工作(Review 链 / QC / QA / compound / close / PR 等)。**interactive 默认不强制** S/M/L/XL。计数细则 → **`references/autonomous-direction-lock.md`** § Scale budget |
85
85
 
86
86
  #### Direction lock modes
87
87
 
@@ -8,7 +8,7 @@ Capability detail for Phase 1 when direction lock mode is **`autonomous`**.
8
8
 
9
9
  - Research (§1.1) and candidate exploration already done — **read repo artifacts before ranking**.
10
10
  - Do not invent roadmap items that have no file or status evidence.
11
- - Scale budget (`S`/`M`/`L`) applies in this mode (or when the caller supplies one); do not retrofit a scale cap onto an interactive start that never asked for one.
11
+ - Scale budget (`S`/`M`/`L`/`XL`) applies in this mode (or when the caller supplies one); do not retrofit a scale cap onto an interactive start that never asked for one.
12
12
 
13
13
  ## Ranking heuristics(highest first)
14
14
 
@@ -29,7 +29,7 @@ Write into compass (and plan Scope as needed):
29
29
  | Rationale | Why this candidate won(cite paths / roadmap lines) |
30
30
  | Acceptance criteria | Iteration-level Done |
31
31
  | Non-goals | Explicit exclusions |
32
- | Scale budget | `S` \| `M` \| `L` and resulting plan-count cap |
32
+ | Scale budget | `S` \| `M` \| `L` \| `XL` and resulting plan-count cap |
33
33
 
34
34
  ## Scale budget
35
35
 
@@ -37,7 +37,8 @@ Write into compass (and plan Scope as needed):
37
37
  |--------|-------------------------|
38
38
  | `S` | 1 |
39
39
  | `M` | 2–3 |
40
- | `L` | 3–4(default cap 4 unless a written constraint requires more) |
40
+ | `L` | 3–4(cap 4) |
41
+ | `XL` | **>4**(5+) |
41
42
 
42
43
  ### What counts toward the budget(HARD)
43
44
 
@@ -52,7 +53,7 @@ Count only **business delivery plans** registered in compass / `status.json` who
52
53
  | Phase 3–5 process | Compound / package promotion, iteration-close, Create PR, merge-ready / CI babysit |
53
54
  | Meta “plans” | “run QC”, “do compound”, “open PR”, “setup harness”, “write compass only” |
54
55
 
55
- Harness steps remain **mandatory gates** outside the budget — they do not consume S/M/L slots and must not be padded into the plan list to “fill” the budget.
56
+ Harness steps remain **mandatory gates** outside the budget — they do not consume S/M/L/XL slots and must not be padded into the plan list to “fill” the budget.
56
57
 
57
58
  If evidence suggests more **business** work than the budget allows, keep overflow in compass `## Roadmap Position` → next iteration — do not silently expand past the budget, and do not replace business plans with process plans to stay under the cap.
58
59
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mstar-phase-gates
3
- description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare(`specify → clarify → plan`)、Execute(`plan(locked) → tasks → implement`;多 task 默认 **`Execution mode: sdd`**)、意图门禁、长期目标优先、分批 roadmap 强制落盘、clarify 核心纪律、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read;`@project-manager` 每轮编排非 hotfix 任务必读;`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节;实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。实现行为见 `mstar-coding-behavior`;SDD 见 `mstar-sdd`;迭代级活动见 `mstar-iteration`。
3
+ description: "Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare(`specify → clarify → plan`)、Execute(`plan(locked) → tasks → implement`;多 task 默认 **`Execution mode: sdd`**)、意图门禁、长期目标优先、分批 roadmap 强制落盘、clarify 核心纪律、hotfix 压缩路径、可验证编辑、Phase Gate 最小证据。**必须**在 PM 判定 gate、首次 implement 派单前、产品/架构参与 Prepare、或解释为何不能跳过 plan/clarify 时 Read;`@project-manager` 每轮编排非 hotfix 任务必读;`@product-manager` / `@architect` 写规格与锁 plan 时必读 Prepare 节;实现角色 Read Execute 与 hotfix 例外即可。Task category 与 `quick` 禁豁免规则仍在 `mstar-harness-core`。实现行为见 `mstar-coding-behavior`;SDD 见 `mstar-sdd`;迭代级活动见 `mstar-iteration`。"
4
4
  ---
5
5
 
6
6
  ## Load order(必读顺序)
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mstar-plan-artifacts
3
- description: Morning Star plan harness artifacts — `{PLAN_DIR}` main plans and durable review summaries, `{SDD_DIR}/review/` ephemeral QC/QA bundles, `{KNOWLEDGE_DIR}` / `{ITERATION_DIR}` indexes, Done compaction, plus `{HARNESS_DIR}/status.json` and root `residual_findings` (severity SSOT, open/archived lifecycle, `notes.json`). Read when writing plans or QC/QA review bundles, maintaining knowledge/iteration indexes, reading or writing `status.json` / R#, Done compaction, or mapping QC severity to JSON. Required for `@project-manager` on status, residuals, and InReview/QC waves; `@qc-specialist*` before writing review bundle reports; `@qa-engineer` before closing R# when `QA gate: mandatory`. Verdict rules: leaf → `mstar-roles/references/qc-specialist/report-template.md`; PM → `mstar-review-qc`. Paths in `mstar-plan-conventions`.
3
+ description: "Morning Star plan harness artifacts — `{PLAN_DIR}` main plans and durable review summaries, `{SDD_DIR}/review/` ephemeral QC/QA bundles, `{KNOWLEDGE_DIR}` / `{ITERATION_DIR}` indexes, Done compaction, plus `{HARNESS_DIR}/status.json` and root `residual_findings` (severity SSOT, open/archived lifecycle, `notes.json`). Read when writing plans or QC/QA review bundles, maintaining knowledge/iteration indexes, reading or writing `status.json` / R#, Done compaction, or mapping QC severity to JSON. Required for `@project-manager` on status, residuals, and InReview/QC waves; `@qc-specialist*` before writing review bundle reports; `@qa-engineer` before closing R# when `QA gate: mandatory`. Verdict rules: leaf → `mstar-roles/references/qc-specialist/report-template.md`; PM → `mstar-review-qc`. Paths in `mstar-plan-conventions`."
4
4
  ---
5
5
 
6
6
  ## Load order
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mstar-review-qc
3
- description: Morning Star QC orchestration — **SDD mandatory plan QC tri-review** (`{SDD_DIR}/review/qc1.md`…`qc3.md` + consolidated); inline/hotfix single-seat (`qc.md` in review bundle); PM dispatch timing, tri identity gate, residual registration contract, layer boundaries, durable plan summary. Leaf QC execution → **`mstar-roles/references/qc-specialist/`**. Per-task review is **`mstar-sdd`** (L2). Primary reader: **`project-manager`** when dispatching or consolidating QC.
3
+ description: "Morning Star QC orchestration — **SDD mandatory plan QC tri-review** (`{SDD_DIR}/review/qc1.md`…`qc3.md` + consolidated); inline/hotfix single-seat (`qc.md` in review bundle); PM dispatch timing, tri identity gate, residual registration contract, layer boundaries, durable plan summary. Leaf QC execution → **`mstar-roles/references/qc-specialist/`**. Per-task review is **`mstar-sdd`** (L2). Primary reader: **`project-manager`** when dispatching or consolidating QC."
4
4
  ---
5
5
 
6
6
  ## Load order(必读顺序)
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mstar-sdd
3
- description: Morning Star subagent-driven development (SDD) — file handoff, per-task implementer + task reviewer (L2), progress ledger, branch review-package for plan QC tri (L3). **Implementer session** `fresh` (default) or **`sticky`** (same dev subagent across tasks — `references/sticky-implementer-session.md`). **Must** Read when project-manager runs `Execution mode: sdd` (multi-task plan, single-plan, or iteration Phase 2), dispatches SDD implementer/reviewer subagents, or prepares review-package paths. Leaf implementer/reviewer subagents skip PM sections via SUBAGENT-STOP in dispatch prompts.
3
+ description: "Morning Star subagent-driven development (SDD) — file handoff, per-task implementer + task reviewer (L2), progress ledger, branch review-package for plan QC tri (L3). **Implementer session** `fresh` (default) or **`sticky`** (same dev subagent across tasks — `references/sticky-implementer-session.md`). **Must** Read when project-manager runs `Execution mode: sdd` (multi-task plan, single-plan, or iteration Phase 2), dispatches SDD implementer/reviewer subagents, or prepares review-package paths. Leaf implementer/reviewer subagents skip PM sections via SUBAGENT-STOP in dispatch prompts."
4
4
  ---
5
5
 
6
6
  ## Load order
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mstar-harness/opencode",
3
- "version": "1.5.2",
3
+ "version": "1.5.3",
4
4
  "description": "Morning Star harness OpenCode plugin (skills bootstrap and agent loading).",
5
5
  "license": "MIT",
6
6
  "repository": {