@mstar-harness/opencode 0.6.6 → 0.6.7

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

@@ -1,6 +1,6 @@
 ---
 name: mstar-host
-description: Morning Star host adapter (OpenCode, Cursor, Codex). Use after mstar-harness-core whenever host entry, clarify, dispatch, or plan UX differs by platform - OpenCode question/@agent-id invoke, Cursor /pm and CreatePlan/SwitchMode dual-write and Task parallel QC, Codex plugin skills plus sandboxed tools/tool discovery. Auto-detect host from session tools; then Read references/<host>.md. Always load after mstar-harness-core.
+description: Morning Star host adapter (OpenCode, Cursor, Codex). Use after mstar-harness-core whenever host entry, clarify, dispatch, or plan UX differs by platform - OpenCode question/@agent-id invoke, Cursor /pm and CreatePlan/SwitchMode dual-write and Task parallel QC, Codex plugin skills plus Plan/Goal Mode, sandboxed tools, and tool discovery. Auto-detect host from session tools; then Read references/<host>.md. Always load after mstar-harness-core.
 ---
 
 # Morning Star Host Adapter
@@ -30,7 +30,7 @@ Use **capability signals** (not filesystem paths):
 | **CreatePlan** / **SwitchMode** available | `cursor` | `references/cursor.md`; Plan mode also `references/cursor-plan-mode-bridge.md` |
 | **`question`** tool or PM **`@<agent-id>`** subagent invoke | `opencode` | `references/opencode.md` |
 | **Task** + `subagent_type`, no CreatePlan | `cursor` | `references/cursor.md` |
-| **Codex app/CLI/plugin context**, `functions.*`, `codex_app.*`, `tool_search`, Browser plugin tools | `codex` | `references/codex.md` |
+| **Codex app/CLI/plugin context**, `/plan`, `/goal`, Goal tools, `functions.*`, `codex_app.*`, `tool_search`, Browser plugin tools | `codex` | `references/codex.md`; Plan/Goal mode also `references/codex-plan-goal-mode-bridge.md` |
 | Still ambiguous | - | Read sections in **`cursor.md`**, **`opencode.md`**, and **`codex.md`** that match tools you have; **`mstar-harness-core` wins** on conflict |
 
 ## Parallel dispatch (invoke-capable hosts)

package/harness-skills/mstar-host/references/codex-plan-goal-mode-bridge.md

