create-harness-vibe-coding 0.8.7 → 0.8.9

package/templates/common/.claude/commands/wf-update.md

@@ -0,0 +1,24 @@
+# /wf-update
+
+Run the Harness update checker script. Do not invoke a skill or start WF mode.
+
+## Flow
+
+1. Run `node Harness/scripts/wf-update-check.mjs --json` and use the `agent` block as the action plan.
+2. Preserve all PRESERVE files. Never overwrite user task, memory, research, README, package, or architecture files.
+3. If `agent.safeApplyCommand` is present, run it to apply SAFE/NEW files first.
+4. For conflicts, compare local with `templateHint` or `remoteUrl`, decide merge/keep-local/overwrite, and record via `--accept-local`, `--accept-merged`, or `--accept-template`.
+5. Run `node Harness/scripts/wf-update-check.mjs --finalize` after all conflicts resolved.
+6. After update, run `node Harness/scripts/validate-harness.mjs` and `node Harness/scripts/scan-clean.mjs`.
+
+Codex users without a direct command surface: use `$wf-update` (skill path) or `node Harness/scripts/wf-update-check.mjs`.
+
+## Recovery
+
+If the script reports `Harness/.harness-version not found` or the update checker script itself is missing (`Harness/scripts/wf-update-check.mjs`), the Harness install predates version-tracking. Recover by regenerating missing infrastructure without overwriting user files:
+
+```
+npx create-harness-vibe-coding@latest <project-name> . -y --on-conflict skip
+```
+
+This creates missing Harness files while preserving CLAUDE.md, README.md, tasks, memory, research, and all user data. After recovery, re-run the update check.

package/templates/common/.claude/rules/ecc/common.md

