@claude-flow/cli 3.28.0 → 3.30.0

package/plugins/ruflo-metaharness/skills/harness-bench/SKILL.md

@@ -1,64 +1,64 @@
----
-name: harness-bench
-description: Manage `@metaharness/darwin` bench suites — `bench create <repo>` scaffolds a JSON suite from a repo's test corpus; `bench verify <suite.json>` checks suite well-formedness. Bench suites are the fixed evaluation corpora that `harness-evolve --bench <suite.json>` scores variants against, decoupling evolution from the repo's natural tests. Degrades gracefully when @metaharness/darwin is absent.
-argument-hint: "--op create --repo <path> [--out <path>]  |  --op verify --suite <path>"
-allowed-tools: Bash
----
-
-Surfaces `metaharness-darwin bench <create|verify>` — the supporting verb
-for `harness-evolve --bench`. Use when you want evolution scored against a
-fixed corpus (independent of `npm test`) so champion fitness is comparable
-across commits or across forks of the same harness.
-
-## When to use
-
-- Setting up a new evolution pipeline for a repo whose `npm test` is
-  flaky, slow, or undersized — scaffold a deterministic bench suite once,
-  then evolve against it repeatedly.
-- CI: `bench verify` the checked-in suite on every PR that touches it
-  (cheap; ~5s).
-- Forking a harness to a new domain: copy and edit the suite to retarget
-  the evaluation without losing comparability to the parent.
-
-## Algorithm
-
-Implementation: [`scripts/bench.mjs`](../../scripts/bench.mjs).
-
-### `--op create`
-1. Resolve `--repo` path; reject if missing.
-2. Shell to `metaharness-darwin bench create <repo> [--out <suite.json>]`.
-3. Default output path: `<repo>/.metaharness/bench/suite.json` (chosen by upstream).
-4. Suite shape (per upstream): array of `{ input, expectedOutput, weight }` tasks
-   derived from existing test cases.
-
-### `--op verify`
-1. Resolve `--suite` path; reject if missing.
-2. Shell to `metaharness-darwin bench verify <suite.json>`.
-3. Exit 1 if any task malformed (upstream's signal).
-
-## Output shape
-
-```json
-{
-  "success": true,
-  "data": {
-    "op": "verify",
-    "taskCount": 42,
-    "wellFormed": true,
-    "durationMs": 870
-  }
-}
-```
-
-## Exit codes
-
-| Code | Meaning |
-|---|---|
-| 0 | OK (or degraded — Darwin absent) |
-| 1 | `--op verify` and suite malformed |
-| 2 | Config error or upstream invocation failure |
-
-## Graceful degradation
-
-When `@metaharness/darwin` is absent, emits the standard `{degraded: true,
-reason: 'metaharness-darwin-not-available'}` payload and exits 0.
+---
+name: harness-bench
+description: Manage `@metaharness/darwin` bench suites — `bench create <repo>` scaffolds a JSON suite from a repo's test corpus; `bench verify <suite.json>` checks suite well-formedness. Bench suites are the fixed evaluation corpora that `harness-evolve --bench <suite.json>` scores variants against, decoupling evolution from the repo's natural tests. Degrades gracefully when @metaharness/darwin is absent.
+argument-hint: "--op create --repo <path> [--out <path>]  |  --op verify --suite <path>"
+allowed-tools: Bash
+---
+
+Surfaces `metaharness-darwin bench <create|verify>` — the supporting verb
+for `harness-evolve --bench`. Use when you want evolution scored against a
+fixed corpus (independent of `npm test`) so champion fitness is comparable
+across commits or across forks of the same harness.
+
+## When to use
+
+- Setting up a new evolution pipeline for a repo whose `npm test` is
+  flaky, slow, or undersized — scaffold a deterministic bench suite once,
+  then evolve against it repeatedly.
+- CI: `bench verify` the checked-in suite on every PR that touches it
+  (cheap; ~5s).
+- Forking a harness to a new domain: copy and edit the suite to retarget
+  the evaluation without losing comparability to the parent.
+
+## Algorithm
+
+Implementation: [`scripts/bench.mjs`](../../scripts/bench.mjs).
+
+### `--op create`
+1. Resolve `--repo` path; reject if missing.
+2. Shell to `metaharness-darwin bench create <repo> [--out <suite.json>]`.
+3. Default output path: `<repo>/.metaharness/bench/suite.json` (chosen by upstream).
+4. Suite shape (per upstream): array of `{ input, expectedOutput, weight }` tasks
+   derived from existing test cases.
+
+### `--op verify`
+1. Resolve `--suite` path; reject if missing.
+2. Shell to `metaharness-darwin bench verify <suite.json>`.
+3. Exit 1 if any task malformed (upstream's signal).
+
+## Output shape
+
+```json
+{
+  "success": true,
+  "data": {
+    "op": "verify",
+    "taskCount": 42,
+    "wellFormed": true,
+    "durationMs": 870
+  }
+}
+```
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| 0 | OK (or degraded — Darwin absent) |
+| 1 | `--op verify` and suite malformed |
+| 2 | Config error or upstream invocation failure |
+
+## Graceful degradation
+
+When `@metaharness/darwin` is absent, emits the standard `{degraded: true,
+reason: 'metaharness-darwin-not-available'}` payload and exits 0.

package/plugins/ruflo-metaharness/skills/harness-drift-from-history/SKILL.md

@@ -1,65 +1,65 @@
----
-name: harness-drift-from-history
-description: One-command drift detection. Composes audit-list + oia-audit + audit-trend into a single primitive — finds the most recent audit in `metaharness-audit` namespace, runs a fresh audit against the current repo, diffs them via ADR-152 §3.1 similarity, and alerts when structural distance crosses `--threshold`. Iter 53 of ADR-150 deep integration.
-argument-hint: "[--path .] [--baseline-since 7d] [--threshold 0.95] [--dry-run] [--format json|table]"
-allowed-tools: Bash
----
-
-The natural ops question after running `oia-audit` weekly is "did anything drift?" Before this skill, the answer required a three-step sequence:
-
-```bash
-npx ruflo metaharness audit-list --format json   # → pick a key by hand
-npx ruflo metaharness oia-audit --format json > /tmp/curr.json
-npx ruflo metaharness audit-trend \
-  --baseline-key <picked-key> --current /tmp/curr.json \
-  --alert-on-distance-below 0.95
-```
-
-This skill collapses it into one command:
-
-```bash
-npx ruflo metaharness drift-from-history --threshold 0.95
-```
-
-## What it does
-
-1. Lists records from `metaharness-audit` namespace via audit-list.mjs
-2. Picks the most recent record by `startedAt` (or `--baseline-since 7d` skips anything newer than 7 days)
-3. Runs a fresh `oia-audit` against the current path
-4. Diffs the two via audit-trend, applying `--alert-on-distance-below ${threshold}`
-5. Returns the structured drift report
-
-## Architectural constraint inheritance (ADR-150)
-
-| Constraint | How drift-from-history satisfies it |
-|---|---|
-| Removable | Pure subprocess composition over existing scripts — no new `@metaharness/*` import |
-| Optional | If oia-audit reports `degraded:true`, this skill exits 3 with a degraded payload |
-| Graceful | Empty audit history → exit 2 with hint to seed it; never crashes |
-| CI-gate | Smoke step 17z16 anchors the dispatcher entry + subcommand listing |
-
-## Exit codes
-
-- 0 — similarity ≥ threshold (or threshold not crossed)
-- 1 — drift detected: similarity < threshold (alert fired)
-- 2 — config error (no history, audit-list failed)
-- 3 — upstream metaharness absent (degraded payload returned)
-
-## Example
-
-```bash
-$ npx ruflo metaharness drift-from-history --threshold 0.95
-# drift-from-history
-
-Baseline:        audit-2026-06-16T22-58-47-840Z
-Current:         2026-06-16T23:05:02.231Z
-
-Structural similarity: 1 (near-identical)
-Distance:              0
-
-✓ similarity ≥ 0.95 — OK
-```
-
-## Implementation
-
-[`scripts/drift-from-history.mjs`](../../scripts/drift-from-history.mjs)
+---
+name: harness-drift-from-history
+description: One-command drift detection. Composes audit-list + oia-audit + audit-trend into a single primitive — finds the most recent audit in `metaharness-audit` namespace, runs a fresh audit against the current repo, diffs them via ADR-152 §3.1 similarity, and alerts when structural distance crosses `--threshold`. Iter 53 of ADR-150 deep integration.
+argument-hint: "[--path .] [--baseline-since 7d] [--threshold 0.95] [--dry-run] [--format json|table]"
+allowed-tools: Bash
+---
+
+The natural ops question after running `oia-audit` weekly is "did anything drift?" Before this skill, the answer required a three-step sequence:
+
+```bash
+npx ruflo metaharness audit-list --format json   # → pick a key by hand
+npx ruflo metaharness oia-audit --format json > /tmp/curr.json
+npx ruflo metaharness audit-trend \
+  --baseline-key <picked-key> --current /tmp/curr.json \
+  --alert-on-distance-below 0.95
+```
+
+This skill collapses it into one command:
+
+```bash
+npx ruflo metaharness drift-from-history --threshold 0.95
+```
+
+## What it does
+
+1. Lists records from `metaharness-audit` namespace via audit-list.mjs
+2. Picks the most recent record by `startedAt` (or `--baseline-since 7d` skips anything newer than 7 days)
+3. Runs a fresh `oia-audit` against the current path
+4. Diffs the two via audit-trend, applying `--alert-on-distance-below ${threshold}`
+5. Returns the structured drift report
+
+## Architectural constraint inheritance (ADR-150)
+
+| Constraint | How drift-from-history satisfies it |
+|---|---|
+| Removable | Pure subprocess composition over existing scripts — no new `@metaharness/*` import |
+| Optional | If oia-audit reports `degraded:true`, this skill exits 3 with a degraded payload |
+| Graceful | Empty audit history → exit 2 with hint to seed it; never crashes |
+| CI-gate | Smoke step 17z16 anchors the dispatcher entry + subcommand listing |
+
+## Exit codes
+
+- 0 — similarity ≥ threshold (or threshold not crossed)
+- 1 — drift detected: similarity < threshold (alert fired)
+- 2 — config error (no history, audit-list failed)
+- 3 — upstream metaharness absent (degraded payload returned)
+
+## Example
+
+```bash
+$ npx ruflo metaharness drift-from-history --threshold 0.95
+# drift-from-history
+
+Baseline:        audit-2026-06-16T22-58-47-840Z
+Current:         2026-06-16T23:05:02.231Z
+
+Structural similarity: 1 (near-identical)
+Distance:              0
+
+✓ similarity ≥ 0.95 — OK
+```
+
+## Implementation
+
+[`scripts/drift-from-history.mjs`](../../scripts/drift-from-history.mjs)

package/plugins/ruflo-metaharness/skills/harness-evolve/SKILL.md

@@ -1,131 +1,131 @@
----
-name: harness-evolve
-description: Run `@metaharness/darwin evolve <repo>` to mutate a harness's seven policy surfaces (planner/contextBuilder/reviewer/retryPolicy/toolPolicy/memoryPolicy/scorePolicy), sandbox-score each variant, and promote only measured wins. The model is frozen; the harness evolves. Closes the loop ADR-150 opens (score+genome describe; evolve changes). Degrades gracefully when @metaharness/darwin is absent (ADR-150 + ADR-153 architectural constraints).
-argument-hint: "--repo <path> [--generations 3] [--children 3] [--concurrency 2] [--sandbox real|mock|agent] [--selection pareto|quality-diversity|...] [--mutator deterministic|ruvllm] [--diagnose] [--confirm]"
-allowed-tools: Bash
----
-
-Surfaces the upstream `metaharness-darwin evolve` CLI as a ruflo skill. The
-**write** layer that pairs with ADR-150's read layer (score / genome /
-mcp-scan / threat-model / oia-audit). Use when you have a harness whose
-readiness scores are flat and you want to discover *which* surface mutation
-moves them — without retraining the foundation model.
-
-## When to use
-
-- A `harness-score` result is below target and you don't know which policy
-  surface is responsible.
-- You're seeding a harness for a new vertical and want to find a good
-  starting configuration empirically rather than hand-tuning.
-- You're comparing your hand-tuned harness against an evolved baseline
-  (treat darwin's champion as the strawman).
-
-## When NOT to use
-
-- For continuous background optimization. Darwin Mode is human-initiated.
-  Wire it into CI for one-shot exploration, not for autonomous self-modification.
-- For ruflo itself in CI. ADR-153 §5 explicitly rejects auto-evolving ruflo
-  — the CI gate verifies graceful degradation, not convergence.
-
-## Algorithm
-
-Implementation: [`scripts/evolve.mjs`](../../scripts/evolve.mjs).
-
-1. Validate args (`--repo` exists, caps on `--generations` ≤ 50, `--children`
-   ≤ 20, `--concurrency` ≤ 8, sandbox/selection/mutator are known values).
-2. Without `--confirm`: print plan + exit 0 (mirrors `harness-mint` safety
-   convention; defense in depth over the upstream `safety.ts` checks).
-3. With `--confirm`: shell to `npx -y @metaharness/darwin@~0.8.0 metaharness-darwin evolve <repo> ...`
-   via the shared `_darwin.mjs` async helper. Per-generation progress is
-   forwarded to stderr; final champion JSON is captured from stdout.
-4. Compute timeout from `generations × children × per-variant` (per-variant
-   ≈ 60s real, ≈ 2s mock). Caller may override with `--timeout-ms`.
-5. Honor upstream exit code 99 — propagate as "safety-disqualified", do not
-   remap. This is a designed-in tripwire (a variant tripped `inspectVariant`
-   for secrets / shell-out / network / dynamic-eval). See ADR-153 §"Safety model".
-6. Optional `--alert-on-no-improvement`: exit 1 when champion ≤ parent.
-
-## The seven mutation surfaces
-
-| Surface | What it owns |
-|---|---|
-| `planner` | task decomposition / step ordering |
-| `contextBuilder` | what gets fed into the prompt |
-| `reviewer` | self-critique / output verification |
-| `retryPolicy` | when + how to retry on failure |
-| `toolPolicy` | which tools the agent may use, under which conditions |
-| `memoryPolicy` | what to persist, recall, forget |
-| `scorePolicy` | how the agent grades its own output |
-
-One mutation per variant. Multi-surface mutations are not allowed (causal
-attribution stays clean).
-
-## Output
-
-Reports land under `<repo>/.metaharness/`:
-
-```
-.metaharness/
-  archive.json         # full lineage tree (sampling next gen draws from this)
-  lineage.json         # parent→child edges only
-  variants/<id>/       # per-variant code (kept for audit)
-  runs/<id>/           # per-variant sandbox test output
-  reports/winner.json  # final champion + score delta vs parent
-```
-
-Skill stdout = JSON `{success, data: {champion, plan, durationMs, improved}}`
-(plus `data.diagnosis` when `--diagnose` is passed — see below).
-
-## Failure diagnosis (`--diagnose`)
-
-GEPA's key trick is natural-language failure diagnosis from execution traces
-feeding the next mutation — not just scalar fitness. `--diagnose` adds a
-modest slice of that: after the evolution completes, the losing / failed
-variants' transcripts are run through darwin's GEPA library ops
-(`analyzeTranscript` + `classifyFailure`, via the shared `importGepa`
-resolver in `scripts/_darwin.mjs`) and a `diagnosis` section is appended to
-the emitted JSON:
-
-```json
-"diagnosis": {
-  "available": true,
-  "scope": "losing-variants",
-  "variants": [
-    { "id": "g1_v0", "transcripts": 2,
-      "failureClasses": { "exploration-loop": 1, "edit-mechanics": 1 },
-      "dominantClass": "exploration-loop" }
-  ],
-  "totals": { "exploration-loop": 1, "edit-mechanics": 1 }
-}
-```
-
-Upstream shape caveats (verified against `@metaharness/darwin@0.8.0`):
-
-- `metaharness-darwin evolve --json` prints a TEXT leaderboard — the stdout
-  carries no JSON and no transcripts. Per-variant run records live at
-  `<repo>/.metaharness/runs/<id>.json`.
-- Those run records hold sandbox exec traces (`{taskId, exitCode, stdout,
-  stderr}`), which are NOT GEPA `{actionRaw, obs}` transcripts. Diagnosis
-  therefore uses GEPA-shaped transcripts when a run record embeds them
-  (agent sandbox / future upstream), falls back to the champion's transcript,
-  and otherwise emits `diagnosis: {available: false, reason, traceSummary}`
-  where `traceSummary` is a mechanical per-variant tally (tasks / failed /
-  timedOut / blockedActions).
-- `--diagnose` NEVER fails the run — any internal error degrades to
-  `{available: false, reason: "diagnosis-failed: ..."}`.
-
-## Exit codes
-
-| Code | Meaning |
-|---|---|
-| 0  | Evolved OK, or dry-run, or degraded (Darwin absent) |
-| 1  | `--alert-on-no-improvement` and champion did not beat parent |
-| 2  | Config error or evolution infrastructure failure |
-| 99 | Upstream "safety-disqualified" (PROPAGATED, not remapped) |
-
-## Graceful degradation (ADR-150 constraint 3 + ADR-153)
-
-When `@metaharness/darwin` is not installed, the script emits
-`{degraded: true, reason: 'metaharness-darwin-not-available', hint: ...}`
-and exits 0. ruflo continues to function. CI's
-`no-metaharness-smoke.yml`-style job asserts this path.
+---
+name: harness-evolve
+description: Run `@metaharness/darwin evolve <repo>` to mutate a harness's seven policy surfaces (planner/contextBuilder/reviewer/retryPolicy/toolPolicy/memoryPolicy/scorePolicy), sandbox-score each variant, and promote only measured wins. The model is frozen; the harness evolves. Closes the loop ADR-150 opens (score+genome describe; evolve changes). Degrades gracefully when @metaharness/darwin is absent (ADR-150 + ADR-153 architectural constraints).
+argument-hint: "--repo <path> [--generations 3] [--children 3] [--concurrency 2] [--sandbox real|mock|agent] [--selection pareto|quality-diversity|...] [--mutator deterministic|ruvllm] [--diagnose] [--confirm]"
+allowed-tools: Bash
+---
+
+Surfaces the upstream `metaharness-darwin evolve` CLI as a ruflo skill. The
+**write** layer that pairs with ADR-150's read layer (score / genome /
+mcp-scan / threat-model / oia-audit). Use when you have a harness whose
+readiness scores are flat and you want to discover *which* surface mutation
+moves them — without retraining the foundation model.
+
+## When to use
+
+- A `harness-score` result is below target and you don't know which policy
+  surface is responsible.
+- You're seeding a harness for a new vertical and want to find a good
+  starting configuration empirically rather than hand-tuning.
+- You're comparing your hand-tuned harness against an evolved baseline
+  (treat darwin's champion as the strawman).
+
+## When NOT to use
+
+- For continuous background optimization. Darwin Mode is human-initiated.
+  Wire it into CI for one-shot exploration, not for autonomous self-modification.
+- For ruflo itself in CI. ADR-153 §5 explicitly rejects auto-evolving ruflo
+  — the CI gate verifies graceful degradation, not convergence.
+
+## Algorithm
+
+Implementation: [`scripts/evolve.mjs`](../../scripts/evolve.mjs).
+
+1. Validate args (`--repo` exists, caps on `--generations` ≤ 50, `--children`
+   ≤ 20, `--concurrency` ≤ 8, sandbox/selection/mutator are known values).
+2. Without `--confirm`: print plan + exit 0 (mirrors `harness-mint` safety
+   convention; defense in depth over the upstream `safety.ts` checks).
+3. With `--confirm`: shell to `npx -y @metaharness/darwin@~0.8.0 metaharness-darwin evolve <repo> ...`
+   via the shared `_darwin.mjs` async helper. Per-generation progress is
+   forwarded to stderr; final champion JSON is captured from stdout.
+4. Compute timeout from `generations × children × per-variant` (per-variant
+   ≈ 60s real, ≈ 2s mock). Caller may override with `--timeout-ms`.
+5. Honor upstream exit code 99 — propagate as "safety-disqualified", do not
+   remap. This is a designed-in tripwire (a variant tripped `inspectVariant`
+   for secrets / shell-out / network / dynamic-eval). See ADR-153 §"Safety model".
+6. Optional `--alert-on-no-improvement`: exit 1 when champion ≤ parent.
+
+## The seven mutation surfaces
+
+| Surface | What it owns |
+|---|---|
+| `planner` | task decomposition / step ordering |
+| `contextBuilder` | what gets fed into the prompt |
+| `reviewer` | self-critique / output verification |
+| `retryPolicy` | when + how to retry on failure |
+| `toolPolicy` | which tools the agent may use, under which conditions |
+| `memoryPolicy` | what to persist, recall, forget |
+| `scorePolicy` | how the agent grades its own output |
+
+One mutation per variant. Multi-surface mutations are not allowed (causal
+attribution stays clean).
+
+## Output
+
+Reports land under `<repo>/.metaharness/`:
+
+```
+.metaharness/
+  archive.json         # full lineage tree (sampling next gen draws from this)
+  lineage.json         # parent→child edges only
+  variants/<id>/       # per-variant code (kept for audit)
+  runs/<id>/           # per-variant sandbox test output
+  reports/winner.json  # final champion + score delta vs parent
+```
+
+Skill stdout = JSON `{success, data: {champion, plan, durationMs, improved}}`
+(plus `data.diagnosis` when `--diagnose` is passed — see below).
+
+## Failure diagnosis (`--diagnose`)
+
+GEPA's key trick is natural-language failure diagnosis from execution traces
+feeding the next mutation — not just scalar fitness. `--diagnose` adds a
+modest slice of that: after the evolution completes, the losing / failed
+variants' transcripts are run through darwin's GEPA library ops
+(`analyzeTranscript` + `classifyFailure`, via the shared `importGepa`
+resolver in `scripts/_darwin.mjs`) and a `diagnosis` section is appended to
+the emitted JSON:
+
+```json
+"diagnosis": {
+  "available": true,
+  "scope": "losing-variants",
+  "variants": [
+    { "id": "g1_v0", "transcripts": 2,
+      "failureClasses": { "exploration-loop": 1, "edit-mechanics": 1 },
+      "dominantClass": "exploration-loop" }
+  ],
+  "totals": { "exploration-loop": 1, "edit-mechanics": 1 }
+}
+```
+
+Upstream shape caveats (verified against `@metaharness/darwin@0.8.0`):
+
+- `metaharness-darwin evolve --json` prints a TEXT leaderboard — the stdout
+  carries no JSON and no transcripts. Per-variant run records live at
+  `<repo>/.metaharness/runs/<id>.json`.
+- Those run records hold sandbox exec traces (`{taskId, exitCode, stdout,
+  stderr}`), which are NOT GEPA `{actionRaw, obs}` transcripts. Diagnosis
+  therefore uses GEPA-shaped transcripts when a run record embeds them
+  (agent sandbox / future upstream), falls back to the champion's transcript,
+  and otherwise emits `diagnosis: {available: false, reason, traceSummary}`
+  where `traceSummary` is a mechanical per-variant tally (tasks / failed /
+  timedOut / blockedActions).
+- `--diagnose` NEVER fails the run — any internal error degrades to
+  `{available: false, reason: "diagnosis-failed: ..."}`.
+
+## Exit codes
+
+| Code | Meaning |
+|---|---|
+| 0  | Evolved OK, or dry-run, or degraded (Darwin absent) |
+| 1  | `--alert-on-no-improvement` and champion did not beat parent |
+| 2  | Config error or evolution infrastructure failure |
+| 99 | Upstream "safety-disqualified" (PROPAGATED, not remapped) |
+
+## Graceful degradation (ADR-150 constraint 3 + ADR-153)
+
+When `@metaharness/darwin` is not installed, the script emits
+`{degraded: true, reason: 'metaharness-darwin-not-available', hint: ...}`
+and exits 0. ruflo continues to function. CI's
+`no-metaharness-smoke.yml`-style job asserts this path.

package/plugins/ruflo-metaharness/skills/harness-genome/SKILL.md

@@ -1,54 +1,54 @@
----
-name: harness-genome
-description: 7-section repo readiness report from `metaharness genome <path>`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
-argument-hint: "[--path .] [--alert-on-risk-above 0.5] [--format table|json]"
-allowed-tools: Bash
----
-
-Companion to `harness-score`. Where score is a 5-dimension numeric
-scorecard, genome is a 7-section categorical/numeric report covering
-repo type, agent topology recommendations, risk score (0-1), MCP
-surface area, test confidence (0-1), and publish readiness (0-1).
-
-## Algorithm
-
-Implementation: [`scripts/genome.mjs`](../../scripts/genome.mjs).
-
-1. Shell out to `npx metaharness genome <path> --json` (60s hard timeout).
-2. Parse the shape: `{ repo_type, agent_topology[], risk_score,
-   mcp_surface, test_confidence, publish_readiness }`.
-3. If `--alert-on-risk-above N`: exit 1 when `risk_score > N`.
-4. Output JSON (default) or markdown.
-
-## Phase-0 baseline (ruflo, measured 2026-06-16)
-
-```
-{
-  "repo_type": "node_mcp_ci",
-  "agent_topology": ["maintainer", "tester", "security", "release"],
-  "risk_score": 0.27,
-  "mcp_surface": "remote",
-  "test_confidence": 0.8,
-  "publish_readiness": 0.9
-}
-```
-
-Ruflo's `risk_score: 0.27` is low (good). `publish_readiness: 0.9` is
-high. The `mcp_surface: "remote"` reflects that ruflo's MCP servers are
-hosted, not bundled.
-
-## When to use
-
-- Pre-mint review: "before scaffolding a custom harness from this repo,
-  should we?" — genome answers it categorically.
-- Drift detection: capture genome snapshots over time, diff via
-  cost-diff-style tooling to spot when `agent_topology` recommendations
-  drift away from a deliberate architecture choice.
-- CI gate: `--alert-on-risk-above 0.5` fails the build when the repo's
-  risk profile crosses a threshold.
-
-## Pairs with
-
-- `harness-score` — numeric readiness
-- `harness-mcp-scan` — static MCP security findings
-- `harness-threat-model` — enterprise-review-grade threat model
+---
+name: harness-genome
+description: 7-section repo readiness report from `metaharness genome <path>`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
+argument-hint: "[--path .] [--alert-on-risk-above 0.5] [--format table|json]"
+allowed-tools: Bash
+---
+
+Companion to `harness-score`. Where score is a 5-dimension numeric
+scorecard, genome is a 7-section categorical/numeric report covering
+repo type, agent topology recommendations, risk score (0-1), MCP
+surface area, test confidence (0-1), and publish readiness (0-1).
+
+## Algorithm
+
+Implementation: [`scripts/genome.mjs`](../../scripts/genome.mjs).
+
+1. Shell out to `npx metaharness genome <path> --json` (60s hard timeout).
+2. Parse the shape: `{ repo_type, agent_topology[], risk_score,
+   mcp_surface, test_confidence, publish_readiness }`.
+3. If `--alert-on-risk-above N`: exit 1 when `risk_score > N`.
+4. Output JSON (default) or markdown.
+
+## Phase-0 baseline (ruflo, measured 2026-06-16)
+
+```
+{
+  "repo_type": "node_mcp_ci",
+  "agent_topology": ["maintainer", "tester", "security", "release"],
+  "risk_score": 0.27,
+  "mcp_surface": "remote",
+  "test_confidence": 0.8,
+  "publish_readiness": 0.9
+}
+```
+
+Ruflo's `risk_score: 0.27` is low (good). `publish_readiness: 0.9` is
+high. The `mcp_surface: "remote"` reflects that ruflo's MCP servers are
+hosted, not bundled.
+
+## When to use
+
+- Pre-mint review: "before scaffolding a custom harness from this repo,
+  should we?" — genome answers it categorically.
+- Drift detection: capture genome snapshots over time, diff via
+  cost-diff-style tooling to spot when `agent_topology` recommendations
+  drift away from a deliberate architecture choice.
+- CI gate: `--alert-on-risk-above 0.5` fails the build when the repo's
+  risk profile crosses a threshold.
+
+## Pairs with
+
+- `harness-score` — numeric readiness
+- `harness-mcp-scan` — static MCP security findings
+- `harness-threat-model` — enterprise-review-grade threat model