@mstar-harness/opencode 0.7.6 → 0.7.7

package/harness-commands/iteration-start.md

@@ -64,9 +64,13 @@ Explore candidate directions targeting **product completeness**:
 - Allow substantive refactoring where it accelerates product maturity
 - Scope 2–4 candidates, each with clear product-completeness goals and trade-offs
 
-## 3. Lock Direction — grill-me
+## 3. Lock Direction — bundled `grill-me`
 
-Run the **grill-me skill** to stress-test candidate directions with the user:
+This command bundles a **non-`mstar-*`** skill at `skills/grill-me/SKILL.md`. **Only this command step** references it — **do not** load it from `mstar-harness-core` or other `mstar-*` skills.
+
+**Before this step:** Read `skills/grill-me/SKILL.md`.
+
+Run **grill-me** to stress-test candidate directions with the user:
 
 - Walk through trade-offs for each candidate
 - Converge on a **single iteration direction** with shared understanding

package/harness-skills/grill-me/SKILL.md

@@ -0,0 +1,10 @@
+---
+name: grill-me
+description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
+---
+
+Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+
+Ask the questions one at a time.
+
+If a question can be answered by exploring the codebase, explore the codebase instead.

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

@@ -26,7 +26,7 @@ description: DESIGN.md design system specification for Morning Star projects. Cr
 
 **YAML frontmatter is the SSOT for token values.** Colors, typography, spacing, rounded, and components live in the frontmatter as structured, machine-readable data. The Markdown body is supplementary documentation (rules, intent, usage guidance). When reading DESIGN.md, always parse the YAML frontmatter first; when writing, keep frontmatter and body in sync.
 
-**Out of scope:** rendered UI artifacts (use Open Design MCP `user-open-design`); frontend implementation that consumes DESIGN.md tokens (use `@frontend-dev` / `@fullstack-dev`); QC review verdict rules (→ **`mstar-review-qc`**).
+**Out of scope:** rendered UI preview tooling outside the repo; frontend implementation that consumes DESIGN.md tokens (use `@frontend-dev` / `@fullstack-dev`); QC review verdict rules (→ **`mstar-review-qc`**).
 
 ## Location
 
@@ -129,14 +129,6 @@ gray-1000: #000   gray-1000: #eee
 - Token names are the **SSOT interface** — consumers reference tokens by name, not raw values
 - `references/design-md-spec.md` § Light/Dark rules defines the contract
 
-## Open Design integration
-
-If `user-open-design` MCP is available:
-- DESIGN.md is the **design intent** (tokens + rules)
-- Open Design manages **rendered artifacts** (HTML/CSS/JSX previews)
-- When DESIGN.md is updated, recommend syncing the Open Design project to reflect new tokens
-- DESIGN.md does not replace Open Design; they are complementary
-
 ## References
 
 - `references/design-md-spec.md` — normative spec: section definitions, token naming conventions, light/dark contract

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

@@ -11,7 +11,13 @@ description: Morning Star (启明星) harness **强制全局入口** —— 信
 
 - 凡 **`mstar-*`**（`name` ≠ `mstar-harness-core`）假定读者**已 Read 本 skill**。
 - **仅读专题、未读核心** → 未完成 harness 加载。
-- 各专题 SKILL.md 含 **Load order**；按 **`mstar-roles`** 角色矩阵按需加载，**禁止**为「保险」通读全部专题。
+- 各专题 SKILL.md 含 **Load order**；按 **`mstar-harness-core`** 专题 skill 索引 + 角色 load contract 按需加载，**禁止**为「保险」通读全部专题。
+
+## Standalone harness（`mstar-*` 自洽）
+
+- **`mstar-*` skill 体系**在本仓库内自洽运行：正文与 load order **不得**依赖仓库外的 skills、CLI、或 MCP 服务。
+- **Commands**（如 `/iteration-start`）可引用本仓库 bundled、**非 `mstar-*`** 的辅助资产（例如 `skills/grill-me/`）；该引用**仅**存在于 command 层，**不**进入 `mstar-*` 专题索引或 load matrix。
+- 框架/SDK/API 问题：先 Read/Grep 项目内文档与源码；不将第三方文档工具写入 `mstar-*` 必读路径。
 
 ## 信息源优先级
 
@@ -117,9 +123,9 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 - plan-writing artifacts land in `{PLAN_DIR}`, not external default plan directories.
 - PM Assignment 键名英文；任务正文可中文；产出/报告默认英文。
 
