@nurix/etna 0.19.84 → 0.19.86

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "574f23e45199",
+    "fingerprint": "476fa48936bb",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/docs/structure.md

@@ -16,6 +16,8 @@ Each topic has one canonical location. Read from here, not from plans or changel
 | API surface | `docs/architecture/` | api.md |
 | Security | `docs/architecture/` | security.md |
 | Feature behavior | `docs/features/` | one `kebab-case.md` doc per feature |
+| Product specification (PRD, personas, journeys, information architecture) | `docs/architecture/` | prd.md, personas.md, journeys.md, information-architecture.md |
+| Acceptance criteria | `docs/acceptance/` | one `kebab-case.md` doc per capability, `AC-n` keyed assert lines |
 | Setup & development | `docs/operations/` | setup.md |
 | Environment / config surface | `docs/operations/` | environment.md |
 | Testing strategy | `docs/tests/` | strategy.md |
@@ -39,6 +41,13 @@ Every doc is a **truth document** (states current absolutes, topic-named, update
 - `docs/features/`: Living reference for implemented features. Each feature doc **carries** the `owns:` / `module:` / `keywords:` / `status:` frontmatter — `owns:` declares the code-path globs it owns (the only ownership key), `module:` is an optional bounded-context label, `keywords:` are discovery terms, `status:` is `active`/`draft`/`deprecated`. The SessionStart hook unions every feature's `owns:` globs into the injected ownership index.
 - `docs/architecture/`: The truth layer for system-wide shape: overview, domain model, glossary, non-goals, API surface, security, and `decisions/` (ADs — one per subject, updated in place, journey in each AD's Decision Changelog). Update when cross-cutting reality changes.
 - `docs/operations/`: How-to procedures for setup, development, and deployment, plus the environment registry. Update when workflows change. One-shot migrations do NOT live here — they are records (`docs/history/migrations/`).
+- `docs/acceptance/`: Acceptance-criteria documents — one per capability, stating the promises the
+  built product must keep as `AC-n` keyed assert lines that verification surfaces parse as claims.
+  Written at specification time, before implementation; carries frontmatter (`type:`, `status:`)
+  like every generated doc. Keys are stable once published — a criterion is retired by marking it,
+  never by renumbering. Distinct from `docs/tests/`: acceptance criteria state what the product
+  promises up front; the checklists in `docs/tests/` are the verification gate's own driving
+  scripts, authored and maintained at the gate.
 - `docs/tests/`: Testing strategy and test docs. Present when the repo has a test posture worth documenting.
 - `docs/history/plans/`: Records. Must have `Status:` field. Never modify after completion.
 - `docs/history/changelog/`: Records. One entry per unit of work (`YYYY-MM-DD-{three-words}.md`), written by whoever does the work and frozen inside the commit it describes. Entries carry the refinement context a diff cannot show — the ask in the user's words, iterations and rejections, skill survived/overridden verdicts, discoveries, pins. Format is the `documentation` skill's `templates/changelog-entry.md`; trigger and lifecycle are the `changelog` rule; distillation is the `retro` agent. Immutability begins at commit — a draft in the working tree is mutable until then, never after. Every entry appends a row to `docs/history/CHANGELOG.md`.

package/data/harnesses/code/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.10.8",
+  "version": "3.10.10",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -15,5 +15,5 @@
     "docs/memory/main.md",
     ".mcp.json"
   ],
-  "digest": "764dc6628d76"
+  "digest": "0f09607cd2d4"
 }

package/data/harnesses/code/hooks/approved-packages.md

@@ -6,9 +6,9 @@ Read by the PreToolUse install gate (`compliance.mjs`) — an off-table install
 | --- | --- | --- | --- |
 | `react` | ^19.2.3 | UI components | — |
 | `vite` | ^8.0.0 | Build tool, dev server | `webpack`, CRA |
-| `tailwindcss` | ^4.1.18 | Styling | `styled-components` |
+| `tailwindcss` | ^4.3.3 | Styling | `styled-components` |
 | `@nurix/components` | ^0.15.12 | The UI component library — import by subpath | `npx shadcn add`, a `components.json` scaffold |
