@nurix/etna 0.19.88 → 0.19.90

package/data/harness-index.json

@@ -1,5 +1,5 @@
 {
-    "fingerprint": "417d61b8de2d",
+    "fingerprint": "8d6f9b80d64d",
     "harnesses": {
         "code": {
             "plugin": "code",

package/data/harnesses/code/CLAUDE.md

@@ -139,7 +139,7 @@ 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. The queue is a queue, never an archive: a drained row is **deleted**, so a fully drained file holds no rows at all.
+- ✅ **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. **Every row is a cache of a condition, not a record of an event** — the session-start sweep re-tests each row against the repo and deletes the ones whose condition has died, `waived:` rows included, so the file empties itself as the work lands. What the sweep cannot re-test ages out instead: **a `waived:` row is unresolved once `expires=` passes**, which returns the wall and re-summons the bookkeeper to re-judge the reason. A waiver defers a finding; it never makes one immortal.
 - ✅ **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.

package/data/harnesses/code/harness.json

@@ -1,7 +1,7 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.10.12",
+  "version": "3.10.13",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
@@ -15,5 +15,5 @@
     "docs/memory/main.md",
     ".mcp.json"
   ],
-  "digest": "8b4f074b1311"
+  "digest": "e58c5f75136f"
 }

package/data/harnesses/code/hooks/awareness.mjs

@@ -126,15 +126,117 @@ function openPlanLines(projectDir) {
   return lines;
 }
 
+// --- the re-verification sweep ---------------------------------------------------------------
+//
+// THE QUEUE IS DERIVED, NOT ACCUMULATED. Every finding here is recomputable from the repo, so a row
+// is a cache of a condition rather than a record of an event — and a cache nothing invalidates is
+// an archive. Before any wall reads the queue, each row is re-tested against the repo as it is NOW,
+// and a row whose condition has died is deleted.
+//
+// THIS RUNS OVER `waived:` ROWS TOO, WHICH IS THE POINT. A waiver defers a finding; it does not
+// make the finding immortal. Without this, waiving was strictly WORSE than leaving a row alone —
+// the one existing resolver filtered `kind === "auto"`, so waiving a self-clearing row opted it out
+// of its own return path forever. The condition, not the row's kind, decides.
+//
+// A kind with no verifier here is not swept — it ages out through `expires=` instead. Add a
+// verifier whenever a finding becomes mechanically checkable; silence is the only failure mode
+// this file has, so a verifier that is unsure must return false and leave the row standing.
+const ROW_VERIFIERS = {
+  // "<rel> lacks its file-path header comment" — dead once the header is there (or the file is gone).
+  "header-missing": (projectDir, body) => {
+    const m = /·\s+header-missing\s+·\s+(\S+)\s+lacks/.exec(body);
+    if (!m) return false;
+    const rel = m[1];
+    if (!fs.existsSync(path.join(projectDir, rel))) return true;
+    return hasHeaderComment(projectDir, rel);
+  },
+
+  // "owns: glob `<glob>` in <doc> matches no files" — dead once the glob matches something again.
+  "dead-glob": (projectDir, body, ctx) => {
+    const m = /`([^`]+)`/.exec(body);
+    if (!m) return false;
+    const re = globToRegExp(m[1]);
+    return ctx.repoFiles.some((f) => re.test(f));
+  },
+
+  // "<rel> is a frozen record and carries uncommitted modifications" — dead once it is committed.
+  // Immutability begins at commit, so the finding exists only while the edit is still in flight.
+  "frozen-record-edited": (projectDir, body) => {
+    const m = /·\s+frozen-record-edited\s+·\s+(\S+)\s+is a frozen record/.exec(body);
+    if (!m) return false;
+    const rel = m[1];
+    if (!fs.existsSync(path.join(projectDir, rel))) return true;
+    const res = spawnSync("git", ["diff", "--quiet", "HEAD", "--", rel], { cwd: projectDir, timeout: 5000 });
+    // status 0 = no uncommitted modifications. A git failure leaves the row standing.
+    return res.status === 0;
+  },
+
+  // "<src> changed; owning doc <doc> may need an update" — dead once the doc is newer than the
+  // source that implicated it, which is the same freshness test the drift report already applies.
+  "doc-implicated": (projectDir, body) => {
+    const m = /·\s+doc-implicated\s+·\s+(\S+)\s+changed;\s+owning doc\s+(\S+?)\s+may need/.exec(body);
+    if (!m) return false;
+    const [, src, doc] = m;
+    const mtime = (rel) => {
+      try {
+        return fs.statSync(path.join(projectDir, rel)).mtimeMs;
+      } catch (e) {
+        return null;
+      }
+    };
+    const docTime = mtime(doc);
+    const srcTime = mtime(src);
+    if (docTime === null) return false; // the doc is gone — a real finding, not a resolved one
+    if (srcTime === null) return true; // the source is gone; nothing implicates the doc any more
+    return docTime >= srcTime;
+  },
+};
+
+// Delete every row — `auto:` or `waived:` — whose condition no longer holds. Returns the count.
+export function sweepResolvedRows(projectDir, repoFiles) {
+  const ctx = { repoFiles: repoFiles || listRepoFiles(projectDir) };
+  return resolveRows(projectDir, (row) => {
+    if (row.kind === "needs-session") return false; // a human judgment, never swept mechanically
+    for (const [kind, verify] of Object.entries(ROW_VERIFIERS)) {
+      if (!row.body.includes(kind)) continue;
+      try {
+        return verify(projectDir, row.body, ctx);
+      } catch (e) {
+        return false; // never delete a row because a verifier threw
+      }
+    }
+    return false;
+  });
+}
+
 // Compute drift facts once; write the full report, return the one-line banner.
 function driftBanner(projectDir) {
   const repoFiles = listRepoFiles(projectDir);
+  // Re-verify before counting: the walls must act on conditions that are live NOW, not on rows
+  // that happen to still be written down.
+  const swept = sweepResolvedRows(projectDir, repoFiles);
   const dead = deadGlobs(projectDir, repoFiles);
   const queueRows = readQueue(projectDir);
   const counts = countRows(queueRows);
   const waivers = unexpiredWaivers(queueRows, "dead-glob", today());
   const unwaivedDead = dead.filter((d) => !waivers.some((w) => w.body.includes(d.glob)));
 
+  // A waiver becomes a wall the day it expires, so the queue says so a week ahead — the deferral
+  // ending should be a date somebody saw coming, not a commit that suddenly blocks.
+  const soon = new Date(Date.now() + 7 * 864e5).toISOString().slice(0, 10);
+  const expiringSoon = queueRows
+    .filter((r) => r.kind === "waived")
+    .map((r) => {
+      const d = (/expires=(\d{4}-\d{2}-\d{2})/.exec(r.body) || [])[1];
+      if (!d || d < today() || d > soon) return null;
+      // Drop the row's own raised-date prefix and its reason tail — the expiry and the finding are
+      // what a reader is scanning for here.
+      const finding = r.body.replace(/^\d{4}-\d{2}-\d{2}\s+·\s+/, "").split(" · reason:")[0];
+      return `expires ${d} · ${finding.slice(0, 120)}`;
+    })
+    .filter(Boolean)
+    .sort();
+
   // A queued dead-glob row covered by an unexpired waiver is resolved history — drop it,
   // so waiving a finding class actually empties the rows it supersedes.
   resolveRows(projectDir, (row) => {
@@ -174,7 +276,10 @@ function driftBanner(projectDir) {
     `## Docs older than owned code (${staleDocs.length})`,
     ...staleDocs.map((d) => `- ${d}`),
     "",
-    `## Bookkeeping queue (${counts.unresolved} unresolved: ${counts.auto} auto · ${counts.note} note · ${counts.needsSession} needs-session · ${counts.waived} waived)`,
+    `## Bookkeeping queue (${counts.unresolved} unresolved: ${counts.auto} auto · ${counts.note} note · ${counts.needsSession} needs-session · ${counts.expiredWaived} expired-waived; ${counts.waived} waived total, ${swept} swept as resolved this session)`,
+    ...(expiringSoon.length
+      ? ["", `## Waivers expiring within 7 days (${expiringSoon.length})`, ...expiringSoon.map((w) => `- ${w}`)]
+      : []),
   ].join("\n");
   try {
     fs.writeFileSync(path.join(stateDir(projectDir), "drift-report.md"), report + "\n");

package/data/harnesses/code/hooks/check-bookkeeping-clean.mjs

@@ -13,7 +13,12 @@ if (counts.unresolved === 0) {
 }
 console.error(
   `check-bookkeeping-clean: ${counts.unresolved} unresolved row(s) in docs/operations/bookkeeping.md ` +
-    `(${counts.auto} auto, ${counts.note} note, ${counts.needsSession} needs-session). ` +
-    "Drain them (bookkeeper agent), resolve them, or convert to waived: with reason + expires=."
+    `(${counts.auto} auto, ${counts.note} note, ${counts.needsSession} needs-session, ` +
+    `${counts.expiredWaived} expired-waived). ` +
+    "Drain them (bookkeeper agent), resolve them, or convert to waived: with reason + expires=. " +
+    (counts.expiredWaived > 0
+      ? "An expired waiver is a deferral that ran out: re-judge whether its reason still holds — " +
+        "re-waive with a fresh date only if it does, and never by default."
+      : "")
 );
 process.exit(1);

package/data/harnesses/code/hooks/compliance.mjs

@@ -567,8 +567,11 @@ function stopGate(projectDir, payload) {
     return {
       decision: "block",
       reason:
-        `${counts.unresolved} unresolved bookkeeping rows from this session (${counts.auto} auto, ${counts.note} note, ${counts.needsSession} needs-session) in docs/operations/bookkeeping.md. ` +
+        `${counts.unresolved} unresolved bookkeeping rows from this session (${counts.auto} auto, ${counts.note} note, ${counts.needsSession} needs-session, ${counts.expiredWaived} expired-waived) in docs/operations/bookkeeping.md. ` +
         "Dispatch the `bookkeeper` agent to drain them, resolve them now, or convert to `waived:` rows with reason + expiry. " +
+        (counts.expiredWaived > 0
+          ? "An expired waiver is a deferral that ran out — re-judge whether its reason still holds rather than re-waiving by default. "
+          : "") +
         "If implementation of the open plan is complete, also report it and offer the verification gate — never run it unbidden.",
     };
   }

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

@@ -5,7 +5,10 @@
 //   - note: {YYYY-MM-DD} · {area} · {context} → lands-in: {owning doc | backlog | memory} | sid=…
 //   - needs-session: {YYYY-MM-DD} · {what could not be grounded} → main session resolves | refs={ts}
 //   - waived: {YYYY-MM-DD} · {what is deferred} · reason: {why} → expires={YYYY-MM-DD}
-// Unresolved = auto + note + needs-session. waived: rows are resolved history until expires= passes.
+// Unresolved = auto + note + needs-session + EXPIRED waived. A `waived:` row is resolved history
+// only while its expires= date is in the future; past it, the deferral is over and the wall returns.
+// Rows are also re-verified against the repo before the walls read them (awareness.mjs's sweep),
+// so a row whose condition died is deleted rather than waiting for its date.
 
 import fs from "node:fs";
 import path from "node:path";
@@ -14,7 +17,7 @@ export const QUEUE_PATH = ["docs", "operations", "bookkeeping.md"];
 
 export const QUEUE_HEADER = `# Bookkeeping
 
-The shared work queue keeping documentation and code in sync — a queue, never an archive. Rows are appended mechanically (auto:) and by working sessions (note:), drained by the bookkeeper agent, and walled at commit: a commit is possible only when every row is either **resolved, which deletes it**, or converted to \`waived:\`. A drained row leaves no trace here; what it closed is recorded in the doc it corrected, and git history holds the row itself. Row grammar and lifecycle: the \`documentation\` skill's \`templates/bookkeeping.md\`. A \`waived:\` row carries \`expires=\` and is PR-reviewable history.
+The shared work queue keeping documentation and code in sync — a queue, never an archive. Rows are appended mechanically (auto:) and by working sessions (note:), drained by the bookkeeper agent, and walled at commit: a commit is possible only when every row is either **resolved, which deletes it**, or converted to \`waived:\`. A drained row leaves no trace here; what it closed is recorded in the doc it corrected, and git history holds the row itself. Row grammar and lifecycle: the \`documentation\` skill's \`templates/bookkeeping.md\`.\n\n**Every row is a cache of a condition, not a record of an event.** A session-start sweep re-tests each row against the repo and deletes the ones whose condition has died — \`waived:\` rows included, because a waiver defers a finding and never makes one immortal. What the sweep cannot mechanically re-test ages out instead: a \`waived:\` row carries \`expires=\`, is PR-reviewable history until that date, and counts as **unresolved** past it — which returns the wall and re-summons the bookkeeper to re-judge whether the reason still holds.
 `;
 
 export function queueFile(projectDir) {
@@ -113,15 +116,30 @@ export function readQueue(projectDir) {
 }
 
 // Counts by kind; `unresolved` is the number the walls act on.
-export function countRows(rows) {
-  const c = { auto: 0, note: 0, needsSession: 0, waived: 0 };
+//
+// AN EXPIRED WAIVER IS AN UNRESOLVED ROW. A waiver is a time-boxed deferral, so `expires=` is the
+// whole difference between deferring a finding and burying it — and until this counted, the date
+// was decorative: nothing but the dead-glob allowlist ever read it, so an expired waiver passed
+// every wall forever. Counting it here is what makes the deferral end, and what re-summons the
+// bookkeeper, whose own instructions already say to re-check a waiver's reason and demote a dead
+// one to `needs-session:`. The reviewer existed; this is the trigger it never had.
+//
+// A waiver with NO `expires=` is malformed and counts as expired — the grammar requires the date,
+// and treating an absent one as "never expires" would make the omission the cheapest way to write
+// a permanent waiver.
+export function countRows(rows, today = new Date().toISOString().slice(0, 10)) {
+  const c = { auto: 0, note: 0, needsSession: 0, waived: 0, expiredWaived: 0 };
   for (const row of rows) {
     if (row.kind === "auto") c.auto += 1;
     else if (row.kind === "note") c.note += 1;
     else if (row.kind === "needs-session") c.needsSession += 1;
-    else if (row.kind === "waived") c.waived += 1;
+    else if (row.kind === "waived") {
+      c.waived += 1;
+      const expires = (/expires=(\d{4}-\d{2}-\d{2})/.exec(row.body) || [])[1];
+      if (!expires || expires < today) c.expiredWaived += 1;
+    }
   }
-  c.unresolved = c.auto + c.note + c.needsSession;
+  c.unresolved = c.auto + c.note + c.needsSession + c.expiredWaived;
   return c;
 }
 

package/data/harnesses/discover/CLAUDE.md

@@ -86,7 +86,7 @@ Cheap, read-only. Scope the target, grade its access, detect which dimensions it
 
 Dispatch one collector per available dimension; collect exhaustively before context is lost. Every collector writes `research/<target>/dimensions/<dim>/_summary.md` (with the **provenance frontmatter** — method · confidence · completeness · gaps) + `raw/`, obeying `.claude/rules/ingestion.md`.
 
-- **Run independents in parallel** — dispatch `docs`, `packages`, `api`, `website`, `community`, `deployed-client-bundle`, `infra-backend-fingerprint`, `distribution-artifacts` together (`subagent_type='<dimension>'`, one message, multiple Agent calls). Seed each collector with **warm entry points (URLs / repos / hosts), not claimed facts** — any fact **or inference** carried from Discovery (a price, a tier name, a version — **or a derived hypothesis like "localStorage-key X ⇒ backend is Y"**) is tagged `verify:may-be-stale` so the collector **re-derives it instead of anchoring** on a possibly-stale (or possibly-wrong) value. A Discovery _inference_ is never seeded as a plan fact: label it a hypothesis in `00-recon-plan.md` and tag it `verify:` in the seed, so a collector that inherits it reports it hedged rather than echoing it as observed (a real run seeded an `apolloAnonId ⇒ GraphQL backend` guess that two captures then repeated before the session refuted it). **A sibling collector's _summary_ is a claim, not a source** — when seeding one collector with something another collector reported, tag it `verify:` too, unless the main session has actually read the underlying `raw/` artifact. A returned summary is a compressed, unverified assertion; relaying it into a fresh brief launders it into apparent provenance, and the receiving sub-agent (which cannot see the conversation) has no way to tell a seeded claim from an established fact. (Origin: Emergent — the orchestrator relayed a "documented limitation: the connector cannot deploy" line from one collector's summary into another's brief; it was **not in the corpus**, and only the receiving agent's own verification caught it.) Only one dimension may drive the browser at a time (see `ingestion` §7 rule 9): the parallel collectors use WebFetch/curl, leaving Chrome to `session`.
+- **Run independents in parallel** — dispatch `docs`, `packages`, `api`, `website`, `community`, `deployed-client-bundle`, `infra-backend-fingerprint`, `distribution-artifacts` together (`subagent_type='<dimension>'`, one message, multiple Agent calls). Seed each collector with **warm entry points (URLs / repos / hosts), not claimed facts** — any fact **or inference** carried from Discovery (a price, a tier name, a version — **or a derived hypothesis like "localStorage-key X ⇒ backend is Y"**) is tagged `verify:may-be-stale` so the collector **re-derives it instead of anchoring** on a possibly-stale (or possibly-wrong) value. A Discovery _inference_ is never seeded as a plan fact: label it a hypothesis in `00-recon-plan.md` and tag it `verify:` in the seed, so a collector that inherits it reports it hedged rather than echoing it as observed (a real run seeded an `apolloAnonId ⇒ GraphQL backend` guess that two captures then repeated before the session refuted it). **A sibling collector's _summary_ is a claim, not a source** — when seeding one collector with something another collector reported, tag it `verify:` too, unless the main session has actually read the underlying `raw/` artifact. A returned summary is a compressed, unverified assertion; relaying it into a fresh brief launders it into apparent provenance, and the receiving sub-agent (which cannot see the conversation) has no way to tell a seeded claim from an established fact. (Origin: Emergent — the orchestrator relayed a "documented limitation: the connector cannot deploy" line from one collector's summary into another's brief; it was **not in the corpus**, and only the receiving agent's own verification caught it.) **Every QUANTITATIVE claim in a brief carries its lane.** The rule above covers a *sibling's summary*; it does not cover a number the **orchestrator itself** picked up in passing — from a search result, a page it skimmed, or its own recollection — and then re-emitted as framing. A figure the main session cannot name a `raw/` anchor for is either seeded **`verify:`** or **omitted**; it is never stated flat. A number in a brief reads as established even when nothing established it, and the receiving agent cannot tell the difference. (Origin: indus-sarvam — the orchestrator seeded a "₹98.68 crore IndiaAI funding" figure into the positioning brief as context; the receiving agent traced it to a **third-party user's GitHub issue body**, not to any first-party source, and had to de-launder it. The vendor states only "compute provided under the IndiaAI mission", with no amount.) Only one dimension may drive the browser at a time (see `ingestion` §7 rule 9): the parallel collectors use WebFetch/curl, leaving Chrome to `session`.
 - **Codebase fan-out** — dispatch `codebase`; it clones + maps + returns a per-package work-list; then the main session fans out one reader per substantial package.
 - **Gated dimensions** — `session` and `wire-capture` (rung ≥2) need explicit user authorization first (see `ingestion` §7). `session` follows `.claude/rules/ingestion.md` §9. When `session` is authorized, **dispatch the non-browser collectors in the background (`run_in_background`) and drive the gated browser session in the main session concurrently** — they don't contend (Chrome belongs to the main session; the collectors use WebFetch/curl), so the whole of Ingestion runs in parallel.
 - **Shared seam** — **seed the two shared files `dimensions/_shared/{api-path-catalog.md, feature-flags.md}` (empty, with a header) once, before the collector fan-out**; bundle/session/wire/ distribution then each _append_ a `source:`-tagged section to the same physical file (never their own copy). One owner dimension per static asset; a second mine of the same asset is one source, not corroboration (`ingestion` §6).

