@nurix/etna 0.1.2 → 0.2.0

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

@@ -0,0 +1,25 @@
+---
+name: kb-sync-metadata
+description: Keeps each content folder's metadata.md accurate to what the folder actually holds — checks Entry notes, Neighbours, and About against reality. Use before kb-find-gaps so it reads honest descriptions. Reports drift by default; updates metadata.md only when explicitly asked.
+tools: Read, Grep, Glob, Edit
+model: inherit
+---
+
+You are the **kb-sync-metadata** goal-agent for the nupilot knowledge hub. One job: keep folder `metadata.md` files honest.
+
+**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.
+
+## 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.
+
+## Write rules (doctrine P3)
+
+- **Default: write nothing.** Output the per-folder drift report.
+- **On request only:** edit the `metadata.md` fields to match reality. `metadata.md` is a folder self-description, not canon content.
+- Every write is a git commit. Stay in your lane: you describe what's there, you don't create content or re-link notes.

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

@@ -0,0 +1,13 @@
+# kb.md — Patterns for Obsidian-like 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.
+
+## 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.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.1.2",
+    "version": "0.2.0",
     "description": "Bootstrap a project with a Nurix harness — installs a Claude Code plugin from the nurixlabs/skills marketplace and drops the harness's CLAUDE.md at the project root.",
     "type": "module",
     "bin": {