create-harness-vibe-coding 0.8.19 → 0.9.3

package/templates/common/.claude/agents/review-manager.md

@@ -1,47 +1,50 @@
 ---
 harness: wf-agent
 name: review-manager
-description: WF-MAX Manager for W2R review wave. Spawns 3-4 parallel reviewers (spec/code/security/perf), deduplicates findings, assigns severity, reports to CEO. Read-only + Agent spawn; no Edit/Write.
-tools: Read, Grep, Glob, Agent, Bash(git *), Bash(git diff *), Bash(node *)
+description: Optional native WF-REVIEW manager. Selects a bounded reviewer fan-out by risk, deduplicates evidence, assigns severity, and reports to the controller. Read-only + native Agent spawn; no Edit/Write or external CLI.
+tools: Read, Grep, Glob, Agent, Bash(git *), Bash(git diff *)
 model: sonnet
 ---
 
-# Review Manager — W2R Review Wave
+# Review Manager - Native WF-REVIEW Fan-Out
 
-You are a Review Manager in the WF-MAX hierarchy. You report to the CEO.
+You are an optional Review Manager in the Harness review workflow. You report
+only to the controller.
 
 ## Role
 
-Multi-dimension review → parallel dispatch of 3-4 reviewers → deduplicate → severity classification → report to CEO for fix assignment.
+Select the smallest useful native reviewer fan-out, collect independent evidence,
+deduplicate findings, classify severity, and report a prioritized fix list.
 
 ## What You Do
 
-1. Receive implementation wave output from CEO
-2. Spawn 3-4 parallel reviewers, each with a distinct dimension:
-   - **reviewer-spec**: does the change match the spec/PRD/acceptance criteria? Extra features = failures.
-   - **reviewer-code**: correctness, maintainability, naming, duplication, architecture compliance
-   - **reviewer-security**: injection, auth, data exposure, input validation, dependency risks
-   - **reviewer-perf** (optional, 4th): algorithmic complexity, N+1 queries, memory, bundle size
-3. ALL spawned in ONE message
-4. Collect findings, deduplicate across dimensions
-5. Assign severity: **critical** (security/data-loss) | **high** (bug/regression) | **medium** (maintainability) | **low** (style/nit)
-6. Report to CEO with prioritized fix list
-
-## What You NEVER Do
+1. Receive the controller's fixed review point, evidence packet, and focus.
+2. Select the smallest useful native fan-out from the requested focus and risk:
+   - 1 reviewer for low-risk or narrow changes
+   - 2 independent lenses for ordinary multi-file changes
+   - 3 lenses for broad changes; add performance only when materially in scope
+   - 4 is the hard maximum and is reserved for broad security-sensitive changes
+3. Spawn the selected reviewers in one native Agent message when fan-out is needed.
+   Use distinct dimensions such as:
+   - **reviewer-spec**: match to the spec, plan, and acceptance criteria
+   - **reviewer-code**: correctness, maintainability, naming, duplication, architecture
+   - **reviewer-security**: injection, auth, data exposure, validation, dependencies
+   - **reviewer-perf** (optional): complexity, memory, query behavior, bundle size
+4. Apply the controller's deadline. A missing or timed-out result is `TIMEOUT`,
+   never an implicit pass.
+5. Collect findings, deduplicate them, and assign severity:
+   **critical** (security/data-loss) | **high** (bug/regression) |
+   **medium** (maintainability/test gap) | **low** (style/nit).
+6. Report the evidence packet to the controller; the controller decides whether
+   to fix, defer, reject, or escalate each finding.
+
+## What You Never Do
 
 - Fix issues yourself (you are a reviewer, not a fixer)
-- Skip dimensions (if only 3, spec + code + security are mandatory)
-- Write to task files
-- Approve or reject — classify and report, CEO decides
-
-## Severity Classification
-
-| Severity | Criteria | Action |
-|----------|----------|--------|
-| Critical | Security vulnerability, data loss, crash | CEO must fix before merge |
-| High | Bug, regression, spec violation | CEO should fix before merge |
-| Medium | Maintainability, duplication, test gap | CEO may defer with justification |
-| Low | Style, naming, nit | Optional |
+- Write to task files or source files
+- Invoke `claude -p`, `codex exec`, `opencode run`, or any other external CLI
+- Ask a reviewer to spawn another reviewer or invoke `/wf-review`
+- Treat empty, malformed, or timed-out reviewer output as PASS
 
 ## Synthesis Format
 