-## 库文档（Context7）
+## 库文档 / API 问题
 
-框架/SDK/API 问题 → **`references/library-docs-protocol.md`**（MCP 优先，CLI 兜底，禁双跑）。
+先 Read/Grep 项目内文档、规格与源码；仍不确定时再向用户澄清。**不**将第三方 MCP/CLI 文档工具写入 `mstar-*` load order。
 
 ## 升级触发
 
@@ -145,14 +151,16 @@ Read **`mstar-host`** after this skill; detect host per its table, then Read the
 | iteration-close 无 frontmatter completed / 漏 compound Phase 6 | `mstar-iteration` §3.0.5、§3.4、§3.2 #5 |
 | iteration 默认 `main` 作 base 或 PR 目标 | `mstar-iteration` §1.2、§2.3；`mstar-plan-conventions` Spec 分支模型 |
 
-## 可选：OpenViking Memory
-
-会话有 **`memsearch`** 工具时 Read **`references/openviking-memory-plugin.md`**。
+## 常见 harness 说法对照（帮助理解角色分工）
 
-## References（保留在 core）
+| 常见说法 | 本仓库实体 |
+|----------|------------|
+| 总编排 | `@project-manager` |
+| 规划/访谈 | `@product-manager` / `@architect` + Prepare 阶段 |
+| category 路由 | **`Task category`** + 路由表 + 子代理选择 |
+| 持续推进 / 不半途而废 | Phase Gate + Todo/`tasks` + 验证门禁 |
+| 行级哈希锚定编辑 | 以 **读后再改 + 小步 Patch** 纪律落实（`mstar-phase-gates`） |
 
-- `references/open-harness-principles.md` — 理念与分层 `AGENTS.md`
-- `references/library-docs-protocol.md` — Context7
-- `references/openviking-memory-plugin.md` — 条件加载
+项目根 **`AGENTS.md` 写什么、分层 bootstrap** → **`mstar-plan-conventions`** `references/harness-bootstrap-and-agents-layering.md`（勿在 core 重复长文）。
 
 **专题 skill**（规则在各自 `SKILL.md`）：`mstar-phase-gates`、`mstar-branch-worktree`、`mstar-plan-artifacts` 等 — 见上表索引。

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

@@ -37,10 +37,6 @@ Use **capability signals** (not filesystem paths):
 
 When PM dispatches **N >= 2** concurrent assignees (QC tri-review, dual-track implement, etc.) and the host exposes actual invoke / Task / subagent tools, read **`references/parallel-dispatch.md`** in the dispatch round (shared with `mstar-dispatch-gates`). Without a callable invoke tool when dispatch is required → **`Blocked`**; Assignment Markdown alone is not dispatch.
 
-## Library docs (Context7)
-
-Follow `mstar-harness-core` → `references/library-docs-protocol.md`.
-
 ## Conflict order
 
 1. User explicit instructions (this turn)

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

@@ -36,22 +36,9 @@ Use host subagent / Task / equivalent per **`parallel-dispatch.md`**. OpenCode P
 - Large unrelated platform injections (e.g. long ecosystem prompts): prefer on-demand / `alwaysApply: false` when not stack-relevant.
 - One default channel per capability class (search, docs).
 
-## Optional MCPs / skills (user-enabled)
-
-Aligned with `mstar-harness-core` `references/open-harness-principles.md`. Editing global `opencode.json` requires explicit user consent.
-
-| Capability | Purpose | Notes |
-|------|------|------|
-| **Current docs** | Versioned API/libs | Context7-like MCP or equivalent |
-| **Web search** | Time-sensitive / migrations | Avoid duplicate search MCPs |
-| **Code pattern search** | Cross-repo references | e.g. grep.app MCP |
-| **Repo graph** | Impact / PR risk | e.g. GitNexus |
-| **Browser / E2E** | Observable QA evidence | agent-browser, Playwright |
-| **Git workflow** | Atomic commits, branch closure | git-commit, finishing-a-development-branch |
-| **Systematic debugging** | RCA before fix | `mstar-coding-behavior` |
-| **OpenViking memory** | Long-term memory tools | Only if `memsearch` present; `openviking-memory-plugin.md` |
-
-**Not recommended**: overlapping search MCPs; extra tools to mask missing harness baseline.
+## Standalone harness note
+
+Bundled **`mstar-*` skills** are self-contained in this repository. User-installed host MCPs, external skills, or CLIs are **outside harness SSOT** — do not add them to `mstar-*` load order or treat them as required for gates.
 
 ## Maintenance boundary
 

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