package/data/harnesses/discover/harness.json

@@ -1,12 +1,12 @@
 {
   "harness": "discover",
   "name": "discover",
-  "version": "0.1.15",
+  "version": "0.1.16",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
   "seeds": [],
-  "digest": "b55e0ea4a713"
+  "digest": "0bf7a6a6f479"
 }

package/data/harnesses/discover/rules/cartography-coverage.md

@@ -111,7 +111,10 @@ experiential / IA coverage axis (`self-correction.md` rubric, axis 2, max 20) is
   unlocated capabilities and hiding them would inflate the rate. But they are **dispositioned**, so they
   never draw the −2 un-dispositioned penalty, and the scorecard carries `features_not_yet_reachable` so a
   reader can tell a *policy/authorization* boundary from a *thoroughness* failure.
-- `flow_coverage` = `100 × (primary journeys diagrammed in ux-flows.md ÷ journeys identified)`.
+- `flow_coverage` = `100 × (primary journeys diagrammed in ux-flows.md ÷ journeys identified)` — **read both
+  numbers from `ux-flows.md`'s `journeys_diagrammed` / `journeys_identified` frontmatter**
+  (`cartography-flows.md`), never re-derive the denominator here. A reconstructed denominator lets the
+  scorer pick the number that flatters the score, and makes the metric non-reproducible across runs.
 - `screenshot_coverage` = `100 × (primary surfaces with a screenshot ÷ all primary surfaces)`.
 - `ia_nav_complete` = every D0 nav destination has a surface card.
 