@@ -0,0 +1,103 @@
+# Codex Plan / Goal Mode x Harness Bridge
+
+> **Load order**: Read **`mstar-harness-core`** first, then **`mstar-host`** and **`references/codex.md`**. When plan management is required, also read **`mstar-plan-conventions`** and **`mstar-plan-artifacts`** before creating or claiming any durable plan state. On conflict, **`mstar-harness-core`** wins.
+
+## Purpose
+
+Codex **Plan Mode** (`/plan`) and **Goal Mode** (`/goal`) are host collaboration surfaces:
+
+- **Plan Mode** helps shape a plan inside the active Codex conversation.
+- **Goal Mode** attaches a persistent objective and success criteria to the active thread.
+
+Morning Star durable state still lives under **`{HARNESS_DIR}`** (default `.mstar/`, legacy `.agents/`). This reference prevents Codex session plans, UI todos, goal text, or goal completion from replacing the harness SSOT.
+
+## Priority (hard)
+
+1. User explicit instructions (this turn)
+2. Project `AGENTS.md` / `CLAUDE.md`
+3. **`{HARNESS_DIR}` / `{PLAN_DIR}` / `status.json`** (harness SSOT)
+4. Codex Goal Mode objective / progress controls
+5. Codex Plan Mode output, `update_plan`, UI todos, chat summaries
+
+**NEVER** cite only a Codex goal, session plan, UI todo, or chat summary in Assignment **Plan Path**, **Context Loaded**, or Completion Report when `{PLAN_DIR}/<plan-id>-<name>.md` should exist.
+
+## When this applies
+
+- Codex Plan Mode is active (`/plan`, Plan collaboration mode, or host guidance says planning-only).
+- Codex Goal Mode is active (`/goal`, host goal controls, or goal tools such as `create_goal`, `get_goal`, `update_goal`).
+- Morning Star plugin or `/pm` is in use under Codex.
+
+## Codex Plan Mode
+
+Use Plan Mode to clarify, inspect, compare approaches, and draft the harness plan. Do **not** treat Plan Mode output as a durable artifact.
+
+Before implementation or PM dispatch:
+
+1. Discover `{HARNESS_DIR}` / `{PLAN_DIR}` per `mstar-plan-conventions`.
+2. Ensure `{HARNESS_DIR}/status.json` exists or initialize it via `mstar-plan-artifacts` templates.
+3. Register a `plans[]` row in `status.json` when a Morning Star plan is needed.
+4. Write `{PLAN_DIR}/<plan-id>-<name>.md` with task checkboxes, branch policy, verification, and roadmap / deferred scope when applicable.
+5. Use the SSOT plan path in Assignment and Completion Report evidence.
+
+Allowed in Plan Mode: exploration, clarify questions, spec/plan drafting, `.mstar/` initialization, SSOT plan/status edits, PM routing decisions.
+
+Not allowed by default in Plan Mode: product implementation, test implementation, QC execution, QA execution, deployment, or ops changes. Switch to normal execution or dispatch through an actual callable subagent/multi-agent tool first.
+
+## Codex Goal Mode
+
+Goal text is useful as the top-level objective and success criteria, but it is **not** a Morning Star plan, status ledger, PM Assignment, QC report, or QA Done authority.
+
+When starting or receiving a Goal Mode objective:
+
+1. If the goal is implementation-sized or long-running, create or update the harness SSOT (`status.json` + `{PLAN_DIR}` plan) before implementation.
+2. Mirror the goal's success criteria into the SSOT plan as acceptance / verification criteria.
+3. If the goal changes, update both Goal Mode text/progress and the SSOT plan/status in the same coordination round.
+4. If the goal conflicts with the SSOT, pause or report **Blocked** until PM/user resolves scope.
+
+### Goal completion gate
+
+Only mark a Codex goal complete when all applicable harness gates are satisfied:
+
+- Required plan checkboxes are complete in `{PLAN_DIR}`.
+- `status.json` reflects the current lifecycle state.
+- Required commits exist on the authorized branch.
+- Verification evidence is recorded.
+- QC/QA authority has passed when the plan requires InReview / Done gates.
+
+If the host asks to complete a goal but harness Done authority is missing, report **Blocked** and list the missing artifacts or gate decisions. Do not call a goal-completion tool as a substitute for PM/QC/QA evidence.
+
+## Resume / compaction
+
+Codex can resume threads and compact context. On resume, before editing product code:
+
+1. Reload `mstar-harness-core` -> `mstar-host` -> `references/codex.md` -> this bridge.
+2. If Goal Mode is active, read the current goal and compare it with `{HARNESS_DIR}/status.json` and the active SSOT plan.
+3. Treat `.mstar/` as durable truth over chat summaries or UI todos.
+4. If the active role or Assignment is missing, resume as PM for coordination and dispatch only.
+
+## `/pm` under Codex Plan / Goal Mode
+
+When `/pm` runs under Plan or Goal Mode:
+
+- `/pm` is still the force entry into Morning Star PM behavior.
+- Prepare phase (`specify -> clarify -> plan`) still applies unless the task qualifies for a documented hotfix path.
+- Goal Mode can hold the high-level objective, but PM must still write Assignment with `Execute as`, `Delegation`, branch policy, SSOT `Plan Path`, and evidence requirements.
+- Without an actual callable subagent/multi-agent tool, Assignment Markdown is coordination text only; execute serially in-session or report Blocked for rerouting.
+
+## Anti-patterns
+
+| Anti-pattern | Fix |
+|--------------|-----|
+| `/plan` output only, no `{HARNESS_DIR}` files | Write SSOT plan + `status.json` entry before implementation |
+| `update_plan` todo done, no commit/evidence | Commit or record required evidence before completion |
+| Goal objective treated as Done authority | Check harness plan/status/QC/QA gates first |
+| Goal changed but `.mstar/` still has old scope | Update Goal Mode and SSOT in the same round |
+| Resume starts coding from chat summary | Reload harness context and SSOT plan/status first |
+| Assignment Plan Path points at Codex transcript/goal | Use `{PLAN_DIR}/...` path |
+
+## Related skills
+
+- `mstar-plan-conventions` - discover `{HARNESS_DIR}`, `{PLAN_DIR}`, legacy layouts
+- `mstar-plan-artifacts` - `status.json`, plan checkboxes, reports, residuals
+- `mstar-phase-gates` - Prepare / Execute and Done authority
+- `mstar-dispatch-gates` - Assignment, Delegation, anti-recursion

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