@@ -51,6 +54,7 @@ Critical findings (must fix):
 High findings (should fix):
 Medium findings (may defer):
 Low findings (optional):
+Timeouts or unavailable lenses:
 Deduplication notes (same finding from multiple reviewers):
 Overall verdict: PASS / PASS_WITH_CONCERNS / FAIL
 Recommended next:

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

@@ -1,5 +1,5 @@
 ---
-description: Run AI-driven browser automation and E2E testing via the wf-browser skill
+description: Run agent-operable browser architecture design and runtime control via the wf-browser skill
 ---
 
 # /wf-browser

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

@@ -13,9 +13,9 @@ which returns this same table without loading `Harness/MEMORY.md` or entering WF
 | `/wf-max <task>` | workflow skill | `/wf-max refactor auth module` | WF-Max-Useful default (fan-out only where independent), WF-Max-Strict override (unconditional fan-out). |
 | `/wf-auto` | workflow skill | `/wf-auto` | Perpetual adaptive auto-optimization using project evidence, dynamic probes, risk obligations, evidence ledger, and confirmation-based exhaustion. |
 | `/wf-auto-spark` | workflow skill | `/wf-auto-spark` | Perpetual inspiration mode with roadmap anchoring and external spark search. |
-| `/wf-review <focus>` | workflow skill | `/wf-review security and test coverage` | Peer CLI review through Claude/Codex/OpenCode, with reviewer subagent fallback. |
-| `/wf-learn` | workflow skill | `/wf-learn` | Force context-master -> memory-master learning cycle after repeated failures or closeout. |
-| `/wf-browser <task>` | workflow skill | `/wf-browser verify checkout flow` | Built-in browser automation/E2E workflow with real UI interaction, screenshots, traces, and CDP/network evidence. |
+| `/wf-review <focus>` | workflow skill | `/wf-review security and test coverage` | Native Harness reviewer subagents with bounded, evidence-backed fan-out. |
+| `/wf-learn` | workflow skill | `/wf-learn` | Extract generalized methods with anti-overfitting and route-load checks after verified failures or closeout. |
+| `/wf-browser <task>` | workflow skill | `/wf-browser verify checkout flow` | Agent-operable browser architecture and runtime-control workflow with WebSocket bridge, UI capability contract, virtual cursor, artifacts, multi-window leases, and Playwright/CDP fallback. |
 | `/wf-readme <task>` | workflow skill | `/wf-readme polish quickstart` | Preserve, merge, or improve README docs without trampling existing project documentation. |
 | `/wf-update` | direct command | `/wf-update` | Check/apply Harness scaffold updates with safe file classification and conflict handling. |
 | `/wf-remove` | workflow skill | `/wf-remove` | Safely remove Harness files while preserving project/user data unless explicitly purged. |
@@ -24,6 +24,8 @@ which returns this same table without loading `Harness/MEMORY.md` or entering WF
 | `/wf-task-archive [--apply]` | direct command | `/wf-task-archive --apply` | Archive completed task capsules (dry-run by default). |
 | `/wf-command-create <wf-command-id>` | direct command | `/wf-command-create wf-report --direct` | Create or modify wf-* command surfaces atomically from the command registry. |
 | `/wf-ui` | direct command | `/wf-ui` | Start the local Harness backend and browser control panel. |
+| `/wf-init` | direct command | `/wf-init` | Initialize this project against the global Harness runtime (thin bridge; global version is authoritative). |
+| `/wf-search` | direct command | `/wf-search <question>` | Evidence-backed search protocol with stateless validate/render helper; optional --save/--task by controller. |
 
 Source of truth: `Harness/README.md#Skill Commands` plus installed skills under
 `.claude/skills/` (Claude Code and OpenCode adapters) or `.agents/skills/`

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

