@nurix/etna 0.19.12 → 0.19.13

package/README.md

@@ -9,15 +9,17 @@ A second install path also exists and is fully supported: `/plugin install <plug
 From the root of the project you want to bootstrap, pick a harness from the interactive menu:
 
 ```sh
-npx @nurix/etna
+npx --yes @nurix/etna
 ```
 
 …or install one directly by name:
 
 ```sh
-npx @nurix/etna --name=code
+npx --yes @nurix/etna --name=code
 ```
 
+The `--yes` flag skips npx's install confirmation, so the command runs unattended. On startup the CLI also **self-updates**: it checks the registry and, if the copy npx resolved is behind the latest published version, re-execs the latest before installing — so `npx --yes @nurix/etna` always runs the newest harness, even when npx has an older copy cached. The check is quick but synchronous; set `ETNA_NO_SELFUPDATE=1` to skip it (CI, offline, or a pinned local build).
+
 After this completes:
 
 ```
@@ -37,7 +39,7 @@ your-project/
 
 That's the entire footprint. Nothing is written outside the project. No marketplace registration, no `enabledPlugins` entry, no global cache dependency — Claude Code picks up the project-scoped agents/skills/rules on its next session start, and the hooks wire in through `.claude/settings.json`.
 
-Re-run `npx @nurix/etna --name=code` anytime to refresh the harness content with what the latest published package ships. Existing same-named files are overwritten; files you've added that aren't part of the harness are left alone. In a git repo the previous `CLAUDE.md` is overwritten in place (recover it with `git checkout CLAUDE.md`); outside a git repo it's backed up to `CLAUDE.md.bak.<ISO-timestamp>`. Because the new `harness.json` carries the installed `{version, digest}`, a re-run whose **major** version is ahead of your repo's stamped `harness-version` is what the reconcile (below) detects as a structural upgrade.
+Re-run `npx --yes @nurix/etna --name=code` anytime to refresh the harness content with what the latest published package ships. Existing same-named files are overwritten; files you've added that aren't part of the harness are left alone. In a git repo the previous `CLAUDE.md` is overwritten in place (recover it with `git checkout CLAUDE.md`); outside a git repo it's backed up to `CLAUDE.md.bak.<ISO-timestamp>`. Because the new `harness.json` carries the installed `{version, digest}`, a re-run whose **major** version is ahead of your repo's stamped `harness-version` is what the reconcile (below) detects as a structural upgrade.
 
 ## After install: bootstrap the harness
 
@@ -60,7 +62,7 @@ The `nurixlabs` marketplace entry in `~/.claude/settings.json` is harmless to le
 
 ## Available harnesses
 
-Listed by `npx @nurix/etna` (no args) using the bundled `data/harness-index.json`.
+Listed by `npx --yes @nurix/etna` (no args) using the bundled `data/harness-index.json`.
 
 | Plugin name | Source in etna | What it ships |
 | --- | --- | --- |

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "c645e418f50b",
+    "fingerprint": "13b2eaeeecb2",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/agents/maintenance.md

@@ -23,7 +23,7 @@ Out of scope (handled by the `boundary` skill, which derives contracts dynamical
 
 Decide the mode once, up front, from the version marker — then run.
 
-1. Resolve the **installed harness version** (semver): read `version` from `.claude/harness.json`, shipped by the CLI at install. Never a number baked into this file. If `.claude/harness.json` is absent, the install predates the marker ⇒ instruct the user to re-run `npx @nurix/etna --name=<harness>`, then retry. The resolved version's **major** is the structural-shape signal — a major bump means the mandated `docs/` shape changed.
+1. Resolve the **installed harness version** (semver): read `version` from `.claude/harness.json`, shipped by the CLI at install. Never a number baked into this file. If `.claude/harness.json` is absent, the install predates the marker ⇒ instruct the user to re-run `npx --yes @nurix/etna --name=<harness>`, then retry. The resolved version's **major** is the structural-shape signal — a major bump means the mandated `docs/` shape changed.
 2. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter (a semver).
    - **Absent** ⇒ the repo is unharnessed ⇒ **baseline mode** (reconcile from nothing), then audit.
    - **Behind on major** ⇒ the mandated shape changed ⇒ **baseline mode** (reconcile across the gap), then audit.

package/data/harnesses/code/harness.json

@@ -7,5 +7,5 @@
     ".prettierignore",
     ".vscode/settings.json"
   ],
