@nurix/etna 0.15.1 → 0.15.2

package/data/harnesses/code/CLAUDE.md

@@ -1,7 +1,7 @@
 ---
 name: code
 description: Canonical Nurix code-project harness (spec v12) — three peer authoring modes (Brainstorming / Spec / Plan), modules as bounded contexts, typed application boundaries via the unified `boundary` skill, a self-migrating harness-manager, ownership rules. The reference CLAUDE.md every Nurix codebase starts with.
-version: 0.15.1
+version: 0.15.2
 keywords:
   - harness
   - code
@@ -54,7 +54,7 @@ Three peer modes plus a Completion step — enter wherever the user's thinking a
 | **Spec** | new feature work | `spec-mode` agent + `documentation` skill | Plan |
 | **Plan** | a spec is approved | `documentation` skill → `docs/history/plans/YYYY-MM-DD-{slug}.md` | Completion |
 
-On **Completion**: freeze the plan (`Status: Complete`) and flip the feature spec to `Status: Active`, extending it with how-it-works sections; then consult `distiller docs` for the just-completed feature's doc — it drafts any pending fact-card deltas for approval (presented, never auto-written). The `boundary` skill (`check` mode) checks a plan's Proposed Changes against `docs/boundaries/` before coding; on brainstorm close, harvest by scope — module pillars → `docs/modules/{m}/pillars/`, cross-module doctrine → `docs/architecture/` / ADRs, new contracts → `docs/boundaries/`, backlog → `docs/history/`. Open questions block close.
+On **Completion**: freeze the plan (`Status: Complete`) and flip the feature spec to `Status: Active`, extending it with how-it-works sections; then distil the plan's trail — if the ledger holds entries past the distiller's high-water mark, run `distiller facts` (ledger→fact-cards), then `distiller docs` for the just-completed feature's doc drafts any pending deltas for approval (presented, never auto-written). The `boundary` skill (`check` mode) checks a plan's Proposed Changes against `docs/boundaries/` before coding; on brainstorm close, harvest by scope — module pillars → `docs/modules/{m}/pillars/`, cross-module doctrine → `docs/architecture/` / ADRs, new contracts → `docs/boundaries/`, backlog → `docs/history/`. Open questions block close.
 
 ---
 

package/data/harnesses/code/harness.json

@@ -1,6 +1,6 @@
 {
   "name": "code",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "epoch": 12,
-  "digest": "1bdfd15cf1e5"
+  "digest": "911060693b53"
 }

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

@@ -43,9 +43,12 @@ procedure that sequences it lives in its own section below.
 
 Runs **in the main session** — no standing sub-agents, no daemon, no cron, no
 watch. The harness **proposes**, the user **disposes**: this skill runs only when
-the user asks, or when the user accepts the `maintenance` agent's threshold
-proposal (≥20 undigested ledger entries). It never schedules itself, never runs
-on a hook, never gates anything.
+the user asks, when the **Completion flow** invokes it (the kit `CLAUDE.md`
+Completion step distils the just-finished plan's trail — `facts` if the ledger
+advanced past the high-water mark, then `docs` which still drafts for approval),
+or when the user accepts the `maintenance` agent's threshold proposal (≥20
+undigested ledger entries). It never schedules itself, never runs on a hook,
+never gates anything.
 
 ---
 
@@ -192,8 +195,9 @@ It NEVER writes a doc on its own — it **drafts and presents**; the human dispo
 - **Findings are questions, not verdicts.** When a candidate appears to
   contradict an existing card, phrase it as a question (is X now superseded by
   Y?) — never assert staleness or falsity.
-- **Never auto-runs.** Invoked by the user or by accepting the maintenance
-  proposal. No cron, no daemon, no hook self-trigger.
+- **Never auto-runs.** Invoked by the user, by the Completion flow (kit
+  `CLAUDE.md`), or by accepting the maintenance proposal. No cron, no daemon, no
+  hook self-trigger — a workflow step the agent runs is not a self-trigger.
 - **qmd is strictly optional.** Guard every qmd call on `command -v qmd`; absent
   ⇒ silent skip. Reconciliation additionally needs the `{repo}-facts` collection
   to hold **cards** — not merely to be registered. "Unbuilt" here means **no

package/package.json

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