@@ -1,45 +1,58 @@
----
-description: "Universal harness constraints"
-alwaysApply: true
----
-
-# Universal Rules
-
-## Context
-
-- Start with `CLAUDE.md`, `Harness/MEMORY.md`, and `Harness/README.md`.
-- Do not bulk-read `Harness/`. Load by router trigger.
-- Keep `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` current when work has multiple steps, files, or agents.
-- project files are the only durable communication channel. chat/subagent transcript state is non-authoritative.
-- Important assumptions, decisions, blockers, evidence, and handoffs must be written to `Harness/tasks/<task-id>/PROGRESS.md`, `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, `Harness/MEMORY.md`, or `Harness/memory/*` as appropriate.
-
-## Verification
-
-- Define acceptance criteria before implementation.
-- New behavior: failing test first, or a written manual check if automation is not feasible yet.
-- Bug fix: reproduction first.
-- Before release, add CI for the chosen stack and run the full verification path.
-
-## Subagents
-
-- Use `Harness/subagents.md` before orchestrating multiple agents.
-- Use `Harness/context-loading.md` before spawning.
-- Use `Harness/dispatch.md` before parallel or multi-agent work.
+---
+description: "Universal harness constraints"
+alwaysApply: true
+---
+
+# Universal Rules
+
+## Context
+
+- Start with `CLAUDE.md`. When `Harness/` exists, also read `Harness/memory/startup-hints.md` (L2 lightweight digest, not full router).
+- When the user explicitly invokes a `/wf-*` command, load `Harness/MEMORY.md` and `Harness/README.md`.
+- For simple single-step tasks without `/wf-*`, operate in direct mode: skip the Harness router and execute directly.
+- Do not bulk-read `Harness/`. Load by router trigger.
+- Keep `Harness/tasks/<task-id>/PROGRESS.md` and `Harness/tasks/<task-id>/PLAN.md` current when work has multiple steps, files, or agents.
+- project files are the only durable communication channel. chat/subagent transcript state is non-authoritative.
+- Important assumptions, decisions, blockers, evidence, and handoffs must be written to `Harness/tasks/<task-id>/PROGRESS.md`, `Harness/tasks/<task-id>/PLAN.md`, the current feature doc, `Harness/MEMORY.md`, or `Harness/memory/*` as appropriate.
+
+## Verification
+
+- Define acceptance criteria before implementation.
+- New behavior: failing test first, or a written manual check if automation is not feasible yet.
+- Bug fix: reproduction first.
+- Before release, add CI for the chosen stack and run the full verification path.
+
+## Low-Noise Progress
+
+- Keep intermediate user updates to 1-2 short sentences.
+- Do not recap plans, paste logs, or narrate obvious file reads while working.
+- Put the detailed summary in the final response: files changed, verification, risks, and commit hash when relevant.
+- During long-running work, report only phase changes, blockers, failed commands, or user decisions needed.
+
+## Subagents
+
+- Use `Harness/subagents.md` before orchestrating multiple agents.
+- Use `Harness/context-loading.md` before spawning.
+- Use `Harness/dispatch.md` before parallel or multi-agent work.
 - Use `Harness/extension.md` before adding stack-specific agents, skills, or rules.
-- Every subagent needs role, task, read boundary, write boundary, and return format.
-- Writing agents must run serially unless write sets are disjoint.
-- If the runtime cannot spawn subagents, emulate the same role pack in a separate bounded pass.
-- Main agent owns integration and final verification.
-
-## Memory
-
-- Record a lightweight reflection in `Harness/memory/tool-usage-reflections.md` when the same tool/use pattern fails 3+ times.
-- Record repeated user corrections or durable preferences in `Harness/memory/user-corrections-preferences.md` when the user corrects the same assumption/pattern 2+ times.
-- Record reusable review/debug lessons in `Harness/memory/agent-lessons-patterns.md`.
-- Keep memory entries concise and never include secrets.
-
-## Security
-
-- No secrets in source code.
-- Validate external input at system boundaries.
-- High-risk actions need explicit user approval or documented permission policy.
+- Every subagent needs role, task, read boundary, write boundary, and return format.
+- Writing agents must run serially unless write sets are disjoint.
+- If the runtime cannot spawn subagents, emulate the same role pack in a separate bounded pass.
+- Main agent owns integration and final verification.
+
+## Memory
+
+- Detect memory candidates when user says: `remember`, `next time`, `don't`, `do not`, `never`, `always`, `I prefer`, `I want you to`, `记住`, `下次`, `以后`, `不要再`, `总是`, `永远不要`, `我偏好`, `我希望你以后`.
+- Explicit user preference that is clear, safe, and scoped can be written to L3 immediately without waiting for `/wf-learn`.
+- Use `Harness/memory/routes.md` for deterministic route matching before loading detailed L3 memory.
+- Record a lightweight reflection in `Harness/memory/tool-usage-reflections.md` when the same tool/use pattern fails 3+ times.
+- Record repeated user corrections or durable preferences in `Harness/memory/user-corrections-preferences.md` when the user corrects the same assumption/pattern 2+ times.
+- Record reusable review/debug lessons in `Harness/memory/agent-lessons-patterns.md`.
+- Never record task logs, process summaries, one-time emotions, transient notes, raw logs, or secrets.
+- Keep memory entries compact and default to no date; only add date/timestamp for superseded, conflicting, or time-sensitive entries.
+
+## Security
+
+- No secrets in source code.
+- Validate external input at system boundaries.
+- High-risk actions need explicit user approval or documented permission policy.

package/templates/common/.claude/settings.json

@@ -29,5 +29,18 @@
       "Read(**/*.key)",
       "Read(**/*.pem)"
     ]
+  },
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node -e \"const fs=require('fs'),p=require('path'),cp=require('child_process');let d=process.env.CLAUDE_PROJECT_DIR||process.cwd();for(;;){const s=p.join(d,'Harness','scripts','wf-auto-update-prompt.mjs');if(fs.existsSync(s)){const r=cp.spawnSync(process.execPath,[s,'--format','claude'],{stdio:'inherit',cwd:d,env:process.env});process.exitCode=(r.status==null)?0:r.status;break}const u=p.dirname(d);if(u===d)break;d=u}\""
+          }
+        ]
+      }
+    ]
   }
 }

