@nurix/etna 0.20.6 → 0.20.8

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

@@ -24,7 +24,7 @@ Document contracts and architecture, not implementation details. Show function s
 
 The journey — dates, migrations, progress, supersessions — lives only in records (`docs/history/`); when reality changes, a truth document simply becomes correct. The full strip-list and the record-side rules: [`references/style-guide.md`](references/style-guide.md) § The Two Natures — Tense & History.
 
-The mechanical subset of these rules is checked by [`scripts/doc-lint.mjs`](scripts/doc-lint.mjs) — run it over changed docs before finishing. Block-severity findings must be fixed; `<!-- doc-lint-disable: <id> -->` with a reason beside it is the escape hatch.
+The mechanical subset of these rules is checked by [`scripts/doc-lint.mjs`](scripts/doc-lint.mjs) — run it over changed docs before finishing. Block-severity findings must be fixed; `<!-- doc-lint-disable: <id> -->` with a reason beside it is the escape hatch. Two invocation traps: the disable comment takes **bare rule ids only** — prose inside the comment silently breaks the parse, so put the reason in a second comment beside it — and the script grades truth-vs-record scope by matching `docs/(history|research|memory)/` against **the path string it is given**, so always hand it a repo-root-relative path; linting a record from inside its own folder grades it as a truth document.
 
 ---
 
@@ -85,7 +85,7 @@ The two guarantees are complementary and both break on mixing: a reader holding
 | Derive/update a feature doc's `owns:` | [`references/frontmatter.md`](references/frontmatter.md) |
 | Update existing doc | § Editing an existing doc (below) |
 | Instruction file (`CLAUDE.md`, a rule, an agent, skill prose) | [`references/instruction-style.md`](references/instruction-style.md) — not these templates; every-load prose stays lean, and the present-tense rule still applies |
-| Author or restructure a **skill** (fit, triggers, shape, anatomy, shipping) | The skill-authoring field guide — the `etna` repo (`nurixlabs/etna`), folder `docs/architecture/skills/playbook/`, chapters `00`–`10`. **No etna checkout available ⇒ ask the user for access to the etna repo, or proceed from first principles** with [`references/instruction-style.md`](references/instruction-style.md) governing the prose. This row is the only place the playbook is referenced |
+| Author or restructure a **skill** (fit, triggers, shape, anatomy, shipping) | The skill-authoring field guide — the `etna` repo (`nurixlabs/etna`), folder `docs/playbooks/skills/`, chapters `00`–`10`. **No etna checkout available ⇒ ask the user for access to the etna repo, or proceed from first principles** with [`references/instruction-style.md`](references/instruction-style.md) governing the prose. This row is the only place the playbook is referenced |
 | **No template matches** | [`references/untemplated.md`](references/untemplated.md) — shape decisions + the co-authoring workflow |
 
 ---

package/data/harnesses/etna/skills/documentation/references/frontmatter.md

@@ -24,13 +24,20 @@ A feature doc's ownership frontmatter is `owns:` (required), `module:` (optional
 
 **1. `owns:`** (the path scope)
 
-Read the doc's content. Extract every source file path it references (file listings, function locations, component paths). Group them into the narrowest glob patterns that cover all referenced files without overlapping another doc's `owns:` globs at equal specificity. A doc may own several globs.
+`owns:` names the **regions whose truth this doc holds** — the directories where a change must be reconciled against this document before it ships. It is an authority claim a human makes, not an inventory of what the feature touches.
 
