@nurix/etna 0.19.21 → 0.19.22

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "2329fc4f3594",
+    "fingerprint": "72062264cf08",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/harness.json

@@ -7,5 +7,5 @@
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "6b9984997d77"
+  "digest": "01d8bfddebb8"
 }

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

@@ -1,6 +1,6 @@
 ---
 name: boundary
-description: Boundary diagnostic for implementation plans. Given a plan file, reads the source the plan touches, identifies the cross-cutting contracts it participates in — db schema, wire envelope, auth, events, env/config, … — where editing one side silently breaks the other, and reports whether the planned changes would violate any of them, severity-ranked, with suggested amendments and a pass/block verdict. Read-only; the report lands in chat. Also runs against a diff or named code area. Triggers on "boundary check", "check this plan", "what could break", "will this break anything", "is it safe to rename this column/endpoint/event", "who uses this", "impact analysis", "/boundary".
+description: "Boundary diagnostic for implementation plans. Reads the source a plan touches, finds the cross-cutting contracts it joins (db schema, wire envelope, auth, events), and reports violations with a pass/block verdict. Read-only; also runs on a diff. Triggers on 'boundary check', 'what could break'."
 ---
 
 # Boundary Diagnostic

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

@@ -1,6 +1,6 @@
 ---
 name: brainstorm
-description: Thinking-partner session for designing large-scale software changes. Invoked ONLY by explicit slash commands `/brainstorm start` and `/brainstorm stop` — never auto-invoke on natural-language phrases like "let's plan", "let's design", or "let's think through X". Entry requires a basis (a reference document, a prior session folder of any format, or a one-shot brain dump); drip-sized asks are redirected. The facilitator owns the conversation and appends everything to an untracked ops ledger; the brainstorm twin agent owns the working surface (thesis / forks / ledger / state / fragments), dispatched at gates — start, on demand, pause, stop — and paired-logged; a detector script owns mechanical integrity. Stop always triggers convergence, a user-approved harvest manifest, a uselessness test, and the folder's move to docs/history/brainstorms/, where the user decides: delete or commit.
+description: "Thinking-partner session for designing large-scale software changes. Invoked ONLY by `/brainstorm start` and `/brainstorm stop` — never on phrases like 'let's plan' or 'let's design'. Entry needs a basis (a reference doc, prior session folder, or brain dump); drip-sized asks are redirected."
 argument-hint: "start | stop"
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 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".
+description: "Discover and document a codebase's major workflows by tracing call chains from user action to database or external system — produces mermaid sequence diagrams and markdown. Triggers on 'map workflows', 'trace flows', 'sequence diagram', or 'how does X work end-to-end'."
 ---
 
 # Workflow Mapper Skill

package/data/harnesses/etna/harness.json

@@ -7,5 +7,5 @@
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "8834d630e6dc"
+  "digest": "3e3243936008"
 }

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

@@ -1,6 +1,6 @@
 ---
 name: boundary
-description: Boundary diagnostic for implementation plans. Given a plan file, reads the source the plan touches, identifies the cross-cutting contracts it participates in — db schema, wire envelope, auth, events, env/config, … — where editing one side silently breaks the other, and reports whether the planned changes would violate any of them, severity-ranked, with suggested amendments and a pass/block verdict. Read-only; the report lands in chat. Also runs against a diff or named code area. Triggers on "boundary check", "check this plan", "what could break", "will this break anything", "is it safe to rename this column/endpoint/event", "who uses this", "impact analysis", "/boundary".
+description: "Boundary diagnostic for implementation plans. Reads the source a plan touches, finds the cross-cutting contracts it joins (db schema, wire envelope, auth, events), and reports violations with a pass/block verdict. Read-only; also runs on a diff. Triggers on 'boundary check', 'what could break'."
 ---
 
 # Boundary Diagnostic

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

@@ -1,6 +1,6 @@
 ---
 name: brainstorm