package/templates/common/.claude/skills/subagent-orchestrator/SKILL.md

@@ -8,6 +8,12 @@ description: Use when work needs bounded subagent coordination, parallel read-on
 This skill is runtime-neutral. Claude Code and Codex expose different
 subagent surfaces; follow the same Harness role contract either way.
 
+## Memory Preflight
+
+1. Direct simple tasks and `/wf-help` are exempt.
+2. For non-direct work, load `CLAUDE.md`, `Harness/MEMORY.md` index only, then `Harness/README.md` before planning, dispatch, edits/deletes, validation, or peer review.
+3. Load `Harness/memory/*` only when `MEMORY_PROTOCOL.md` scenario hints match; otherwise record "memory hints: none".
+
 ## Load
 
 - `Harness/subagents.md`
@@ -16,7 +22,7 @@ subagent surfaces; follow the same Harness role contract either way.
 - `Harness/agent-workflow.md`
 - `Harness/PROGRESS.md`
 - Active `Harness/tasks/<task-id>/PROGRESS.md` and `PLAN.md`, when present
-- `Harness/WF.md` when in `/wf`, `wf mode`, `workflow mode`, or `wk mode`
+- `Harness/WF.md` when in explicit `/wf`, `$wf`, or `/skills wf`
 
 ## Runtime Mapping
 
@@ -36,9 +42,7 @@ subagent surfaces; follow the same Harness role contract either way.
   integrates returns, and owns final verification.
 - Subagents or bounded passes are readers and reporters unless a write set is
   explicitly assigned and disjoint.
-- Explicit WF/WK mode requires complete role-chain coverage from intake through
-  final acceptance: plan, research/docs research as needed, architecture, test,
-  implement, independent validation, cross-review, reflector, and accept.
+- Explicit WF/WF-MAX requires tier-specific role coverage per `Harness/WF.md`.
 - Every dispatch needs role, goal, mode, read set, write set, forbidden scope,
   injected docs, dependencies, evidence, stop condition, and return format.
 - Prefer parallel read-only exploration first. Serialize writers unless write

package/templates/common/.claude/skills/wf/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wf
-description: Use for /wf in Claude Code, $wf or /skills wf in Codex, or any long, uncertain, multi-file, migration, recovery, or architecture-heavy task that should follow Harness WF mode.
+description: Use for /wf in Claude Code, $wf or /skills wf in Codex. WF is explicit only — the user must type /wf, $wf, or /skills wf to enter.
 ---
 
 # WF Mode Adapter
@@ -15,10 +15,16 @@ This skill is a thin tool adapter. The authoritative workflow lives in
 - Codex app may also list enabled skills in the `/` menu, depending on the
   current surface and feature state.
 
+## Memory Preflight
+
+1. Direct simple tasks and `/wf-help` are exempt.
+2. For non-direct work, load `CLAUDE.md`, `Harness/MEMORY.md` index only, then `Harness/README.md` before planning, dispatch, edits/deletes, validation, or peer review.
+3. Load `Harness/memory/*` only when `MEMORY_PROTOCOL.md` scenario hints match; otherwise record "memory hints: none".
+
 ## Load
 
 1. `CLAUDE.md`
-2. `Harness/MEMORY.md`
+2. `Harness/MEMORY.md` (index only per Memory Preflight)
 3. `Harness/README.md`
 4. `Harness/PROGRESS.md`
 5. `Harness/WF.md`
@@ -27,14 +33,15 @@ This skill is a thin tool adapter. The authoritative workflow lives in
 ## Rules
 
 - Create or update a task capsule under `Harness/tasks/<task-id>/`.
+- Select the right WF tier: WF-Light (low-risk, planner/test/verifier), WF-Standard (multi-file, compact ACs, one review lens), WF-Full (high-risk/cross-layer, full role chain).
 - Run the WF loop from `Harness/WF.md`: intake, bounded exploration, second
   plan, implementation, review, verification, recovery, and closeout.
