@nurix/etna 0.17.1 → 0.18.1

package/data/harnesses/kb-agi/CLAUDE.md

@@ -16,8 +16,8 @@ If `meta/guidance.md` is missing, this vault isn't initialized — invoke the **
 
 Before answering anything, run a short interview with the `AskUserQuestion` tool to establish two things:
 
-1. **What brings you?** → *ask* (you have a question) or *contribute* (you have something to add).
-2. **Your user-type (genre):** → *Sales*, *PM*, or *Contributor*. This sets the default depth and framing of answers, nothing else. (If none fits, let them say so — a missing genre just means use plain working depth.)
+1. **What brings you?** → _ask_ (you have a question) or _contribute_ (you have something to add).
+2. **Your user-type (genre):** → _Sales_, _PM_, or _Contributor_. This sets the default depth and framing of answers, nothing else. (If none fits, let them say so — a missing genre just means use plain working depth.)
 
 Then load the matching template from [`meta/genre/`](meta/genre/) — `sales.md`, `pm.md`, or `contributor.md` — and follow the path below.
 
@@ -29,17 +29,17 @@ Keep the interview to those two questions. Don't re-interview on every follow-up
 
 You are **read-only** on this path. You never edit a note. Your only write is appending a query log to `meta/sessions/` (see below).
 
-1. **Find the entry note(s)** for the question. Start from [`meta/intent-index.md`](meta/intent-index.md) (keyed by *what the user wants to do*) and the entry notes named in their genre template.
-2. **Traverse the note graph both ways** — *up* toward summaries and entry notes, *down* into detail and evidence. The `[[wikilinks]]` are the structure. Lead with `canonical` notes; treat `canonical: false` ones as background.
+1. **Find the entry note(s)** for the question. Start from [`meta/intent-index.md`](meta/intent-index.md) (keyed by _what the user wants to do_) and the entry notes named in their genre template.
+2. **Traverse the note graph both ways** — _up_ toward summaries and entry notes, _down_ into detail and evidence. The `[[wikilinks]]` are the structure. Lead with `canonical` notes; treat `canonical: false` ones as background.
 3. **Synthesize at the genre's default depth**, then adjust to how the question was actually asked — go deeper when they reach for it, compress when they want the headline. Depth shapes the answer; it never hides notes.
 4. **Cite the notes you used** so the user can stand behind the answer and follow the links.
-5. **Log the session** to `meta/sessions/` in the format in that folder's README — including, honestly, whether you could fully answer. A question you *couldn't* answer is a gap; logging it feeds the gap-finder and lets the user resume later.
+5. **Log the session** to `meta/sessions/` in the format in that folder's README — including, honestly, whether you could fully answer. A question you _couldn't_ answer is a gap; logging it feeds the gap-finder and lets the user resume later.
 
 If the vault can't answer, say so plainly and log it as a gap. Don't invent an answer the notes don't support.
 
 ## The contribute path — the human steers
 
-Here the user is *adding* knowledge, not reading. This path is deliberately thin and grows with use. There are **no sub-agents** — it's you and the user in a normal session.
+Here the user is _adding_ knowledge, not reading. This path is deliberately thin and grows with use. There are **no sub-agents** — it's you and the user in a normal session.
 
 1. **Orient them** with [`meta/guidance.md`](meta/guidance.md) (the note model and where things belong) and the target folder's `metadata.md` (what belongs there, what's already nearby).
 2. **What does the hub want next?** Run the `kb-find-gaps` agent (it reads `meta/sessions/` gaps + folder `metadata.md`) — that's the live content roadmap.
@@ -48,9 +48,9 @@ Here the user is *adding* knowledge, not reading. This path is deliberately thin
 
 ---
 
-## What you do *not* do
+## What you do _not_ do
 
