@nurix/etna 0.15.2 → 0.15.3

package/data/harnesses/re/rules/re-discovery.md

@@ -0,0 +1,266 @@
+# Discovery Reference — Scope Gate · Access Vector · Dimension Catalog
+
+The reference knowledge for **Discovery** (`re` harness, Mode 1). It carries all three of
+Discovery's steps in the order they run:
+
+- **Part A — Scope-feasibility gate** (Step 0): resolve the target's identity and emit a verdict
+  so the run never wastes effort on an infeasible target.
+- **Part B — Access vector** (Step 1): grade the four-axis capability vector that decides which
+  dimensions are reachable and which method each uses.
+- **Part C — Dimension catalog** (Step 2): the canonical list of dimensions, their detection
+  signals, dump strategy, and owning agent.
+
+`ingestion` also reads **Part C** to dispatch the right agent with the right method.
+
+---
+
+# Part A — Scope-feasibility gate (Step 0)
+
+Run this **before** any dimension probing. It resolves the target's identity and emits one of four
+verdicts. The rules are mechanical — execute them with cheap probes (`WebSearch`, `curl`,
+`git ls-remote`, `npm view`) in well under a minute.
+
+Output: `research/<target>/00-scope-verdict.md` + a `scope:` block in `00-recon-plan.md`. If the
+verdict is not `accept`, Discovery **halts** (presents the narrowing prompt, or refuses) and does
+not proceed to dimension probing.
+
+## Verdicts
+
+| Verdict | Meaning | Downstream |
+|---------|---------|-----------|
+| **accept** | bounded target with ≥1 real surface | continue to dimension probing |
+| **narrow** | too-broad-suite or ambiguous-name | present the narrowing prompt; halt for user reply |
+| **redirect** | a commodity primitive (behavior = its public spec) | offer a facet menu; halt for user reply |
+| **refuse** | ethically/legally out-of-bounds (hard stop only here) | stop; no run |
+
+A **no-reachable-surface** result is a **soft prompt** ("log in / give me a URL or repo"), not a
+hard refuse — only the ethics gate (Gate B) is a hard refuse.
+
+## The decision algorithm (priority-ordered; first match wins)
+
+**0a — Resolve identity.** If the user gave a concrete URL/repo/package, identity is fixed → skip
+ambiguity. Else `WebSearch "<target>"` + `"<target> software"`; collect canonical homepage, vendor,
+one-line category.
+
+**Gate A — ambiguity.** Top results map to ≥2 unrelated vendors/categories → `narrow` (disambiguate). STOP.
+
+**Gate B — ethics.** Resolved product is piracy/cracking/malware/CSAM/credential-harvesting/spyware,
+or the only way in is bypassing auth/paywall/TOS the user has no right to → `refuse` (ethics). STOP.
+*(Highest priority once identity is known — never proceed on an out-of-bounds target even if reachable.)*
+
+**Gate C — suite size.** Fetch homepage; count distinct independently-marketed products N (nav
+"Products" items each with their own `/pricing` or `/docs` tree; or a `WebSearch "<target> products"`
+grid). If N ≥ 4 **OR** the entity is on the umbrella seed list → `narrow` (pick-product). STOP.
+> Umbrella seed list: AWS, Azure, GCP, Salesforce, Microsoft 365, SAP, Oracle Cloud, Google
+> Workspace, Adobe Creative Cloud, Atlassian.
+> Guard against false positives: "one platform, many *modules* sharing one account/API/pricing page"
+> (Stripe: Payments/Billing/Connect) is **one product → accept**, not a suite. The N≥4 count alone
+> isn't enough — require separate pricing/docs trees, not just a broad nav.
+
+**Gate D — primitive.** Target is a single foundational building block whose behavior is a published
+spec with no hidden app surface (managed primitives like S3/EC2/Lambda; single-purpose util libs
+with <~5 exports; protocol/spec names; a raw DB engine) → `redirect` (pick-facet). STOP.
+> Bias: only `redirect` when behavior is fully a public spec. When a hosted SaaS wrapper exists
+> (Redis Cloud, MongoDB Atlas), prefer `accept` on the wrapper.
+
+**Gate E — reachability.** Run the cheapest probe per dimension as a boolean (does ANY surface
+exist?): `git ls-remote` OR npm/PyPI hit OR `llms.txt`/docs subdomain OR homepage-200-with-content
+OR user-has-session. If ZERO surfaces → **soft prompt** ("No reachable surface — log in, or give me
+a repo/docs/URL"). If exactly one thin non-session surface → `accept` (thin) with a shallow-coverage
+warning.
+
+**Fallthrough → `accept`.** Compute the access vector (Part B) and proceed to dimension probing.
+
+**Recursion:** a narrowed pick re-enters Step 0 (so "Salesforce → Marketing Cloud" is itself
+feasibility-checked and may narrow again). **Max narrow-depth = 2**, then accept-the-narrowest with
+a partial-coverage warning.
+
+## `00-scope-verdict.md` shape
+
+```markdown
+---
+target: <slug>
+scope_checked_at: <YYYY-MM-DD>
+verdict: accept | narrow | redirect | refuse
+verdict_reason: clean | too-broad-suite | primitive | ambiguous-name | no-surface | ethics | over-scoped
+resolved_identity: <canonical homepage / repo / package>
+suite_product_count: <N>
+surfaces_present: [codebase?, docs?, api?, website?, session?]
+awaiting_user: <true|false>
+---
+# <Target> — Scope Verdict: <VERDICT>
+## Resolution        (what the name resolved to + evidence)
+## Gate trace        (which gate fired A–E + the verbatim signal)
+## Verdict & reason
+## Narrowing prompt   (if narrow/redirect — the exact question + options)
+## If refused         (one-line reason + what would make it acceptable)
+```
+Mirror `verdict` into a `scope:` frontmatter block on `00-recon-plan.md` so ingestion reads one field.
+
+## Narrowing prompt templates
+
+**NARROW-SUITE (Gate C):** "I can recon a focused product, but **<Target>** is a suite of ~<N>
+independently-built products — a single run would be shallow across all of them. Which one should I
+tear down?" + a numbered list auto-built from the homepage product nav, each tagged with its likely
+access-grade. Always append "0. A specific feature within one of these (tell me which)."
+
+**NARROW-DISAMBIGUATE (Gate A):** "**<Target>** resolves to more than one product. Which did you
+mean?" + numbered candidates (vendor · one-line · URL) + "none of these — give me a URL."
+
+**REDIRECT-PRIMITIVE (Gate D):** "**<Target>** is a documented primitive, not a product with hidden
+internals — its behavior is the public spec. I can still recon a facet. Which angle?" + a facet menu
+(for a managed service: console/dashboard UX · public API surface · consistency/semantics model ·
+pricing & limits as a product · competitive positioning) + "Or point me at a real product that USES
+<Target> and I'll recon that instead."
+
+## Worked verdicts (regression fixtures)
+
+| Target | Gate | Verdict | Note |
+|--------|------|---------|------|
+| AWS S3 | D | redirect (primitive) | "behavior is the public API; pick a facet or a product built on S3" |
+| Salesforce | C | narrow (suite) | "pick a cloud: Sales / Service / Marketing / Flow Builder / Apex / …" |
+| Microsoft 365 | C | narrow (suite) | umbrella seed list; options Word/Excel/Teams/… each tagged |
+| Notion | fallthrough | accept | single product; docs+api+website+session, no public monorepo |
+| Liveblocks | fallthrough | accept (Case 1) | open monorepo + SDKs + docs + OpenAPI + site + session |
+| bare "Atlas" | A | narrow (ambiguous) | MongoDB Atlas vs Ory Atlas vs Palantir |
+| leftpad-class util | D | redirect (primitive) | "<5 exports; source IS the spec" |
+| coming-soon splash, no session | E | soft prompt | "no reachable surface — log in or give me a repo/URL" |
+| torrent/credential-stuffing service | B | refuse (ethics) | no prompt, no run |
+
+---
+
+# Part B — Access is a capability VECTOR (Step 1)
+
+A target's "access" is **four orthogonal axes**, each carrying `{value, confidence, evidence}`.
+The vector — not a single grade — decides which dimensions are reachable and which extraction
+*method* each uses.
+
+| Axis | Values | Unlocks dimensions | Anchors |
+|------|--------|--------------------|---------|
+| **source** | full · partial · none | codebase, packages | *Case 1* (full = OSS repo) |
+| **runtime** | reachable · gated · none | deployed-client-bundle, api, infra-backend-fingerprint, wire-capture | *Case 2* (reachable + source:none) |
+| **auth** | have-login · none | session | *Case 3* (have-login) |
+| **presence** | rich · thin · none | docs, website, community | (almost always rich) |
+
+The three named **cases** are presets over this vector — a target can light several at once
+(Liveblocks = source:full + runtime:reachable + auth:obtainable + presence:rich → nearly all
+dimensions). Rules:
+- **`auth:obtainable` is a hint, not actionable** — the harness never self-signs-up; it only counts as `have-login` if the *user* hands over a session.
+- **Dimension-level access overrides the target headline** for method selection (a Case-1 target can still have a Case-3 session dimension).
+- Method swaps on axis *value*: `source:full` ⇒ `clone-and-map`; `source:partial` ⇒ `source-map-reassembly`; `runtime:reachable + source:none` ⇒ `bundle-string-mine` + wire-capture.
+
+Discovery records the resolved vector in the `access_grade` frontmatter of `00-recon-plan.md`.
+
+---
+
+# Part C — The dimension catalog (Step 2)
+
+| # | Dimension | Agent | Unlocking axis | One-line strategy |
+|---|-----------|-------|----------------|-------------------|
+| 1 | **codebase** | `codebase` | source:full | clone → structural map → per-package fan-out |
+| 2 | **docs** | `docs` | presence | `llms.txt` → else crawl/clip → organize by section |
+| 3 | **packages** | `packages` | source/presence | registry metadata + exports + type defs |
+| 4 | **api** | `api` | runtime/presence | OpenAPI/GraphQL → endpoint catalog (+ **MCP/tool-catalog fold-in**) |
+| 5 | **website** | `website` | presence | crawl public pages → features, pricing, positioning |
+| 6 | **community** | `community` | presence | first-party changelog/issues/discord themes |
+| 7 | **session** | `session` | auth:have-login | delegate to the session playbook (§9 of `re-ingestion`: 3-pass, P0–P6) |
+| 8 | **deployed-client-bundle** | `deployed-client-bundle` | runtime:reachable | unauth SPA: route table, API-path catalog, flags, env, source maps |
+| 9 | **infra-backend-fingerprint** | `infra-backend-fingerprint` | runtime/presence | DNS, cert-transparency, CDN/cloud, headers (+ **sub-processor/trust fold-in**) |
+| 10 | **wire-capture** | `wire-capture` | runtime (source:none) | the 3-rung ladder for non-browser/no-source clients (gated) |
+| 11 | **distribution-artifacts** | `distribution-artifacts` | runtime (non-web client) | extension CRX / Electron `.asar` / mobile binary / CLI |
+
+> **Deferred (available on request, not built):** `external-reputation` (G2/Reddit/HN — the only
+> "what others say" surface) and `hiring-intel` (job posts leak the backend stack). Strong
+> candidates, declined for this iteration. Re-add via self-correction if a run needs them.
+
+An **absent** dimension is a finding — record it with its evidence; never silently drop it.
+
+## 1–7 — the core dimensions (strategy in brief)
+
+See git history / the source playbook for the full strategy text; in brief:
+- **codebase** — shallow-clone into `source/<target>/`, read orientation files + manifests, map
+  packages + internal dep hierarchy, return a per-package work-list for the main-session fan-out.
+- **docs** — prefer in-repo docs, then `llms.txt`/`llms-full.txt`, then crawl; organize by section.
+- **packages** — per public package: registry metadata, `exports` map + `.d.ts` type surface, health.
+- **api** — fetch the spec verbatim, build an endpoint catalog (auth, envelope, pagination, webhooks).
+  **NEW fold-in:** also probe MCP/tool surfaces — `/.well-known/mcp`, an MCP server manifest, a
+  function-calling tool schema, an LLM "actions" file — and write `raw/tool-catalog.md` (an MCP tool
+  list *is* an API catalog; it lives here, not in its own dimension).
+- **website** — crawl home/features/pricing/customers/integrations; extract positioning, pricing
+  matrix, target market.
+- **community** — *first-party only*: changelog cadence + direction, issue/discussion themes, blog.
+- **session** — the deepest, opt-in, user-gated dimension; delegates to the session playbook in
+  `re-ingestion` §9 (3-pass, P0–P6, captures/raw/curls).
+
+## 8 — deployed-client-bundle — `deployed-client-bundle`
+
+**Unlocked by:** `runtime:reachable`. The **unauthenticated app shell** — distinct from `website`
+(marketing) and `session` (authenticated). Works on closed SaaS with no repo and no login.
+
+**Detection:** an app subdomain (`app.<target>.*`) or SPA route serves a JS bundle;
+`sourceMappingURL` present; a `/assets/*.js` graph.
+
+**Strategy:** fetch the main bundle(s); string-mine the **route table**, the **API-path catalog**
+(→ shared `raw/api-path-catalog.md`, `source: bundle`), **feature flags** (→ shared
+`raw/feature-flags.md`), embedded **env config** (`VITE_*`, `NEXT_PUBLIC_*`, public keys —
+field-names only, redact values), and reassemble **source maps** if shipped (`method:
+source-map-reassembly`, confidence high). Digest huge bundles, don't paste.
+
+**Artifacts:** `_summary.md` + `raw/{route-table.md, api-path-catalog.md, feature-flags.md, env-config.md, bundle-map.md}`.
+
+## 9 — infra-backend-fingerprint — `infra-backend-fingerprint`
+
+**Unlocked by:** `runtime`/`presence`. Reconstructs the backend you can't see in the repo.
+
+**Detection:** always attemptable for any live domain.
+
+**Strategy:** DNS records; **cert-transparency subdomain enumeration** (crt.sh → staging/internal/
+api hosts); CDN/cloud fingerprint (CNAMEs, IP/ASN, response headers); security headers; tech
+fingerprint (framework/analytics tells). **Sub-processor fold-in:** fetch the `/legal`, `/trust`,
+`/security`, `/dpa` pages → `raw/sub-processors.md` — the sub-processor list **names the vendor
+stack** (cloud, payments, AI provider, email, telephony), which is exactly this dimension's job.
+
+**Artifacts:** `_summary.md` + `raw/{dns-and-subdomains.md, cloud-cdn-fingerprint.md, security-headers.md, sub-processors.md}`.
+
+## 10 — wire-capture — `wire-capture` (first-class, GATED)
+
+**Unlocked by:** `runtime` when the interesting client is **non-browser** or there's **no source**
+(your Case 2). The runtime-evidence complement to `distribution-artifacts` (static): the binary says
+what hosts it *might* call; the capture says what it *actually* calls.
+
+**Detection:** a non-browser client exists (from distribution-artifacts) OR an unauth SPA makes
+structured XHRs worth a tap, AND the appropriate ethics rung is authorized.
+
+**Strategy:** the **3-rung ladder** (lowest privilege first) — see `re-ingestion` §7.1:
+1. browser network tap (unauth, default) → `wire-tap-browser`;
+2. HAR export → `wire-har`;
+3. mitmproxy (**gated, opt-in, user-run, first-party traffic only**) → `wire-mitmproxy`.
+
+**Artifacts:** `_summary.md` + `captures/wire-narrative.md` + `raw/{flows.json (redacted/digested), api-path-catalog.md (source: wire)}` + `curls.md`. Record the chosen rung + authorization in `_meta`.
+
+## 11 — distribution-artifacts — `distribution-artifacts`
+
+**Unlocked by:** `runtime` (a downloadable non-web client). Often the closest thing to source for a
+closed product.
+
+**Detection:** a Chrome/Firefox web-store listing; a "Download for Mac/Windows" (Electron/Tauri)
+button; an App Store / Play Store listing; a published CLI (`npm i -g`, brew, GitHub releases).
+
+**Strategy:** **extension** — decode `manifest.json` (permissions/hosts/content-scripts = a
+capability map). **Electron** — `npx asar extract app.asar` → map JS modules + the shared
+route/API/flag catalog from the desktop client (often richer than web). **mobile** — `Info.plist`/
+`AndroidManifest` hosts, ATS exceptions, embedded-SDK list from strings (**redact any embedded
+keys**). **CLI** — help text/subcommands = an API catalog. Read the artifact's EULA first (see
+`re-ingestion` §7.2); never silently decompile a restrictively-licensed binary.
+
+**Artifacts:** `_summary.md` + `raw/{extension-manifest.md, electron-asar-map.md, mobile-strings.md, cli-catalog.md}` (whichever apply) + `raw/api-path-catalog.md` (source: distribution).
+
+---
+
+## How Discovery uses this reference
+
+Step 0 — run **Part A** (the gate); halt unless `accept`. Step 1 — grade the **Part B** vector with
+evidence. Step 2 — for each dimension in **Part C**, check its unlocking axis against the resolved
+vector, run the cheap detection probe, and record **available / partial / absent** with evidence
+into `00-recon-plan.md`. Gated dimensions (session, wire-capture rung 3) are flagged for user
+confirmation before ingestion dispatches them.