-| `@tailwindcss/vite` | ^4.1.18 | Tailwind v4 Vite plugin | `postcss`, `tailwind.config.js` |
+| `@tailwindcss/vite` | ^4.3.3 | Tailwind v4 Vite plugin — 4.3.x is the vite-8 peer line; 4.1.x tops out at vite 7 | `postcss`, `tailwind.config.js` |
 | `@vitejs/plugin-react-swc` | ^4.2.2 | JSX compilation | `@vitejs/plugin-react` |
 | `react-router-dom` | ^7.11.0 | Routing | — |
 | `@reduxjs/toolkit` | ^2.11.2 | State management | `zustand`, `jotai` |

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

@@ -72,6 +72,7 @@ The two guarantees are complementary and both break on mixing: a reader holding
 | Security / threat model | [`templates/security-overview.md`](templates/security-overview.md) |
 | Testing strategy | [`templates/testing-strategy.md`](templates/testing-strategy.md) |
 | Behavioral checklist for one feature (`docs/tests/{feature}.md`) | [`templates/behavioral-checklist.md`](templates/behavioral-checklist.md) — the verification gate's driving script, and the source its suite tests are drawn from |
+| Acceptance criteria for one capability (`docs/acceptance/{capability}.md`) | [`templates/acceptance-criteria.md`](templates/acceptance-criteria.md) — the promises the built product must keep, as stable `AC-n` keyed assert lines verification surfaces parse as claims |
 | Recurring procedure/setup | [`templates/operations-procedure.md`](templates/operations-procedure.md) |
 | Cold-start build order (implementation map) | [`templates/implementation-map.md`](templates/implementation-map.md) — authored by the executing session at build start, updated in place as waves complete |
 | Capture mid-execution knowledge (`docs/history/journal.md`) | [`templates/journal.md`](templates/journal.md) (record — append-only; a row resolves by landing in its owning doc) |
@@ -118,7 +119,13 @@ The two guarantees are complementary and both break on mixing: a reader holding
 
 ## Frontmatter Derivation
 
-A feature doc carries ownership frontmatter — `owns:` (required), `module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. Deriving it from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
+**Frontmatter is compulsory on every document this skill authors** — `type:` (the genre) on every
+doc, plus the genre's own keys beside it; a document without its frontmatter fails the skill's
+contract and is not done. A feature doc carries the full ownership set — `owns:` (required),
+`module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. An
+acceptance-criteria doc (`docs/acceptance/`) carries `type:` and `status:`. The single sanctioned
+exception is a genre the placement map explicitly marks frontmatter-less (the behavioral checklists
+in `docs/tests/`). Deriving ownership frontmatter from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
 
 ---
 

package/data/harnesses/code/skills/documentation/templates/acceptance-criteria.md

@@ -0,0 +1,37 @@
+# Acceptance Criteria
+
+Truth document. Use for: the promises one capability must keep, stated as machine-parseable
+claims. Lives in `docs/acceptance/`, one `kebab-case.md` per capability. Written at specification
+time — before implementation — and read by verification surfaces, which parse each `AC-n` line as
+a claim to grade the built product against.
+
+### Rules
+
+- **Frontmatter is required**: `type: acceptance-criteria`, `status:` (`draft` → `active` →
+  `deprecated`). No `owns:` — acceptance criteria own no code.
+- **One `AC-n` key per criterion, stable forever.** Keys are never renumbered and never reused: a
+  criterion that no longer applies is marked retired in place, so every claim a past verification
+  graded still resolves.
+- **Each criterion is one observable assert**, phrased as a checkable statement about the running
+  product — never about the code's internals. If it cannot be observed from outside, it is a
+  design note, not a criterion.
+- **The `AC-n:` line grammar is load-bearing** — verification parses these lines. Keep the key at
+  line start, exactly `AC-<number>:`, followed by the assert sentence. Formatting that buries the
+  key (tables, emphasis-wrapped keys, nested bullets) breaks the parse.
+
+### Template
+
+```markdown
+---
+type: acceptance-criteria
+status: draft
+---
+
+# Acceptance Criteria: {Capability}
+
+Scope: {one line — what part of the product these criteria bind}.
+
+- AC-1: {observable assert about the running product}.
+- AC-2: {observable assert}.
+- AC-3 (retired): {kept verbatim, marked retired — never renumbered}.
+```