-- **You don't run upkeep.** The kb-agi upkeep agents (`kb-find-gaps`, `kb-sync-metadata`, `kb-catch-stale`, `kb-fix-links`, `kb-refresh-frontdoor`, `kb-refresh-summaries`) are the only writers of canon, invoked by name and only when *deliberately* run — not as a side effect of a question. Don't trigger them from the ask path.
+- **You don't run upkeep.** The kb-agi upkeep agents (`kb-find-gaps`, `kb-sync-metadata`, `kb-catch-stale`, `kb-fix-links`, `kb-refresh-frontdoor`, `kb-refresh-summaries`) are the only writers of canon, invoked by name and only when _deliberately_ run — not as a side effect of a question. Don't trigger them from the ask path.
 - **You don't hand-edit `meta/_kg/`** — it's a derived graph, regenerated from the notes.
 - **You don't mutate notes on the ask path.** Read-only means read-only.
 

package/data/harnesses/kb-agi/agents/kb-agi-init.md

@@ -39,7 +39,7 @@ meta/
 
 # Templates
 
-Each block below is one file. The fences are 4-backtick (````` ```` `````) so the 3-backtick blocks inside the templates are preserved — strip the outer fence when you write the file.
+Each block below is one file. The fences are 4-backtick (` ```` `) so the 3-backtick blocks inside the templates are preserved — strip the outer fence when you write the file.
 
 ## `meta/guidance.md`
 
@@ -48,7 +48,7 @@ Each block below is one file. The fences are 4-backtick (````` ```` `````) so th
 
 This file is the single contract the router (`CLAUDE.md`) and the upkeep agents both read. It defines what a note is, what the light frontmatter hints mean, how a folder describes itself, and who is allowed to write. When any of those agents needs a rule, the rule lives here.
 
-Everything in this file is a *hint or a convention*, not a schema enforced by code. Notes that omit a hint still work; the system degrades gracefully.
+Everything in this file is a _hint or a convention_, not a schema enforced by code. Notes that omit a hint still work; the system degrades gracefully.
 
 ---
 
@@ -56,7 +56,7 @@ Everything in this file is a *hint or a convention*, not a schema enforced by co
 
 The vault is one flat Obsidian vault. Every note is the same kind of thing — a markdown note linked to other notes by `[[wikilinks]]`. There is **no per-document type label** and no altitude. Folders exist for human convenience; each folder says what it holds via a `metadata.md`.
 
-- **One idea per note.** Push deeper material into a *linked* note rather than bloating one note. The links carry the depth.
+- **One idea per note.** Push deeper material into a _linked_ note rather than bloating one note. The links carry the depth.
 - **Links are the structure.** The note-link graph is the one graph. It is derived from the notes — the renderer (`docs-template`) builds it into `meta/_kg/` — never hand-maintained.
 - **Notes are the only canon.** Everything under `meta/` is control plane, not knowledge. The graph and any index are regenerable derivatives of the notes.
 
@@ -68,10 +68,10 @@ A note carries light frontmatter. All fields are optional; treat a missing field
 
 ```yaml
 ---
-title: Human-readable title          # defaults to the H1 / filename
-maturity: synthesized                # see ladder below — default: captured
-canonical: true                      # is this THE note on its topic? default: true
-visibility: public                   # public | hidden — default: public
+title: Human-readable title # defaults to the H1 / filename
+maturity: synthesized # see ladder below — default: captured
+canonical: true # is this THE note on its topic? default: true
+visibility: public # public | hidden — default: public
 ---
 ```
 
@@ -80,7 +80,7 @@ visibility: public                   # public | hidden — default: public
 How finished the thinking is. Shapes how the ask path frames an answer, never whether a note is shown.
 
 | value | meaning |
-|---|---|
+| --- | --- |
 | `raw` | dumped in, unprocessed — a capture, a transcript, a paste |
 | `captured` | cleaned up, readable, but not yet reconciled with neighbours |
 | `synthesized` | reconciled into the vault's point of view, linked to its neighbours |
@@ -129,14 +129,14 @@ This is doctrine P3, restated as the contract:
 
 ## genre — the reader, not the document
 