package/data/harnesses/re/rules/re-evaluation.md

@@ -0,0 +1,100 @@
+# Evaluation Templates
+
+`evaluation` reads every `dimensions/<dim>/_summary.md` (its **provenance frontmatter** +
+Findings) and reconciles them into **cross-dimension** documents under
+`research/<target>/evaluation/`. The value is the reconciliation — cross-checking views into one
+coherent picture, **weighted by how each claim was obtained**, with disagreements flagged.
+
+**Three rules for every evaluation doc:**
+1. **Anchor + tag every claim** with its dimension *and provenance*: `(api: raw/endpoint-catalog.md
+   · openapi-verbatim · high)`. The method + confidence come verbatim from the source dimension's
+   `_summary.md` frontmatter.
+2. **Weight, don't average.** A claim's confidence = the **max** of its sources' confidence,
+   **promoted one band only if corroborated by ≥2 *independent* dimensions**, capped at source
+   confidence when single-source. Conflicts are **flagged, never averaged**.
+3. **Cross-check, don't concatenate.** Agree → state as fact. Disagree / single-source / low-conf →
+   render hedged ("observed but unverified…") and flag in the doc's reconciliation section.
+
+**Independence (for the promotion rule):** `codebase`, `api`, `session`, `wire-capture`,
+`distribution-artifacts` are mutually independent and independent of marketing. **`website` and
+`docs` are NOT independent** for *feature claims* (docs often restate marketing) — two of them
+agreeing is still one source. A bundle-declared route + a session-observed route ARE independent.
+
+**Presentation mapping:** high → stated as fact; low/single-source → hedged as tentative;
+conflicted → flagged. (This is the "lighter" form of the provenance-weighting — done inline in the
+prose, not via a separate `claims.yaml`.)
+
+---
+
+## 1. `evaluation/technology-architecture.md`
+```markdown
+# <Target> — Technology & Architecture
+## TL;DR                  (3–5 sentences; the single most distinctive choice)
+## Stack                  (languages/frameworks/build/runtime — table, each anchored+tagged)
+## Architecture           (client/server split, packages+deps, runtime/sync/data model, transport)
+## How it's built         (monorepo layout, public/private, codegen, CI, release cadence)
+## Notable design choices  (the 3–5 worth stealing + why)
+## Cross-dimension reconciliation  (agreements/disagreements + confidence per claim)
+## Open questions
+```
+
+## 2. `evaluation/product-features.md`
+```markdown
+# <Target> — Product Features & Capabilities
+## What it does           (one paragraph)
+## Feature map            (every capability · user · maturity GA/beta/docs-only — anchored+tagged)
+## User-facing surfaces   (dashboard/editor/components/CLI/widgets)
+## User journeys          (the 2–3 primary flows end-to-end)
+## Gaps & rough edges     (from community signal)
+## Cross-dimension reconciliation  (marketing claims vs. what code/docs actually support — flag over-claims)
+```
+
+## 3. `evaluation/data-model-api-surface.md`
+```markdown
+# <Target> — Data Model & API / SDK Surface
+## Core entities          (domain objects + relations; ER-style)
+## Integration surface    (SDK/packages public API · REST/HTTP catalog · realtime/wire protocol)
+## Auth & tenancy model   (token type, where it lives, scope expression)
+## Three-way API-path diff (the seam rule: bundle-declared vs session-observed vs wire-observed —
+                            dormant/unshipped routes are findings)
+## Cross-dimension reconciliation  (published surface [api/packages/docs] vs observed wire [session/
+                            wire-capture]; document drift — published=fact, observed-drift=tentative)
+## Open questions
+```
+
+## 4. `evaluation/competitive-positioning.md`
+```markdown
+# <Target> — Competitive Positioning
+## Positioning            (their pitch + market — website/blog)
+## Pricing & packaging    (plans, what gates what, unit economics — website pricing + platform/limits)
+## Differentiation        (claimed moat vs the teardown's read of the real moat — often infra/data)
+## Alternatives & comparison  (named competitors + how it differs)
+## Strategic read         (direction from changelog/blog)
+```
+
+---
+
+## 5. `research/<target>/README.md` — the run story
+```markdown
+# <Target> — Recon Run
+> One paragraph: what it is + why we ran recon.
+## Access grade           (the resolved vector — source/runtime/auth/presence — + matched case[s])
+## Dimensions covered     (table: dimension | status | method | confidence | headline finding)
+## Headline findings      (5–10, each anchored+tagged)
+## How to navigate         (00-scope-verdict.md, 00-recon-plan.md, dimensions/, evaluation/, 04-self-correction-proposal.md)
+## Lessons                 (candidate methodology learnings → feed self-correction)
+## Reproduction
+```
+
+---
+
+## Evaluation method
+1. Read every `dimensions/*/_summary.md` frontmatter first (the provenance index) — note method +
+   confidence + status + gaps per dimension.
+2. Read Findings; drop into specific `raw/` artifacts only when a claim needs a precise value.
+3. Draft the four rollups + the README — each rollup may be drafted by its own sub-agent dispatched
+   from the **main session** (overlapping reads, independent writes), then a single reconciliation
+   pass keeps them consistent.
+4. Tag every claim with provenance; weight per the rules above; flag every disagreement; record
+   every gap. A confident doc built on one low-confidence dimension is worse than an honest
+   "single-source, unverified."

