@nurix/etna 0.19.48 → 0.19.49

package/bin/etna.js

@@ -318,7 +318,7 @@ function mergeHooks(targetDir, bundledHooksJson) {
     const settings = readJson(settingsPath);
     settings.hooks = settings.hooks || {};
     let added = 0;
-    // Harness-shipped permission defaults (e.g. Edit/Write on docs/** flow without prompts —
+    // Harness-shipped permission defaults (e.g. Edit on docs/** flows without prompts —
     // the deny hooks still hard-block frozen/protected paths underneath). Additive, idempotent.
     for (const rule of bundled.permissions?.allow || []) {
         settings.permissions = settings.permissions || {};

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "6af99ea8c41f",
+    "fingerprint": "889424d916fc",
     "harnesses": {
         "apollo": {
             "plugin": "apollo",

package/data/harnesses/apollo/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "apollo",
   "name": "apollo",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -14,5 +14,5 @@
     "docs/history/backlog.md",
     "docs/memory/main.md"
   ],
-  "digest": "5d04f43486c8"
+  "digest": "113c398c1e31"
 }

package/data/harnesses/apollo/hooks/hooks.json

@@ -1,8 +1,7 @@
 {
   "permissions": {
     "allow": [
-      "Edit(docs/**)",
-      "Write(docs/**)"
+      "Edit(docs/**)"
     ]
   },
   "hooks": {

package/data/harnesses/apollo/skills/testing/SKILL.md

@@ -50,6 +50,28 @@ Derive the stack first, then place tests: a placement argument that starts "this
 
 Why this is the cheap strategy at the horizon: layering makes cost **additive** — a new API behavior costs one layer-2 test and maybe a layer-3 edge, zero frontend tests; a new UI state costs one layer-7 test, zero backend tests. A flat suite pays N×M, because every top-layer path implicitly re-verifies every behavior beneath it.
 
+## The tree
+
+The directory layout follows the strata, so a test's home states its layer and the runner split is mechanical, not per-file judgment:
+
+```
+tests/
+  schema/      L1 — infrastructure-bound runner (real engine)
+  domain/      L2 — infrastructure-bound runner (real storage, modeled ports)
+  routes/      L3 — infrastructure-bound runner (in-process app)
+  contract/    L4 — no runner; typed fixtures + interception handlers
+  client/      L5 — plain unit runner
+  view/        L6 — plain unit runner
+  component/   L7 — unit runner + DOM environment (per-file opt-in)
+  helpers/     shared seeds, fakes, and builders — owned by no stratum
+e2e/           L8 — its own config, never mixed into the unit runner's glob
+```
+
+- **A stratum the app lacks gets no directory** — an empty `component/` in a backend service is a lie about the app's shape.
+- **One shared glob list, imported by both runner configs** — the infrastructure-bound runner *includes* `schema|domain|routes`, the unit runner *excludes* them. Two hand-maintained lists drift; one imported constant cannot.
+- **Which concrete runner, framework, and DOM environment fill these slots is `testing.md`'s per-stack table** — this skill names the slot, never the brand, so the two files cannot disagree.
+- **Contract modules the provider binds** (the layer-4 source types) live in the app's shared source zone — importable by both provider and consumer builds — not in the test tree; `tests/contract/` holds only the fixtures and fakes compiled from them.
+
 ## Bridge to the obligation ledger
 
 The `test-plan` skill's ledger assigns each obligation a runner altitude — `unit` / `component` / `integration` / `e2e`. Those are coarse names for where a test *runs*; the strata here say what it may *assert*. The mapping:

package/data/harnesses/code/harness.json

@@ -1,12 +1,12 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.6.0",
+  "version": "3.6.1",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "d1663c2f882b"
+  "digest": "0efadb49b336"
 }

package/data/harnesses/code/hooks/hooks.json

@@ -1,8 +1,7 @@
 {
   "permissions": {
     "allow": [
-      "Edit(docs/**)",
-      "Write(docs/**)"
+      "Edit(docs/**)"
     ]
   },
   "hooks": {

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

@@ -50,6 +50,28 @@ Derive the stack first, then place tests: a placement argument that starts "this
 
 Why this is the cheap strategy at the horizon: layering makes cost **additive** — a new API behavior costs one layer-2 test and maybe a layer-3 edge, zero frontend tests; a new UI state costs one layer-7 test, zero backend tests. A flat suite pays N×M, because every top-layer path implicitly re-verifies every behavior beneath it.
 
+## The tree
+
+The directory layout follows the strata, so a test's home states its layer and the runner split is mechanical, not per-file judgment:
+
+```
+tests/
+  schema/      L1 — infrastructure-bound runner (real engine)
+  domain/      L2 — infrastructure-bound runner (real storage, modeled ports)
+  routes/      L3 — infrastructure-bound runner (in-process app)
+  contract/    L4 — no runner; typed fixtures + interception handlers
+  client/      L5 — plain unit runner
+  view/        L6 — plain unit runner
+  component/   L7 — unit runner + DOM environment (per-file opt-in)
+  helpers/     shared seeds, fakes, and builders — owned by no stratum
+e2e/           L8 — its own config, never mixed into the unit runner's glob
+```
+
+- **A stratum the app lacks gets no directory** — an empty `component/` in a backend service is a lie about the app's shape.
+- **One shared glob list, imported by both runner configs** — the infrastructure-bound runner *includes* `schema|domain|routes`, the unit runner *excludes* them. Two hand-maintained lists drift; one imported constant cannot.
+- **Which concrete runner, framework, and DOM environment fill these slots is `testing.md`'s per-stack table** — this skill names the slot, never the brand, so the two files cannot disagree.
+- **Contract modules the provider binds** (the layer-4 source types) live in the app's shared source zone — importable by both provider and consumer builds — not in the test tree; `tests/contract/` holds only the fixtures and fakes compiled from them.
+
 ## Bridge to the obligation ledger
 
 The `test-plan` skill's ledger assigns each obligation a runner altitude — `unit` / `component` / `integration` / `e2e`. Those are coarse names for where a test *runs*; the strata here say what it may *assert*. The mapping:

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.19.48",
+    "version": "0.19.49",
     "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": "6af99ea8c41f"
+    "etnaFingerprint": "889424d916fc"
 }