@@ -0,0 +1,44 @@
+---
+description: Initialize this project with the Harness runtime — global bridge by default (`--scope global`), or classic full project-level install (`--scope project`)
+---
+
+# /wf-init
+
+Initialize the current project with the Harness runtime. This is a direct command.
+Do not invoke a skill, do not start WF mode, and do not dispatch agents.
+
+Run from the project root:
+
+```bash
+create-harness-vibe-coding init .
+```
+
+If you are inside the generator source repository and the global binary is not
+available, use the local source entry:
+
+```bash
+node bin/create-harness-vibe-coding.js init .
+```
+
+Otherwise use the package fallback:
+
+```bash
+npx create-harness-vibe-coding@0.8.21 init .
+```
+
+Install scopes:
+
+- `--scope global` (default) — thin bridge: the project keeps only bridge docs (CLAUDE.md, AGENTS.md, Harness README/MEMORY/SETUP) plus its own state (`Harness/tasks/`, memory, `PROGRESS.md`, settings). Framework files, commands, skills, agents, and scripts load once from the machine-level global runtime, which is the single version source of truth.
+- `--scope project` — classic full project-level install: the whole framework is copied into the project so it stays self-contained; update per project with `/wf-update`.
+
+Useful flags:
+
+- `--dry-run` — print the plan without writing.
+- `--on-conflict <policy>` — `fail`, `skip` (default), `backup`, or `overwrite`. Keep `skip` so user-authored files are never clobbered.
+- `--global-dir <dir>` / `--host-global-dir <dir>` — override the global runtime and host-copy locations (global scope only).
+
+Rules:
+
+- Never overwrite user-authored files; the default conflict policy is `skip`.
+- If Harness already exists in the project, report the update path and stop — do not re-init.
+- Return the printed install scope, the global runtime path (global scope), and the next-step hints (`/wf-ui`, `/wf <task>`).

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

@@ -1,16 +1,42 @@
 ---
-description: Run the context-master -> memory-master learning cycle via the wf-learn skill
+description: Run the explicit evidence-to-method wf-learn cycle with an anti-overfitting gate
 ---
 
 # /wf-learn
 
-This is a **workflow command**, not a direct command. Do not execute it as a
-static help or script command.
+This is a workflow command, not a direct command. It runs only when the user
+explicitly invokes /wf-learn, $wf-learn, or /skills wf-learn. Editing this
+command or discussing a learning rule is not an invocation and must not write
+memory.
 
-1. Load `CLAUDE.md`, `Harness/MEMORY.md` (index only per Memory Preflight), then `Harness/README.md`.
-2. Preserve cache-first order per `Harness/specs/runtime/context-loading.md#Cache-First Context Contract`.
-3. Execute per the skill adapter `.claude/skills/wf-learn/SKILL.md` (mirror: `.agents/skills/wf-learn/SKILL.md`).
-4. Do not duplicate the workflow here. The skill adapter and `Harness/specs/protocols/MEMORY_PROTOCOL.md` are authoritative.
+## Command Contract
+
+1. Load CLAUDE.md, the Harness/MEMORY.md index, Harness/README.md, and the
+   active task context when one exists.
+2. Preserve the cache-first order in
+   Harness/specs/runtime/context-loading.md#Cache-First Context Contract.
+3. Read and follow the wf-learn skill adapter. It is the authoritative
+   implementation for routing, generalization, deduplication, and memory writes.
+4. Build a compact environment profile from capabilities, not machine-specific
+   literals: runtime family, OS family, shell family, project layout, and
+   available agent runtimes.
+5. Start with a scoped, de-duplicating query:
+   `node Harness/scripts/memory-context.mjs query --project <absolutePath> --text <topic> --scope project --json`.
+   Validate candidates with `memory-context.mjs validate --input <candidate.json>`;
+   apply only validated evidence with `memory-context.mjs apply --project <absolutePath>
+   --input <candidate.json> --apply`; record task-local outcomes with
+   `memory-context.mjs feedback --project <absolutePath> --task <task-id> --entry <id>
+   --outcome useful|unused|incorrect --reason <text> --apply`.
+6. Apply the Generalization Gate before any memory write. Instance facts such
+   as a port number, device label, absolute path, timestamp, or one-run ID stay
+   in task evidence. Durable memory receives the method and its validation
+   criteria only.
+7. Return load proof, candidates written, facts kept task-local, candidates
+   skipped for overfitting, and the guarantee status. If a registered critical
+   route was not loaded, report the result as not guaranteed and do not pretend
+   the learning cycle completed.
 
 If this runtime cannot invoke the skill directly, read