package/data/harnesses/delivery/harness.json

@@ -1,12 +1,12 @@
 {
   "harness": "delivery",
   "name": "delivery",
-  "version": "0.2.16",
+  "version": "0.2.17",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "58c1beda728f"
+  "digest": "2d09f618c300"
 }

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

@@ -72,6 +72,7 @@ The two guarantees are complementary and both break on mixing: a reader holding
 | Security / threat model | [`templates/security-overview.md`](templates/security-overview.md) |
 | Testing strategy | [`templates/testing-strategy.md`](templates/testing-strategy.md) |
 | Behavioral checklist for one feature (`docs/tests/{feature}.md`) | [`templates/behavioral-checklist.md`](templates/behavioral-checklist.md) — the verification gate's driving script, and the source its suite tests are drawn from |
+| Acceptance criteria for one capability (`docs/acceptance/{capability}.md`) | [`templates/acceptance-criteria.md`](templates/acceptance-criteria.md) — the promises the built product must keep, as stable `AC-n` keyed assert lines verification surfaces parse as claims |
 | Recurring procedure/setup | [`templates/operations-procedure.md`](templates/operations-procedure.md) |
 | Cold-start build order (implementation map) | [`templates/implementation-map.md`](templates/implementation-map.md) — authored by the executing session at build start, updated in place as waves complete |
 | Capture mid-execution knowledge (`docs/history/journal.md`) | [`templates/journal.md`](templates/journal.md) (record — append-only; a row resolves by landing in its owning doc) |
@@ -118,7 +119,13 @@ The two guarantees are complementary and both break on mixing: a reader holding
 
 ## Frontmatter Derivation
 
-A feature doc carries ownership frontmatter — `owns:` (required), `module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. Deriving it from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
+**Frontmatter is compulsory on every document this skill authors** — `type:` (the genre) on every
+doc, plus the genre's own keys beside it; a document without its frontmatter fails the skill's
+contract and is not done. A feature doc carries the full ownership set — `owns:` (required),
+`module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. An
+acceptance-criteria doc (`docs/acceptance/`) carries `type:` and `status:`. The single sanctioned
+exception is a genre the placement map explicitly marks frontmatter-less (the behavioral checklists
+in `docs/tests/`). Deriving ownership frontmatter from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
 
 ---
 

package/data/harnesses/delivery/skills/documentation/templates/acceptance-criteria.md

@@ -0,0 +1,37 @@
+# Acceptance Criteria
+
+Truth document. Use for: the promises one capability must keep, stated as machine-parseable
+claims. Lives in `docs/acceptance/`, one `kebab-case.md` per capability. Written at specification
+time — before implementation — and read by verification surfaces, which parse each `AC-n` line as
+a claim to grade the built product against.
+
+### Rules
+
+- **Frontmatter is required**: `type: acceptance-criteria`, `status:` (`draft` → `active` →
+  `deprecated`). No `owns:` — acceptance criteria own no code.
+- **One `AC-n` key per criterion, stable forever.** Keys are never renumbered and never reused: a
+  criterion that no longer applies is marked retired in place, so every claim a past verification
+  graded still resolves.
+- **Each criterion is one observable assert**, phrased as a checkable statement about the running
+  product — never about the code's internals. If it cannot be observed from outside, it is a
+  design note, not a criterion.
+- **The `AC-n:` line grammar is load-bearing** — verification parses these lines. Keep the key at
+  line start, exactly `AC-<number>:`, followed by the assert sentence. Formatting that buries the
+  key (tables, emphasis-wrapped keys, nested bullets) breaks the parse.
+
+### Template
+
+```markdown
+---
+type: acceptance-criteria
+status: draft
+---
+
+# Acceptance Criteria: {Capability}
+
+Scope: {one line — what part of the product these criteria bind}.
+
+- AC-1: {observable assert about the running product}.
+- AC-2: {observable assert}.
+- AC-3 (retired): {kept verbatim, marked retired — never renumbered}.
+```

package/data/harnesses/etna/harness.json

@@ -1,12 +1,12 @@
 {
   "harness": "etna",
   "name": "etna",
-  "version": "1.5.5",
+  "version": "1.5.6",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "223330f92bc3"
+  "digest": "6114240474ef"
 }

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