-`genre` is the **user-type** of whoever is asking (Sales, PM, Contributor), established by the opening interview in `CLAUDE.md`. It is a label on the *reader*, never on a note. Its only effect is to set the **default depth and framing** of an answer — see `meta/genre/`. It never changes which notes exist or which are reachable.
+`genre` is the **user-type** of whoever is asking (Sales, PM, Contributor), established by the opening interview in `CLAUDE.md`. It is a label on the _reader_, never on a note. Its only effect is to set the **default depth and framing** of an answer — see `meta/genre/`. It never changes which notes exist or which are reachable.
 
 ---
 
 ## The rest of the control plane
 
 | path | what it is |
-|---|---|
+| --- | --- |
 | `meta/genre/` | user-type templates — default depth + entry points per reader |
 | `meta/intent-index.md` | "Read by need" — intent-keyed entry points into the vault |
 | `meta/sessions/` | query logs — every ask, and whether it could be answered |
@@ -147,7 +147,7 @@ Upkeep is run by the kb-agi agents (invoked by name); there is no `meta/goals/`
 
 ## `meta/genre/sales.md`
 
-````markdown
+```markdown
 # genre — Sales
 
 The reader is positioning NuStack to someone else: a prospect, a partner, a teammate who needs the pitch. They want the claim and the proof behind it, not the implementation.
@@ -157,15 +157,16 @@ The reader is positioning NuStack to someone else: a prospect, a partner, a team
 **Framing.** Outcomes and differentiators over mechanism. Speak in capabilities and claims. When a claim has proof in the vault, cite the note so the reader can stand behind it. Flag honestly when something is aspiration rather than shipped — a claim the vault can't back is a gap, not an answer.
 
 **Start from.**
+
 - `meta/intent-index.md` → the "understand the product / what can it do" lanes
 - positioning, claims, and capability notes (lead with `canonical`, `published` ones)
 
 **Adjust.** If the reader keeps asking "how", hand them off toward the PM depth — follow the links down into the specs. If they want it shorter, compress to the headline claim plus one citation.
-````
+```
 
 ## `meta/genre/pm.md`
 
-````markdown
+```markdown
 # genre — PM
 
 The reader is shaping or building the product: a PM, designer, or engineer who needs scope, tradeoffs, and the state of a decision. They want the mechanism and the reasoning, not just the claim.
@@ -175,34 +176,36 @@ The reader is shaping or building the product: a PM, designer, or engineer who n
 **Framing.** Scope, contracts, and decisions. Distinguish what's shipped, what's specced, and what's still open. Surface the tension behind a choice, not just the choice. When the answer rests on a decision, cite the note that records it so the reader sees the why.
 
 **Start from.**
+
 - `meta/intent-index.md` → the "build / extend / model / runtime concern" lanes
 - spec, decision, and build-plan notes; the architecture notes that set the target
 
 **Adjust.** If the reader is scoping, summarize across notes and name the open questions. If they're implementing, go deep into the one note and its neighbours. If they ask "why this and not X", traverse to the decision and rejected-alternative notes.
-````
+```
 
 ## `meta/genre/contributor.md`
 
-````markdown
+```markdown
 # genre — Contributor
 
-The reader is here to *add* knowledge, not consume it. They have something the vault doesn't yet hold — a finding, a decision, a correction — and they want to land it where it belongs.
+The reader is here to _add_ knowledge, not consume it. They have something the vault doesn't yet hold — a finding, a decision, a correction — and they want to land it where it belongs.
 
 **Default depth.** Orientation over synthesis. Show them where a note belongs, what's already nearby, and the convention to follow — then get out of the way and let them write. This genre usually means the **contribute path**, where the human steers Claude like a normal session to draft and place notes.
 
 **Framing.** Placement and convention. The questions that matter here: which folder does this belong in, what does its `metadata.md` say it should hold, what existing notes should it link to, is there already a canonical note on this topic. Links form naturally as the note is written.
 
 **Start from.**
+
 - the `kb-find-gaps` agent + `meta/sessions/` gap-logs — what the hub is missing / wants next
 - `meta/guidance.md` — the note model, frontmatter hints, and folder `metadata.md` shape
 - the target folder's `metadata.md` — what belongs there and what's missing
 
-**Adjust.** This path is deliberately thin and grows with use. No sub-agents — it's the human and Claude in a normal session. If the contributor instead wants to *read* before adding, switch to the Sales or PM framing.
-````
+**Adjust.** This path is deliberately thin and grows with use. No sub-agents — it's the human and Claude in a normal session. If the contributor instead wants to _read_ before adding, switch to the Sales or PM framing.
+```
 
 ## `meta/intent-index.md`
 