-`.claude/skills/wf-learn/SKILL.md` and follow it in place.
+.claude/skills/wf-learn/SKILL.md (Codex mirror:
+.agents/skills/wf-learn/SKILL.md) and follow the contract in place. Do not
+duplicate the detailed learning procedure in this command file.

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

@@ -1,5 +1,5 @@
 ---
-description: Run WF-MAX with mandatory subagent fan-out and recorded degradation
+description: Run WF-MAX with evidence-driven fan-out and recorded suppression or degradation
 ---
 
 # /wf-max
@@ -10,11 +10,21 @@ static help or script command.
 1. Load `CLAUDE.md`, `Harness/MEMORY.md` (index only per Memory Preflight), then `Harness/README.md`.
 2. Load and follow `.claude/skills/wf-max/SKILL.md` (mirror: `.agents/skills/wf-max/SKILL.md`) and `Harness/specs/workflows/WF-MAX.md`.
 3. Preserve cache-first order per `Harness/specs/runtime/context-loading.md#Cache-First Context Contract`.
-4. MUST attempt native runtime subagent fan-out before planning is considered complete:
-   - start `task-scribe` when available for task ledger/state;
-   - start W0 exploration through manager/explorer/researcher roles with disjoint read sets;
-   - when running in OpenCode, require project `opencode.json` to have `subagent_depth >= 2` and manager agents to have `permission.task` allowlists for manager -> worker fan-out;
-   - if nested manager fan-out is unavailable, dispatch leaf workers directly from the primary agent with exact WF-MAX dispatch packets.
-5. In every runtime, MUST attempt native subagent fan-out before implementation planning is considered complete; never silently continue as a solo controller.
-6. If native fan-out fails, record `fanoutAttempted: true`, runtime, channel tried, agents requested, failure/degradation reason, and the fallback path in `Harness/tasks/<task-id>/PLAN.md` or `PROGRESS.md`.
-7. Continue with WF-Max-Useful by default or WF-Max-Strict only when the user explicitly requests strict mode.
+4. After the task id is known, generate a bounded controller/worker input with
+   `node Harness/scripts/task-context.mjs pack <task-id> --project <absolutePath> --role <role> --budget-bytes <n> --json`.
+   Resume by consuming a fresh `show`/`pack`; do not inject the full task log.
+5. Before external lookup, run
+   `node Harness/scripts/research-policy.mjs decide --trigger <trigger> --task-type <type> --json`.
+   Search web, GitHub, or Hugging Face only when the decision says `search: true`;
+   record source URL, title, version, license, date, and adopt/adapt/reject.
+6. Use WF-Max-Useful by default. The CEO may suppress fan-out when work is a
+   dependency chain, has no independent acceptance, or coordination cost has
+   no measured benefit; persist `fanoutSuppressed: true` plus the reason and
+   budget/capacity evidence. Workers still own any required source edits.
+7. WF-Max-Strict is active only for explicit `--strict`, `strict wf-max`, or
+   `strict mode`; then the controller MUST attempt native runtime subagent fan-out
+   and the span formula within real runtime capacity.
+   If a strict dispatch fails, record `fanoutAttempted: true`, channel, limit,
+   failure, and fallback in the task capsule. If Useful selects OpenCode
+   manager-to-worker fan-out, first require `subagent_depth >= 2` and a
+   `permission.task` child allowlist; otherwise record suppression.

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

@@ -1,5 +1,5 @@
 ---
-description: Run peer CLI or reviewer-subagent review via the wf-review skill
+description: Run native Harness reviewer-subagent review via the wf-review skill
 ---
 
 # /wf-review
@@ -9,8 +9,8 @@ static help or script command.
 
 1. Load `CLAUDE.md`, `Harness/MEMORY.md` (index only per Memory Preflight), then `Harness/README.md`.
 2. Preserve cache-first order per `Harness/specs/runtime/context-loading.md#Cache-First Context Contract`.