@@ -72,6 +72,7 @@ The two guarantees are complementary and both break on mixing: a reader holding
 | Security / threat model | [`templates/security-overview.md`](templates/security-overview.md) |
 | Testing strategy | [`templates/testing-strategy.md`](templates/testing-strategy.md) |
 | Behavioral checklist for one feature (`docs/tests/{feature}.md`) | [`templates/behavioral-checklist.md`](templates/behavioral-checklist.md) — the verification gate's driving script, and the source its suite tests are drawn from |
+| Acceptance criteria for one capability (`docs/acceptance/{capability}.md`) | [`templates/acceptance-criteria.md`](templates/acceptance-criteria.md) — the promises the built product must keep, as stable `AC-n` keyed assert lines verification surfaces parse as claims |
 | Recurring procedure/setup | [`templates/operations-procedure.md`](templates/operations-procedure.md) |
 | Cold-start build order (implementation map) | [`templates/implementation-map.md`](templates/implementation-map.md) — authored by the executing session at build start, updated in place as waves complete |
 | Capture mid-execution knowledge (`docs/history/journal.md`) | [`templates/journal.md`](templates/journal.md) (record — append-only; a row resolves by landing in its owning doc) |
@@ -118,7 +119,13 @@ The two guarantees are complementary and both break on mixing: a reader holding
 
 ## Frontmatter Derivation
 
-A feature doc carries ownership frontmatter — `owns:` (required), `module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. Deriving it from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
+**Frontmatter is compulsory on every document this skill authors** — `type:` (the genre) on every
+doc, plus the genre's own keys beside it; a document without its frontmatter fails the skill's
+contract and is not done. A feature doc carries the full ownership set — `owns:` (required),
+`module:` (optional), `keywords:` (required), `status:` (required), optional `last-reviewed:`. An
+acceptance-criteria doc (`docs/acceptance/`) carries `type:` and `status:`. The single sanctioned
+exception is a genre the placement map explicitly marks frontmatter-less (the behavioral checklists
+in `docs/tests/`). Deriving ownership frontmatter from code and keeping it accurate is [`references/frontmatter.md`](references/frontmatter.md) — every feature-doc create or update, and the `maintenance` agent's baseline pass, route there.
 
 ---
 

package/data/harnesses/etna/skills/documentation/templates/acceptance-criteria.md

@@ -0,0 +1,37 @@
+# Acceptance Criteria
+
+Truth document. Use for: the promises one capability must keep, stated as machine-parseable
+claims. Lives in `docs/acceptance/`, one `kebab-case.md` per capability. Written at specification
+time — before implementation — and read by verification surfaces, which parse each `AC-n` line as
+a claim to grade the built product against.
+
+### Rules
+
+- **Frontmatter is required**: `type: acceptance-criteria`, `status:` (`draft` → `active` →
+  `deprecated`). No `owns:` — acceptance criteria own no code.
+- **One `AC-n` key per criterion, stable forever.** Keys are never renumbered and never reused: a
+  criterion that no longer applies is marked retired in place, so every claim a past verification
+  graded still resolves.
+- **Each criterion is one observable assert**, phrased as a checkable statement about the running
+  product — never about the code's internals. If it cannot be observed from outside, it is a
+  design note, not a criterion.
+- **The `AC-n:` line grammar is load-bearing** — verification parses these lines. Keep the key at
+  line start, exactly `AC-<number>:`, followed by the assert sentence. Formatting that buries the
+  key (tables, emphasis-wrapped keys, nested bullets) breaks the parse.
+
+### Template
+
+```markdown
+---
+type: acceptance-criteria
+status: draft
+---
+
+# Acceptance Criteria: {Capability}
+
+Scope: {one line — what part of the product these criteria bind}.
+
+- AC-1: {observable assert about the running product}.
+- AC-2: {observable assert}.
+- AC-3 (retired): {kept verbatim, marked retired — never renumbered}.
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nurix/etna",
-  "version": "0.19.84",
+  "version": "0.19.86",
   "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": {
@@ -42,5 +42,5 @@
     "agent",
     "plugin"
   ],
-  "etnaFingerprint": "574f23e45199"
+  "etnaFingerprint": "476fa48936bb"
 }