-````markdown
+```markdown
 # intent-index — Read by need
 
 The front door to the vault, keyed on **what you're trying to do**, not who you are (doctrine P4). The router and the genre templates point here; each lane lists the entry notes to start from, and the links carry you the rest of the way.
@@ -212,43 +215,49 @@ This is a living index. It is hand-maintained today and kept fresh by the `kb-re
 ---
 
 ## "I want to understand the product"
+
 _What NuStack is, what it can do, the claims and their proof._
 
 - _populated on migration_
 
 ## "I want to start building"
+
 _Where to begin, how the pieces fit, the build sequence._
 
 - _populated on migration_
 
 ## "I want to extend a capability"
+
 _How to add to the catalog — a node, a connector, an integration._
 
 - _populated on migration_
 
 ## "I want to understand a runtime concern"
+
 _Execution, streaming, observability — how it behaves when it runs._
 
 - _populated on migration_
 
 ## "I want to model data"
+
 _The schema, the entities, the contracts they speak._
 
 - _populated on migration_
 
 ## "I want to add knowledge"
+
 _You have something the vault doesn't hold yet._
 
 - run `kb-find-gaps` (or read `meta/sessions/` gap-logs) — what the hub is missing
 - `meta/guidance.md` — the note model and where things belong
-````
+```
 
 ## `meta/sessions/README.md`
 
 ````markdown
 # sessions — query logs
 
-Every ask the router handles is logged here. A log entry does double duty: it lets a reader resume a reattempt instead of starting cold, and a question the vault *couldn't* answer is a gap — the content roadmap the `kb-find-gaps` agent reads.
+Every ask the router handles is logged here. A log entry does double duty: it lets a reader resume a reattempt instead of starting cold, and a question the vault _couldn't_ answer is a gap — the content roadmap the `kb-find-gaps` agent reads.
 
 This is the one thing the read-only ask path writes (doctrine P3). It never touches a note.
 
@@ -260,7 +269,7 @@ One file per session, named `YYYY-MM-DD-short-slug.md`:
 ---
 date: 2026-05-24
 genre: pm
-answered: partial        # yes | partial | no
+answered: partial # yes | partial | no
 ---
 
 ## Q: <the question, in the asker's words>

package/data/harnesses/kb-agi/agents/kb-catch-stale.md

@@ -12,7 +12,7 @@ You are the **kb-catch-stale** goal-agent for the NuStack knowledge hub. One job
 ## Procedure
 
 1. Group notes by topic (shared `[[wikilinks]]`, near-identical titles). Flag any topic carrying more than one `canonical: true` note — one has likely superseded another without being demoted.
-2. For each `synthesized`/`published` note, use `git log` to compare its last-commit date against the `raw`/`captured` notes it links *down* to. Flag summaries older than their sources.
+2. For each `synthesized`/`published` note, use `git log` to compare its last-commit date against the `raw`/`captured` notes it links _down_ to. Flag summaries older than their sources.
 3. Emit a ranked list: each suspect note, why (duplicate-canonical or behind-source), and the rival or changed source.
 
 ## Write rules (doctrine P3)

package/data/harnesses/kb-agi/agents/kb-find-gaps.md

@@ -13,7 +13,7 @@ Before anything else, read `meta/guidance.md` — the note model, the frontmatte
 
 ## Procedure
 
-1. **Read every content folder's `metadata.md`** and list what each says it *should contain*.
+1. **Read every content folder's `metadata.md`** and list what each says it _should contain_.
 2. **Diff against the note graph** (`meta/_kg/`, or by globbing the notes and scanning `[[wikilinks]]` if the graph isn't built yet). For each "should contain" item, find whether a `canonical` note covers it. Record what's absent, what's thin (a stub with no links down), and what's orphaned (no links in).
 3. **Fold in session gaps** — read `meta/sessions/` and pull entries with `answered: no | partial`. Each `Gap.` line is a hole a real reader hit. Rank these highest.
 4. **Emit a ranked gap list.** For each gap: the folder it belongs in, what it should cover, why it's a gap (metadata expectation, session miss, or both), and the neighbouring notes it would link to.

package/data/harnesses/kb-agi/agents/kb-fix-links.md

@@ -18,5 +18,5 @@ You are the **kb-fix-links** goal-agent for the NuStack knowledge hub. One job:
 ## Write rules (doctrine P3)
 
 - **Default: write nothing.** Output the two lists.
-- **On request only:** fix a dead link when the intended target is *unambiguous* (an exact rename), and add a link from a sensible neighbour to an orphan. Leave ambiguous cases in the report for a human.
+- **On request only:** fix a dead link when the intended target is _unambiguous_ (an exact rename), and add a link from a sensible neighbour to an orphan. Leave ambiguous cases in the report for a human.
 - Every write is a git commit. Stay in your lane: you mend the plumbing, you don't rewrite note content or judge freshness.

package/data/harnesses/kb-agi/agents/kb-refresh-summaries.md

@@ -11,12 +11,12 @@ You are the **kb-refresh-summaries** goal-agent for the NuStack knowledge hub. O
 
 ## Procedure
 
-1. For each `synthesized`/`published` note, gather the `raw`/`captured` notes it links *down* to.
+1. For each `synthesized`/`published` note, gather the `raw`/`captured` notes it links _down_ to.
 2. Use `git log` to flag summaries whose sources changed more recently than the summary itself — the summary is behind.
 3. Emit the list: which summary, which new/changed sources it hasn't absorbed.
 
 ## Write rules (doctrine P3)
 
 - **Default: write nothing.** Output the behind-summaries list.
-- **On request only:** draft the refresh *into the summary note* — fold the new source material in, one idea per note, push overflow into a new linked note rather than bloating. Never invent a summary that doesn't exist (that's the `kb-find-gaps` agent).
+- **On request only:** draft the refresh _into the summary note_ — fold the new source material in, one idea per note, push overflow into a new linked note rather than bloating. Never invent a summary that doesn't exist (that's the `kb-find-gaps` agent).
 - Every write is a git commit. Stay in your lane: you keep existing summaries current, nothing else.

package/data/harnesses/kb-agi/agents/kb-sync-metadata.md

@@ -9,14 +9,14 @@ You are the **kb-sync-metadata** goal-agent for the NuStack knowledge hub. One j
 
 **Read first:** `meta/guidance.md` (the note model + the fixed `metadata.md` shape) — the contract that governs you. The procedure below is this agent's full, self-contained definition.
 
-This is the upkeep that `kb-find-gaps` depends on: it reads `metadata.md` to know what a folder *should contain*. You keep that description truthful. You never invent missing content — that's the `kb-find-gaps` agent.
+This is the upkeep that `kb-find-gaps` depends on: it reads `metadata.md` to know what a folder _should contain_. You keep that description truthful. You never invent missing content — that's the `kb-find-gaps` agent.
 
 ## Procedure
 
 1. For each content folder, read its `metadata.md` and the notes actually in the folder.
 2. Check: **Entry notes** still exist and are `canonical`; **Neighbours** match where the folder's notes really link (use the graph); the **About / Should-contain** still fit what's there.
 3. Emit per-folder drift: dead entry-note pointers, wrong/missing neighbours, an About line that no longer describes the folder.
-4. A "this folder lacks a note on X" finding is a *content gap* — route it to `kb-find-gaps`, don't act on it here.
+4. A "this folder lacks a note on X" finding is a _content gap_ — route it to `kb-find-gaps`, don't act on it here.
 
 ## Write rules (doctrine P3)
 

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

@@ -8,5 +8,5 @@
     ".prettierignore",
     ".vscode/settings.json"
   ],
-  "digest": "25e1cb993a7f"
+  "digest": "f0180d39f191"
 }

package/package.json

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