-3. Execute per the skill adapter `.claude/skills/wf-review/SKILL.md` (mirror: `.agents/skills/wf-review/SKILL.md`).
-4. Do not duplicate the workflow here. The skill adapter and the wf-review peer-review contract are authoritative.
+3. Execute per the native-only skill adapter `.claude/skills/wf-review/SKILL.md` (mirror: `.agents/skills/wf-review/SKILL.md`).
+4. Do not invoke another CLI. Do not duplicate the workflow here. The skill adapter and the wf-review native review contract are authoritative.
 
 If this runtime cannot invoke the skill directly, read
 `.claude/skills/wf-review/SKILL.md` and follow it in place.

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

@@ -0,0 +1,55 @@
+---
+description: Run one evidence-backed research pass (/wf-search) with a stateless validate/render helper
+---
+
+# /wf-search
+
+Run a single evidence-backed research pass over a real question using the
+current host's actual search tools. This is a direct command. Do not invoke a skill
+for it in Claude Code or OpenCode; load the protocol file named
+below directly. Do not start WF mode and do not load `Harness/MEMORY.md`
+(classification=direct, taskCapsulePolicy=none).
+
+## Usage
+
+```text
+/wf-search <question> [--mode auto|fact|verify|compare|troubleshoot] [--depth quick|standard|deep] [--task <task-id>] [--save]
+```
+
+Defaults: `--mode auto`, `--depth standard`. `auto` is resolved by the agent
+into one primary mode (`fact`/`verify`/`compare`/`troubleshoot`) plus optional
+secondary intents; the helper validates the four primary modes only.
+
+## Execution
+
+1. Load `.claude/skills/wf-search/SKILL.md` and follow that protocol. This
+   command file fixes argument semantics only; the skill owns the research
+   algorithm, source routing, budgets, and the evidence contract.
+2. The skill loads only the references it needs for the matched mode:
+   `references/policies/<mode>.md`, then `references/source-routing.md`,
+   `references/tool-adapters.md`, and `references/evidence-contract.md`.
+3. When assisting an existing WF task (`--task <task-id>`), the search
+   attaches evidence to that task only. It never creates, exits, downgrades,
+   closes, or switches the active task, and it never changes the task
+   lifecycle.
+
+## runtimeRoot
+
+- Project install that ships `Harness/scripts/wf-search.mjs`: run
+  `node Harness/scripts/wf-search.mjs <subcommand>` from the project root.
+- Global bridge without a project-local helper: read `globalDir` from
+  `Harness/.harness-version` and run
+  `node <globalDir>/Harness/scripts/wf-search.mjs <subcommand>`.
+- The helper is stateless: it reads only the given input file (or stdin) and
+  writes to stdout/stderr. It never creates directories, caches, locks, or
+  reports, and it makes no network calls.
+
+## Saving
+
+`--save` and `--task <task-id>` are executed only by a controller that has
+write permission, following the skill's save flow (validate -> render ->
+write -> read back). Read-only researcher roles return the structured
+ResearchResult JSON to the controller and never persist reports themselves.
+
+Codex compatibility: `$wf-search` or `/skills wf-search` reaches the same
+protocol through the wf-search skill shim.

package/templates/common/.claude/commands/wf-task-archive.md

@@ -8,17 +8,18 @@ DIRECT command. Wraps `node Harness/scripts/task-state.mjs archive`. Never loads
 
 ## Usage
 
-/wf-task-archive [--dry-run] [--apply] [--task <id>] [--keep <n>]
+/wf-task-archive [--dry-run] [--apply] [--task <id>] [--group <project>] [--keep <n>]
 
 - Defaults to dry-run (`--dry-run`) without `--apply`.
-- With `--apply`: moves eligible task directories into yearly subdirectories under `_archive/`.
+- With `--apply`: moves eligible task directories into dated paths under `_archive/YYYY/MM/DD/`.
 - With `--task <id>`: targets a specific task for archive eligibility check.
 - With `--keep <n>`: keeps N most recent non-archived task capsules (default 5).
