@nurix/etna 0.12.1 → 0.14.0

package/README.md

@@ -9,7 +9,7 @@ A second install path also exists and is fully supported: `/plugin install <plug
 From the root of the project you want to bootstrap:
 
 ```sh
-npx @nurix/etna nurix-harness
+npx @nurix/etna code
 ```
 
 After this completes:
@@ -26,7 +26,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 project-scoped agents/skills/rules/scripts on its next session start.
 
-Re-run `npx @nurix/etna nurix-harness` 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>`.
+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>`.
 
 ## Migrating from 0.1.x
 
@@ -40,7 +40,7 @@ Listed by `npx @nurix/etna` (no args) using the bundled `data/harness-index.json
 
 | Plugin name | Source in etna | What it ships |
 |---|---|---|
-| `nurix-harness` | [`plugins/nurix-harness.md`](../../plugins/nurix-harness.md) → top-level catalogs | Governance agents, baseline workflow skills, ownership/drift scripts |
+| `code` | [`plugins/code.md`](../../plugins/code.md) → top-level catalogs | Governance agents, baseline workflow skills, ownership/drift scripts |
 | `kb-agi` | [`plugins/kb-agi.md`](../../plugins/kb-agi.md) → top-level catalogs | Knowledge-vault scaffolding |
 
 ## How it works
@@ -53,7 +53,7 @@ The plugin manifest's YAML frontmatter declares which top-level `agents/`, `skil
 
 ```yaml
 ---
-name: nurix-harness
+name: code
 skills: [documentation, introspect, workflow-mapper]
 agents: [spec-mode, maintenance, contract-monitor, …]
 scripts: [build-ownership-index, check-doc-drift]

package/data/harness-index.json

@@ -1,6 +1,6 @@
 {
     "plugins": {
-        "nurix-harness": "code",
+        "code": "code",
         "kb-agi": "kb-agi"
     }
 }

package/data/harnesses/code/CLAUDE.md

@@ -1,7 +1,7 @@
 ---
 name: code
 description: Canonical Nurix code-project harness (spec v11) — three peer authoring modes (Brainstorming / Spec / Plan), modules as bounded contexts, typed application boundaries via the unified `boundary` skill, a self-migrating harness-manager, ownership rules. The reference CLAUDE.md every Nurix codebase starts with.
-version: 0.12.0
+version: 0.14.0
 keywords:
   - harness
   - code
@@ -9,7 +9,7 @@ keywords:
   - documentation
   - boundaries
   - nurix
-plugin: nurix-harness
+plugin: code
 ---
 
 # Agent Instructions
@@ -159,4 +159,3 @@ Maintenance triggers (act on these without re-reading `structure.md`):
 
 - After plan completion: add a `docs/history/changelog/` entry + update `docs/history/CHANGELOG.md` (no confirmation; include `Commits:` if multi-commit). Non-plan changes (refactors, fixes, API changes): prompt first.
 - When you add, move, or delete a doc: update `docs/routing.md` and `docs/README.md` to match. When you move or rename source files: fix the `owns`/`touches` frontmatter in the owning doc; new docs that own code need `owns`/`touches`/`depends_on`.
-- Before creating changelogs, feature docs, or plans: ensure the repo is reconciled (`docs/structure.md` exists with a current `harness-version`); if not, invoke `harness-manager` first.

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

@@ -3,7 +3,7 @@ name: brainstorm
 description: Brainstorming-mode facilitator — a thin orchestrator over the self-contained `brainstorm` skill, which owns every session mechanic (the three modes, the tentative→committed lifecycle, the realignment cascade, the scope-routed harvest, the 10 pillar templates, greenfield rules). Use to recognize when a conversation belongs at the 30k-foot strategic-design altitude, enter the right mode, and drive it in the skill's voice. Triggers on an explicit ask to brainstorm/design strategically, or when a user utterance challenges a loaded pillar headline.
 tools: Read, Glob, Grep, AskUserQuestion, Write
 model: inherit
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Brainstorm Agent

package/data/harnesses/code/agents/change-review.md

@@ -3,7 +3,7 @@ name: change-review
 description: Velocity + change-risk analysis. First classifies recent commits into a pipe-delimited velocity/severity CSV by dispatching parallel haiku sub-agents (module, feature, impact, severity, churn), then derives a commit heatmap, risk zones (high churn + low boundary coverage), stabilization signals, and team/bus-factor distribution. Self-contained — produces its own CSV, no separate git-history step. Use when planning where to invest in better boundaries or rules.
 tools: Bash, Read, Write, Glob, Grep, Task
 model: inherit
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Change-Review Agent

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

@@ -3,7 +3,7 @@ name: harness-manager
 description: The harness's own migrator and structural-health auditor. Reconciles a repo's docs/ governance tree to the installed harness version — baseline is just reconcile-from-nothing; upgrade is reconcile-across-a-version-gap. Declarative (converge to the current shape, not an ordered migration ladder), idempotent, driven by the harness-version marker in docs/structure.md. Owns the Bootstrap. On demand, audits structural conformance to the harness spec. Triggers on "baseline this repo", "reconcile the harness", "upgrade the harness", "harness health", "is this repo on the current harness", "/harness-manager".
 tools: Read, Glob, Grep, Bash, Write, Edit
 model: inherit
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Harness-Manager Agent
@@ -16,7 +16,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 nurix-harness`) refreshes the *engine* — `CLAUDE.md` + `.claude/{agents,skills,rules,scripts}/`. That is not your job; the install does it.
+- 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.
 - **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.

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

