@nurix/etna 0.17.0 → 0.18.0

package/README.md

@@ -6,17 +6,26 @@ A second install path also exists and is fully supported: `/plugin install <plug
 
 ## Usage
 
-From the root of the project you want to bootstrap:
+From the root of the project you want to bootstrap, pick a harness from the interactive menu:
 
 ```sh
-npx @nurix/etna code
+npx @nurix/etna
+```
+
+…or install one directly by name:
+
+```sh
+npx @nurix/etna --name=code
 ```
 
 After this completes:
 
 ```
 your-project/
-├── CLAUDE.md              ← harness policy (your existing file → CLAUDE.md.bak.<ISO>)
+├── CLAUDE.md              ← harness policy (non-git repo: existing file → CLAUDE.md.bak.<ISO>)
+├── .prettierrc.json       ← markdown formatting (proseWrap: never)
+├── .prettierignore
+├── .vscode/settings.json  ← editor settings (markdown formatter on save)
 └── .claude/
     ├── skills/            ← documentation, boundary, distiller, brainstorm, workflow-mapper
     ├── agents/            ← harness-manager, spec-mode, brainstorm, maintenance, change-review, performance-review
@@ -28,7 +37,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 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. The previous `CLAUDE.md` is backed up to `CLAUDE.md.bak.<ISO-timestamp>`. Because the new `harness.json` carries the installed `{version, epoch, digest}`, a re-run that's ahead of your repo's stamped `harness-version` is what the reconcile (below) detects as an upgrade.
+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, epoch, digest}`, a re-run that's ahead of your repo's stamped `harness-version` is what the reconcile (below) detects as an upgrade.
 
 ## After install: bootstrap the harness
 

package/bin/etna.js

@@ -1,11 +1,14 @@
 #!/usr/bin/env node
 // packages/cli/bin/etna.js
-// `npx @nurix/etna <harness-name>` — copy a Nurix harness into the current
-// directory. Drops the harness's CLAUDE.md at the project root and copies its
-// skills, agents, rules, and scripts into <project>/.claude/. No marketplace,
-// no plugin enablement — files live in the project, version-controlled and
-// editable per project. Re-run `etna` to refresh. Harnesses are addressed by
-// their harness/<folder> name; several harnesses may share one plugin.
+// `npx @nurix/etna [harness-name]` — copy a Nurix harness into the current
+// directory. Given a name it installs straight away; with no name (in a TTY) it
+// prompts you to pick one. Drops the harness's CLAUDE.md + project-root config
+// files (.prettierrc.json, .vscode/settings.json, …) at the project root, and
+// copies its skills, agents, rules, scripts, and hooks into <project>/.claude/.
+// No marketplace, no plugin enablement — files live in the project,
+// version-controlled and editable per project. Re-run `etna` to refresh.
+// Harnesses are addressed by their harness/<folder> name; several harnesses may
+// share one plugin.
 
 import {
     existsSync,
@@ -20,6 +23,7 @@ import {
 } from 'node:fs';
 import { join, dirname, resolve } from 'node:path';
 import { fileURLToPath } from 'node:url';
+import * as p from '@clack/prompts';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const pkgRoot = resolve(__dirname, '..');
@@ -31,29 +35,38 @@ const dataDir = join(pkgRoot, 'data');
 // the settings merge reads it from the bundle, not the project copy).
 const PLUGIN_SUBDIRS = ['skills', 'agents', 'rules', 'scripts', 'hooks'];
 
-function usage() {
-    const idx = loadHarnessIndex();
-    console.log(`\nUsage: npx @nurix/etna <harness-name>\n`);
-    const entries = Object.entries(idx.harnesses || {});
-    if (entries.length) {
-        console.log(`Available harnesses:`);
-        for (const [folder, plugin] of entries) {
-            console.log(`  ${folder}${plugin && plugin !== folder ? ` (plugin: ${plugin})` : ''}`);
-        }
+const sleep = (ms) => new Promise((r) => setTimeout(r, ms));
+
+// True when both stdin and stdout are a terminal — clack prompts can't resolve
+// otherwise (CI, piped stdin), so the no-arg pick must fall back to an error.
+function isInteractive() {
+    return Boolean(process.stdin.isTTY && process.stdout.isTTY);
+}
+
+// Boxed list of installable harnesses (name + description), for --help and error paths.
+function printHarnessList(harnesses) {
+    const entries = Object.entries(harnesses);
+    if (!entries.length) {
+        p.log.warn('No harnesses are bundled. Run `npm run build:data` from the package root.');
+        return;
     }
-    console.log();
+    const width = Math.max(...entries.map(([folder]) => folder.length));
+    const lines = entries.map(
+        ([folder, meta]) => `${folder.padEnd(width)}${meta?.description ? `  ${meta.description}` : ''}`,
+    );
+    p.note(lines.join('\n'), 'Available harnesses');
 }
 
 function loadHarnessIndex() {
     const path = join(dataDir, 'harness-index.json');
     if (!existsSync(path)) {
-        die(`harness-index.json missing — run \`npm run build:data\` from the package root.`);
+        die('harness-index.json missing — run `npm run build:data` from the package root.');
     }
     return JSON.parse(readFileSync(path, 'utf8'));
 }
 
 function die(msg, code = 1) {
-    console.error(`error: ${msg}`);
+    p.log.error(msg);
     process.exit(code);
 }
 