@@ -2,6 +2,8 @@
 
 Load when **`mstar-host`** detection resolves **codex** (Codex app/CLI session, Codex plugin installed from `.codex-plugin/plugin.json`, Codex custom agents linked from `codex/agents/*.toml`, or Codex tool namespaces such as `functions.*`, `codex_app.*`, `tool_search`, `image_gen`, or Browser plugin tools).
 
+Plan / Goal Mode: read **`codex-plan-goal-mode-bridge.md`** when Codex Plan Mode (`/plan`) or Goal Mode (`/goal`, goal tools, or goal progress controls) is active. Codex session plans, UI todos, and goal text are not durable harness SSOT.
+
 Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an actual multi-agent / Task-style invocation tool. If no callable invoke tool exists, Assignment Markdown is coordination text only; do **not** claim subagent dispatch.
 
 ## Codex-only context
@@ -17,8 +19,9 @@ Parallel PM dispatch: read **`parallel-dispatch.md`** only when Codex exposes an
 
 1. Read `mstar-harness-core`.
 2. Read `mstar-host` and this Codex reference.
-3. Load `mstar-roles` and the active role reference.
-4. Load topic skills on demand per the role reference.
+3. If Plan Mode or Goal Mode is active, read `codex-plan-goal-mode-bridge.md`.
+4. Load `mstar-roles` and the active role reference.
+5. Load topic skills on demand per the role reference.
 
 Use skill names in prompts and references. Avoid absolute local paths unless the user is maintaining this repository or the skill is not installed and must be read from the checkout.
 
@@ -28,6 +31,7 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 - If a structured user-input tool is available in the active mode, use it for concise 1-3 choice decisions.
 - Otherwise ask one concise Markdown question only after codebase exploration cannot answer it.
 - `update_plan` / local todo UI is session progress only; it does not replace `{PLAN_DIR}` plans or `{HARNESS_DIR}/status.json`.
+- Codex Goal Mode objective is completion criteria for the host thread, not Morning Star Done authority; mirror it into the SSOT plan when the work is implementation-sized.
 
 ## Dispatch and role execution
 
@@ -54,4 +58,4 @@ Use skill names in prompts and references. Avoid absolute local paths unless the
 
 - Codex plugin install gives skills; Morning Star role subagents require custom agent TOML files linked from `codex/agents/`.
 - Tool discovery (`tool_search`) can reveal capabilities, but availability is not authorization; Assignment `Delegation` still controls use.
-- Session plans, chat summaries, and UI todos are not durable harness SSOT unless mirrored to `{HARNESS_DIR}`.
+- Session plans, Goal Mode text, chat summaries, and UI todos are not durable harness SSOT unless mirrored to `{HARNESS_DIR}`.

package/package.json

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