-- Tasks with active, blocked, in_progress, running, pending, or needs-user-decision status are never auto-archived.
+- Only closed tasks are archive candidates. Legacy completed status values remain
+  readable and are treated as closed during eligibility checks.
 
 ## Execution
 
-Run: `node Harness/scripts/task-state.mjs archive [--dry-run] [--apply] [--task <id>] [--keep <n>] [--json]`
+Run: `node Harness/scripts/task-state.mjs archive [--dry-run] [--apply] [--task <id>] [--group <project>] [--keep <n>] [--json]`
 
 ## Return
 

package/templates/common/.claude/commands/wf-task-list.md

@@ -8,15 +8,18 @@ DIRECT command. Wraps `node Harness/scripts/task-state.mjs list --json`. Never l
 
 ## Usage
 
-/wf-task-list [--json]
+/wf-task-list [--project <project>] [--group <project>] [--status <status>] [--by-group] [--json]
 
 - By default, returns a human-readable listing of all task capsules.
 - With --json, returns structured JSON output.
-- Shows active, open, blocked, verified tasks with dependency info.
+- Shows active, open, blocked, and closed tasks with dependency info.
+- `--project` is canonical; `--group` remains a compatible alias.
+- The generated machine/human task route is rebuilt by `node Harness/scripts/task-state.mjs index`; lifecycle writes refresh it automatically.
+- Search with `node Harness/scripts/task-state.mjs query <keyword> [--project <project>] [--status <status>] --json`.
 
 ## Execution
 
-Run: `node Harness/scripts/task-state.mjs list --json`
+Run: `node Harness/scripts/task-state.mjs list [--project <project>] [--group <project>] [--status <status>] [--by-group] --json`
 
 ## Return
 

package/templates/common/.claude/commands/wf-task-record.md

@@ -8,15 +8,23 @@ DIRECT command. Wraps `node Harness/scripts/task-state.mjs record`. Never loads
 
 ## Usage
 
-/wf-task-record [<task-id>] [--title <slug>] [--note <text>] [--context <text>] [--new] [--create] [--status <status>] [--mode <mode>] [--text "description"]
+/wf-task-record [<task-id>] [--title <slug>] [--note <text>] [--context <text>] [--new] [--create] [--status <status>] [--mode <mode>] [--project <project>] [--group <project>] [--tag <tag[,tag...]>] [--text "description"]
 
 - With <task-id>: record to that task (existing semantics).
 - Without <task-id>: --title/--note/--context required. Deterministically matches open tasks; updates if unique match found; creates new if no match; fails if ambiguous unless --new.
 - Never uses LLM or embeddings — slug + keyword overlap only.
 
+`--project` is the canonical project collection key. `--group` remains a
+compatible alias for older repositories.
+
+To declare durable WF ownership at creation, pass `--mode wf` or `--mode
+wf-max`; a later mode promotion is rejected. A managed task can only move
+between `active`/`blocked` and then terminal `closed`; create a new capsule for
+the next WF unit.
+
 ## Execution
 
-Run: `node Harness/scripts/task-state.mjs record [<task-id>] [--title <slug>] [--note <text>] [--context <text>] [--new] [--create] [--apply] [--text "..."] [--status <status>] [--mode <mode>] [--json]`
+Run: `node Harness/scripts/task-state.mjs record [<task-id>] [--title <slug>] [--note <text>] [--context <text>] [--new] [--create] [--apply] [--text "..."] [--status <status>] [--mode <mode>] [--project <project>] [--group <project>] [--tag <tag[,tag...]>] [--json]`
 
 ## Return
 

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

@@ -10,17 +10,24 @@ Do not invoke a skill, do not start WF mode, and do not dispatch agents.
 Run from the project root:
 
 ```bash
-create-harness-vibe-coding wf-ui --project . --host 127.0.0.1 --port 0 --open
+create-harness-vibe-coding wf-ui --project . --host 127.0.0.1 --port 56670 --open --detach
 ```
 