@@ -74,6 +74,8 @@ PM 在新迭代启动时执行。
 
 **Branch policy gate**：若用户、现有 roadmap、或项目约定未明确 `iteration_base_branch` / `target_branch`，PM 必须检查当前分支并向用户确认。**不得**因为存在 `main` / `master` 就默认从默认分支开 iteration 或向默认分支提 PR。
 
+**Direction lock**：compass/plans 初稿落盘前，PM 须与用户逐问收敛**单一**迭代方向、成功标准、非目标，并确认 delivery branch policy；决策写入 compass `## Scope` / `## Acceptance Criteria` / `## Non-Goals` 与 Delivery Branch Policy。
+
 ### 1.3 创建迭代 compass
 
 写入 `{ITERATION_DIR}/<iteration-id>-delivery-compass.md`。**必须**使用 `references/iteration-compass-template.md` 完整结构（YAML frontmatter + `## Roadmap Position` + close 占位节）。`end_date` 仅在 iteration-close 填入；禁止用正文 completion prose 替代 frontmatter `status`。

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-roles
-description: Morning Star role prompt hub — `agents/*.md` shells plus full behavior in `references/*.md`, each with a **Required Skill Dependencies** list (which `mstar-*` topic skills to load after `mstar-harness-core`). Always load for any Morning Star role (`project-manager`, `product-manager`, `architect`, `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, `qa-engineer`, `qc-specialist*`, `ops-engineer`, `writing-specialist`, `prompt-engineer`). Cross-role summary table in this SKILL.md; per-role lists are authoritative for that role's session.
+description: Morning Star role prompt hub — `agents/*.md` shells plus full behavior in `references/*.md`, each with a **Required Skill Dependencies** list (which `mstar-*` topic skills to load after `mstar-harness-core`). Always load for any Morning Star role (`project-manager`, `product-manager`, `architect`, `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, `qa-engineer`, `qc-specialist*`, `ops-engineer`, `writing-specialist`, `prompt-engineer`). Cross-role **Role → typical topic skills** summary in this SKILL.md; per-role lists in `references/*.md` are authoritative for that role's session. Full topic skill index → **`mstar-harness-core`**.
 ---
 
 ## Load Order (Required)
@@ -33,28 +33,6 @@ If any conflict appears, `mstar-harness-core` remains the authoritative source f
 | `writing-specialist` | `references/writing-specialist.md` | — |
 | `prompt-engineer` | `references/prompt-engineer.md` | — |
 
-## Shared Skill Dependencies
-
-Treat these as baseline dependencies **where the role touches implementation, review, verification, or ops execution** (see `mstar-harness-core` load contract). Load **on demand**, not as a fixed bundle.
-
-| Skill | Use when task involves |
-| --- | --- |
-| `mstar-harness-core` | **Always** (non-trivial work): entry, state machine, Task category, explore boundary, skill index |
-| `mstar-phase-gates` | Prepare/Execute gates, clarify, hotfix path, intention gate |
-| `mstar-dispatch-gates` | PM dispatch; **all leaf executors** before any Task/subagent call |
-| `mstar-branch-worktree` | Git write, parallel worktrees, QC/QA checkout fields |
-| `mstar-plan-conventions` | `{HARNESS_DIR}` discovery, init, Spec branch naming, plan-writing path gate |
-| `mstar-plan-artifacts` | Main plan, `reports/`, `status.json`, residual, knowledge/iteration, Done compaction |
-| `mstar-design-md` | DESIGN.md design system spec — create/audit/maintain tokens, completeness checklist, light/dark dual-theme |
-| `mstar-review-qc` | QC workflow, template, verdict, high-risk checks |
-| `mstar-coding-behavior` | Implementation/debug/refactor/review-feedback handling (**not** PM orchestration-only) |
-| `mstar-skill-authoring` | New skills, major skill rewrites, trigger descriptions, behavior-shaping skill validation |
-| `mstar-compound` | Capturing solved problems as structured knowledge in `{KNOWLEDGE_DIR}`; Discoverability check; CONCEPTS.md synergy |
-| `mstar-compound-refresh` | Auditing/updating/consolidating knowledge docs; maintaining `{KNOWLEDGE_DIR}` accuracy |
-| `mstar-iteration` | Iteration lifecycle: iteration-start (scope/roadmap lock), Autonomous Execute (per-plan dispatch loop), iteration-close (compound + roadmap update) |
-| `mstar-strategy` | Creating/maintaining `STRATEGY.md`; project vision, principles, technology direction |
-| `mstar-host` | Host-specific behavior (auto-detect; `references/opencode.md` / `cursor.md` / `codex.md`) |
-
 ### Role → typical topic skills (after `mstar-harness-core`)
 
 | Role | Typical adds |

package/harness-skills/mstar-roles/references/prompt-engineer.md

@@ -51,7 +51,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 When creating a new skill, making a major skill rewrite, changing frontmatter `description`, or changing behavior-shaping skill text:
 
 1. MUST read `mstar-skill-authoring` before editing.
-2. MUST follow the repository `skill-creator` requirement when the change is a new skill or major rewrite.
+2. MUST follow the repository **`skill-creator`** requirement when the change is a new skill or major rewrite (`AGENTS.md` → Skill-Creator Requirement).
 3. MUST include validation evidence for behavior-shaping changes, or explicitly state why only manual/search validation is practical.
 
 ## Prompt Change Minimal Checklist

package/package.json

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

package/harness-skills/mstar-harness-core/references/library-docs-protocol.md

@@ -1,35 +0,0 @@
-# Context7 Library Docs Protocol (Shared)
-
-This protocol is shared by all hosts in Morning Star. Host adapter skills should consume this section, not redefine it.
-
-## When to use
-
-- The question is about library/framework/SDK/CLI/cloud API syntax, config options, migration behavior, or version-specific usage.
-- The answer quality depends on current docs rather than model memory.
-
-## When not to use
-
-- Pure refactoring strategy.
-- Writing scripts from scratch without external API dependence.
-- Business logic debugging not tied to third-party docs.
-- Generic programming concepts.
-- PR/code review judgment.
-
-## Single-path policy
-
-Use one path per question. Do not run MCP and CLI in parallel for the same library/question pair.
-
-1. **Primary path: Context7 MCP (if available)**
-   - Read tool schema first.
-   - Query with the user's full question.
-   - Prefer versioned library IDs when version is known.
-2. **Fallback path: ctx7 CLI (only if MCP unavailable/fails)**
-   - `npx ctx7@latest library <name> "<user question>"`
-   - `npx ctx7@latest docs <libraryId> "<user question>"`
-   - Max 3 commands per question.
-
-## Guardrails
-
-- Never include secrets in commands or queries.
-- Switch to fallback only after primary path fails.
-- Report uncertainty when docs retrieval fails on both paths.

package/harness-skills/mstar-harness-core/references/open-harness-principles.md

@@ -1,76 +0,0 @@
-# 开源 Agent Harness 理念（Morning Star）
-
-## 定位
-
-本文归纳从公开 agent harness 实践中提炼的**流程理念**，并已写入 `mstar-harness-core`、`mstar-roles` skill 的 `project-manager` 角色 等，作为本配置的默认行为约定。
-
-## 已内化的原则（执行时必须遵守）
-
-| 理念 | 含义 | 在本仓库的落点 |
-|------|------|----------------|
-| **意图优先于字面** | 先弄清「用户真正要达成什么」，再分类与分派 | `mstar-phase-gates` SKILL.md Prepare · `clarify` / `plan` 意图门禁；PM「第一性原理」 |
-| **先准备再实现** | 访谈式规划、锁范围、再写代码 | Prepare：`specify -> clarify -> plan`；Execute：`plan locked -> tasks -> implement` |
-| **`clarify` 核心纪律** | 逐方面核对至共享理解；沿设计决策树逐枝、一次一决；能探索代码库则先探索；每问带推荐答案 | **`mstar-phase-gates`** SKILL.md（含 Phase Gate Playbook） |
-| **按任务类别选能力与模型** | 视觉/深读/快改/硬逻辑等用不同强项 | `mstar-harness-core` SKILL.md「Task category」；Assignment 字段 **`Task category`**；宿主侧按角色配置 model（如 OpenCode 的 `opencode.json`） |
-| **可验证编辑** | 减少「凭记忆 Patch」导致的漂移与损坏 | `mstar-phase-gates` SKILL.md「可验证编辑与上下文纪律」：读后再改、失败则重读 |
-| **持续推进与可核对完成** | 长任务有清单、有关门证据，避免空转 | `mstar-phase-gates` / `mstar-review-qc`；实现侧自检见 `mstar-coding-behavior` |
-| **编码行为约束（轻量）** | 降低静默假设、过度设计与无关改动 | `mstar-coding-behavior`：Think Before Coding / Simplicity First / Surgical Changes / Goal-Driven Execution |
-| **并行与边界** | 多线任务不踩同一写归属、不绕过分支门禁；**开发**阶段同仓多可写并发须独立 **`git worktree`**；**QC / QA** 在 **同一检出**（`Review cwd`）与 **同一 `plan_id` + `Review range` / `Diff basis`** 上审查与验证，保证三票同一功能 | `mstar-branch-worktree`；`mstar-review-qc`；`mstar-dispatch-gates` |
-| **分层上下文（可选）** | 大仓库用目录级 `AGENTS.md` 降噪；根 `AGENTS.md` 维护边界见下文专节 | `mstar-harness-core` SKILL.md「分层上下文」；由业务项目维护者按需添加 |
-| **结构化澄清（按宿主）** | 向用户澄清/抉择时，**有 `question` 类能力则优先**；否则结构化正文；长问兜底 | `mstar-phase-gates` SKILL.md Prepare · `clarify`；当前宿主的 `mstar-host` skill；`mstar-roles` · `project-manager` |
-
-## 与常见 harness 说法的对照（帮助理解角色分工）
-
-| 常见说法 | 本仓库实体 |
-|----------|------------|
-| 总编排 | `@project-manager` |
-| 规划/访谈 | `@product-manager` / `@architect` + Prepare 阶段 |
-| category 路由 | **`Task category`** + 路由表 + 子代理选择 |
-| 持续推进 / 不半途而废 | Phase Gate + Todo/`tasks` + 验证门禁 |
-| 行级哈希锚定编辑 | 本仓库以 **读后再改 + 小步 Patch** 纪律落实（见 `mstar-harness-core`） |
-
-## 项目根 `AGENTS.md` 写什么、不写什么（建议）
-
-业务仓库根目录（或分层中的目录级）`AGENTS.md` 适合承载：**长期有效的规则、技术栈约束、工作流门禁**；不宜承载易变状态或已另有 SSOT 的内容，以免双轨漂移。
-
-### 宜放入
-
-- 技术栈与架构边界（变更时更新）
-- 开发与验证命令、目录布局、命名约定
-- 与 harness 对齐的**持久**规则（分支策略引用、**`{HARNESS_DIR}`** / **`{PLAN_DIR}`** 路径说明等）
-
-### 不宜放入（应指向专门落点）
-
-| 内容 | 更合适的落点 |
-|------|----------------|
-| 详细计划状态、阻塞列表、当前 sprint 叙述 | `{HARNESS_DIR}/status.json`（及可选 `{HARNESS_DIR}/notes.json` 程序时间线） |
-| 规格正文、枚举定义、API 契约全文 | 项目约定的冻结规格目录（如 `docs/spec/`、`.agents/designs/...`，名称自定） |
-| 迭代/版本级 delivery compass、program 范围快照 | `{ITERATION_DIR}`（并维护索引 README，见 `mstar-plan-conventions`） |
-| 某一 plan 的评审稿、gap 分析、跨版本实施 SSOT | `{KNOWLEDGE_DIR}`（并维护索引 README，见 `mstar-plan-conventions`） |
-| 临时 workaround、仅本轮有效的结论 | 主 plan 文件或 knowledge，收口后提炼再考虑进 `AGENTS.md` |
-
-### 更新前自检（避免污染单一权威）
-
-- 是否为**持久规则**，而非一两次性的当前状态？
-- 是否适用于**整个项目**，而非单个 plan？
-- 是否与冻结规格**重复**？若重复，应改为「引用路径」而非粘贴全文。
-- 是否其实属于 **`{HARNESS_DIR}/status.json`**（状态、门禁摘要、时间线）？
-
-### 典型信息源层级（模板）
-
-项目可自定义目录名；逻辑顺序常为：
-
-1. **冻结规格 / 设计权威**（版本化、显式变更流程）
-2. **根 `AGENTS.md`** — 项目级规则与约定
-3. **`{HARNESS_DIR}/status.json`** — 当前执行状态与 open residual 的 SSOT
-4. **`{ITERATION_DIR}`** — 迭代/版本级 compass（可选）
-5. **`{KNOWLEDGE_DIR}`** — 支撑实施的上下文文档（可选）
-
-若 `AGENTS.md` 与冻结规格冲突，**以规格为准**，并修订 `AGENTS.md` 对齐。细节分工与可到达性要求见 `mstar-plan-conventions`。
-
-## 延伸阅读
-
-- 按能力选配 MCP/skills：OpenCode → `mstar-host` `references/opencode.md`；其它宿主见 `mstar-host` 检测表
-- Evidence and checkpoints: `mstar-phase-gates` / `mstar-review-qc`; implementation self-checks: `mstar-coding-behavior`
-- 库文档检索共享协议：`mstar-harness-core` `references/library-docs-protocol.md`
-- 跨角色编码行为准则（轻量、可复用）：`mstar-coding-behavior`

package/harness-skills/mstar-harness-core/references/openviking-memory-plugin.md

@@ -1,45 +0,0 @@
-# OpenViking Memory Plugin (OpenCode, optional)
-
-This reference applies **only** when the current agent session exposes OpenViking tools (detection: **`memsearch`** is available in the tool list). It documents harness-aligned usage; implementation details follow the OpenCode plugin (for example `openviking-memory.ts` beside `openviking-config.json` under the user’s OpenCode plugins directory).
-
-## What the plugin provides
-
-Typical tools (names match the reference plugin):
-
-| Tool | Purpose |
-| --- | --- |
-| `memsearch` | Unified semantic search over memories, resources, and skills (`mode`: `auto` / `fast` / `deep`). |
-| `memread` | Read a single item by `viking://` URI with progressive depth (`abstract` / `overview` / `read` / `auto`). |
-| `membrowse` | List / tree / stat views under a `viking://` prefix. |
-| `memcommit` | Trigger session commit / memory extraction for the mapped OpenViking session (optional mid-session). |
-
-**URI rule**: `memread` and `membrowse` require URIs starting with `viking://` (validated by the plugin).
-
-**Service dependency**: The plugin calls an OpenViking HTTP API (default `http://localhost:1933` unless overridden). If tools error with connection or health failures, treat memory as **unavailable** for this turn; do not block core harness gates on memory.
-
-**Auto features** (when enabled in plugin config): conversation capture, periodic auto-commit, and optional **auto-recall** injection (`<relevant-memories>` appended to the latest user message). Recall is best-effort and must not replace explicit search when you need traceable evidence.
-
-## Harness alignment (mandatory)
-
-1. **Subordinate to SSOT**: `mstar-harness-core` state machine, phase gates, branch/worktree rules, and QC/QA alignment **always** override any suggestion retrieved from memory. If memory conflicts with plan, `status.json`, or Assignment, **follow the written artifacts** and record the conflict in notes or Completion Report.
-
-2. **No secrets in memory tools**: Do not paste API keys, tokens, or private credentials into `memsearch` queries or stored memories. Redact before commit-style operations.
-
-3. **Evidence for claims**: Memory hits are **hints**, not proof. For library/API facts, still follow `references/library-docs-protocol.md` (Context7 MCP / ctx7) when the question depends on current docs.
-
-4. **When to call `memsearch`**: Prefer early in a **new** task or thread when user preferences, prior decisions, or plan IDs may exist in OpenViking; after major clarify/plan changes, a fresh search can reduce stale context.
-
-5. **`memread` after `memsearch`**: Use URIs from search results; escalate depth (`overview` → `read`) only when needed to avoid token burn.
-
-6. **`memcommit`**: Use for explicit “persist now” or mid-session extraction when the user asks or when wrapping a milestone. Do **not** spam commits after every trivial edit; the plugin may already run **auto-commit** on an interval—respect that and user policy.
-
-7. **Parallel / multi-agent**: Memory tools do **not** replace PM dispatch, worktree isolation, or QC tri-review invokes. They do not authorize subagent recursion.
-
-## When **not** to rely on this reference
-
-- `memsearch` (and sibling tools) are **absent** → skip this file; no OpenViking rules apply.
-- Non-OpenCode hosts (unless they expose the same tool names with the same semantics) → ignore.
-
-## Configuration (user-owned)
-
-Plugin reads `openviking-config.json` next to the plugin file and env vars such as `OPENVIKING_API_KEY`, `OPENVIKING_ACCOUNT`, `OPENVIKING_USER`. Agents must **not** edit user global config without explicit user consent (see `mstar-harness-core` guardrails).