@nurix/etna 0.19.32 → 0.19.34

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

@@ -1,61 +1,61 @@
 # General Standards
 
-Runtime versions and the canonical package list — the workspace baseline every Nurix code harness loads. Web-frontend/styling conventions are [`frontend.md`](frontend.md); the Express server and the API response envelope are [`express.md`](express.md).
+Runtime versions, the canonical package list, and GitHub Actions pins — the workspace baseline. Web-frontend/styling conventions are [`frontend.md`](frontend.md); the Express server and the API response envelope are [`express.md`](express.md).
 
 ## Runtime Versions
 
 - **Node.js:** 24 LTS
-- **Package manager:** detect from lockfile (`pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `package-lock.json` → npm). Don't hardcode one.
+- **Package manager:** detect from the lockfile — **never** hardcode one.
 - **PostgreSQL:** 17 · **Redis:** 7.x (latest)
 
-## Recommended Packages
-
-No alternatives. Just use these.
-
-| Package                  | Version   | Use                    | Don't use                  |
-| ------------------------ | --------- | ---------------------- | -------------------------- |
-| react                    | ^19.2.3   | UI components          | -                          |
-| vite                     | ^8.0.0    | Build tool, dev server | webpack, CRA               |
-| tailwindcss              | ^4.1.18   | Styling                | styled-components          |
-| @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             |
-| react-redux              | ^9.2.0    | Redux React bindings   | -                          |
-| axios                    | ^1.13.2   | HTTP requests          | fetch                      |
-| date-fns                 | ^4.1.0    | Date formatting        | moment, dayjs              |
-| @dnd-kit/core            | ^6.3.1    | Drag and drop          | react-beautiful-dnd        |
-| @xyflow/react            | ^12.11.0  | Node-based flow charts | reactflow, react-flow-renderer |
-| motion                   | ^12.23.26 | Animations             | react-spring               |
-| sonner                   | ^2.0.7    | Toast notifications    | react-toastify             |
-| react-window             | ^2.2.3    | List virtualization    | react-virtualized          |
-| nanoid                   | ^6.0.0    | ID generation          | uuid                       |
-| express                  | ^5.2.1    | HTTP server            | fastify, koa               |
-| drizzle-orm              | ^0.45.2   | Database ORM           | prisma, sequelize, typeorm |
-| drizzle-kit              | ^0.31.10  | Schema tooling         | -                          |
-| zod                      | ^4.2.1    | Schema validation      | yup, joi                   |
-| jose                     | ^6.1.3    | JWT handling           | jsonwebtoken               |
-| microdiff                | ^1.5.0    | JSON object diffing    | deep-diff, just-diff       |
-| react18-json-view        | ^0.2.9    | JSON tree view         | react-json-view            |
-| @tiptap/react            | ^3.11.1   | Rich text editor       | slate, quill, draft-js     |
-| shiki                    | ^4.3.1    | Syntax highlighting    | prism, highlight.js        |
-| lucide-react             | ^1.26.0   | Icons                  | react-icons, heroicons     |
-| @pdfme/generator         | ^6.1.12   | PDF generation         | jspdf, pdfkit              |
-| cmdk                     | ^1.1.1    | Command palette        | kbar, ninja-keys           |
-| @monaco-editor/react     | ^4.7.0    | Code editor            | codemirror, ace            |
-| localforage              | ^1.10.0   | Client-side storage    | idb, dexie                 |
-| react-markdown           | ^10.1.0   | Markdown rendering     | marked, markdown-it        |
-| remark-gfm               | ^4.0.1    | GFM (tables, tasklists) | remark-github, custom      |
-| fast-deep-equal          | ^3.1.3    | Deep equality checks   | lodash.isEqual             |
-| @ngneat/falso            | latest    | Fake data generation   | @faker-js/faker, chance    |
-| pino                     | ^10.1.0   | Logging                | winston                    |
+## Packages
+
+**Only** these — no alternatives.
+
+| Package | Version | Use | Don't use |
+| --- | --- | --- | --- |
+| `react` | ^19.2.3 | UI components | — |
+| `vite` | ^8.0.0 | Build tool, dev server | `webpack`, CRA |
+| `tailwindcss` | ^4.1.18 | Styling | `styled-components` |
+| `@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` |
+| `react-redux` | ^9.2.0 | Redux React bindings | — |
+| `axios` | ^1.13.2 | HTTP requests | `fetch` |
+| `date-fns` | ^4.1.0 | Date formatting | `moment`, `dayjs` |
+| `@dnd-kit/core` | ^6.3.1 | Drag and drop | `react-beautiful-dnd` |
+| `@xyflow/react` | ^12.11.0 | Node-based flow charts | `reactflow`, `react-flow-renderer` |
+| `motion` | ^12.23.26 | Animations | `react-spring` |
+| `sonner` | ^2.0.7 | Toast notifications | `react-toastify` |
+| `react-window` | ^2.2.3 | List virtualization | `react-virtualized` |
+| `nanoid` | ^6.0.0 | ID generation | `uuid` |
+| `express` | ^5.2.1 | HTTP server | `fastify`, `koa` |
+| `drizzle-orm` | ^0.45.2 | Database ORM | `prisma`, `sequelize`, `typeorm` |
+| `drizzle-kit` | ^0.31.10 | Schema tooling | — |
+| `zod` | ^4.2.1 | Schema validation | `yup`, `joi` |
+| `jose` | ^6.1.3 | JWT handling | `jsonwebtoken` |
+| `microdiff` | ^1.5.0 | JSON object diffing | `deep-diff`, `just-diff` |
+| `react18-json-view` | ^0.2.9 | JSON tree view | `react-json-view` |
+| `@tiptap/react` | ^3.11.1 | Rich text editor | `slate`, `quill`, `draft-js` |
+| `shiki` | ^4.3.1 | Syntax highlighting | `prism`, `highlight.js` |
+| `lucide-react` | ^1.26.0 | Icons | `react-icons`, `heroicons` |
+| `@pdfme/generator` | ^6.1.12 | PDF generation | `jspdf`, `pdfkit` |
+| `cmdk` | ^1.1.1 | Command palette | `kbar`, `ninja-keys` |
+| `@monaco-editor/react` | ^4.7.0 | Code editor | `codemirror`, `ace` |
+| `localforage` | ^1.10.0 | Client-side storage | `idb`, `dexie` |
+| `react-markdown` | ^10.1.0 | Markdown rendering | `marked`, `markdown-it` |
+| `remark-gfm` | ^4.0.1 | GFM (tables, tasklists) | `remark-github`, custom |
+| `fast-deep-equal` | ^3.1.3 | Deep equality checks | `lodash.isEqual` |
+| `@ngneat/falso` | latest | Fake data generation | `@faker-js/faker`, `chance` |
+| `pino` | ^10.1.0 | Logging | `winston` |
 
 ## GitHub Actions
 
 Pin the major, and check it against the action's releases — a major behind still runs, so a stale pin never fails, it only warns.
 
-| Action                     | Version | Use                        |
-| -------------------------- | ------- | -------------------------- |
-| actions/checkout           | v7      | Repo checkout              |
-| actions/setup-node         | v7      | Node toolchain + npm cache |
+| Action | Version | Use |
+| --- | --- | --- |
+| `actions/checkout` | v7 | Repo checkout |
+| `actions/setup-node` | v7 | Node toolchain + npm cache |
 
-Set `node-version` from the Runtime Versions block above, not from whatever the runner defaults to.
+Set `node-version` from the Runtime Versions block above, **never** from the runner's default.

package/data/harnesses/etna/rules/kb.md

@@ -1,13 +1,6 @@
-# kb.md — Patterns for Obsidian-like Folders
+# Knowledge-Base Folders
 
-Conventions for any folder that is majority markdown — `docs/`, `research/`, an Obsidian vault, or any knowledge base. Rules grow over time; append new ones below.
+Conventions for any folder that is majority markdown — `docs/`, `research/`, an Obsidian vault, any knowledge base. Folder shape and linking only.
 
-## Rules
-
-### 1. Every topic gets a `Readme.md`
-
-When you start documenting a topic, create `Readme.md` as the folder's landing page. Don't use `index.md` or unscoped filenames — `Readme.md` is what readers and tools (GitHub, Obsidian) look for first, and it makes the folder self-introducing.
-
-### 2. Always link documents to each other
-
-When one document references an idea, concept, or topic covered in another, link to it. Wikilinks (`[[other-doc]]`) inside Obsidian-native vaults; relative markdown links (`[label](../other-doc.md)`) elsewhere. If you mention it, you link it — that's how the folder becomes a knowledge graph instead of a pile of files.
+- **Every topic folder carries a `Readme.md`**, created with the topic's first document — **never** `index.md` or an unscoped filename. `Readme.md` is what GitHub and Obsidian surface first, so every folder introduces itself.
+- **Every mention is a link** — wikilinks (`[[other-doc]]`) inside Obsidian-native vaults, relative markdown links (`[label](../other-doc.md)`) everywhere else. Unlinked mentions decay a knowledge graph into a pile of files.

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

@@ -1,34 +1,34 @@
-# Nomenclature Guidelines
+# Nomenclature
 
-## Naming Guidelines
+Naming and casing for code — identifiers, files, folders. The rationale throughout is consistency: one concept, one name, one casing shape, in every repo that loads this rule. Database naming is not here — see § Database.
 
-- Use descriptive names that reveal intent, purpose, and usage
-- Names should explain why something exists and how it's used
-- Favor clarity over brevity
-- Maintain consistency within the codebase
-- Avoid abbreviations unless they're universally understood
+Names state intent in full words — clarity over brevity; no abbreviations unless universally understood (`id`, `url` ✅ · `cfg`, `btn`, `idx` ❌).
 
-## Naming Styles
+## Casing
 
-- Variables : Use nouns or noun phrases. Examples: `userData`, `firstName`, `paymentStatus`, `configOptions`
-- Functions & Methods : Use verbs or verb phrases that describe the action. Examples: `calculateTotal`, `getUserInfo`, `validateInput`, `sendNotification`
-- Boolean Variables : Prefix with is**, has**, can**, or should**. Examples: `isValid`, `hasPermission`, `canEdit`, `shouldRefresh`
-- Arrays : Use plural nouns. Examples: `users`, `productList`, `errorMessages`, `activeConnections`
-- Classes & Components : Use singular nouns or noun phrases. Examples: `RequestHandler`, `UserProfile`, `PaymentProcessor`, `DataValidator`
-- Constants : Use uppercase with meaningful names. Examples: `DEFAULT_TIMEOUT`, `API_BASE_URL`, `MAX_RETRY_COUNT`, `COLOR_PRIMARY`
-- Event Handlers : Use Prefix with handle or on. Examples: `handleSubmit`, `onUserLogin`, `handleInputChange`, `onPageLoad`
-- Interfaces & Types : Use Consider prefixing with I for interfaces (if preferred). Examples: `IUserData`, `IConfigOptions`, `AuthResponse`, `RequestParams`
-- Promises & Async Functions : Use Consider using future tense or suffixes like Async. Examples: `fetchUserData`, `getUserProfileAsync`, `loadConfigAsync`, `processPayment`
-- File & Folder Structure : Use lowercase with descriptive names. Group by feature or function type. Example: `auth/login_service.js`
+| Casing | Used for | Example |
+| --- | --- | --- |
+| `camelCase` | variables, functions, methods, properties; a module file exporting no component | `calculateTotal`, `sessionClient.ts` |
+| `PascalCase` | classes, type definitions, components; the file exporting one | `PaymentProcessor`, `AppsListPage.tsx` |
+| `UPPER_SNAKE_CASE` | constants, environment variables | `MAX_RETRY_COUNT` |
+| `kebab-case` | URLs, CSS class names, HTML IDs, multi-word folders | `user-profile`, `workspace-provisioning/` |
+| `snake_case` | database tables, columns, indexes — § Database | `created_at` |
 
-## Casing Styles
+**A file exporting one component carries that component's name exactly**, so an import names the file it came from; a single-word folder is plain lowercase (`lib`, `surfaces`). ❌ Never `snake_case` a file or folder — that casing belongs to the database.
 
-- camelCase : Used in Variables, function names, method names, property names. Examples: `userData`, `calculateTotal`, `firstName`, `isValidEmail`
-- PascalCase : Used in Class names, component names, type definitions. Examples: `UserProfile`, `DataService`, `AuthProvider`, `RequestHandler`
-- snake_case : Used in File names, folder names. Examples: `user_service`, `api_utils`, `auth_middleware`, `data_models`
-- UPPER_SNAKE_CASE : Used in Constants, environment variables. Examples: `MAX_RETRY_COUNT`, `API_KEY`, `DEFAULT_TIMEOUT`, `COLOR_PRIMARY`
-- kebab-case : Used in URLs, CSS class names, HTML IDs. Examples: `nav-container`, `user-profile`, `button-primary`, `form-wrapper`
+## Identifier shape
+
+| Identifier | Shape | Example |
+| --- | --- | --- |
+| Variable | noun phrase | `paymentStatus` |
+| Function / method | verb phrase naming the action | `validateInput` |
+| Boolean | `is` / `has` / `can` / `should` prefix — **never** a bare adjective | `hasPermission` |
+| Array / collection | plural noun | `errorMessages` |
+| Class / component | singular noun phrase | `RequestHandler` |
+| Event handler | `handle` or `on` prefix | `handleSubmit`, `onPageLoad` |
+| Interface | `I` prefix acceptable; type aliases stay plain | `IConfigOptions`, `AuthResponse` |
+| Async function | verb phrase; `Async` suffix acceptable | `loadConfigAsync` |
 
 ## Database
 
-Table, column, index, and key naming for relational schemas — the `id` / `slug` / `label` vocabulary, junction `_map` tables, and Drizzle mirrors — lives in [`database.md`](database.md), the cross-project database conventions rule. Kept there, not here, so there is one canonical home and the same concept carries the same name in every project.
+Table, column, index, and key naming for relational schemas — the `id` / `slug` / `label` vocabulary, junction `_map` tables, and Drizzle mirrors — lives in [`database.md`](database.md), which routes general code naming back here.

package/data/harnesses/etna/rules/testing.md

@@ -1,25 +1,23 @@
 # Testing
 
-Framework choice is never ad hoc and never the user's problem mid-task: detect the stack, use its row. If the repo already has a runner, that runner wins — never introduce a second framework beside it.
+Test technology and placement — framework per stack, suite layout, mocking policy; the suite-first policy (what gets tests, run-and-report discipline) is the harness `CLAUDE.md` Tests guardrail, not here. Framework choice is **never** ad hoc and never the user's problem mid-task: detect the stack, use its row; if the repo already has a runner, that runner wins — **never** introduce a second framework beside it.
 
 ## Frameworks by stack
 
-No alternatives. Just use these.
-
 | Stack | Unit / integration | Component | E2E | HTTP mocking | Don't use |
 | --- | --- | --- | --- | --- | --- |
-| Node + Vite / React (web) | vitest | @testing-library/react (+ @testing-library/user-event, happy-dom) | @playwright/test | msw | jest, mocha, jasmine, cypress, enzyme |
-| Express APIs | vitest | — | supertest against the app instance | msw (outbound calls) | jest, chai-http |
-| React Native / Expo | jest via the jest-expo preset | @testing-library/react-native | maestro | msw | detox, enzyme |
-| Cloudflare Workers | vitest + @cloudflare/vitest-pool-workers | — | @playwright/test against `wrangler dev` | msw | jest |
+| Node + Vite / React (web) | `vitest` | `@testing-library/react` (+ `@testing-library/user-event`, `happy-dom`) | `@playwright/test` | `msw` | `jest`, `mocha`, `jasmine`, `cypress`, `enzyme` |
+| Express APIs | `vitest` | — | `supertest` against the app instance | `msw` (outbound calls) | `jest`, `chai-http` |
+| React Native / Expo | `jest` via the `jest-expo` preset | `@testing-library/react-native` | `maestro` | `msw` | `detox`, `enzyme` |
+| Cloudflare Workers | `vitest` + `@cloudflare/vitest-pool-workers` | — | `@playwright/test` against `wrangler dev` | `msw` | `jest` |
 | Rust | `cargo test` (built-in) | — | — | — | — |
 
-All npm packages at `latest`. Fake data comes from `@ngneat/falso` (the repo standard — never faker/chance).
+Test packages install at `latest` — they sit outside [`general.md`](general.md)'s pinned table. Fake data comes from `@ngneat/falso` — **never** `@faker-js/faker` / `chance` (its row there).
 
 ## Conventions
 
-- **Suite, not scripts.** Tests live in the canonical test tree — `tests/` mirroring `src/`, or the convention the repo already uses (detect, don't invent) — named `<subject>.test.ts`. Shared fixtures, factories, and helpers live in `tests/helpers/` (or the suite's existing shared location). The harness `CLAUDE.md` Tests guardrail carries the suite-first policy (what gets tests, discipline); this rule owns the technology and placement choices.
-- **Wire the canonical command.** `"test"` in package.json runs the whole unit suite (`vitest run`); e2e runs under `"test:e2e"`. A repo where `pnpm test`/`npm test` doesn't run the suite is misconfigured.
-- **Unit and E2E trees stay separate.** Vitest/Jest suites in `tests/`; Playwright/Maestro suites in `e2e/` with their own config — never mixed into the unit runner's glob.
-- **No test doubles for what you own.** Prefer real instances — in-memory SQLite for drizzle, the actual Express app via supertest — over mocks; mock only true externals (network via msw, time via the runner's fake timers).
-- **Determinism.** No real network, no real time, no shared mutable state between tests; every test must pass alone and in any order.
+- **Suite, not scripts.** Tests live in the canonical test tree — `tests/` mirroring `src/`, or the convention the repo already uses — named `<subject>.test.ts`; shared fixtures, factories, and helpers in `tests/helpers/` (or the suite's existing shared home).
+- **Wire the canonical command.** `"test"` in `package.json` runs the whole unit suite (`vitest run`); e2e under `"test:e2e"`. A repo where `pnpm test` / `npm test` doesn't run the suite is misconfigured — fix the wiring, **never** route around it.
+- **Unit and E2E trees stay separate.** Vitest/Jest suites in `tests/`; Playwright/Maestro suites in `e2e/` with their own config — **never** mixed into the unit runner's glob.
+- **No test doubles for what you own.** Prefer real instances — in-memory SQLite for drizzle, the actual Express app via `supertest` — over mocks; mock **only** true externals (network via `msw`, time via the runner's fake timers).
+- **Determinism.** No real network, no real time, no shared mutable state between tests; every test **must** pass alone and in any order.

package/data/harnesses/hr/harness.json

@@ -1,11 +1,11 @@
 {
   "harness": "hr",
   "name": "hr",
-  "version": "0.1.11",
+  "version": "0.1.13",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "2cd2d7347c4f"
+  "digest": "077993d5c509"
 }

package/data/harnesses/hr/rules/code-eval-batcher.md

@@ -1,45 +1,45 @@
 # Code-Eval Batcher
 
-When asked to evaluate and rank **multiple code projects** against the production-readiness + product-quality rubric — candidate take-homes, submissions, a folder of repos — you (the main agent) drive this directly. You can dispatch sub-agents in parallel; a sub-agent cannot, which is why this is a rule you perform, not an agent you delegate to.
-
-This is distinct from `interview-eval` (which scores how a person *steered a session*). This rule scores the *project's code and product*, across many projects, and ranks them.
+Evaluating and ranking **multiple code projects** — candidate take-homes, submissions, a folder of repos — against the production-readiness + product-quality rubric. The main agent drives this directly: it can dispatch sub-agents in parallel and a sub-agent cannot, so this is a rule to perform, not an agent to delegate to. A single project does **not** need this rule — invoke the `evaluator` skill directly. Scoring how a person *steered a session* is `interview-eval`, not this rule.
 
 ## Division of labor
 
-Per-project scoring — the rubric, gates, absolute banding, the 8 sub-criteria, every recipe — belongs to the **`evaluator` skill** (`.claude/skills/evaluator/`). Do not re-derive or re-band it here. This rule owns only what the skill deliberately doesn't: **enumeration, parallel dispatch, weighting, and the cross-project rollup.** Bands are absolute — never re-band a project against the others; only weight and normalize.
+Per-project scoring — the rubric, gates, absolute banding, the 8 sub-criteria, every recipe — belongs to the **`evaluator` skill** (`.claude/skills/evaluator/`); never re-derive it here. This rule owns only what the skill deliberately doesn't: **enumeration, parallel dispatch, weighting, and the cross-project rollup.** **Never re-band a project against the others** — cohort-relative banding is the anti-pattern this design removed; the only cross-project levers live in the weights block.
 
 ## Procedure
 
 | # | Step |
 | --- | --- |
-| 0 | **Preflight once:** `bash .claude/skills/evaluator/preflight.sh`. Halt on non-zero and report the missing tools — do not score with degraded signals. |
-| 1 | **Enumerate** the projects → a list of local paths, one slug each (its dir name). Choose an `out_dir` (default `./code-eval-out`). |
-| 2 | **Dispatch in parallel — rolling window of 4.** For each project, `Agent(subagent_type="general-purpose", run_in_background=True, …)` instructing it to invoke the `evaluator` skill on that one project path, write the workspace to `<out_dir>/<slug>/`, validate it (`python3 .claude/skills/evaluator/validate_scorecard.py <out_dir>/<slug>/scorecard.yaml`), and return the workspace path + the scorecard's `normalized`. Fire a replacement the moment any slot frees so 4 are always in flight. |
-| 3 | **Collect** every `<out_dir>/*/scorecard.yaml`. Re-dispatch any that fail validation once; on a second failure mark the project `VALIDATION_FAILED` and continue. |
+| 0 | **Preflight once:** `bash .claude/skills/evaluator/preflight.sh`. Halt on non-zero and report the missing tools — never score with degraded signals. |
+| 1 | **Enumerate** the projects → local paths, one slug each (its dir name). Choose an `out_dir` (default `./code-eval-out`). |
+| 2 | **Dispatch in parallel — rolling window of 4.** Per project: `Agent(subagent_type="general-purpose", run_in_background=True, …)` instructing it to invoke the `evaluator` skill on that one path, write the workspace to `<out_dir>/<slug>/`, validate it (`python3 .claude/skills/evaluator/validate_scorecard.py <out_dir>/<slug>/scorecard.yaml`), and return the workspace path + the scorecard's `normalized`. Fire a replacement the moment a slot frees. |
+| 3 | **Collect** every `<out_dir>/*/scorecard.yaml`. Re-dispatch a validation failure once; on the second failure mark the project `VALIDATION_FAILED` and continue. |
 | 4 | **Weight + normalize** every project (math below) using the weights block. |
-| 5 | **Rollup** → `<out_dir>/results/{scorecard.csv, ranking.md, summary.md}`, sorted by rank score desc. Echo the exact weights + normalization used into `summary.md` so the ranking is reproducible. Leave everything uncommitted. |
-
-A single project does **not** need this rule — invoke the `evaluator` skill directly.
+| 5 | **Rollup** → `<out_dir>/results/{scorecard.csv, ranking.md, summary.md}` (contents below), sorted by rank score desc. Leave everything uncommitted. |
 
 ## Weighting math
 
-For each project `p`, read the raw 0–5 `score` of each sub-criterion `s` from its `scorecard.yaml`:
+For each project `p`, read each sub-criterion `s`'s raw 0–5 `score` (the evaluator's absolute band) from its `scorecard.yaml`:
 
-1. **Weighted (0–100)** over sub-criteria with a non-null band and `weight > 0`:
-   `weighted_p = 100 × Σ_s (band_{p,s} / 5 × weight_s) / Σ_s weight_s`
+1. **Weighted (0–100)** over sub-criteria with a non-null `score` and `weight > 0`:
+   `weighted_p = 100 × Σ_s (score_{p,s} / 5 × weight_s) / Σ_s weight_s`
 2. **Gate penalty:** `adjusted_p = max(0, weighted_p − Σ_{g ∈ gates_triggered_p} gate_penalties[g])`.
-3. **Normalize across the set** `{adjusted_p}` per `normalization`:
-   - `percent_of_max` → `adjusted_p` unchanged (absolute; comparable across runs).
-   - `min_max` → `100 × (adjusted_p − min) / (max − min)`; if `max == min`, all = 100.
-   - `z_score` → `clamp(0, 100, 50 + 10 × (adjusted_p − mean) / sd)`; if `sd == 0` or n < 2, fall back to `adjusted_p`.
+3. **Normalize** across the set `{adjusted_p}` per `normalization`:
+   - `percent_of_max` (default) → `adjusted_p` unchanged — absolute, comparable across runs.
+   - `min_max` → `100 × (adjusted_p − min) / (max − min)`; `max == min` ⇒ all 100. Spreads a tight set; not comparable across runs.
+   - `z_score` → `clamp(0, 100, 50 + 10 × (adjusted_p − mean) / sd)`; `sd == 0` or n < 2 ⇒ fall back to `adjusted_p`.
 
-`VALIDATION_FAILED` projects are excluded from min/max/mean/sd and listed separately. A null sub-criterion drops out of that project's weighted average — don't impute a 0. Compute with a short throwaway script over the scorecards; round reported scores to 2 decimals.
+`VALIDATION_FAILED` projects are excluded from min/max/mean/sd and listed separately. A null sub-criterion drops out of that project's weighted average — never impute a 0. Compute with a short throwaway script over the scorecards; round reported scores to 2 decimals.
 
-`scorecard.csv` columns: `rank, project, <8 bands>, gates, short_circuited, evaluator_total, weighted, penalty, rank_score`. `ranking.md`: a ranked table headed with the normalization method (the sort key). `summary.md`: n scored, the weights/penalties/normalization used, top-5 / bottom-5, gate frequency, any `VALIDATION_FAILED`.
+| Output | Contents |
+| --- | --- |
+| `scorecard.csv` | `rank, project, <8 scores>, gates, short_circuited, evaluator_total, weighted, penalty, rank_score` |
+| `ranking.md` | ranked table headed with the normalization method — the sort key |
+| `summary.md` | n scored, the exact weights / penalties / normalization used, top-5 / bottom-5, gate frequency, any `VALIDATION_FAILED` |
 
 ## Weights — edit this block to change the ranking
 
-These are the only cross-project knobs. Edit the values to re-rank; the math above consumes them verbatim. (Edits here are overwritten if you re-install the harness — to persist a custom weighting, drop a `code-eval-batcher.weights.json` with the same shape in your `out_dir` and read that instead.)
+The math above consumes these values verbatim. Edits here are overwritten on a harness re-install — to persist a custom weighting, drop a `code-eval-batcher.weights.json` with the same shape in the `out_dir` and read that instead.
 
 ```json
 {
@@ -61,11 +61,7 @@ These are the only cross-project knobs. Edit the values to re-rank; the math abo
 }
 ```
 
-- **`weights`** — relative importance of each sub-criterion; any non-negative numbers (normalized to sum 100 over the present, weighted ones). Set one to `0` to drop that sub-criterion. Defaults (all 12.5) reproduce the evaluator's own equal-weight total.
-- **`gate_penalties`** — flat 0–100-scale points docked per triggered gate, on top of the band caps the evaluator already applied. Default 0 = rely only on the evaluator's caps. E.g. `SECRETS: 15` docks 15 from any project with a committed secret.
-- **`normalization`** — `percent_of_max` (absolute, default) · `min_max` (spreads a tight set; not comparable across runs) · `z_score` (distance from the set mean).
-
-## Discipline
+- **`weights`** — relative importance; any non-negative numbers, normalized to sum 100 over the present, weighted sub-criteria. `0` drops a sub-criterion. The all-12.5 default reproduces the evaluator's own equal-weight total.
+- **`gate_penalties`** — flat 0–100-scale points docked per triggered gate, on top of the band caps the evaluator already applied. Default 0 = rely on the evaluator's caps alone. E.g. `SECRETS: 15` docks 15 from any project with a committed secret.
 
-- **No silent fallback.** A malformed weights block, a failed preflight, or a scorecard that won't validate is reported loudly — never worked around.
-- **You weight; the evaluator bands.** Changing a project's band because of how others scored is the cohort-relative anti-pattern this design removed. Your only cross-project levers are the weights block.
+**No silent fallback.** A malformed weights block, a failed preflight, or a scorecard that won't validate is reported loudly — never worked around.

package/package.json

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