package/data/harnesses/discover/rules/cartography-flows.md

@@ -60,6 +60,15 @@ job id, a streamed result). Stop at the terminal write or external response.
 
 ````markdown
 # <Target> — UX Flows
+---
+journeys_identified: <N>   # REQUIRED — every primary journey the corpus identifies, whether or not it
+                           # was diagrammed. This is the DENOMINATOR of feature-coverage's
+                           # `flow_coverage`; without it the metric is reconstructed by whoever scores
+                           # it, and a run that identifies few journeys scores the same as one that
+                           # identifies many and diagrams them all.
+journeys_diagrammed: <N>   # the count of sequence diagrams below
+undiagrammed: [<name>, …]  # the named difference — never an empty list with N_identified > N_diagrammed
+---
 ## TL;DR                  (how the product gets work done: sync-REST vs async-job, where realtime lives,
                            the approval/gate pattern, what's brokered server-side)
 ## Flow index             (table: flow · category · trigger · participants · complexity)

package/data/harnesses/discover/rules/ingestion.md

@@ -78,11 +78,11 @@ Keep `status` and `confidence` honest — they drive the entire evaluation weigh
 
 ## 3. Method & confidence vocabulary (drives evaluation weighting)
 
-`method` is one of: `clone-and-map`, `source-map-reassembly`, `registry-metadata`, `ats-api`, `openapi-verbatim`, `graphql-introspection`, `crawl-clip`, `docs-reconstructed`, `bundle-string-mine`, `dns-ct-fingerprint`, `wire-tap-browser`, `wire-har`, `wire-mitmproxy`, `binary-extract` (asar/apk/crx), `session-playbook`, `sdk-harness`, `inferred`.
+`method` is one of: `clone-and-map`, `source-map-reassembly`, `registry-metadata`, `ats-api`, `first-party-api-json`, `openapi-verbatim`, `graphql-introspection`, `crawl-clip`, `docs-reconstructed`, `bundle-string-mine`, `dns-ct-fingerprint`, `wire-tap-browser`, `wire-har`, `wire-mitmproxy`, `binary-extract` (asar/apk/crx), `session-playbook`, `sdk-harness`, `inferred`.
 
 **Confidence is a function of method** (evaluation relies on this mapping):
 
