@nurix/etna 0.19.15 → 0.19.17

package/README.md

@@ -2,7 +2,7 @@
 
 CLI to bootstrap a project with a Nurix harness. Copies the harness's `CLAUDE.md`, skills, agents, rules, and hooks (plus scripts, if the harness ships any) into the project so they live with the code — version-controllable, editable per project, and visible without leaving the repo.
 
-A second install path also exists and is fully supported: `/plugin install <plugin>@nurixlabs` from inside Claude Code, which installs the harness as a plugin from the `nurixlabs/skills` marketplace. The two paths are first-class equals — pick the one that matches how you want to manage the harness. See [`docs/architecture/harness/install-model.md`](../../docs/architecture/harness/install-model.md) for the comparison.
+A second install path also exists and is fully supported: `/plugin install <plugin>@nurixlabs` from inside Claude Code, which installs the harness as a plugin from the `nurixlabs/skills` marketplace. The two paths are first-class equals — pick the one that matches how you want to manage the harness. See [`docs/architecture/harness/Readme.md`](../../docs/architecture/harness/Readme.md#the-install-model) for the comparison.
 
 ## Usage
 
@@ -64,24 +64,27 @@ The `nurixlabs` marketplace entry in `~/.claude/settings.json` is harmless to le
 
 Listed by `npx --yes @nurix/etna` (no args) using the bundled `data/harness-index.json`.
 
-| Plugin name | Source in etna | What it ships |
+| Harness | Source in etna | What it ships |
 | --- | --- | --- |
-| `code` | [`plugins/code/`](../../plugins/code/) | Governance + session agents, baseline workflow skills, the ownership-index hook |
-| `kb-agi` | [`plugins/kb-agi/`](../../plugins/kb-agi/) | Knowledge-vault scaffolding |
+| `code` | [`harness/code/`](../../harness/code/) | Governance + session agents, baseline workflow skills, the ownership-index hook (merged single-folder layout) |
+| `kb-agi` | [`harness/kb-agi/`](../../harness/kb-agi/) | Knowledge-vault scaffolding |
 
 ## How it works
 
-Each harness has two halves in the etna repo:
+Each harness lives in a single folder in the etna repo — `harness/<name>/`:
 
-- `plugins/<name>/` — the **plugin** (what a Claude Code plugin natively bundles): `definition.md` (manifest — identity + `skills:`/`rules:`/`agents:` lists), `hooks/`, and any unlisted, harness-specific `agents/`.
-- `harness/<name>/` — the **policy**: `CLAUDE.md` (pure policy, no frontmatter — installed as a verbatim copy) plus `index.md`, whose `plugin:` key names the plugin this harness pairs with. All harness-folder frontmatter lives in `index.md` alone.
+- `readme.md` — the **manifest**: identity (name, description, version, keywords) plus the shared `skills:`/`rules:`/`agents:` lists it pulls in from the top-level catalogs. Its body becomes the harness's published README.
+- `CLAUDE.md` — the **policy**: pure policy, no frontmatter, installed as a verbatim copy at the consumer repo's root.
+- Any owned `agents/`, `rules/`, `hooks/`, `scripts/` — purpose-built components that belong to this harness alone.
+
+Shared root config common to every harness (`.prettierrc.json`, `.prettierignore`, `.vscode/settings.json`) lives once, in `harness/common/`, instead of duplicated per harness.
 
 Two kinds of membership:
 
-- **Shared, listed** — skills, rules, and agents live in the flat top-level `skills/`/`rules/`/`agents/` catalogs, reusable across plugins. The manifest names the ones it pulls in:
+- **Shared, listed** — skills, rules, and agents live in the flat top-level `skills/`/`rules/`/`agents/` catalogs, reusable across harnesses. The manifest names the ones it pulls in:
 
 ```yaml
-# plugins/code/definition.md
+# harness/code/readme.md
 ---
 name: code
 skills: [boundary, brainstorm, documentation, workflow-mapper, design]
@@ -90,9 +93,9 @@ agents: [brainstorm, change-review, lld-mode, maintenance, performance-review]
 ---
 ```
 
-- **Owned, by location** — hooks (and any unlisted, harness-specific agents) live inside the plugin (`plugins/<name>/{agents,hooks}/`). No list — membership is presence in the folder, exactly how a Claude Code plugin ships them. Shared governance agents are listed instead (above) and resolved from the `agents/` catalog, local-first; a plugin can still drop its own copy beside it to override one by name.
+- **Owned, by location** — hooks, scripts (and any unlisted, harness-specific agents) live inside the harness folder (`harness/<name>/{agents,hooks,scripts}/`). No list — membership is presence in the folder, exactly how a Claude Code plugin ships them. Shared governance agents are listed instead (above) and resolved from the `agents/` catalog, local-first; a harness can still drop its own copy beside it to override one by name.
 
-`scripts/build-data.js` (run by `prepack`) resolves the listed skills/rules/agents from the catalogs (local-first), copies any unlisted plugin-owned agents plus the plugin's `hooks/` wholesale into `data/harnesses/<folder>/`; a listed skill/rule/agent that doesn't exist is a hard error. The marketplace channel (`.github/scripts/publish.mjs`) reads the same plugin folder, so both channels resolve identical membership — and both ship the plugin's hooks. The installer (`bin/etna.js`) reads from the bundle at install time; no GitHub fetch at runtime.
+`scripts/build-data.js` (run by `prepack`) resolves the listed skills/rules/agents from the catalogs (local-first), copies any unlisted harness-owned agents plus the harness's `hooks/` and `scripts/` wholesale into `data/harnesses/<folder>/`; a listed skill/rule/agent that doesn't exist is a hard error. The marketplace channel (`.github/scripts/publish.mjs`) reads the same harness folder, so both channels resolve identical membership — and both ship the harness's hooks and scripts. The installer (`bin/etna.js`) reads from the bundle at install time; no GitHub fetch at runtime.
 
 ## Building / contributing
 

package/data/harness-index.json

@@ -1,9 +1,9 @@
 {
-    "fingerprint": "560f385fe688",
+    "fingerprint": "a7791e9cf297",
     "harnesses": {
         "code": {
             "plugin": "code",
-            "description": "Nurix code-project harness"
+            "description": "the foundation every Nurix project starts with"
         },
         "discover": {
             "plugin": "discover",

package/data/harnesses/code/harness.json

@@ -1,11 +1,11 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.1.11",
+  "version": "3.1.12",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "99962f63174b"
+  "digest": "cc025f7950c3"
 }

package/data/harnesses/code/hooks/generate-ownership-index.mjs

@@ -1,4 +1,4 @@
-// plugins/code/hooks/generate-ownership-index.mjs — SessionStart hook: scan docs/features/**/*.md,
+// harness/code/hooks/generate-ownership-index.mjs — SessionStart hook: scan docs/features/**/*.md,
 // extract the focal frontmatter (owns / module / keywords / status), and inject a compact
 // code-path → owning-doc index via additionalContext. Fires on startup/resume/clear/compact so the
 // map survives /clear and /compact and is regenerated fresh every time. Writes no file.

package/data/harnesses/discover/CLAUDE.md

@@ -40,7 +40,7 @@ Agent name = dimension name. ⚠ = gated (needs user authorization before dispat
 
 Cheap, read-only. Scope the target, grade its access, detect which dimensions it exposes.
 
-**0. Resolve the corpus root** — the folder this run writes into. The harness chooses it _intelligently_ rather than hardcoding one: default `research/` at the repo root, but if the project already holds a discovery corpus (any folder with a prior run's `*/00-scope-verdict.md`) under another name (`recon/`, `discovery/`, `teardowns/`, `analysis/`, …) **reuse it**, and honor a folder the user names. **Confirm the chosen root in one line** before writing. Every `research/<target>/` path in this harness is the _default form_ — read it as `<corpus>/<target>/`, relative to the resolved root.
+**0. Resolve the corpus root** — the folder this run writes into. The harness chooses it _intelligently_ rather than hardcoding one: default `research/` at the repo root, but if the project already holds a discovery corpus (any folder with a prior run's `*/00-scope-verdict.md`) under another name (`discovery/`, `analysis/`, …) **reuse it**, and honor a folder the user names. **Confirm the chosen root in one line** before writing. Every `research/<target>/` path in this harness is the _default form_ — read it as `<corpus>/<target>/`, relative to the resolved root.
 
 1. **Scope-feasibility gate** — run the `.claude/rules/discovery.md` Part A (scope gate) algorithm: resolve identity → ambiguity → ethics → suite-size → primitive → reachability. If the verdict isn't `accept`, **halt** (present the narrowing/redirect prompt, or refuse). Write `research/<target>/00-scope-verdict.md`.
 2. **Grade the access vector** (the four axes, with evidence) per `discovery` (Part B).

package/data/harnesses/discover/harness.json

@@ -1,11 +1,11 @@
 {
   "harness": "discover",
   "name": "discover",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "e19de8dc405a"
+  "digest": "a672787b9962"
 }

package/data/harnesses/discover/rules/discovery.md

@@ -14,7 +14,7 @@ The reference knowledge for **Discovery** (`discover` harness, Mode 1). It carri
 
 Before Part A, decide **where this run writes** — the harness picks intelligently, it does not hardcode `research/`:
 
-1. **Reuse an existing discovery corpus** if the project has one — search for any folder containing a prior run's `*/00-scope-verdict.md` (commonly `research/`, but also `recon/`, `discovery/`, `teardowns/`, `analysis/`, or a folder the user names).
+1. **Reuse an existing discovery corpus** if the project has one — search for any folder containing a prior run's `*/00-scope-verdict.md` (commonly `research/`, but also `discovery/`, `analysis/`, or a folder the user names).
 2. If several exist, prefer the one the user points at, else the most recently written.
 3. If none exists and the user hasn't named one, default to `research/` at the repo root.
 4. **Confirm the chosen root in one line** before writing `00-scope-verdict.md`.

package/data/harnesses/discover/rules/evaluation.md

@@ -107,7 +107,7 @@
 
 ## Pricing & packaging (plans, what gates what, unit economics — website pricing + platform/limits)
 
-## Differentiation (claimed moat vs the teardown's read of the real moat — often infra/data)
+## Differentiation (claimed moat vs the discovery's read of the real moat — often infra/data)
 
 ## Alternatives & comparison (named competitors + how it differs)
 

package/data/harnesses/discover/rules/tradecraft.md

@@ -1,6 +1,6 @@
 # Discover Harness — Session & Wire Tradecraft (keyboard-level reference)
 
-The executable field layer the browser-driving dimensions (`session`, `wire-capture`) reach for at the keyboard. Everything here is **runnable verbatim** — taps, scrubbers, escape snippets — not prose to re-derive. It is the distilled tradecraft from real teardowns; the `§1.x`/`§2.x` anchors are the origin tags from those runs.
+The executable field layer the browser-driving dimensions (`session`, `wire-capture`) reach for at the keyboard. Everything here is **runnable verbatim** — taps, scrubbers, escape snippets — not prose to re-derive. It is the distilled tradecraft from real discovery runs; the `§1.x`/`§2.x` anchors are the origin tags from those runs.
 
 **How the dimensions use this file:**
 

package/data/harnesses/discussion/harness.json

@@ -1,10 +1,10 @@
 {
   "harness": "discussion",
   "name": "discussion",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "digest": "51812973828b"

package/data/harnesses/etna/CLAUDE.md

@@ -27,7 +27,7 @@ etna authors the components it also runs and ships, so **three copies of every c
 
 | Copy | Where | Role |
 | --- | --- | --- |
-| **Source** (canonical) | the shared catalogs — `skills/`, `agents/`, `rules/`, plus `plugins/*/` (composition) and `harness/*/` (harness definitions) | Edit here. Etna is the source of truth. |
+| **Source** (canonical) | the shared catalogs — `skills/`, `agents/`, `rules/`, plus `harness/*/` (each harness — its `readme.md` manifest, `CLAUDE.md` policy, and owned trees in one folder) | Edit here. Etna is the source of truth. |
 | **Dogfood** | `.claude/skills/`, `.claude/agents/`, `.claude/rules/`, `.claude/hooks/` (git-tracked) | The subset the `etna` harness installs on itself — the copy this repo actually runs this session. |
 | **Shipped bundle** | `packages/cli/data/harnesses/*/` (git-tracked build artifact, regenerated by `packages/cli/scripts/build-data.js`) | Generated — never hand-edit. |
 
@@ -38,7 +38,7 @@ etna authors the components it also runs and ships, so **three copies of every c
 
 ## Workflows
 
-Three peer modes plus a Completion step — enter wherever the user's thinking already is. Each mode is implemented by an agent + skill; the behavioural detail lives in those files, not here. "Code" below means **authoring artifacts** — a feature LLD owns `skills/**`, `plugins/**`, `packages/cli/**`, not `src/`.
+Three peer modes plus a Completion step — enter wherever the user's thinking already is. Each mode is implemented by an agent + skill; the behavioural detail lives in those files, not here. "Code" below means **authoring artifacts** — a feature LLD owns `skills/**`, `harness/**`, `packages/cli/**`, not `src/`.
 
 | Mode | Enter when | Implemented by | Exits to |
 | --- | --- | --- | --- |
@@ -64,7 +64,7 @@ These three mechanisms keep the repo self-updating: **ownership** routes you to
 
 ### Ownership — route before you edit
 
-Which doc is canonical for which paths is the **feature doc's own frontmatter**. A feature doc (flat in `docs/features/`) carries `owns:` (path globs — the only ownership key, pointing at `skills/**`, `plugins/**`, `packages/cli/**`, …), an optional `module:` label, `keywords:`, and `status:`. Path → doc ownership is the union of every feature doc's `owns:` globs, surfaced as the generated ownership index at session start. Architecture docs describe cross-cutting patterns and own nothing; operations docs describe procedures.
+Which doc is canonical for which paths is the **feature doc's own frontmatter**. A feature doc (flat in `docs/features/`) carries `owns:` (path globs — the only ownership key, pointing at `skills/**`, `harness/**`, `packages/cli/**`, …), an optional `module:` label, `keywords:`, and `status:`. Path → doc ownership is the union of every feature doc's `owns:` globs, surfaced as the generated ownership index at session start. Architecture docs describe cross-cutting patterns and own nothing; operations docs describe procedures.
 
 Before modifying a component in an unfamiliar area:
 
@@ -77,7 +77,7 @@ The `lld-mode` agent checks for ownership conflicts during LLD research — feat
 
 etna has no db schema, wire envelope, or auth of its own — the `boundary` skill's stack mechanisms describe the contracts of the **rules etna ships**, checked in the consumer's repo, not here. etna's **own** live contracts are authoring and distribution ones, each with no static link between the two sides:
 
-- a plugin `definition.md`'s `skills:` / `rules:` / `agents:` list ↔ the shared catalogs it resolves from (local-first);
+- a harness `readme.md` manifest's `skills:` / `rules:` / `agents:` list ↔ the shared catalogs it resolves from (local-first);
 - a component's **source ↔ `.claude/` dogfood ↔ shipped bundle** (three-way parity, per Authoring & Distribution);
 - a hook script ↔ its `hooks.json` registration;
 - the CLI's managed-block edits ↔ a consumer's `settings.json` / `.env`.

package/data/harnesses/etna/harness.json

@@ -1,11 +1,11 @@
 {
   "harness": "etna",
   "name": "etna",
-  "version": "1.1.8",
+  "version": "1.1.9",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "e4e80329bda9"
+  "digest": "b93279e6959d"
 }

package/data/harnesses/hr/harness.json

@@ -1,10 +1,10 @@
 {
   "harness": "hr",
   "name": "hr",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "digest": "1d5cfc7eb67e"

package/data/harnesses/kb-agi/harness.json

@@ -1,10 +1,10 @@
 {
   "harness": "kb-agi",
   "name": "kb-agi",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "files": [
-    ".prettierrc.json",
     ".prettierignore",
+    ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "digest": "11b127dd4a61"

package/lib/codex/README.md

@@ -25,7 +25,7 @@ Owning doc: [`docs/features/codex-support.md`](../../../../docs/features/codex-s
 ```bash
 node packages/cli/lib/codex/gen-agents.mjs                 # shared catalog (agents/*.md), stale/missing only
 node packages/cli/lib/codex/gen-agents.mjs --force          # regenerate all shared agents
-node packages/cli/lib/codex/gen-agents.mjs --include-plugins # + plugins/*/agents/*.md
+node packages/cli/lib/codex/gen-agents.mjs --include-harness # + harness/*/agents/*.md
 ```
 
 `gen-agents.mjs` runs `codex exec` per agent and writes a committed `agents/<name>.codex.toml` sibling. It runs **only on a laptop with `codex` installed + authenticated — never in CI**. `build-data.js` and `publish.mjs` then ship those committed TOML; the installer copies them, so **consumers need no Codex CLI**. Regenerate an agent's TOML in the same change that edits its `.md` (source↔generated parity).

package/lib/codex/gen-agents.mjs

@@ -1,7 +1,7 @@
 // packages/cli/lib/codex/gen-agents.mjs
 // AUTHORING-TIME generator — runs ON A LAPTOP with the Codex CLI installed and
 // authenticated, NEVER in CI. For each Claude subagent (agents/<name>.md in the
-// shared catalog, plus plugins/*/agents/*.md with --include-plugins) it runs
+// shared catalog, plus harness/*/agents/*.md with --include-harness) it runs
 // `codex exec` to translate the markdown into an OpenAI Codex subagent TOML and
 // writes a committed sibling agents/<name>.codex.toml. The shippers (build-data.js,
 // publish.mjs) then carry those committed files; the installer copies them into a
@@ -10,7 +10,7 @@
 // Usage:
 //   node packages/cli/lib/codex/gen-agents.mjs            # shared catalog, only stale/missing
 //   node packages/cli/lib/codex/gen-agents.mjs --force    # regenerate all shared agents
-//   node packages/cli/lib/codex/gen-agents.mjs --include-plugins  # + plugins/*/agents/*.md
+//   node packages/cli/lib/codex/gen-agents.mjs --include-harness  # + harness/*/agents/*.md
 
 import {
     existsSync,
@@ -45,7 +45,7 @@ const CONVERSION_PROMPT = [
 
 const args = process.argv.slice(2);
 const force = args.includes('--force');
-const includePlugins = args.includes('--include-plugins');
+const includeHarness = args.includes('--include-harness');
 
 function die(msg) {
     console.error(`gen-codex-agents: ${msg}`);
@@ -60,7 +60,7 @@ function assertCodexReady() {
     }
 }
 
-// Every agents/<name>.md to convert: the shared catalog, plus plugin-owned agents on request.
+// Every agents/<name>.md to convert: the shared catalog, plus harness-owned agents on request.
 function collectAgentFiles() {
     const files = [];
     const shared = join(repoRoot, 'agents');
@@ -69,11 +69,12 @@ function collectAgentFiles() {
             if (f.endsWith('.md')) files.push(join(shared, f));
         }
     }
-    if (includePlugins) {
-        const pluginsDir = join(repoRoot, 'plugins');
-        if (existsSync(pluginsDir)) {
-            for (const plugin of readdirSync(pluginsDir)) {
-                const agentsDir = join(pluginsDir, plugin, 'agents');
+    if (includeHarness) {
+        const harnessDir = join(repoRoot, 'harness');
+        if (existsSync(harnessDir)) {
+            for (const harness of readdirSync(harnessDir)) {
+                if (harness === 'common') continue; // not a harness — the shared root-files folder
+                const agentsDir = join(harnessDir, harness, 'agents');
                 if (!existsSync(agentsDir)) continue;
                 for (const f of readdirSync(agentsDir)) {
                     if (f.endsWith('.md')) files.push(join(agentsDir, f));

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.19.15",
+    "version": "0.19.17",
     "description": "Bootstrap a project with a Nurix harness — copies the harness's CLAUDE.md, skills, agents, rules, and hooks directly into the project from a bundled payload (no marketplace fetch, no network).",
     "type": "module",
     "bin": {