-- For explicit WF invocation, schedule the complete role chain at intake:
+- **Tier-aware acceptance**:
+  - **WF-Light**: planner + test-writer + implementer + verifier suffice. Verification passes = closeout. Cross-review and reflector are NOT mandatory unless risk triggers them.
+  - **WF-Standard**: one independent review lens required. Reflector may be triggered by risk.
+  - **WF-Full**: cross-review + reflector PASS required before final acceptance.
+- WF-Full requires the complete role chain at intake:
   plan, research/docs research as needed, architecture, test, implement,
-  independent validation, cross-review, reflector, and final acceptance. Use
-  real subagents when the runtime supports them; otherwise record bounded-pass
-  fallback coverage in the task plan.
-- Do not mark accepted until cross-review passes and the reflector returns
-  PASS.
+  independent validation, cross-review, reflector, and final acceptance.
 - Keep `Harness/tasks/<task-id>/PROGRESS.md#Heartbeat` current before long
   commands, after failures, and at closeout.

package/templates/common/.claude/skills/wf-auto/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wf-auto
-description: Perpetual auto-optimization mode. Never stops until 8-angle exhaustion. Inherits WF acceptance gates and subagent orchestration per cycle. Use for Claude /wf-auto, Codex $wf-auto, auto mode, or unbounded self-directed optimization.
+description: Perpetual adaptive auto-optimization mode. Selects probes from project evidence instead of a fixed angle count. Inherits WF acceptance gates and subagent orchestration per cycle. Use for Claude /wf-auto, Codex $wf-auto. Explicit only — the user must type /wf-auto, $wf-auto, or /skills wf-auto.
 ---
 
 # WF Auto - Perpetual Auto-Optimization
@@ -8,6 +8,7 @@ description: Perpetual auto-optimization mode. Never stops until 8-angle exhaust
 ## Load
 
 - `Harness/WF-AUTO.md`
+- `Harness/WF-AUTO-ANGLES.md`
 - `Harness/subagents.md`
 - `Harness/dispatch.md`
 - `Harness/agent-workflow.md`
@@ -17,7 +18,8 @@ description: Perpetual auto-optimization mode. Never stops until 8-angle exhaust
 
 - Claude `/wf-auto`
 - Codex `$wf-auto`
-- `wf auto`, `auto mode`, or a request for continuous self-directed improvement
+
+Do not use unless the user explicitly invokes `/wf-auto`, `$wf-auto`, or `/skills wf-auto`. The phrases "auto mode", "never stop", "self-improve", "continuous optimize", "unbounded self-directed optimization" are NOT triggers — only an explicit command token enters WF-AUTO.
 
 Do not use when the user gives a bounded task, requests maximum parallelism
 (`/wf-max`), needs an urgent production hotfix, or the codebase is tiny enough
@@ -25,12 +27,13 @@ that auto scanning costs more than it helps.
 
 ## Hard Rules
 
-1. Never stop except the A-GATE: all 8 angles empty, oracle empty, spark empty,
-   and 2 confirmation rounds.
+1. Never stop except the Adaptive Coverage A-GATE: dynamic high-risk
+   obligations are covered, two different confirmation strategies are empty,
+   and unresolved uncertainty is recorded.
 2. CEO never edits production source. CEO may write only
    `Harness/tasks/auto/PLAN.md` and `Harness/tasks/auto/PROGRESS.md`.
-3. Dispatch all W0 sources in one batch when the runtime allows it: 8 angles,
-   oracle, and spark searchers.
+3. Build a project profile each W0 cycle and dispatch only the selected probes;
+   invoke oracle and spark searchers when evidence justifies them.
 4. One accepted finding per cycle: <=3 files and <=50 changed lines. Larger
    ideas escalate to `/wf` or `/wf-max`, then return to auto.
 5. Every accepted cycle inherits the full WF chain:
@@ -45,7 +48,7 @@ that auto scanning costs more than it helps.
 ## Loop
 
 ```text
-W0: SENSE (8 angles + oracle + spark sources)
+W0: SENSE (adaptive probes + oracle + spark sources as triggered)
 A-GATE: continue, oracle, spark, confirm, or stop
 W1: PRIORITIZE one finding
 W2-W5: Mini PRD -> AC -> test/validation plan -> implementer -> verifier -> cross-review -> reflector PASS

package/templates/common/.claude/skills/wf-learn/SKILL.md

@@ -10,9 +10,13 @@ consolidates. Use the active runtime's available subagent mechanism when
 present, otherwise emulate the same roles as bounded passes and record that
 fallback.
 
+**Note:** Explicit user preferences (remember/next time/never/always/记住/下次/不要再) can be written immediately via candidate detection without waiting for `/wf-learn`. `/wf-learn` is for proactive pattern consolidation and closeout extraction.
+
 ## Load
 
 - `Harness/MEMORY.md`
+- `Harness/memory/routes.md`
+- `Harness/memory/startup-hints.md`
 - `Harness/memory/tool-usage-reflections.md`
 - `Harness/memory/user-corrections-preferences.md`
 - `Harness/memory/agent-lessons-patterns.md`
@@ -22,8 +26,11 @@ fallback.
 
 1. Analyze the session for repeated failures, durable user corrections, and
    reusable review/debug lessons.
-2. Deduplicate against existing memory.
-3. Write only concise, durable, non-secret lessons to `Harness/memory/*`.
+2. Check `Harness/memory/routes.md` for existing entries before writing.
+3. Deduplicate against existing memory.
+4. Write only concise, durable, non-secret lessons to `Harness/memory/*`.
+   Use compact format (default no date):
+   `- When <scenario>: <rule>. Avoid <over-application>. Signals: <signals>.`
 
 ## Return
 

package/templates/common/.claude/skills/wf-max/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wf-max
-description: Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex, or maximum-parallelism Harness work with WF strict-superset gates and CEO -> manager -> worker decomposition.
+description: Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex. WF-MAX is explicit only — the user must type /wf-max, $wf-max, or /skills wf-max.
 ---
 
 # WF-MAX Adapter
@@ -13,10 +13,16 @@ routes and summarizes hard constraints.
 - Claude Code: `/wf-max [task]`
 - Codex: `$wf-max` or `/skills` then choose `wf-max`
 
+## Memory Preflight
+
+1. Direct simple tasks and `/wf-help` are exempt.
+2. For non-direct work, load `CLAUDE.md`, `Harness/MEMORY.md` index only, then `Harness/README.md` before planning, dispatch, edits/deletes, validation, or peer review.
+3. Load `Harness/memory/*` only when `MEMORY_PROTOCOL.md` scenario hints match; otherwise record "memory hints: none".
+
 ## Load
 
 1. `CLAUDE.md`
-2. `Harness/MEMORY.md`
+2. `Harness/MEMORY.md` (index only per Memory Preflight)
 3. `Harness/README.md`
 4. `Harness/WF-MAX.md`
 5. `Harness/subagents.md`
@@ -25,20 +31,32 @@ routes and summarizes hard constraints.
 
 ## Rules
 
-WF-MAX is a WF strict superset: every WF role, gate, and acceptance rule still
-applies, then execution expands through:
+WF-MAX inherits the selected WF tier and the shared WF-KERNEL gates
+(`Harness/WF-KERNEL.md`), then expands safe parallelism. WF-Max-Useful is
+default; WF-Max-Strict only on explicit strict request. Execution expands
+through:
 
 1. Global mode: `wf-max`
 2. Agent role: `ceo | manager | worker | reviewer | verifier | reflector`
 3. Dispatch permission: `writeSet`, `forbidden`, `verification`
 
+WF-Max-Useful (default): `/wf-max` fans out only where write sets or review
+lenses are meaningfully independent. Overhead > 0.30 degrades the wave.
+
+WF-Max-Strict (explicit override): user says `--strict`, `strict wf-max`, or
+`strict mode`. Unconditional fan-out per the original span formula.
+
 - CEO reads, plans, dispatches, synthesizes, and writes task state only. CEO
   never edits production source.
 - Workers edit only the dispatch `writeSet`; outside write set is blocked.
 - Managers coordinate and synthesize. Reviewers read/report only.
 - D-GATE is mandatory before implementation waves: dispatch table, AC IDs,
   disjoint file claims, self-audit, and reviewer plan.
-- Final acceptance requires verifier evidence, cross-review, and reflector PASS.
+- Final acceptance is tier-aware per `Harness/WF-KERNEL.md`:
+  - WF-Light + `/wf-max`: verification + state evidence suffices unless risk
+    triggers review/reflector.
+  - WF-Standard + `/wf-max`: verifier evidence + one independent review PASS.
+  - WF-Full or risk-triggered `/wf-max`: cross-review PASS + reflector PASS.
 
 ## Fan-Out Discipline
 

package/templates/common/.claude/skills/wf-readme/SKILL.md

@@ -1,49 +1,49 @@
----
-name: wf-readme
-description: Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.
----
-
-# README Optimizer
-
-Improve `README.md` without breaking project-owned public docs.
-
-## Load
-
-- root `README.md`
-- package files and scripts (`package.json`, `pyproject.toml`, `go.mod`, etc.)
-- CI files when present
-- `Harness/PROGRESS.md`
-- `Harness/tasks/<task-id>/PLAN.md` when available
-- `Harness/architecture.md` only when an architecture summary or diagram is requested
-
-## Mode
-
-Ask the user which mode they approve when the existing README is meaningful:
-
-| Mode | Use when | Allowed edit |
-| --- | --- | --- |
-| Preserve + append | default for existing projects | Add only a compact Development, Test, Build, Git, or Harness section |
-| Structure pass | README is stale, hard to scan, or missing operational docs | Reorganize with headings, tables, command blocks, and links while preserving facts |
-| Full rewrite | user explicitly wants a polished public README | Rewrite after approval; keep claims source-backed |
-
-If unanswered, use Preserve + append.
-
-## Rules
-
-- Preserve existing product, package, API, and public-facing content unless the user approves a rewrite.
-- Do not invent features, benchmarks, roadmap, support policy, badges, install commands, or CI status.
-- Use tables for command matrices, environment variables, endpoints, and deployment notes when facts are known.
-- Use Mermaid or ASCII architecture diagrams only when the structure is observed or approved; label uncertain diagrams as proposed.
-- Keep detailed architecture in `Harness/architecture.md`; README may link to it or show a short overview.
-- Keep agent rules in `CLAUDE.md`/`AGENTS.md`, not README.
-- Record the chosen mode and any skipped README improvements in `Harness/tasks/<task-id>/PLAN.md` when available.
-
-## Output
-
-Before broad edits, return:
-
-1. chosen mode
-2. sections to preserve
-3. sections to add or reorganize
-4. facts still unknown
-5. verification command or manual review step
+---
+name: wf-readme
+description: Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.
+---
+
+# README Optimizer
+
+Improve `README.md` without breaking project-owned public docs.
+
+## Load
+
+- root `README.md`
+- package files and scripts (`package.json`, `pyproject.toml`, `go.mod`, etc.)
+- CI files when present
+- `Harness/PROGRESS.md`
+- `Harness/tasks/<task-id>/PLAN.md` when available
+- `Harness/architecture.md` only when an architecture summary or diagram is requested
+
+## Mode
+
+Ask the user which mode they approve when the existing README is meaningful:
+
+| Mode | Use when | Allowed edit |
+| --- | --- | --- |
+| Preserve + append | default for existing projects | Add only a compact Development, Test, Build, Git, or Harness section |
+| Structure pass | README is stale, hard to scan, or missing operational docs | Reorganize with headings, tables, command blocks, and links while preserving facts |
+| Full rewrite | user explicitly wants a polished public README | Rewrite after approval; keep claims source-backed |
+
+If unanswered, use Preserve + append.
+
+## Rules
+
+- Preserve existing product, package, API, and public-facing content unless the user approves a rewrite.
+- Do not invent features, benchmarks, roadmap, support policy, badges, install commands, or CI status.
+- Use tables for command matrices, environment variables, endpoints, and deployment notes when facts are known.
+- Use Mermaid or ASCII architecture diagrams only when the structure is observed or approved; label uncertain diagrams as proposed.
+- Keep detailed architecture in `Harness/architecture.md`; README may link to it or show a short overview.
+- Keep agent rules in `CLAUDE.md`/`AGENTS.md`, not README.
+- Record the chosen mode and any skipped README improvements in `Harness/tasks/<task-id>/PLAN.md` when available.
+
+## Output
+
+Before broad edits, return:
+
+1. chosen mode
+2. sections to preserve
+3. sections to add or reorganize
+4. facts still unknown
+5. verification command or manual review step

package/templates/common/.claude/skills/wf-remove/SKILL.md

@@ -1,10 +1,10 @@
----
-name: wf-remove
-description: Use for /wf-remove in Claude Code, $wf-remove or /skills wf-remove in Codex, or any request to uninstall Harness safely.
----
-
-# WF Remove Adapter
-
+---
+name: wf-remove
+description: Use for /wf-remove in Claude Code, $wf-remove or /skills wf-remove in Codex, or any request to uninstall Harness safely.
+---
+
+# WF Remove Adapter
+
 ## Invocation
 
 - Claude Code: use `/wf-remove` or select the `wf-remove` skill.

package/templates/common/.claude/skills/wf-update/SKILL.md

@@ -1,14 +1,17 @@
 ---
 name: wf-update
-description: Use for /wf-update in Claude Code, $wf-update or /skills wf-update in Codex, or any request to check for or apply Harness scaffold updates.
+description: Codex compatibility: use $wf-update or /skills wf-update in Codex. In Claude Code and OpenCode, /wf-update is a direct command (see .claude/commands/wf-update.md and .opencode/commands/wf-update.md).
 ---
 
 # WF Update Adapter
 
+This skill is a Codex compatibility shim plus script-flow reference. Claude Code and OpenCode handle `/wf-update` as a direct command; do not route them through this skill.
+
 ## Invocation
 
-- Claude Code: use `/wf-update` or select the `wf-update` skill.
 - Codex CLI or IDE: use `$wf-update` or `/skills` then choose `wf-update`.
+- Claude Code: `/wf-update` is a direct command. Use `.claude/commands/wf-update.md`, not this skill.
+- OpenCode: `/wf-update` is a direct command. Use `.opencode/commands/wf-update.md`, not this skill.
 
 ## Load
 
@@ -37,6 +40,16 @@ description: Use for /wf-update in Claude Code, $wf-update or /skills wf-update
    JSON plan has zero conflicts.
 6. After update, run the validator and then scan-clean.
 
+## Recovery
+
+If `Harness/scripts/wf-update-check.mjs` is missing (old install without updater), or `Harness/.harness-version` is missing or corrupted, do NOT reinstall from scratch. Recover by regenerating missing infrastructure:
+
+```
+npx create-harness-vibe-coding@latest <project-name> . -y --on-conflict skip
+```
+
+The `--on-conflict skip` policy preserves all existing user files (CLAUDE.md, README.md, tasks, memory, research, architecture) and only creates missing Harness infrastructure files. After recovery, re-run the update check.
+
 ## Return
 
 Report version, SAFE/NEW updates, conflicts and decisions, preserved files,

package/templates/common/.codex/hooks.json

@@ -0,0 +1,17 @@
+{
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$(git rev-parse --show-toplevel)/Harness/scripts/wf-auto-update-prompt.mjs\" --format codex",
+            "commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -Command \"$root=(git rev-parse --show-toplevel 2>$null); if (-not $root) { $root=(Get-Location).Path }; node (Join-Path $root 'Harness/scripts/wf-auto-update-prompt.mjs') --format codex\"",
+            "statusMessage": "Checking Harness updates",
+            "timeout": 35
+          }
+        ]
+      }
+    ]
+  }
+}