@@ -204,22 +217,44 @@ function mergeHooks(targetDir, bundledHooksJson) {
     return added;
 }
 
-async function main(args) {
-    if (args.includes('-h') || args.includes('--help') || args.length === 0) {
-        usage();
-        process.exit(args.length === 0 ? 1 : 0);
+// Resolve the harness to install: the --name value, or — in a TTY — an interactive pick
+// showing each harness's description. Returns the chosen folder, or null on cancel.
+async function resolveHarnessName(name, harnesses) {
+    const names = Object.keys(harnesses);
+    if (name !== null) {
+        if (!name || !harnesses[name]) {
+            p.log.error(name ? `Unknown harness '${name}'.` : 'Empty --name value.');
+            printHarnessList(harnesses);
+            p.outro('Pass --name=<harness> with one of the names above.');
+            process.exit(1);
+        }
+        return name;
     }
-
-    const harnessName = args[0];
-    const idx = loadHarnessIndex();
-    const harnesses = idx.harnesses || {};
-    if (!harnesses[harnessName]) {
-        die(
-            `Unknown harness '${harnessName}'. Available: ${Object.keys(harnesses).join(', ') || '(none)'}`,
-        );
+    if (!isInteractive()) {
+        p.log.error('No --name given, and not running in an interactive terminal.');
+        printHarnessList(harnesses);
+        p.outro('Re-run as `npx @nurix/etna --name=<harness>`.');
+        process.exit(1);
     }
-    const harnessFolder = harnessName;
+    const choice = await p.select({
+        message: 'Which harness do you want to install here?',
+        options: names.map((folder) => ({
+            value: folder,
+            label: folder,
+            hint: harnesses[folder]?.description || undefined,
+        })),
+    });
+    if (p.isCancel(choice)) {
+        p.cancel('Cancelled — nothing installed.');
+        return null;
+    }
+    return choice;
+}
 
+// Copy one harness's bundled payload into the current directory. All file ops run
+// inside a spinner; the per-item detail + any warnings are emitted after it stops.
+async function installHarness(harnessName, harnesses) {
+    const harnessFolder = harnessName;
     const bundledHarnessDir = join(dataDir, 'harnesses', harnessFolder);
     const bundledClaudeMd = join(bundledHarnessDir, 'CLAUDE.md');
     if (!existsSync(bundledClaudeMd)) {
@@ -229,40 +264,44 @@ async function main(args) {
     const targetDir = process.cwd();
     const claudeMdDest = join(targetDir, 'CLAUDE.md');
 
-    // Read the bundled epoch marker up front so the install banner can name the
-    // harness version; the file itself is copied into the project further down.
+    // Bundled epoch marker — names the version for the banner and carries the
+    // `files` list (project-root config shipped outside the plugin route).
     const bundledHarnessJson = join(bundledHarnessDir, 'harness.json');
     const harnessMeta = existsSync(bundledHarnessJson) ? readJson(bundledHarnessJson) : {};
     const versionTag = harnessMeta.version ? ` v${harnessMeta.version}` : '';
     // The underlying plugin's name — may differ from the harness name, and several
     // harnesses may share it. Used only for legacy marketplace-entry cleanup.
-    const pluginName = harnessMeta.name || harnesses[harnessName] || harnessName;
-
-    console.log(`\nInstalling ${harnessName}${versionTag} into ${targetDir}`);
+    const pluginName = harnessMeta.name || harnesses[harnessName]?.plugin || harnessName;
 
-    const claudeBackup = backupIfExists(claudeMdDest);
-    if (claudeBackup) console.log(`  backed up existing CLAUDE.md → ${claudeBackup}`);
+    const spin = p.spinner();
+    spin.start(`Installing ${harnessName}${versionTag} into ${targetDir}`);
 
-    // CLAUDE.md ships frontmatter-free (the harness's metadata lives in its index.md and the
-    // plugin's definition.md), so it installs as a verbatim copy — no stripping.
-    // Tracks the categories actually present in this harness, for the closing
-    // summary — so a harness that ships no skills or hooks reads as an explicit,
-    // honest list rather than a silently missing line.
     const installed = [];
-
+    const notices = [];
+    const warnings = [];
+
+    // CLAUDE.md ships frontmatter-free, so it installs as a verbatim copy — no stripping.
+    // It's harness-owned and overwritten in place. If the project is a git repo the old copy
+    // is recoverable from history, so we skip the backup; if it isn't, there's no safety net,
+    // so we back it up and tell the user. (Backup applies to CLAUDE.md only.)
+    const claudeExisted = existsSync(claudeMdDest) || isSymlink(claudeMdDest);
+    const projectHasGit = existsSync(join(targetDir, '.git'));
+    if (claudeExisted) {
+        if (projectHasGit) {
+            notices.push('Overwrote existing CLAUDE.md (tracked by git — `git checkout CLAUDE.md` to restore).');
+        } else {
+            const claudeBackup = backupIfExists(claudeMdDest);
+            warnings.push(
+                `No .git here, so no version-control safety net — backed up existing CLAUDE.md → ${claudeBackup}`,
+            );
+        }
+    }
     cpSync(bundledClaudeMd, claudeMdDest, { force: true });
-    console.log(`  installed CLAUDE.md → ${claudeMdDest}`);
-    installed.push('CLAUDE.md');
+    installed.push('CLAUDE.md → ./');
 
     for (const sub of PLUGIN_SUBDIRS) {
-        const count = copyHarnessSubdir(
-            join(bundledHarnessDir, sub),
-            join(targetDir, '.claude', sub),
-        );
-        if (count > 0) {
-            console.log(`  copied ${count} ${sub} → ${targetDir}/.claude/${sub}/`);
-            installed.push(`${count} ${sub}`);
-        }
+        const count = copyHarnessSubdir(join(bundledHarnessDir, sub), join(targetDir, '.claude', sub));
+        if (count > 0) installed.push(`${count} ${sub} → .claude/${sub}/`);
     }
 
     // Copy the epoch marker so harness-manager can resolve the installed epoch.
@@ -270,33 +309,103 @@ async function main(args) {
         const harnessJsonDest = join(targetDir, '.claude', 'harness.json');
         mkdirSync(dirname(harnessJsonDest), { recursive: true });
         cpSync(bundledHarnessJson, harnessJsonDest, { force: true });
-        const tag = [harnessMeta.version && `v${harnessMeta.version}`, harnessMeta.epoch && `epoch ${harnessMeta.epoch}`]
-            .filter(Boolean)
-            .join(', ');
-        console.log(`  installed harness.json → ${harnessJsonDest}${tag ? ` (${tag})` : ''}`);
+    }
+
+    // Verbatim project-root files bundled outside the plugin route (.prettierrc.json,
+    // .vscode/settings.json, …), listed in harness.json's `files`. They land at the project
+    // root at their relative path — NOT under .claude/ — and overwrite unconditionally with no
+    // backup: the harness owns this config, and re-running etna refreshes it.
+    for (const rel of harnessMeta.files || []) {
+        const src = join(bundledHarnessDir, rel);
+        if (!existsSync(src)) continue;
+        const dest = join(targetDir, rel);
+        mkdirSync(dirname(dest), { recursive: true });
+        cpSync(src, dest, { recursive: true, force: true });
+        installed.push(`${rel} → ./${rel}`);
     }
 
     // Retire hooks earlier epochs shipped before merging, so the additive merge
     // never resurrects an entry pointing at a script this bundle no longer carries.
-    const retiredHooks = retireOldHooks(targetDir);
-    for (const r of retiredHooks) console.log(`  removed ${r}`);
+    for (const r of retireOldHooks(targetDir)) notices.push(`removed ${r}`);
 
     // Merge the bundle's hooks.json into the project's settings.json (idempotent).
     const added = mergeHooks(targetDir, join(bundledHarnessDir, 'hooks', 'hooks.json'));
-    if (added > 0) {
-        console.log(`  merged ${added} hook(s) → ${targetDir}/.claude/settings.json`);
+    if (added > 0) installed.push(`${added} hook(s) → .claude/settings.json`);
+
+    for (const entry of migrateFromPluginInstall(targetDir, pluginName)) {
+        notices.push(`removed stale ${entry}`);
     }
 
-    const migrated = migrateFromPluginInstall(targetDir, pluginName);
-    for (const entry of migrated) console.log(`  removed stale ${entry}`);
+    spin.stop(`Installed ${harnessName}${versionTag}`);
+
+    p.note(installed.join('\n'), 'Written');
+    for (const notice of notices) p.log.info(notice);
+    for (const warning of warnings) p.log.warn(warning);
 
-    console.log(`\nDone — ${harnessName}${versionTag} installed: ${installed.join(', ')}.`);
-    console.log(
-        `Open Claude Code in ${targetDir}. Re-run \`npx @nurix/etna ${harnessName}\` anytime to refresh harness content.\n`,
+    p.outro(
+        `${harnessName}${versionTag} ready in ${targetDir}. ` +
+            `Re-run \`npx @nurix/etna --name=${harnessName}\` anytime to refresh harness content.`,
     );
 }
 
+// Parse argv. `--name=<harness>` / `--name <harness>` selects a harness; -h/--help shows
+// help; any other bare token is the dropped positional form (a breaking change in 0.18.0).
+function parseArgs(args) {
+    let name = null;
+    let help = false;
+    let positional = null;
+    for (let i = 0; i < args.length; i++) {
+        const a = args[i];
+        if (a === '-h' || a === '--help') help = true;
+        else if (a.startsWith('--name=')) name = a.slice('--name='.length);
+        else if (a === '--name') name = args[++i] ?? '';
+        else if (!a.startsWith('-') && positional === null) positional = a;
+    }
+    return { name, help, positional };
+}
+
+async function main(args) {
+    const idx = loadHarnessIndex();
+    const harnesses = idx.harnesses || {};
+    const { name, help, positional } = parseArgs(args);
+
+    if (help) {
+        p.intro('@nurix/etna — Nurix harness installer');
+        p.log.message(
+            'Usage:\n' +
+                '  npx @nurix/etna                   pick a harness from the menu\n' +
+                '  npx @nurix/etna --name=<harness>  install that harness directly',
+        );
+        printHarnessList(harnesses);
+        p.outro('No args → interactive menu. --name=<harness> → direct install.');
+        return;
+    }
+
+    p.intro('@nurix/etna — Nurix harness installer');
+
+    // Breaking change (0.18.0): the positional form `etna <harness>` was replaced by
+    // `--name=<harness>`. Fail loudly with the new syntax rather than silently misfiring.
+    if (positional && name === null) {
+        p.log.error(
+            `Positional arguments are no longer supported. Install with \`npx @nurix/etna --name=${positional}\`.`,
+        );
+        printHarnessList(harnesses);
+        p.outro('Use --name=<harness> to install, or no args to pick from the menu.');
+        process.exit(1);
+    }
+
+    const boot = p.spinner();
+    boot.start('Starting up');
+    await sleep(2000);
+    boot.stop('Ready');
+
+    const harnessName = await resolveHarnessName(name, harnesses);
+    if (!harnessName) return; // user cancelled the interactive pick
+
+    await installHarness(harnessName, harnesses);
+}
+
 main(process.argv.slice(2)).catch((e) => {
-    console.error(e?.stack || e);
+    p.log.error(e?.stack || String(e));
     process.exit(1);
 });

package/data/harness-index.json

@@ -1,10 +1,25 @@
 {
-    "fingerprint": "b51d4ebd2a1e",
+    "fingerprint": "2a8b6a3ea74d",
     "harnesses": {
-        "code": "code-fable",
-        "code-fable": "code-fable",
-        "discover": "discover",
-        "hr": "hr",
-        "kb-agi": "kb-agi"
+        "code": {
+            "plugin": "code-fable",
+            "description": "Nurix code-project harness"
+        },
+        "code-fable": {
+            "plugin": "code-fable",
+            "description": "Nurix code-project harness"
+        },
+        "discover": {
+            "plugin": "discover",
+            "description": "Product Discovery harness"
+        },
+        "hr": {
+            "plugin": "hr",
+            "description": "Hiring / AI-Steering Evaluation harness"
+        },
+        "kb-agi": {
+            "plugin": "kb-agi",
+            "description": "self-improving knowledge-base harness"
+        }
     }
 }

package/data/harnesses/code/.prettierignore

@@ -0,0 +1,12 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed agent/skill definitions (installed under .claude/)
+.claude

package/data/harnesses/code/.prettierrc.json

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/code/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  }
+}

package/data/harnesses/code/agents/harness-manager.md

@@ -15,7 +15,7 @@ Reconcile is **declarative, not a migration ladder.** You converge to the *curre
 
 ## The two version layers (don't confuse them)
 
-- The **CLI** (`npx @nurix/etna code`) refreshes the *engine* — `CLAUDE.md` + `.claude/{agents,skills,rules,scripts}/`. That is not your job; the install does it.
+- The **CLI** (`npx @nurix/etna --name=code`) refreshes the *engine* — `CLAUDE.md` + `.claude/{agents,skills,rules,scripts}/`. That is not your job; the install does it.
 - **You** reconcile the *repo's authored data* — the `docs/` tree — to match that engine.
 
 The upgrade story is the two run back-to-back: install refreshes the engine → you reconcile the docs to it.
@@ -37,7 +37,7 @@ You never edit a doc for content fidelity (that is `maintenance`); `maintenance`
 ## Before starting
 
 1. Verify a **root `CLAUDE.md` exists** before any reconcile. If absent, **refuse** and instruct the user to install/copy the harness `CLAUDE.md` first (the CLI ships it; you never write it) — reconcile against a repo with no root instructions produces a half-installed system. Detect-and-instruct, not a gate.
-2. Resolve the **installed harness epoch** — read it 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 code`, then retry. The resolved epoch is the target.
+2. Resolve the **installed harness epoch** — read it 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=code`, then retry. The resolved epoch is the target.
 3. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter. Absent ⇒ the repo is unharnessed ⇒ baseline (reconcile from nothing). Equal to installed ⇒ report and stop, **except** when re-invoked for the Step 6 module proposal: the version is already current from your first pass, so skip the stop and go straight to Step 6. (Health asked ⇒ run Health.) Behind ⇒ reconcile forward.
 4. If `docs/memory/harness-manager.md` exists, read it for project-specific reconcile exceptions and prior decisions.
 
@@ -158,7 +158,7 @@ Confirm all mandated files exist; `structure.md` carries the current `harness-ve
 Conformance, not fidelity. Report a table; fix nothing destructively without asking.
 
 - **Version currency** — `harness-version` present in `structure.md` and equal to installed? If behind/absent → recommend Reconcile. (This is the *repo-vs-installed* gap — it self-heals once the consumer reinstalls and re-runs you. The next two checks catch what reinstall *hasn't* happened yet, or was bypassed by a hand-edit.)
-- **Published-version currency** *(advisory, network)* — the installed `.claude/harness.json` records the kit's `version`; the published kit may have moved past it. Attempt `npm view @nurix/etna version` (the kit is a restricted package — needs npm auth + network). **Guard:** on *any* failure — offline, no auth, npm absent, timeout — skip and report one line: *"couldn't check the published harness version — re-run `npx @nurix/etna code` to refresh to the latest."* On success, compare the published version against `.claude/harness.json`'s `version`; if published is ahead, recommend re-running the CLI to pull the newer kit. Never a gate, never blocks.
+- **Published-version currency** *(advisory, network)* — the installed `.claude/harness.json` records the kit's `version`; the published kit may have moved past it. Attempt `npm view @nurix/etna version` (the kit is a restricted package — needs npm auth + network). **Guard:** on *any* failure — offline, no auth, npm absent, timeout — skip and report one line: *"couldn't check the published harness version — re-run `npx @nurix/etna --name=code` to refresh to the latest."* On success, compare the published version against `.claude/harness.json`'s `version`; if published is ahead, recommend re-running the CLI to pull the newer kit. Never a gate, never blocks.
 - **Kit build fingerprint (digest)** *(informational)* — `.claude/harness.json` carries a `digest`: a deterministic fingerprint of the exact kit **build** the consumer installed (`build-data` computes it over the shipped bundle). Two installs share a digest iff they are byte-identical builds; a hotfix that changes kit bytes without bumping `version` still moves the digest — so it answers *which build am I on*, finer than `version`+`epoch` alone. **Don't recompute it over `.claude/` to self-check:** the installed layout is a superset of the build (the project `CLAUDE.md` sits at the repo root, `.claude/` adds `settings.json`/`harness.json`/local rule files), so paths and file sets differ **by design** — a recompute would never match. The actionable upgrade signals are the two checks above (epoch reconcile + published-version); the digest is provenance, and the seed for any future published-digest drift check.
 - **Scaffold completeness** — every mandated file present.
 - **Dissolved-version residue** — any `operations/guardrails.md`, repo-wide `docs/pillars/`, `architecture/overview.md`, a persisted `docs/boundaries/` tree, or other old-shape artifact lingering.

package/data/harnesses/code/harness.json

@@ -3,5 +3,10 @@
   "name": "code-fable",
   "version": "0.17.0",
   "epoch": 14,
-  "digest": "adc67e13b079"
+  "files": [
+    ".prettierrc.json",
+    ".prettierignore",
+    ".vscode/settings.json"
+  ],
+  "digest": "a897772819ce"
 }

package/data/harnesses/code-fable/.prettierignore

@@ -0,0 +1,12 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed agent/skill definitions (installed under .claude/)
+.claude

package/data/harnesses/code-fable/.prettierrc.json

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/code-fable/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  }
+}

package/data/harnesses/code-fable/agents/harness-manager.md

@@ -15,7 +15,7 @@ Reconcile is **declarative, not a migration ladder.** You converge to the *curre
 
 ## The two version layers (don't confuse them)
 
-- The **CLI** (`npx @nurix/etna code`) refreshes the *engine* — `CLAUDE.md` + `.claude/{agents,skills,rules,scripts}/`. That is not your job; the install does it.
+- The **CLI** (`npx @nurix/etna --name=code`) refreshes the *engine* — `CLAUDE.md` + `.claude/{agents,skills,rules,scripts}/`. That is not your job; the install does it.
 - **You** reconcile the *repo's authored data* — the `docs/` tree — to match that engine.
 
 The upgrade story is the two run back-to-back: install refreshes the engine → you reconcile the docs to it.
@@ -37,7 +37,7 @@ You never edit a doc for content fidelity (that is `maintenance`); `maintenance`
 ## Before starting
 
 1. Verify a **root `CLAUDE.md` exists** before any reconcile. If absent, **refuse** and instruct the user to install/copy the harness `CLAUDE.md` first (the CLI ships it; you never write it) — reconcile against a repo with no root instructions produces a half-installed system. Detect-and-instruct, not a gate.
-2. Resolve the **installed harness epoch** — read it 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 code`, then retry. The resolved epoch is the target.
+2. Resolve the **installed harness epoch** — read it 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=code`, then retry. The resolved epoch is the target.
 3. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter. Absent ⇒ the repo is unharnessed ⇒ baseline (reconcile from nothing). Equal to installed ⇒ report and stop, **except** when re-invoked for the Step 6 module proposal: the version is already current from your first pass, so skip the stop and go straight to Step 6. (Health asked ⇒ run Health.) Behind ⇒ reconcile forward.
 4. If `docs/memory/harness-manager.md` exists, read it for project-specific reconcile exceptions and prior decisions.
 
@@ -158,7 +158,7 @@ Confirm all mandated files exist; `structure.md` carries the current `harness-ve
 Conformance, not fidelity. Report a table; fix nothing destructively without asking.
 
 - **Version currency** — `harness-version` present in `structure.md` and equal to installed? If behind/absent → recommend Reconcile. (This is the *repo-vs-installed* gap — it self-heals once the consumer reinstalls and re-runs you. The next two checks catch what reinstall *hasn't* happened yet, or was bypassed by a hand-edit.)
-- **Published-version currency** *(advisory, network)* — the installed `.claude/harness.json` records the kit's `version`; the published kit may have moved past it. Attempt `npm view @nurix/etna version` (the kit is a restricted package — needs npm auth + network). **Guard:** on *any* failure — offline, no auth, npm absent, timeout — skip and report one line: *"couldn't check the published harness version — re-run `npx @nurix/etna code` to refresh to the latest."* On success, compare the published version against `.claude/harness.json`'s `version`; if published is ahead, recommend re-running the CLI to pull the newer kit. Never a gate, never blocks.
+- **Published-version currency** *(advisory, network)* — the installed `.claude/harness.json` records the kit's `version`; the published kit may have moved past it. Attempt `npm view @nurix/etna version` (the kit is a restricted package — needs npm auth + network). **Guard:** on *any* failure — offline, no auth, npm absent, timeout — skip and report one line: *"couldn't check the published harness version — re-run `npx @nurix/etna --name=code` to refresh to the latest."* On success, compare the published version against `.claude/harness.json`'s `version`; if published is ahead, recommend re-running the CLI to pull the newer kit. Never a gate, never blocks.
 - **Kit build fingerprint (digest)** *(informational)* — `.claude/harness.json` carries a `digest`: a deterministic fingerprint of the exact kit **build** the consumer installed (`build-data` computes it over the shipped bundle). Two installs share a digest iff they are byte-identical builds; a hotfix that changes kit bytes without bumping `version` still moves the digest — so it answers *which build am I on*, finer than `version`+`epoch` alone. **Don't recompute it over `.claude/` to self-check:** the installed layout is a superset of the build (the project `CLAUDE.md` sits at the repo root, `.claude/` adds `settings.json`/`harness.json`/local rule files), so paths and file sets differ **by design** — a recompute would never match. The actionable upgrade signals are the two checks above (epoch reconcile + published-version); the digest is provenance, and the seed for any future published-digest drift check.
 - **Scaffold completeness** — every mandated file present.
 - **Dissolved-version residue** — any `operations/guardrails.md`, repo-wide `docs/pillars/`, `architecture/overview.md`, a persisted `docs/boundaries/` tree, or other old-shape artifact lingering.

package/data/harnesses/code-fable/harness.json

@@ -3,5 +3,10 @@
   "name": "code-fable",
   "version": "0.17.0",
   "epoch": 14,
-  "digest": "6e3420a69727"
+  "files": [
+    ".prettierrc.json",
+    ".prettierignore",
+    ".vscode/settings.json"
+  ],
+  "digest": "7ce2d78b5ead"
 }

package/data/harnesses/discover/.prettierignore

@@ -0,0 +1,12 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed agent/skill definitions (installed under .claude/)
+.claude

package/data/harnesses/discover/.prettierrc.json

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/discover/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  }
+}

package/data/harnesses/discover/harness.json

@@ -3,5 +3,10 @@
   "name": "discover",
   "version": "0.1.7",
   "epoch": null,
-  "digest": "459be63d0534"
+  "files": [
+    ".prettierrc.json",
+    ".prettierignore",
+    ".vscode/settings.json"
+  ],
+  "digest": "bd18173c697a"
 }

package/data/harnesses/hr/.prettierignore

@@ -0,0 +1,12 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed agent/skill definitions (installed under .claude/)
+.claude

package/data/harnesses/hr/.prettierrc.json

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/hr/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  }
+}