-If the global binary is not available, use the package fallback:
+If you are inside the generator source repository and the global binary is not
+available, use the local source entry:
 
 ```bash
-npx create-harness-vibe-coding@0.8.19 wf-ui --project . --host 127.0.0.1 --port 0 --open
+node bin/create-harness-vibe-coding.js wf-ui --project . --host 127.0.0.1 --port 56670 --open --detach
+```
+
+Otherwise use the package fallback:
+
+```bash
+npx create-harness-vibe-coding@0.8.21 wf-ui --project . --host 127.0.0.1 --port 56670 --open --detach
 ```
 
 Rules:
 - Bind only to `127.0.0.1`.
-- Use port `0` unless the user asks for a fixed port.
-- Leave the server running until the user stops it.
+- Use port `56670`; if occupied, wf-ui tries the next port upward until one opens. Use `--port 0` only when the user explicitly wants an OS-assigned free port.
+- Detach the server so the command returns after printing the URL.
 - Return the local URL printed by the command.

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

@@ -37,6 +37,10 @@ Scope resolution is deterministic:
 Older installs that do not have the runner fall back to
 `Harness/scripts/wf-update-check.mjs`.
 
+All update paths are bounded: pass `--timeout-ms <positive-ms>` or set
+`WF_UPDATE_TIMEOUT_MS`; timeout exits with code `3`, an active update lock with
+code `4`, and successful transaction state is removed from `Harness/.temp`.
+
 1. Run `node Harness/scripts/wf-update-runner.mjs --json` first when present;
    otherwise run `node Harness/scripts/wf-update-check.mjs --json`. Use the
    `agent` block as the action plan. Preserve `agent.releaseHighlights` for the

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

@@ -10,7 +10,18 @@ static help or script command.
 1. Load `CLAUDE.md`, `Harness/MEMORY.md` (index only per Memory Preflight), then `Harness/README.md`.
 2. Preserve cache-first order per `Harness/specs/runtime/context-loading.md#Cache-First Context Contract`.
 3. Execute per the skill adapter `.claude/skills/wf/SKILL.md` (mirror: `.agents/skills/wf/SKILL.md`).
-4. Do not duplicate the workflow here. The skill adapter and `Harness/specs/workflows/WF.md` are authoritative.
+4. Once the task id is known, create the bounded dispatch input with
+   `node Harness/scripts/task-context.mjs pack <task-id> --project <absolutePath> --role <role> --budget-bytes <n> --json`.
+   Pass the returned pack to the controller and each worker; on resume, use
+   `show`/`pack` again instead of injecting the complete task log. `--input`
+   is optional for `pack`.
+5. Before external lookup, run
+   `node Harness/scripts/research-policy.mjs decide --trigger <trigger> --task-type <type> --json`.
+   Use web, GitHub, or Hugging Face sources only when `search: true`; record
+   the URL, title, version, license, checked date, and adopt/adapt/reject
+   decision in the task evidence. Do not research every workflow by default.
+6. Do not duplicate the workflow here. The skill adapter and
+   `Harness/specs/workflows/WF.md` are authoritative.
 
 If this runtime cannot invoke the skill directly, read
 `.claude/skills/wf/SKILL.md` and follow it in place.

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

@@ -8,7 +8,7 @@ alwaysApply: true
 ## 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 workflow command (`/wf-*`, `$wf-*`, or `/skills wf-*`), excluding `/wf-help`, `$wf-help`, `/skills wf-help`, `/wf-update`, `$wf-update`, `/skills wf-update`, `/wf-task-record`, `$wf-task-record`, `/skills wf-task-record`, `/wf-task-list`, `$wf-task-list`, `/skills wf-task-list`, `/wf-task-archive`, `$wf-task-archive`, `/skills wf-task-archive`, `/wf-command-create`, `$wf-command-create`, `/skills wf-command-create`, `/wf-ui`, `$wf-ui`, and `/skills wf-ui`, load `Harness/MEMORY.md` and `Harness/README.md`.
