@nurix/etna 0.19.60 → 0.19.62

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "2d248a0cd94a",
+    "fingerprint": "51ceda35d5cc",
     "harnesses": {
         "apollo": {
             "plugin": "apollo",

package/data/harnesses/apollo/CLAUDE.md

@@ -139,7 +139,8 @@ Defaults — ❌ prohibitions hold unless the user explicitly asks otherwise;
 - ❌ **Branches & Worktrees [override]** – Never self-create git branches or worktrees; commit straight to the checked-out branch. This replaces any built-in "branch first on the default branch" default. Exception: when the user asks for a pull request, create the branch the PR requires before committing its changes.
 - ❌ **Protected Files** – Once per session, if `docs/operations/protected-files.md` exists, read it and never modify any path it lists; never modify `AGENTS.md` (harness-regenerated) or `protected-files.md` itself.
 - ✅ **Browser Automation** – If the runtime provides browser automation, use it freely; no need to ask first. If it doesn't — or the executing agent can't hold the browser connection (see Runtime Notes) — return a browser-verification checklist (URLs, actions, expected outcomes) for the orchestrating session or the user to run.
-- ✅ **Bookkeeping** — hooks silently append doc-debt rows to `docs/operations/bookkeeping.md`; the commit hook blocks while unresolved rows remain — dispatch the `bookkeeper` agent to drain the queue.
+- ✅ **Bookkeeping** — hooks silently append doc-debt rows to `docs/operations/bookkeeping.md`; the commit hook blocks while unresolved rows remain — dispatch the `bookkeeper` agent to drain the queue. The queue is a queue, never an archive: a drained row is **deleted**, so a fully drained file holds no rows at all.
+- ✅ **Cleanup removes the cause, not the record of it.** When the user asks for something to be deleted or cleaned up, the ask is for the underlying condition to be gone. Deleting the record while the condition survives is worse than doing nothing — it destroys the only evidence the debt exists. The order is fixed: **read what the record is masking** (a `waived:` row, an `UNBUILT:` marker, a `status:` flag, a lint suppression — each asserts something is fine; check whether that is still true), **fix the condition**, **then delete the record**. Reversing it backfires concretely: a deleted waiver's finding is re-appended by the detector as an `auto:` row, which *fails* the commit wall the `waived:` row passed.
 - ✅ **Delegation** — when to fan out, tiers, and trust are § Delegation.
 - ⚠️ **Plans** – Plans are created directly in `docs/history/plans/` (see Workflows). Once `Status: Complete` or `Status: Abandoned`, the file is frozen — never edited. Abandoning a plan whose code was committed first converts its undischarged Test Obligations into backlog items (the `testing` rule). If scope changes after completion, write a new dated plan that links back to the old one.
 - ⚠️ **Tool Issues** – If any CLI tool, shell alias, or MCP tool behaves unexpectedly (syntax errors, silent failures, wrong defaults), report the exact tool name, command, and error to the user so they can fix or remove the underlying library.

package/data/harnesses/apollo/agents/bookkeeper.md

@@ -24,4 +24,5 @@ Ground every edit in this ladder, in order. Never invent content; a fact you can
 - **Every touched doc goes through the `documentation` skill's rules** — present tense, two-natures, no history narration in truth documents.
 - **Resolution = deletion.** A finished row is removed from the queue, not annotated. Only `waived:` conversions (a reason plus `expires=YYYY-MM-DD`) and `needs-session:` rows survive your pass.
 - **Never waive on your own judgment** — waiving is the main session's (or the user's) call; your outcomes are fixed, landed, or `needs-session:`.
+- **A waiver's reason expires before its date.** Most waivers defer to something — "plan X reconciles this at completion", "the concurrent session resolves its own doc impact". When you pass a `waived:` row, check whether that reason still holds: a waiver naming a `Status: Complete` plan is discharged debt wearing a live badge, and its `expires=` date will not fire for weeks. Report those rows as `needs-session:` rather than waiving them onward — the finding underneath is live, and the unexpired date is precisely why nothing else will catch it.
 - **Report by row**: one line each — the row, the outcome (fixed / landed in {doc} / needs-session), and the files touched. The main session relays this; keep it terse.

package/data/harnesses/apollo/agents/maintenance.md

@@ -113,6 +113,8 @@ For unowned code paths:
 
 **Declined realignment.** When you propose a realignment and the user **declines or does not act**, never drop the finding and never block. Append it to `docs/history/backlog.md` as `- **[P0–P3]** <finding> — discovered by maintenance`, priority = the finding's own severity **on the same P0–P3 scale as code items** — never a segregated "compliance" section, never auto-relegated to the lowest tier. Record once: dedupe against existing entries; if already present, leave it.
 
+> **Never regenerate `.claude/state/drift-report.md` by running the awareness hook when the bookkeeping queue is what you are measuring.** `driftBanner()` calls `resolveRows()`, which *mutates* the queue as a side effect of reporting on it — so the act of refreshing the report changes the thing the report describes. Read the existing report, or recompute the facts directly from `deadGlobs()` / `scanFeatureDocs()`.
+
 ### Step 6: Report & update tracking
 
 1. Update `docs/structure.md` Health Log with today's date and summary — **append to the end**, never date-sorted into the middle. Rows are positional: one may say "the row above is…", and an inserted row silently breaks that reference. A Health Log entry is a **generated row, not a narrative essay**: one line — date · counts (stale docs fixed, dead globs, unowned paths, backlog items created) · links to anything that needs a human.

package/data/harnesses/apollo/harness.json

@@ -15,5 +15,5 @@
     "docs/memory/main.md",
     ".mcp.json"
   ],