-| Doc references                       | Glob                      |
-| ------------------------------------ | ------------------------- |
-| Multiple files under one directory   | `src/feature/**`          |
-| Specific files in a shared directory | List each file explicitly |
-| A single entry-point file            | The exact file path       |
+**A file the doc merely references is not a file the doc owns.** Reaching across a boundary into a shared module is a fact about the code, and it belongs to whoever owns that module's region. Transcribing those reach edges as `owns:` entries is how an index stops being a routing table and becomes a hand-maintained import graph: rows then track the dependency graph rather than the feature count, and the shared upstream file ends up filed under whichever downstream feature happened to name it first — a consumer recorded as the authority.
+
+Prefer one region glob over many file globs. Ten paths say nothing about which is the entry point; one region says where the doc's writ runs.
+
+| The doc governs                              | Glob                                 |
+| -------------------------------------------- | ------------------------------------ |
+| A feature's own directory                     | `src/feature/**`                     |
+| A feature split across two directories        | One glob each                        |
+| A single entry-point file, and nothing beside it | The exact file path                  |
+| A shared file several features import         | **Nothing — leave it unowned**       |
+
+**An unowned shared file is the system working, not a gap.** A shared module's authority is the contract it exposes, not any one consumer, so a library-references file or a common utility legitimately has no owning doc. Claiming it would make the index bigger and the routing less certain at once.
 
 Glob each pattern against the codebase. At `status: active`, drop any that match nothing; at `status: draft`, projected globs may match nothing yet — confirm them against real code when the doc flips to `active`.
 

package/data/harnesses/etna/skills/documentation/templates/plan.md

@@ -71,7 +71,10 @@ Why this work is happening *now*. Link to the spec for *what* we're building; th
 <!-- Written by the `testing` skill (plan-gate mode) at the plan gate (after `boundary`). One row per
      promised behavior: layer · target file · oracle · fixtures · an empty Outcome cell the
      verification gate fills (satisfied / owes nothing / blocked → backlog). Amendable while the
-     plan is open. Do not hand-author. -->
+     plan is open. Do not hand-author. NEVER put a pipe in a ledger cell, escaped or not — the
+     compliance hook splits rows on `|` at a fixed column index with no unescaping, so a
+     markdown-legal `\|` shifts every later cell and the wall blocks a row that is in fact
+     discharged. Write "`install` or `update`", not "`install \| update`". -->
 
 ## Open Questions
 

package/data/harnesses/hr/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "hr",
   "name": "hr",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "files": [
     ".prettierignore",
     ".prettierrc.json",

package/data/harnesses/kb-agi/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "kb-agi",
   "name": "kb-agi",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "files": [
     ".prettierignore",
     ".prettierrc.json",

package/lib/codex/README.md

@@ -32,7 +32,7 @@ The two channels do not install the same set. The **CLI** writes the full Codex
 
 ## Subagents are authored, not derived at install
 
-`.claude/agents/*.md → .codex/agents/*.toml` is a semantic conversion, so the twin is **authored from the `.md` by following** [`docs/architecture/harness/authoring-agents.md`](../../../../docs/architecture/harness/authoring-agents.md) — the model that writes or edits the agent produces the twin inline (frontmatter → `name`/`description`, body verbatim → `developer_instructions`, `tools:` dropped to a comment, Claude model aliases omitted), with **no external CLI**. The committed `agents/<name>.codex.toml` is checked by the validation gate:
+`.claude/agents/*.md → .codex/agents/*.toml` is a semantic conversion, so the twin is **authored from the `.md` by following** [`docs/playbooks/agents.md`](../../../../docs/playbooks/agents.md) — the model that writes or edits the agent produces the twin inline (frontmatter → `name`/`description`, body verbatim → `developer_instructions`, `tools:` dropped to a comment, Claude model aliases omitted), with **no external CLI**. The committed `agents/<name>.codex.toml` is checked by the validation gate:
 
 ```bash
 node packages/cli/lib/codex/validate-codex-agents.mjs   # or: npm run validate:codex-agents

package/lib/codex/validate-codex-agents.mjs

@@ -1,6 +1,6 @@
 // packages/cli/lib/codex/validate-codex-agents.mjs
 // The Codex-twin validation gate — decoupled from any generator. A `<name>.codex.toml`
-// twin is now authored by the AI following docs/architecture/harness/authoring-agents.md,
+// twin is now authored by the AI following docs/playbooks/agents.md,
 // so this is the check that keeps a malformed or Claude-only twin from shipping: the twins
 // are copied UNPARSED into the bundle (build-data.js) and a consumer's .codex/agents/, so
 // nothing else catches a bad one before Codex fails to load it in that repo. Run it after

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nurix/etna",
-  "version": "0.20.6",
+  "version": "0.20.8",
   "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": "5e362f34919c"
+  "etnaFingerprint": "bcf04d8d525c"
 }