@nurix/etna 0.19.4 → 0.19.5

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "21e76b5126aa",
+    "fingerprint": "ced70ba6f73f",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/harness.json

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

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

@@ -1,6 +1,6 @@
 ---
 name: design
-description: Design, build, review, polish, redesign, judge, or introspect internal operator UIs — CRMs, ticket queues, admin panels, analytics dashboards, log viewers, command centers, and any internal/back-office tool an operator, agent, or analyst works in all day. Resolves the project's brand from its design-tokens artifact (design.tokens.json), derives structure from the domain objects, emits a working React + Tailwind UI against @nurix/components or shadcn/ui, and holds it to operator-grade quality across a full sixteen-dimension taxonomy. Triggers on "build a dashboard", "design an admin panel", "review this CRM UI", "polish this queue", "redesign this internal tool", "judge this UI", "does this look right", "screenshot review", "why does this table feel off", "why does this feel off visually" (introspect keeps the causal why; judge owns the rendered whether), "make it feel like Linear", or any create/improve/introspect request for an internal operator interface. Coverage is the operator pack: marketing sites, landing pages, storefronts, homepages, and mobile-native apps are out of scope — no carried pack covers them, so refuse cleanly and redirect. The machinery is not the limit; the packs are.
+description: 'Design, build, review, polish, judge, or introspect internal operator UIs — CRMs, ticket queues, admin panels, dashboards, log viewers, command centers — as React + Tailwind from design.tokens.json. Also "does this look right" and "why does this feel off". Not marketing or mobile-native.'
 ---
 
 # design

package/data/harnesses/code/skills/design/references/personality.md

@@ -266,7 +266,7 @@ radius scale. Two cascade contracts keep the personality in charge; both are har
 emitted in-CSS comments below, enforced by the code-and-token rules (`cod-*`) in
 [hard-rules.md](./hard-rules.md), and verified **rendered** by the render rung's per-theme drift
 check (cod-15). Measured at `@nurix/components@0.14.0`, the library directly consumes 15 of the 17
-v1 semantic color roles but only one personality primitive (`--radius`) — everything else reaches
+shadcn-standard semantic color roles but only one personality primitive (`--radius`) — everything else reaches
 it through the consumer Tailwind build this file feeds (shadows, weights, tracking, and the density
 remap below).
 
@@ -288,12 +288,12 @@ remap below).
 *The exact loss mode:* a bare `:root { --background: … }` is specificity `(0,1,0)` — the library's
 own `:root { --background: … }` is also `(0,1,0)` and imported *later*, so it wins by source order
 and every surface silently reverts to shadcn gray. A lone `[data-theme="dark"]` attribute selector
-is the same `(0,1,0)` and loses the same way — the historical dark defect was exactly that
-unarmored selector, shipped while every static gate stayed green. The `:root[data-theme="…"]` arm
+is the same `(0,1,0)` and loses the same way — and it ships while every static gate stays green,
+because no static check sees the cascade. The `:root[data-theme="…"]` arm
 is `(0,2,0)` and out-wins — but only if `<html>` actually carries the attribute; scaffold writes it
 from the payload's `theme-default`, and the render rung's cod-15 measures the rendered
 `--background`/`--foreground`/`--primary` per declared theme context against the authored values,
-so a cascade-dead theme block can no longer pass.
+so a cascade-dead theme block cannot pass.
 
 **CASCADE CONTRACT 2 — the five-step import order.** The emitted `globals.css` opens:
 
@@ -419,7 +419,7 @@ on upgrades). This is user-owned upstream work — never patched with brittle pe
   color props: scaffold's `src/lib/chart-colors.ts` wires `var(--chart-1..5)` through the series
   props and the status roles (`--success`/`--warning`/`--destructive` + the accent/muted homes for
   info/empty) through the BarGraph map, so charts inherit the theme today. Chart *chrome*
-  (gridlines, axis labels) stays hardcoded — a substrate limit, filed, never a v3 bug.
+  (gridlines, axis labels) stays hardcoded — a substrate limit, filed, never a skill defect.
 - **Motion & icon stroke** — JS motion durations and icon `strokeWidth` numbers; `--duration-*` and
   `--icon-stroke` reach consumer-emitted markup but not library internals. The density dial also
   no-ops inside library tables (`h-8` row height).

package/package.json

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