-  "digest": "91d17fd2366f"
+  "digest": "d01be54a3e94"
 }

package/data/harnesses/apollo/hooks/lib/ownership.mjs

@@ -78,9 +78,18 @@ export function field(block, key) {
     const raw = m[1].trim();
     if (raw === "") {
       // A bare key may continue as an indented inline array on the next line, or a `- item` block.
+      // The array may span several lines, so join through the closing bracket before parsing —
+      // reading only the first line yields a bare "[", which parses to [] and makes the whole doc
+      // look like it owns nothing. `scanFeatureDocs` skips such docs, so the failure is invisible:
+      // the doc drops out of the ownership index and out of every dead-glob count.
       const next = (lines[i + 1] || "").trim();
       if (next.startsWith("[")) {
-        return parseInlineArray(next);
+        let joined = "";
+        for (let j = i + 1; j < lines.length; j++) {
+          joined += (joined ? " " : "") + lines[j].trim();
+          if (lines[j].includes("]")) break;
+        }
+        return parseInlineArray(joined);
       }
       const items = [];
       for (let j = i + 1; j < lines.length; j++) {

package/data/harnesses/code/CLAUDE.md

@@ -137,7 +137,8 @@ Defaults — ❌ prohibitions hold unless the user explicitly asks otherwise;
 - ❌ **Branches & Worktrees [override]** – Never self-create git branches or worktrees; commit straight to the checked-out branch. This replaces any built-in "branch first on the default branch" default. Exception: when the user asks for a pull request, create the branch the PR requires before committing its changes.
 - ❌ **Protected Files** – Once per session, if `docs/operations/protected-files.md` exists, read it and never modify any path it lists; never modify `AGENTS.md` (harness-regenerated) or `protected-files.md` itself.
 - ✅ **Browser Automation** – If the runtime provides browser automation, use it freely; no need to ask first. If it doesn't — or the executing agent can't hold the browser connection (see Runtime Notes) — return a browser-verification checklist (URLs, actions, expected outcomes) for the orchestrating session or the user to run.
-- ✅ **Bookkeeping** — hooks silently append doc-debt rows to `docs/operations/bookkeeping.md`; the commit hook blocks while unresolved rows remain — dispatch the `bookkeeper` agent to drain the queue.
+- ✅ **Bookkeeping** — hooks silently append doc-debt rows to `docs/operations/bookkeeping.md`; the commit hook blocks while unresolved rows remain — dispatch the `bookkeeper` agent to drain the queue. The queue is a queue, never an archive: a drained row is **deleted**, so a fully drained file holds no rows at all.
+- ✅ **Cleanup removes the cause, not the record of it.** When the user asks for something to be deleted or cleaned up, the ask is for the underlying condition to be gone. Deleting the record while the condition survives is worse than doing nothing — it destroys the only evidence the debt exists. The order is fixed: **read what the record is masking** (a `waived:` row, an `UNBUILT:` marker, a `status:` flag, a lint suppression — each asserts something is fine; check whether that is still true), **fix the condition**, **then delete the record**. Reversing it backfires concretely: a deleted waiver's finding is re-appended by the detector as an `auto:` row, which *fails* the commit wall the `waived:` row passed.
 - ✅ **Delegation** — when to fan out, tiers, and trust are § Delegation.
 - ⚠️ **Plans** – Plans are created directly in `docs/history/plans/` (see Workflows). Once `Status: Complete` or `Status: Abandoned`, the file is frozen — never edited. Abandoning a plan whose code was committed first converts its undischarged Test Obligations into backlog items (the `testing` rule). If scope changes after completion, write a new dated plan that links back to the old one.
 - ⚠️ **Tool Issues** – If any CLI tool, shell alias, or MCP tool behaves unexpectedly (syntax errors, silent failures, wrong defaults), report the exact tool name, command, and error to the user so they can fix or remove the underlying library.

package/data/harnesses/code/agents/bookkeeper.md

@@ -24,4 +24,5 @@ Ground every edit in this ladder, in order. Never invent content; a fact you can
 - **Every touched doc goes through the `documentation` skill's rules** — present tense, two-natures, no history narration in truth documents.
 - **Resolution = deletion.** A finished row is removed from the queue, not annotated. Only `waived:` conversions (a reason plus `expires=YYYY-MM-DD`) and `needs-session:` rows survive your pass.
 - **Never waive on your own judgment** — waiving is the main session's (or the user's) call; your outcomes are fixed, landed, or `needs-session:`.
+- **A waiver's reason expires before its date.** Most waivers defer to something — "plan X reconciles this at completion", "the concurrent session resolves its own doc impact". When you pass a `waived:` row, check whether that reason still holds: a waiver naming a `Status: Complete` plan is discharged debt wearing a live badge, and its `expires=` date will not fire for weeks. Report those rows as `needs-session:` rather than waiving them onward — the finding underneath is live, and the unexpired date is precisely why nothing else will catch it.
 - **Report by row**: one line each — the row, the outcome (fixed / landed in {doc} / needs-session), and the files touched. The main session relays this; keep it terse.

package/data/harnesses/code/agents/maintenance.md

@@ -113,6 +113,8 @@ For unowned code paths:
 
 **Declined realignment.** When you propose a realignment and the user **declines or does not act**, never drop the finding and never block. Append it to `docs/history/backlog.md` as `- **[P0–P3]** <finding> — discovered by maintenance`, priority = the finding's own severity **on the same P0–P3 scale as code items** — never a segregated "compliance" section, never auto-relegated to the lowest tier. Record once: dedupe against existing entries; if already present, leave it.
 
+> **Never regenerate `.claude/state/drift-report.md` by running the awareness hook when the bookkeeping queue is what you are measuring.** `driftBanner()` calls `resolveRows()`, which *mutates* the queue as a side effect of reporting on it — so the act of refreshing the report changes the thing the report describes. Read the existing report, or recompute the facts directly from `deadGlobs()` / `scanFeatureDocs()`.
+
 ### Step 6: Report & update tracking
 
 1. Update `docs/structure.md` Health Log with today's date and summary — **append to the end**, never date-sorted into the middle. Rows are positional: one may say "the row above is…", and an inserted row silently breaks that reference. A Health Log entry is a **generated row, not a narrative essay**: one line — date · counts (stale docs fixed, dead globs, unowned paths, backlog items created) · links to anything that needs a human.

package/data/harnesses/code/harness.json

@@ -10,5 +10,5 @@
   "seeds": [
     ".mcp.json"
   ],
-  "digest": "77f419c9b4da"
+  "digest": "00ab519e0423"
 }

package/data/harnesses/code/hooks/lib/ownership.mjs

@@ -78,9 +78,18 @@ export function field(block, key) {
     const raw = m[1].trim();
     if (raw === "") {
       // A bare key may continue as an indented inline array on the next line, or a `- item` block.
+      // The array may span several lines, so join through the closing bracket before parsing —
+      // reading only the first line yields a bare "[", which parses to [] and makes the whole doc
+      // look like it owns nothing. `scanFeatureDocs` skips such docs, so the failure is invisible:
+      // the doc drops out of the ownership index and out of every dead-glob count.
       const next = (lines[i + 1] || "").trim();
       if (next.startsWith("[")) {
-        return parseInlineArray(next);
+        let joined = "";
+        for (let j = i + 1; j < lines.length; j++) {
+          joined += (joined ? " " : "") + lines[j].trim();
+          if (lines[j].includes("]")) break;
+        }
+        return parseInlineArray(joined);
       }
       const items = [];
       for (let j = i + 1; j < lines.length; j++) {

package/data/harnesses/delivery/agents/maintenance.md

@@ -113,6 +113,8 @@ For unowned code paths:
 
 **Declined realignment.** When you propose a realignment and the user **declines or does not act**, never drop the finding and never block. Append it to `docs/history/backlog.md` as `- **[P0–P3]** <finding> — discovered by maintenance`, priority = the finding's own severity **on the same P0–P3 scale as code items** — never a segregated "compliance" section, never auto-relegated to the lowest tier. Record once: dedupe against existing entries; if already present, leave it.
 
+> **Never regenerate `.claude/state/drift-report.md` by running the awareness hook when the bookkeeping queue is what you are measuring.** `driftBanner()` calls `resolveRows()`, which *mutates* the queue as a side effect of reporting on it — so the act of refreshing the report changes the thing the report describes. Read the existing report, or recompute the facts directly from `deadGlobs()` / `scanFeatureDocs()`.
+
 ### Step 6: Report & update tracking
 
 1. Update `docs/structure.md` Health Log with today's date and summary — **append to the end**, never date-sorted into the middle. Rows are positional: one may say "the row above is…", and an inserted row silently breaks that reference. A Health Log entry is a **generated row, not a narrative essay**: one line — date · counts (stale docs fixed, dead globs, unowned paths, backlog items created) · links to anything that needs a human.

package/data/harnesses/delivery/harness.json

@@ -8,5 +8,5 @@
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "9200d5f0c074"
+  "digest": "e35c6d22e9ba"
 }

package/data/harnesses/etna/agents/maintenance.md

@@ -113,6 +113,8 @@ For unowned code paths:
 
 **Declined realignment.** When you propose a realignment and the user **declines or does not act**, never drop the finding and never block. Append it to `docs/history/backlog.md` as `- **[P0–P3]** <finding> — discovered by maintenance`, priority = the finding's own severity **on the same P0–P3 scale as code items** — never a segregated "compliance" section, never auto-relegated to the lowest tier. Record once: dedupe against existing entries; if already present, leave it.
 
+> **Never regenerate `.claude/state/drift-report.md` by running the awareness hook when the bookkeeping queue is what you are measuring.** `driftBanner()` calls `resolveRows()`, which *mutates* the queue as a side effect of reporting on it — so the act of refreshing the report changes the thing the report describes. Read the existing report, or recompute the facts directly from `deadGlobs()` / `scanFeatureDocs()`.
+
 ### Step 6: Report & update tracking
 
 1. Update `docs/structure.md` Health Log with today's date and summary — **append to the end**, never date-sorted into the middle. Rows are positional: one may say "the row above is…", and an inserted row silently breaks that reference. A Health Log entry is a **generated row, not a narrative essay**: one line — date · counts (stale docs fixed, dead globs, unowned paths, backlog items created) · links to anything that needs a human.

package/data/harnesses/etna/harness.json

@@ -8,5 +8,5 @@
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "dbb7424aa7c7"
+  "digest": "b78faf3cf571"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.19.60",
+    "version": "0.19.62",
     "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": "2d248a0cd94a"
+    "etnaFingerprint": "51ceda35d5cc"
 }