-description: Thinking-partner session for designing large-scale software changes. Invoked ONLY by explicit slash commands `/brainstorm start` and `/brainstorm stop` — never auto-invoke on natural-language phrases like "let's plan", "let's design", or "let's think through X". Entry requires a basis (a reference document, a prior session folder of any format, or a one-shot brain dump); drip-sized asks are redirected. The facilitator owns the conversation and appends everything to an untracked ops ledger; the brainstorm twin agent owns the working surface (thesis / forks / ledger / state / fragments), dispatched at gates — start, on demand, pause, stop — and paired-logged; a detector script owns mechanical integrity. Stop always triggers convergence, a user-approved harvest manifest, a uselessness test, and the folder's move to docs/history/brainstorms/, where the user decides: delete or commit.
+description: "Thinking-partner session for designing large-scale software changes. Invoked ONLY by `/brainstorm start` and `/brainstorm stop` — never on phrases like 'let's plan' or 'let's design'. Entry needs a basis (a reference doc, prior session folder, or brain dump); drip-sized asks are redirected."
 argument-hint: "start | stop"
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 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".
+description: "Discover and document a codebase's major workflows by tracing call chains from user action to database or external system — produces mermaid sequence diagrams and markdown. Triggers on 'map workflows', 'trace flows', 'sequence diagram', or 'how does X work end-to-end'."
 ---
 
 # Workflow Mapper Skill

package/data/harnesses/hr/harness.json

@@ -7,5 +7,5 @@
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "95a724a4ef64"
+  "digest": "b547d3ca2c1b"
 }

package/data/harnesses/hr/skills/evaluator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: evaluator
-description: Apply a generic production-readiness + product-quality rubric to a single software project. Takes a repo reference + an output directory, writes a per-project workspace (`<out_dir>/<project>/` containing `README.md`, `scorecard.yaml`, and a flat `raw/` directory where every file is named `<sub-criterion>-<artifact>.ext` — e.g. `raw/code-quality-semgrep-quality.json`, `raw/maintainability-deptry.json`), and returns the workspace path. The scorecard is a YAML with 8 sub-criterion blocks (4 Code + 4 Product, 12.5 pts each = 100 pts), a 0–5 score + evidence + data per item, gates triggered, and `total` / `available` / `normalized`. Bands are **absolute** per-signal thresholds declared in each recipe. The skill scores exactly one project and is unaware of any caller, cohort, or cross-project comparison. Triggers on "evaluate this project", "score this repo against the rubric", "run the evaluator on <path>".
+description: "Apply a production-readiness + product-quality rubric to a single software project. Takes a repo + output dir; writes a per-project workspace (README, `scorecard.yaml`, flat `raw/`) scoring 8 sub-criteria (4 Code + 4 Product) to /100 with evidence and gates. Scores one project, no cohort."
 ---
 
 # Evaluator

package/data/harnesses/hr/skills/interview-eval/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: interview-eval
-description: Evaluate how well a person steered a Claude Code session — the human's prompting, decomposition, verification, debugging, course-correction, and engineering judgment — from one or more session transcripts (.jsonl). Built for interview/hiring assessment of engineers using AI coding agents. Takes 1+ Claude Code session `.jsonl` files (or a directory of them) plus an output directory; writes a per-session `report.md` + `scorecard.yaml`, and (for multiple sessions) a `candidate-rollup.md`. Scores 9 weighted dimensions on a 0–5 band scale against absolute anchors in `rubric.md`, normalizes to /100, maps to a steering level (Exemplary / Strong / Competent / Developing / Weak), applies hard-cap gates for unsafe behavior, and anchors every score to quoted turns. It judges the HUMAN'S steering, not Claude's code. Triggers on "evaluate this Claude Code session", "score how the candidate steered Claude", "judge these session transcripts", "how good is this person's prompting", "assess AI-pairing skill from a session log", or a `.jsonl` transcript handed over for review.
+description: "Score how a human steered a Claude Code session — prompting, decomposition, verification, debugging, judgment — from `.jsonl` transcripts. For interview/hiring assessment of engineers using AI coding agents; writes a per-session report + scorecard plus a rollup. Judges the human, not the code."
 ---
 
 # interview-eval

package/package.json

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