@@ -3,7 +3,7 @@ name: maintenance
 description: Docs-vs-code coherence audit. Detects and fixes docs drifting from code — stale docs, broken ownership, routing table drift, unowned source paths. Run weekly or after major changes. Contract violations (code drifting from docs) are handled by the `boundary` skill (`init` mode); pre-implementation impact checks by its `check` mode.
 tools: Read, Glob, Grep, Edit, Write, Bash
 model: inherit
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Maintenance Agent

package/data/harnesses/code/agents/performance-review.md

@@ -3,7 +3,7 @@ name: performance-review
 description: Combined dependency + code health audit. Part A audits the dependency supply chain — security CVEs, outdated packages, license compliance, abandoned packages, unwanted transitive dependencies, install size. Part B audits code-level health — bundle size, tree-shaking issues, performance anti-patterns, code-quality flags. Run weekly or before releases. Merges the former `dep-health` and `review` agents so the package tree and the code that uses it are audited together.
 tools: Read, Glob, Grep, Bash
 model: inherit
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Performance-Review Agent

package/data/harnesses/code/agents/spec-mode.md

@@ -5,7 +5,7 @@ tools: Read, Glob, Grep, WebSearch, WebFetch
 model: inherit
 skills:
   - documentation
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Spec Mode Agent

package/data/harnesses/code/rules/general.md

@@ -1,6 +1,6 @@
 ---
 applyTo: "**"
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Technology Choices & Standards

package/data/harnesses/code/rules/nomenclature.md

@@ -1,6 +1,6 @@
 ---
 applyTo: "**"
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Nomenclature Guidelines

package/data/harnesses/code/skills/boundary/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: boundary
 description: The single home for a repo's typed application boundaries — the cross-cutting contracts (db-schema, wire envelope, store shape, auth, tenancy, event schemas, edge bindings, …) where editing one module silently breaks another. One skill, four modes — `generate` (baseline all boundaries from the detected stack + IA), `create` (add/update one boundary), `check` (pre-implementation: does this plan touch a boundary? severity-ranked impact), `init` (reconcile: ensure files exist, scan live code for violations + drift, backfill new catalog types). All four read one shared knowledge root, `references/boundary-taxonomy.md`, so they can never drift apart. Triggers on "application boundary", "baseline boundaries", "map boundaries", "generate boundaries", "create a boundary", "introspect", "check this plan", "impact analysis", "what could break", "scan for boundary violations", "boundary drift", "/boundary".
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Application Boundary Skill

package/data/harnesses/code/skills/brainstorm/SKILL.md

@@ -2,7 +2,7 @@
 name: brainstorm
 description: Structured planning/design session for software that hasn't been built yet. Invoked ONLY by explicit slash commands `/brainstorm start` and `/brainstorm stop`. Do NOT auto-invoke on natural-language phrases like "let's plan", "let's design", "let's think through X", or any other phrasing — those are not triggers. The skill maintains 10 pillar documents (questions, decisions, doctrine, glossary, inventory, non-goals, references, rejected, milestones, backlog) inside a `pillars/` subfolder, plus a top-level `state.md` tracking session open/closed AND the active mode (explore / decide / step-back). Refuses to write production code outside the brainstorm folder while a session is active.
 argument-hint: "start | stop"
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Brainstorm

package/data/harnesses/code/skills/documentation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: documentation
 description: Template & generator library for technical docs — the skill agents call to produce a doc from a template. Use to (1) document a feature or module, (2) create or update a changelog entry, (3) document data flows or Redux state, (4) add to protected files, (5) provide the generic boundary-file template (typed-boundary *generation* is the `boundary` skill), (6) record an architecture decision (ADR), (7) create or update the project root README, (8) create or update a plan, (9) derive ownership frontmatter (`owns`/`touches`/`depends_on`) from code, (10) scaffold a standard doc (README, structure.md, CHANGELOG, backlog, memory) from its template, or (11) co-author any technical doc. Baselining / reconciling a repo's docs to the installed harness version is the **`harness-manager` agent** (which calls this skill for each template) — this skill does not orchestrate baseline. Triggers on "document this", "create docs", "update changelog", "add to protected files", "ADR", "architecture decision", "root README", "plan", "feature doc".
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Technical Documentation Skill

package/data/harnesses/code/skills/workflow-mapper/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workflow-mapper
 description: Discover and document all major workflows in a codebase by tracing call chains from user action to database/external system. Produces mermaid sequence diagrams and markdown documentation. Use when the user asks to map workflows, trace flows, document sequences, understand how features work end-to-end, or generate architecture diagrams. Triggers on "map workflows", "trace workflows", "workflow diagram", "sequence diagram", "how does X work end-to-end", "document flows", "codebase workflows", "how does this feature work", "trace the request flow", "show me the call chain", "what happens when a user does X", "end-to-end flow".
-plugins: [nurix-harness]
+plugins: [code]
 ---
 
 # Workflow Mapper Skill

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.12.1",
+    "version": "0.14.0",
     "description": "Bootstrap a project with a Nurix harness — installs a Claude Code plugin from the nurixlabs/skills marketplace and drops the harness's CLAUDE.md at the project root.",
     "type": "module",
     "bin": {