package/data/harnesses/hr/CLAUDE.md

@@ -24,7 +24,7 @@ mistake, the redirect that pulled it off a bad path. Turn count, prompt length,
 ## 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 hr` (or point you at the skill) before continuing. Confirm
+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.
 
 ## Step 1 — intake interview

package/data/harnesses/hr/harness.json

@@ -3,5 +3,10 @@
   "name": "hr",
   "version": "0.1.1",
   "epoch": null,
-  "digest": "dfc7c529bbec"
+  "files": [
+    ".prettierrc.json",
+    ".prettierignore",
+    ".vscode/settings.json"
+  ],
+  "digest": "c1632f70fcdb"
 }

package/data/harnesses/kb-agi/.prettierignore

@@ -0,0 +1,12 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed agent/skill definitions (installed under .claude/)
+.claude

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

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/kb-agi/.vscode/settings.json

@@ -0,0 +1,10 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  }
+}

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

@@ -3,5 +3,10 @@
   "name": "kb-agi",
   "version": "0.10.1",
   "epoch": null,
-  "digest": "856a9f4e297a"
+  "files": [
+    ".prettierrc.json",
+    ".prettierignore",
+    ".vscode/settings.json"
+  ],
+  "digest": "25e1cb993a7f"
 }

package/package.json

@@ -1,11 +1,14 @@
 {
     "name": "@nurix/etna",
-    "version": "0.17.0",
+    "version": "0.18.0",
     "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": {
         "etna": "bin/etna.js"
     },
+    "dependencies": {
+        "@clack/prompts": "^0.11.0"
+    },
     "files": [
         "bin/",
         "data/",