+- When the user explicitly invokes a workflow command (`/wf-*`, `$wf-*`, or `/skills wf-*`), excluding `/wf-help`, `$wf-help`, `/skills wf-help`, `/wf-update`, `$wf-update`, `/skills wf-update`, `/wf-task-record`, `$wf-task-record`, `/skills wf-task-record`, `/wf-task-list`, `$wf-task-list`, `/skills wf-task-list`, `/wf-task-archive`, `$wf-task-archive`, `/skills wf-task-archive`, `/wf-command-create`, `$wf-command-create`, `/skills wf-command-create`, `/wf-ui`, `$wf-ui`, `/skills wf-ui`, `/wf-init`, `$wf-init`, `/skills wf-init`, `/wf-search`, `$wf-search`, and `/skills wf-search`, 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.
@@ -41,6 +41,15 @@ alwaysApply: true
 - If the runtime cannot spawn subagents, emulate the same role pack in a separate bounded pass.
 - Main agent owns integration and final verification.
 
+## Agent Team Cooperation (WF / WF-MAX)
+
+- On `/wf` / `$wf` / `/wf-max` / `$wf-max`, the main Agent node autonomously: understands the task, decides whether team collaboration is needed, finds existing agents by role/capability, connects or creates sub-agents (role profile: displayName + roleTitle), shares context via Markdown nodes (nodeId only), sends structured requests, waits via Timer wakeup messages (checked on next turn), aggregates replies, ticks Goal items, and completes when done.
+- Ambiguous target → ask the user; never blindly create/connect.
+- Never edit `Harness/a2a/**/state.json` directly; use typed actions only.
+- Timer is the only wakeup source; the Goal node never wakes agents.
+- Subagent mode comes from node settings (built-in-subagents default = native helpers, no canvas nodes; wf-node-subagents = visible canvas agents); natural language "内部助手"/"内置子代理" → built-in, "画布节点"/"WF node协作" → wf-node. Discover everything at runtime: help --json, workflow-context, manuals <type>, snapshot, workflow-ontology.
+- No jargon for users: no broadcast/A2A/thread/shared-context terminology.
+
 ## Memory
 
 - Detect memory candidates when user says: `remember`, `next time`, `don't`, `do not`, `never`, `always`, `I prefer`, `I want you to`, `记住`, `下次`, `以后`, `不要再`, `总是`, `永远不要`, `我偏好`, `我希望你以后`.

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

@@ -37,8 +37,44 @@ listed loads in order, load only routed skills/tools, append task state and
 latest tool output after stable docs, and return compact evidence instead of
 logs or transcripts.
 
+## Bounded Context and Research Routing
+
+After the controller has a task id, generate a role-scoped input and use that
+artifact for dispatch and recovery:
+
+```text
+node Harness/scripts/task-context.mjs pack <task-id> --project <absolutePath> --role <role> --budget-bytes <n> --json
+```
+
+The pack is a bounded summary of intent, constraints, unresolved items, and
+role-relevant evidence. Workers and resumed controllers consume a fresh
+`show`/`pack`; they do not receive the complete task log. `--input` is optional
+for `pack` and the controller chooses the byte budget from the task risk.
+
+Before searching outside the project, ask the local policy router:
+
+```text
+node Harness/scripts/research-policy.mjs decide --trigger <trigger> --task-type <type> --json
+```
+
+Valid triggers cover a capability gap, volatile API, explicit user request,
+repeated failure, and benchmark gap. Search web, GitHub, or Hugging Face only
+when `search: true`. An agent that searches reads the primary source, records
+URL/title/version/license/date, and records an `adopt`, `adapt`, or `reject`
+decision with its reason. A normal workflow does not load all memory or go
+online by default.
+
 ## Rules
 
+- On the first `/wf` or `$wf` entry, create or enter the task with `mode: wf`;
+  on `/wf-max`, use `mode: wf-max`. This explicit mode is the durable
+  lifecycle declaration, not a label inferred from task complexity.
+- When an open `wf`/`wf-max` task is the Harness active focus, resume it on the
+  next session automatically. Do not ask the user to repeat the trigger or
+  silently fall back to direct mode.
+- A task that started without `/wf` or `/wf-max` stays outside WF lifecycle;
+  never promote it. A managed task cannot downgrade or exit; close it, then
+  create a new task capsule for the next unit of work.
 - Create or update a task capsule under `Harness/tasks/<task-id>/`; new task
   ids MUST match `task-<verb>-<noun>[-detail]`.
 - 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).