package/data/harnesses/re/rules/re-ingestion.md

@@ -0,0 +1,266 @@
+# Ingestion Contract — Dump Shape · Provenance · Ethics · Session Playbook
+
+The reference knowledge for **Ingestion** (`re` harness, Mode 2). Every dimension dump obeys the
+contract in §1–8 so (a) the **evaluation** mode can rely on a stable shape and weight each claim by
+*how it was obtained*, and (b) a future agent can reproduce or extend any dump. §9 carries the
+deepest, gated dimension's method — the logged-in browser-session playbook — which the `session`
+agent follows.
+
+This contract generalizes the source playbook's three-format contract (`captures/*.md` narrative +
+`raw/*.json` verbatim + `curls.md`) to *any* dimension.
+
+> **Contract style = "lighter".** Provenance ("how it was dumped") lives in the
+> **`_summary.md` frontmatter**, not a separate `manifest.yaml`. There is no parallel YAML
+> machine-spine — everything stays markdown-with-frontmatter. Evaluation reads the frontmatter
+> to weight claims; self-correction reads it to detect under-delivery.
+
+---
+
+## 1. Folder layout
+
+```
+research/<target>/dimensions/<dimension>/
+├── _summary.md        ← decoded narrative + provenance frontmatter (human + machine read this)
+└── raw/               ← verbatim artifacts (the reproducer reads these)
+```
+
+Richer dimensions inherit the playbook contract (extra files, same `_summary.md` provenance):
+- **session**: `dimensions/session/{_summary.md, captures/p*.md, raw/*.json, curls.md}`
+- **wire-capture**: `dimensions/wire-capture/{_summary.md, captures/wire-narrative.md, raw/flows.json, curls.md}`
+
+---
+
+## 2. `_summary.md` — required shape (with provenance frontmatter)
+
+```markdown
+---
+dimension: <codebase|docs|packages|api|website|community|session|deployed-client-bundle|infra-backend-fingerprint|wire-capture|distribution-artifacts>
+target: <slug>
+status: complete | partial | blocked
+# --- provenance (the "how it was dumped" layer evaluation weights on) ---
+access_grade_used: <source:full | runtime:reachable | auth:have-login | presence:rich | ...>
+method: <the ACTUAL extraction method — see §3 vocabulary>
+completeness_pct: <0-100, honest self-estimate of reachable surface captured>
+confidence: high | medium | low      # how much to TRUST what was captured (see §3)
+captured_at: <YYYY-MM-DD>
+sources: [<urls / paths actually consulted>]
+gaps: [<structured — each is a thing evaluation must NOT treat as covered>]
+---
+
+# <Target> — <Dimension> dump
+
+## Method
+Exactly what was done, which tools, what was skipped and why. (The prose behind the frontmatter `method`.)
+
+## Findings
+Ordered, concrete observations — real values (package names, versions, endpoint paths, file
+paths, page URLs, prices). Tables liberally. The load-bearing section.
+
+## Inferences
+What the findings imply. Mark inference vs. fact.
+
+## Open questions
+What couldn't be captured and why. Never fabricate to fill a gap.
+
+## Artifacts
+Index of `raw/` files, one line each.
+```
+
+Keep `status` and `confidence` honest — they drive the entire evaluation weighting.
+
+---
+
+## 3. Method & confidence vocabulary (drives evaluation weighting)
+
+`method` is one of: `clone-and-map`, `source-map-reassembly`, `registry-metadata`,
+`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`, `inferred`.
+
+**Confidence is a function of method** (evaluation relies on this mapping):
+- **high** — verbatim machine artifacts: `openapi-verbatim`, `graphql-introspection`, `registry-metadata`, `clone-and-map`, `binary-extract`.
+- **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.
+
+---
+
+## 4. `raw/*` — required shape
+
+Structured captures (API responses, registry metadata, schemas) → JSON with a `_meta` header:
+```json
+{
+  "_meta": { "source": "...", "captured_at": "YYYY-MM-DD", "kind": "...", "byte_length": 0, "redactions": ["field → <REDACTED:...>"] },
+  "body": { /* verbatim, PII + secrets redacted */ },
+  "_decoded": { "field": "meaning + observed values" },
+  "_observation": "optional — what's load-bearing"
+}
+```
+Prose captures (doc/marketing pages, structure maps, catalogs) → markdown with a metadata line:
+`<!-- source: <url-or-path> · captured_at: YYYY-MM-DD · method: <method> -->`
+
+**One file per logical artifact**, named by what it is (`endpoint-catalog.md`, `react-exports.md`,
+`pricing.md`, `structure-map.md`).
+
+---
+
+## 5. Size discipline — reduce, don't dump
+
+Large artifacts (a 3 MB bundle, a 5 MB response, a 700-page sitemap) are **digested**, not pasted:
+the schema/shape, enum distributions, one redacted representative sample, counts. A `raw/` file is
+readable, not a memory dump. Set `digested: true` context in the artifact's `_meta`.
+
+---
+
+## 6. The shared-surface seam rule (bundle ↔ session ↔ wire-capture)
+
+`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:
+
+- Use **one canonical artifact name** across all three: `raw/api-path-catalog.md` and
+  `raw/feature-flags.md`, each row carrying a `source: bundle | session | wire` column.
+- Evaluation owns the **three-way diff** (static-declared vs browser-observed vs nonbrowser-observed)
+  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.
+
+---
+
+## 7. Ethics & redaction (non-negotiable — binds EVERY dimension)
+
+Carried from the source playbook (`setup.md` §6). Violating them voids the work.
+
+1. **Never enter credentials.** The user signs into any logged-in surface beforehand.
+2. **Storage: shape, not values.** No raw cookies/tokens/JWT-signatures. Decode JWT *structure* with identity claims (`sub`,`email`,`phone`,`user_id`,`uid`,`sid`) redacted.
+3. **Never save secrets.** Before any `raw/` write, redact every credential-shaped field → `<REDACTED:...>` + log in `_meta.redactions`. Field patterns: `api_key`,`*_secret`,`client_secret`,`webhook_secret`,`signing_*`,`password`,`private_key`,`access_token`/`refresh_token` in bodies, vendor-named secrets. Value patterns: `sk_live_…`/`pk_live_…` (Stripe), `sk-…` (OpenAI), `xox[bp]-…` (Slack), `AKIA…` (AWS), `gh[ps]_…` (GitHub), `AIza…` (Google), `eyJ…` (JWT), opaque base64 ≥32 chars in a credential field. Over-redact when unsure.
+4. **Confirm before state changes** — anything that creates state, costs money, or is visible to others (even a draft toggle). State the exact action + estimated cost.
+5. **No destructive actions.** Document the absence; move on.
+6. **No bypassing safety harnesses** — redact, never evade.
+7. **No exfiltration.** Captures stay local under `research/<target>/`.
+8. **Respect TOS & robots.** For spec-writing / integration / competitive analysis — not credential theft, rate-limit bypass, or scraping.
+
+### 7.1 wire-capture & active-interception ethics (the strictest tier)
+
+The `wire-capture` dimension climbs a **3-rung ladder, lowest privilege first**, and records the
+chosen rung in `_meta`:
+
+1. **Browser network tap (default, unauth).** Chrome `read_network_requests` + the in-page
+   fetch/XHR interceptor on the **public** surface only. Capture request/response *shapes*; redact
+   in the wrapper before disk. No login. → `method: wire-tap-browser`.
+2. **HAR export.** Export DevTools HAR of the unauth SPA's XHRs, digest to an endpoint catalog,
+   scrub `Authorization`/`Cookie`/secret-shaped values. → `method: wire-har`.
+3. **mitmproxy / intercepting proxy — GATED, opt-in, user-run.** ONLY first-party traffic the
+   **user owns** (their own desktop/mobile/CLI client), ONLY with explicit chat authorization, ONLY
+   TOS-checked. The harness NEVER stands up a proxy against a third party's infra unattended; the
+   *user* installs the CA and routes their client — the agent only ingests exported flows. →
+   `method: wire-mitmproxy`. Same explicit-authorization loop as session Pass-2.
+
+> Wireshark / packet capture is explicitly **not** used: for HTTPS it yields only TLS ciphertext,
+> and a packet sweep of a third party is the bright line this harness will not cross.
+
+### 7.2 distribution-artifacts ethics
+Downloading a public binary (CRX/`.asar`/`.ipa`/`.apk`) and reading its manifest/strings is fine.
+But binary **decompilation** can cross from "inspect" to "reverse-engineer in violation of EULA":
+the agent reads the artifact's own license/EULA first and records a restrictive one as an Open
+question rather than silently decompiling.
+
+---
+
+## 8. Completeness check
+A dump is complete when: `_summary.md` exists with full provenance frontmatter + honest `status`;
+every Finding is backed by a `raw/` artifact or inline value; `raw/` artifacts have `_meta` +
+decoding (large ones digested); redaction pass run; `gaps` recorded (never fabricated).
+
+---
+
+## 9. The session dimension — logged-in browser-session playbook
+
+The method for the **session** dimension: reverse-engineering the *authenticated runtime* of a
+product by driving it through a browser (Chrome MCP) and instrumenting it. It produces a
+section-by-section understanding of a product's wire protocol, auth, and state model **without
+source-code access**. The `session` agent follows this section.
+
+This is the deepest and most sensitive dimension. The ethics in §7 above bind hardest here.
+
+### 9.1 Prerequisites (verify before anything else — all three non-negotiable)
+
+| # | Precondition | How to verify |
+|---|--------------|---------------|
+| 1 | Target is **pre-logged-in** in Chrome | open the target URL in the connected tab → an authenticated surface (a dashboard, not a sign-in page). The agent never enters credentials. |
+| 2 | **Claude Chrome extension** installed | `mcp__claude-in-chrome__tabs_context_mcp` returns live tabs |
+| 3 | **Chrome CDP** connected | the same call returns stable tab IDs |
+
+If any fails, return `blocked` naming the missing precondition.
+
+### 9.2 The three-pass strategy
+
+A single linear sweep wastes context on things you can read for free and wastes credits on
+actions whose response shape you could infer. Use three passes.
+
+**Pass 1 — read-only mining (no money, no state change).** If the user already has data (a
+project, conversation, account, order), mine it first. Hit every list/state/history endpoint with
+the existing token; capture verbatim bodies. This yields ~70% of the spec for free. Mine, by role:
+identity (`/me`, `/account`, `/workspaces`), list (the canonical taxonomy), single-resource state
+(server-injected vs client-sent fields), history/event-log (a whole trajectory in one call),
+runtime/preview state, per-resource billing, account billing, feature flags/cohort, integration
+catalog (`/mcp/`, `/integrations/`), and schema/capabilities (`/openapi.json`, `/.well-known/*`,
+`/page-metadata`).
+
+**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.
+
+**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.
+
+### 9.3 The P0 → P6 phases
+
+The same phases apply whether the target is an AI builder, analytics dashboard, CRM, or collab tool:
+
+| Phase | Focus |
+|-------|-------|
+| **P0 Surface** | routes, bundles, storage shape, the API host(s), the auth tell |
+| **P1 Auth** | token type + issuer + storage location + refresh path; tenancy model |
+| **P2 Core action** | the primary write — the submit/create body and its server resolution |
+| **P3 Streaming** | the realtime transport (WS / SSE / WebChannel / Pusher / none) + event catalog |
+| **P4 Runtime/state** | sandbox/preview/build/deploy state; the live result surface |
+| **P5 Iteration** | the follow-up/edit endpoint (often surprisingly named) + any auto-iteration loop |
+| **P6 Synthesis** | reconcile into the dimension's `_summary.md` + `captures/` + `curls.md` |
+
+### 9.4 Runtime taps (Pass-1 instrumentation, run in-page)
+
+- **WebSocket / EventSource / fetch+XHR interceptors** — wrap the constructors/methods to log
+  URLs, frames, and bodies (shapes, not secrets — redact in the wrapper before anything reaches
+  disk). Add a `SCRUB(value)` step inside the fetch wrapper so credentials never reach the harness.
+- **Storage shape inspector** — enumerate localStorage / sessionStorage / cookies / IndexedDB
+  **key names + lengths**, never raw values.
+- **JWT decoder** — decode the token *structure* (alg, claim names, exp) with identity claims
+  (`sub`, `email`, `phone`, `user_id`, `uid`, `sid`) redacted.
+- If a Pusher/realtime SDK is loaded, bind a global listener to capture the event catalog.
+
+### 9.5 The capture contract (richer than a standard dimension dump)
+
+Under `research/<target>/dimensions/session/`:
+
+- **`captures/p*.md`** — per-phase narrative for the human: frontmatter (title, summary, scope,
+  status), **Method** (taps run, actions taken), **Findings** (concrete values — URLs, fields,
+  status codes), **Inferences**, **Diff vs reference**, **Open questions**. Decoded, opinionated;
+  don't paste raw bodies here.
+- **`raw/*.json`** — verbatim endpoint captures for the reproducer: a `_meta` header
+  (endpoint, auth-shape, captured_at, status, byte_length, redactions) + `body` (PII + secrets
+  redacted) + `_decoded_fields`. Digest bodies > 50 KB into a structured summary.
+- **`curls.md`** — reproducible curl per endpoint, the auth model documented, a variables block,
+  and an endpoint-catalog table.
+- **`_summary.md`** — the standard dimension bridge file (provenance frontmatter per §2) pointing
+  into the above, so Evaluation treats session like any other dimension. `method: session-playbook`,
+  `confidence: low` for Pass-1-only/inferred.
+
+### 9.6 Session ethics (binds hardest here — see §7 above)
+
+Never enter credentials; storage shape not values; redact every secret **inside the tap wrapper**
+before it reaches disk; **confirm before any Pass-2 state change or cost** (exact action + exact
+cost); no destructive actions; no bypassing the harness (redact, never evade); captures stay local;
+respect TOS. The provenance/redaction rules in §1–8 apply to everything written here.

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@nurix/etna",
-    "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.",
+    "version": "0.15.3",
+    "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": {
         "etna": "bin/etna.js"