-- **high** — verbatim machine artifacts: `openapi-verbatim`, `graphql-introspection`, `registry-metadata`, `ats-api`, `clone-and-map`, `binary-extract`.
+- **high** — verbatim machine artifacts: `openapi-verbatim`, `graphql-introspection`, `registry-metadata`, `ats-api`, `first-party-api-json`, `clone-and-map`, `binary-extract`.
 
 > **`ats-api` — a first-party job-board / ATS JSON API is NOT a crawl.** A response from an official
 > applicant-tracking endpoint (`boards-api.greenhouse.io/v1/boards/<slug>/jobs?content=true`,
@@ -94,6 +94,20 @@ Keep `status` and `confidence` honest — they drive the entire evaluation weigh
 > (Origin: Emergent — a 433 KB verbatim Greenhouse JSON body carrying a byte-identical declared tech stack
 > across two postings was labelled `crawl-clip` with `confidence: high`, a mismatch against this very
 > table. The confidence was right and the vocabulary had no word for the artifact.)
+
+> **`first-party-api-json` — the general case of the rule above.** `ats-api` fixed the *hiring* instance
+> of a wider gap: **any verbatim JSON response from a first-party or official platform API is a machine
+> artifact, not a crawl**, and maps to **high**. Use it for a GitHub org/issues/releases API response
+> (`api.github.com/orgs/<org>/repos`, `/search/issues?q=org:<org>`), a status-page API
+> (`status.<vendor>.com/api/v2/summary.json`), a changelog/release JSON feed, a public app-store listing
+> API, or any comparable official endpoint. **The distinction is the artifact, not the topic:** the
+> *rendered page* of the same information is `crawl-clip` (medium); the *API body* is
+> `first-party-api-json` (high). Prefer the more specific term where one exists — `registry-metadata` for
+> npm/PyPI/crates, `ats-api` for job boards, `openapi-verbatim` for a served spec — and reach for this one
+> only when none fits. (Origin: indus-sarvam — the `community` lane mined the GitHub API and, finding no
+> correct term, graded itself `registry-metadata`. The evidence class and the `high` confidence were both
+> right; the label named the wrong registry. A vocabulary with no word for an artifact does not stop a
+> collector using it — it just makes the provenance record lie.)
 - **medium** — `crawl-clip`, `docs-reconstructed`, `bundle-string-mine`, `dns-ct-fingerprint`, `wire-har`.
 - **low** — `inferred`, `session-playbook` Pass-1-only, `wire-tap-browser` shapes-only, any wire-drift observation without a spec.
 
@@ -284,7 +298,7 @@ the elements needing redaction change as you navigate.
 
 `deployed-client-bundle` (static unauth SPA), `session` (authenticated browser runtime), and `wire-capture` (non-browser client) can all surface the same **API path catalog** and **feature flags**. To keep them consumable instead of triplicated **N times** (a real run forked `api-path-catalog.md` up to 7×, and "two copies agree" then mis-reads as corroboration):
 
-- **One physical file, one canonical location, append-only.** The seam files live at `dimensions/_shared/api-path-catalog.md` and `dimensions/_shared/feature-flags.md` — **Ingestion seeds the two empty files (with a header) once, before the collector fan-out.** Every contributing dimension **appends a `source:`-tagged section** (`source: bundle | session | wire | distribution`) and **never creates its own copy**; each collector's `_summary.md` Artifacts list **links** the shared file rather than duplicating it. **Shared-seam allowlist:** these two filenames are the _only_ shared/single-physical artifacts — every other `raw/*` is dimension-private.
+- **One physical file, one canonical location, append-only.** The seam files live at `dimensions/_shared/api-path-catalog.md` and `dimensions/_shared/feature-flags.md` — **Ingestion seeds the two empty files (with a header) once, before the collector fan-out.** Every contributing dimension **appends a `source:`-tagged section** (`source: bundle | session | wire | distribution | api`) and **never creates its own copy**; each collector's `_summary.md` Artifacts list **links** the shared file rather than duplicating it. **Shared-seam allowlist:** these two filenames are the _only_ shared/single-physical artifacts — every other `raw/*` is dimension-private.
 - Evaluation owns the **API-path diff** (an _adaptive N-way_ diff over whichever runtime sources were actually run — see evaluation template 3) in `data-model-api-surface.md`. A path that appears in `bundle` but never in `session`/`wire` is a dormant/unshipped route — a finding, not noise.
 - **The cloned source tree is a shared working copy too (a sequencing race, not just the seam files).** On a `source:full` target, `codebase` clones into `source/<target>/`, and other dimensions (`docs`/`packages`) may read in-repo files from it. A clone-dependent collector dispatched **concurrently** with the clone can read a **mid-checkout tree** (a `.git`-only state) and silently fall back to a weaker source. So either (a) treat the `codebase` clone as a **sequencing barrier** — let it finish before dispatching any collector that reads `source/<target>/` — or (b) require each clone-dependent collector to **fetch its own copy** (GitHub API / its own shallow clone) and never assume the shared clone is ready. (Origin: Twenty — `docs` raced the `codebase` clone, saw a `.git`-only tree, and fell back to the live docs site; `packages` correctly fetched its own manifests and was unaffected.)
 
@@ -294,7 +308,9 @@ the elements needing redaction change as you navigate.
 >
 > **Paired inputs make the diff feedable (capture cue).** The split is only emittable if BOTH lanes were captured: when a target has **a published API AND an authed session**, the **pre-nav in-page fetch/XHR tap** (`session` — the app-own paths it actually calls) and the **unauth bundle/route-manifest** (`deployed-client-bundle` — the published paths) are **paired required inputs**. Install the tap _before_ navigation (else on-load app calls are missed) and capture the manifest unauth; a session that only screenshots, or a bundle mine with no session, leaves the diff un-feedable. (Origin: Akeneo — 54 session-observed app-own paths vs a 124-path unauth `/api/rest/v1` manifest, near-disjoint.)
 >
-> **Host-level dimensions cite, they don't append (seam allowlist).** The shared `api-path-catalog.md` `## source:` allowlist is **bundle / session / wire / distribution** only — the path-contributing runtime lanes. A host-level dimension (`infra-backend-fingerprint`) that wants to cross-reference the catalog does so **from its own `raw/`** (cite hosts/paths by reference), and does **not** append its own `## source:` section to the shared file. (Origin: Akeneo — infra appended a host-level note to the path catalog; benign but blurs the allowlist.)
+> **Host-level dimensions cite, they don't append (seam allowlist).** The shared `api-path-catalog.md` `## source:` allowlist is **bundle / session / wire / distribution** (the path-contributing *runtime* lanes) **plus `api`** (the *published* lane — see below). A host-level dimension (`infra-backend-fingerprint`) that wants to cross-reference the catalog does so **from its own `raw/`** (cite hosts/paths by reference), and does **not** append its own `## source:` section to the shared file. (Origin: Akeneo — infra appended a host-level note to the path catalog; benign but blurs the allowlist.)
+>
+> **`api` IS on the allowlist — but it is the PUBLISHED lane, and it never corroborates a runtime path.** The published developer/partner spec belongs in the same physical file as the runtime lanes because the **published-vs-app-own diff** (evaluation template 3) is the whole point of the seam, and it is far easier to compute when both sides sit side by side under one header. Two hard constraints ride with the inclusion: (a) an `## source: api` section carries the **spec-declared** surface only — never a path the collector merely inferred; and (b) **`api` is excluded from the promotion rule for app-own paths** — a path appearing in `## source: api` and in `## source: session` is *the published surface and the runtime surface agreeing*, which is a **finding about drift (or its absence)**, not two independent dimensions corroborating one claim. (Origin: indus-sarvam — the `api` lane appended a 70-operation published catalog in violation of the then-allowlist; deleting it would have made the corpus strictly worse, because that section is exactly what made the published-vs-app-own diff feedable. The rule was wrong, not the collector.)
 
 ---
 
@@ -559,7 +575,27 @@ A single linear sweep wastes context on things you can read for free and wastes
 
 **Pass 2 — fresh-run validation (with explicit cost/state-change confirmation).** Only after Pass 1, and only with explicit user OK stating the exact action + cheapest mode + estimated cost. Catches what Pass 1 can't: the submit/write request body, live state-machine transitions, the completion event, server-side resolution of shorthand, ID/slug-generation, the real iteration endpoint, and the full realtime event catalog. **Legitimate to skip** if the user opts out — leave write-side shapes as open questions; never fabricate them.
 
-> **Record the write-side decision as a machine flag, not re-derived prose.** A Pass-1-only run leaves the _entire_ write/generate/launch surface unobserved — feature _existence/gating_ is solid, but feature _execution behavior_ rests on marketing/docs and must never be promoted to fact (this caveat otherwise gets re-hedged across 3–4 rollups every cost-gated run). So the session `_summary.md` frontmatter carries `write_side_observed: <true|false>` and `pass2: <not-applicable | offered-pending | declined-by-user | deferred | done>` (this flag is the load-bearing part — it lets Evaluation render the write-side gap _once_). When it would help a later run resume, optionally add `captures/pass2-followup.md` listing the **exact cheapest-mode write actions + est. cost** that would close the gap. Discovery seeds the `pass2:` decision in `00-recon-plan.md` for any `auth:have-login` target.
+> **Record the write-side decision as a machine flag, not re-derived prose.** A Pass-1-only run leaves the _entire_ write/generate/launch surface unobserved — feature _existence/gating_ is solid, but feature _execution behavior_ rests on marketing/docs and must never be promoted to fact (this caveat otherwise gets re-hedged across 3–4 rollups every cost-gated run). So the session `_summary.md` frontmatter carries `write_side_observed: <true|false>` and `pass2: <not-applicable | offered-pending | declined-by-user | deferred | authorized-declined | done>` (this flag is the load-bearing part — it lets Evaluation render the write-side gap _once_).
+
+> **An AUTHORIZED Pass-2 that is never exercised is a DEFECT, not a default.** When the user has granted
+> Pass-2 (explicitly, or by saying the run may spend credits / test it), the session lane must do one of
+> exactly two things before Evaluation:
+>
+> 1. **Exercise the cheapest write action** that closes the gap — and there is almost always a cheap one:
+>    a simulated/dry run, a draft save, a version bump, a single smallest-unit generation. Price it, name
+>    it, run it, capture the request+response envelope.
+> 2. **Record `pass2: authorized-declined` with the reason** (the user wrapped the run early; the cheapest
+>    action still mutated shared state; no non-destructive write exists), plus the exact actions and costs
+>    that would close it.
+>
+> `pass2: deferred` is **not** a valid terminal state for an authorized run — it is the state that lets an
+> authorization quietly expire. Mode 5 treats an authorized-but-unexercised Pass-2 as a **medium Ingestion
+> defect** and charges it, because a run that holds permission to observe the write side and ships without
+> it has left its single largest blind spot open by inattention rather than by policy. (Origin:
+> indus-sarvam — the user granted credit spend mid-run; the orchestrator acknowledged it, planned around
+> it, asked which action to take, and shipped `write_side_observed: false` when no reply arrived. The
+> whole write surface, the deploy transition and the live-call realtime plane went unobserved with 100
+> credits unspent.) When it would help a later run resume, optionally add `captures/pass2-followup.md` listing the **exact cheapest-mode write actions + est. cost** that would close the gap. Discovery seeds the `pass2:` decision in `00-recon-plan.md` for any `auth:have-login` target.
 
 **Pass 3 — synthesis.** Walk the captures, pull each finding into the dimension's `_summary.md`, note the cleverest design choices, defaults imposed, performance characteristics, and open questions.
 

package/data/harnesses/discover/rules/tradecraft.md

@@ -128,6 +128,40 @@ pbpaste > capture.json      # macOS
 xclip -o  > capture.json    # Linux
 ```
 
+> **⚠ VERIFY THE PASTE — `copied=true` is NOT proof the OS clipboard changed.** `execCommand('copy')`
+> reports success from *inside the page* and can still leave the system clipboard holding a **previously
+> copied payload** — most reliably when Chrome is not the OS-focused window (the agent's terminal is).
+> A naive `pbpaste > raw/x.json` then writes **the wrong body** into `raw/` under a confident `_meta`,
+> which is the worst artifact class there is: a stale file that scores silently.
+>
+> **Always assert the length matches what the tap reported**, before trusting the file:
+>
+> ```bash
+> EXPECT=14866                      # the len= the __CP call returned
+> GOT=$(pbpaste | wc -m | tr -d ' ')   # -m = CHARACTERS, never -c (bytes). See below.
+> [ "$GOT" -ge $((EXPECT-100)) ] && [ "$GOT" -le $((EXPECT+100)) ] \
+>   && pbpaste > raw/capture.json && echo "ok len=$GOT" \
+>   || echo "STALE CLIPBOARD: expected ~$EXPECT, got $GOT — do NOT write"
+> ```
+>
+> **Compare CHARACTERS (`wc -m`), not BYTES (`wc -c`).** JavaScript's `String.length` counts UTF-16 code
+> units; `wc -c` counts UTF-8 bytes. Any non-ASCII payload makes the two diverge badly — Devanagari,
+> Bengali, Tamil, CJK and emoji are 3–4 bytes per character, so a perfectly fresh 16,378-character capture
+> measures 19,740 bytes and a byte-based guard **rejects a good artifact**. Allow ±100 for the trailing
+> newline and minor encoding slack. (Origin: indus-sarvam — this guard's own first use produced a false
+> positive on a Hindi-language agent transcript; the clipboard was fine and the check was wrong. On a
+> multilingual target the byte form fails *more often than it succeeds*.)
+>
+> Cheap corroboration: also compare a head token (`pbpaste | head -c 40`) against the head the tap
+> returned. **Escalation ladder when it is stale:** (1) click inside the page and retry — it is flaky, not
+> permanently broken; (2) retry once more with the textarea left mounted a beat longer; (3) fall back to
+> paging via `javascript_tool` slices (budget ~1 KB of *usable* output per slice, not the 3 KB the slice
+> size suggests); (4) if paging is uneconomic, write a **decoded** artifact with `verbatim: false`,
+> `_meta.why_not_verbatim` naming the failure, and `_meta.refetch` carrying the exact command — an honest
+> decoded artifact beats a confident wrong one. (Origin: indus-sarvam — a 14,866-byte flag payload
+> reported `copied=true` three times while `pbpaste` kept returning a 195,216-byte body copied minutes
+> earlier. Caught only because the length was checked.)
+
 **Scrub before copying**, not after: build the object with `__SCRUB` first, then `window.__CP(pack)`. The
 clipboard is local, so this stays inside the no-exfiltration rule (ingestion §7 rule 7).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nurix/etna",
-  "version": "0.19.88",
+  "version": "0.19.90",
   "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": "417d61b8de2d"
+  "etnaFingerprint": "8d6f9b80d64d"
 }