-  "digest": "92dafa9099ea"
+  "digest": "12a37e3bf155"
 }

package/data/harnesses/discussion/agents/discussion-baseline.md

@@ -11,7 +11,7 @@ You are the **discussion-baseline** agent. One job: converge a workspace to the
 
 Decide once, up front, from two reads:
 
-- **Installed version** — `version` in `.claude/harness.json`, shipped by the CLI at install. If `harness.json` is absent, stop and instruct the user to run `npx @nurix/etna --name=discussion`, then retry.
+- **Installed version** — `version` in `.claude/harness.json`, shipped by the CLI at install. If `harness.json` is absent, stop and instruct the user to run `npx --yes @nurix/etna --name=discussion`, then retry.
 - **Workspace version** — the `harness-version:` field in the YAML frontmatter of `metadata/TOPICS.md`.
 
 | Workspace version | Mode |

package/data/harnesses/discussion/harness.json

@@ -7,5 +7,5 @@
     ".prettierignore",
     ".vscode/settings.json"
   ],
-  "digest": "670ff91f4b1b"
+  "digest": "6fc08db4ab3c"
 }

package/data/harnesses/etna/agents/maintenance.md

@@ -23,7 +23,7 @@ Out of scope (handled by the `boundary` skill, which derives contracts dynamical
 
 Decide the mode once, up front, from the version marker — then run.
 
-1. Resolve the **installed harness version** (semver): read `version` from `.claude/harness.json`, shipped by the CLI at install. Never a number baked into this file. If `.claude/harness.json` is absent, the install predates the marker ⇒ instruct the user to re-run `npx @nurix/etna --name=<harness>`, then retry. The resolved version's **major** is the structural-shape signal — a major bump means the mandated `docs/` shape changed.
+1. Resolve the **installed harness version** (semver): read `version` from `.claude/harness.json`, shipped by the CLI at install. Never a number baked into this file. If `.claude/harness.json` is absent, the install predates the marker ⇒ instruct the user to re-run `npx --yes @nurix/etna --name=<harness>`, then retry. The resolved version's **major** is the structural-shape signal — a major bump means the mandated `docs/` shape changed.
 2. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter (a semver).
    - **Absent** ⇒ the repo is unharnessed ⇒ **baseline mode** (reconcile from nothing), then audit.
    - **Behind on major** ⇒ the mandated shape changed ⇒ **baseline mode** (reconcile across the gap), then audit.

package/data/harnesses/etna/harness.json

@@ -7,5 +7,5 @@
     ".prettierignore",
     ".vscode/settings.json"
   ],
-  "digest": "ac886b2bc4b1"
+  "digest": "cfa478ce100b"
 }

package/data/harnesses/hr/CLAUDE.md

@@ -21,7 +21,7 @@ Pick the mode from what the user hands you:
 
 ## Step 0 — first run
 
-If the `interview-eval` skill isn't resolvable (no `.claude/skills/interview-eval/`), this project isn't set up — tell the user to run `npx @nurix/etna --name=hr` (or point you at the skill) before continuing. Confirm `python3` is on PATH; the extractor is stdlib-only and needs nothing else.
+If the `interview-eval` skill isn't resolvable (no `.claude/skills/interview-eval/`), this project isn't set up — tell the user to run `npx --yes @nurix/etna --name=hr` (or point you at the skill) before continuing. Confirm `python3` is on PATH; the extractor is stdlib-only and needs nothing else.
 
 ## Step 1 — intake interview
 

package/data/harnesses/hr/harness.json

@@ -7,5 +7,5 @@
     ".prettierignore",
     ".vscode/settings.json"
   ],
-  "digest": "6d11004d6849"
+  "digest": "1d5cfc7eb67e"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.19.12",
+    "version": "0.19.13",
     "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": {