@nurix/etna 0.19.41 → 0.19.43

package/data/harnesses/code/harness.json

@@ -1,11 +1,12 @@
 {
   "harness": "code",
   "name": "code",
-  "version": "3.5.8",
+  "version": "3.5.9",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "5dafd73481fb"
+  "seeds": [],
+  "digest": "b48a9de4fe22"
 }

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

@@ -27,7 +27,7 @@ Decide the mode once, up front, from the version marker — then run.
 2. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter (a semver).
    - **Absent** ⇒ the repo is unharnessed ⇒ **baseline mode** (reconcile from nothing), then audit.
    - **Behind on major** ⇒ **baseline mode** (reconcile across the gap), then audit.
-   - **Behind on minor/patch** ⇒ **probe before deciding.** Run the Step B2 detection pass read-only: if any old-shape artifact in the fold table is present, **or** any **scaffolded file** in the target tree is missing (`docs/README.md`, `docs/structure.md`, `docs/history/CHANGELOG.md`, `docs/history/backlog.md`, `docs/memory/index.md`), the shape *did* change ⇒ **baseline mode**. Only when the probe finds nothing ⇒ re-stamp the version (no reshape), then audit.
+   - **Behind on minor/patch** ⇒ **probe before deciding.** Run the Step B2 detection pass read-only: if any old-shape artifact in the fold table is present, **or** any **scaffolded file** in the target tree is missing (`docs/README.md`, `docs/structure.md`, `docs/history/CHANGELOG.md`, `docs/history/backlog.md`, `docs/memory/main.md`), the shape *did* change ⇒ **baseline mode**. Only when the probe finds nothing ⇒ re-stamp the version (no reshape), then audit.
 
    > **Never probe on a missing folder.** Git does not track empty directories, so an unused folder is absent on every clone — reading that as drift puts the repo in baseline mode *forever* and contradicts this agent's own idempotency guarantee. Only the five scaffolded files above are shape signals; every folder in the target tree is created on first use.
    - **Equal to installed** ⇒ **audit only** (the default spine).
@@ -148,7 +148,7 @@ docs/
 │   ├── research/          # Deep-research records ({topic}/ — README.md synthesis + findings.md + sources.md); frozen, cited, owns no code
 │   └── backlog.md       ✱ # Tracked work items by priority (P0-P3)
 ├── memory/
-│   └── index.md         ✱ #   plus main.md, {agent}.md — project knowledge + per-agent strategy memory
+│   └── main.md          ✱ #   plus {agent}.md — project knowledge + per-agent strategy memory
 └── tests/                 # Behavioral test checklists ({feature}.md, step → **Assert**), derived at plan Completion via the `documentation` skill; author-maintained
 ```
 

package/data/harnesses/delivery/codex/agents/maintenance.toml

@@ -25,7 +25,7 @@ Decide the mode once, up front, from the version marker — then run.
 2. Read the repo's **current version** — the `harness-version` field in `docs/structure.md` frontmatter (a semver).
    - **Absent** ⇒ the repo is unharnessed ⇒ **baseline mode** (reconcile from nothing), then audit.
    - **Behind on major** ⇒ **baseline mode** (reconcile across the gap), then audit.
-   - **Behind on minor/patch** ⇒ **probe before deciding.** Run the Step B2 detection pass read-only: if any old-shape artifact in the fold table is present, **or** any **scaffolded file** in the target tree is missing (`docs/README.md`, `docs/structure.md`, `docs/history/CHANGELOG.md`, `docs/history/backlog.md`, `docs/memory/index.md`), the shape *did* change ⇒ **baseline mode**. Only when the probe finds nothing ⇒ re-stamp the version (no reshape), then audit.
+   - **Behind on minor/patch** ⇒ **probe before deciding.** Run the Step B2 detection pass read-only: if any old-shape artifact in the fold table is present, **or** any **scaffolded file** in the target tree is missing (`docs/README.md`, `docs/structure.md`, `docs/history/CHANGELOG.md`, `docs/history/backlog.md`, `docs/memory/main.md`), the shape *did* change ⇒ **baseline mode**. Only when the probe finds nothing ⇒ re-stamp the version (no reshape), then audit.
 
    > **Never probe on a missing folder.** Git does not track empty directories, so an unused folder is absent on every clone — reading that as drift puts the repo in baseline mode *forever* and contradicts this agent's own idempotency guarantee. Only the five scaffolded files above are shape signals; every folder in the target tree is created on first use.
    - **Equal to installed** ⇒ **audit only** (the default spine).
@@ -146,7 +146,7 @@ docs/
 │   ├── research/          # Deep-research records ({topic}/ — README.md synthesis + findings.md + sources.md); frozen, cited, owns no code
 │   └── backlog.md       ✱ # Tracked work items by priority (P0-P3)
 ├── memory/
-│   └── index.md         ✱ #   plus main.md, {agent}.md — project knowledge + per-agent strategy memory
+│   └── main.md          ✱ #   plus {agent}.md — project knowledge + per-agent strategy memory
 └── tests/                 # Behavioral test checklists ({feature}.md, step → **Assert**), derived at plan Completion via the `documentation` skill; author-maintained
 ```
 

package/data/harnesses/delivery/harness.json

@@ -1,11 +1,12 @@
 {
   "harness": "delivery",
   "name": "delivery",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "6fb95b8c81d5"
+  "seeds": [],
+  "digest": "ee08c0d0162a"
 }

package/data/harnesses/discover/codex/agents/api.toml

@@ -30,4 +30,28 @@ You collect a target's documented machine interface into `research/<target>/dime
 A one-paragraph headline (the API surface in a sentence) + endpoint-family counts + the auth model. Flag overlap with the packages/docs dimensions (the published SDK often wraps this API) and especially any drift vs. the session dimension's _observed_ wire surface, for synthesis.
 
 **Discipline:** the spec is the load-bearing artifact — capture it accurately, digest if huge. Redact any embedded keys/example tokens. A disabled-introspection or undocumented API is a finding, recorded as an Open question, not a guess.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the served spec **exactly as served** (`openapi.json` / SDL / introspection result) saved with `curl -o` — never a re-typed table; plus each probed endpoint's raw response body.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/codebase.toml

@@ -40,4 +40,28 @@ Return a **per-unit work-list** as a compact table so the main session can dispa
 Plus a one-paragraph headline of what the codebase reveals. The main session will dispatch readers that each write `raw/<unit>.md` (install/exports/key-files/architecture for that unit).
 
 **Discipline:** breadth over depth; digest large trees; never read or write secrets (scan `.env*`, config, fixtures for credentials and redact before quoting). An empty/over-large area is an Open question, not a guess.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the resolved manifests (`package.json`, `pyproject.toml`, lockfile summaries) and the structure map — the clone in `source/<target>/` is itself the artifact.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/community.toml

@@ -28,4 +28,28 @@ You collect a target's living signal into `research/<target>/dimensions/communit
 A one-paragraph headline (where the product is heading + its biggest acknowledged gap) + the top 3–5 themes. This feeds the competitive-positioning and product-features rollups.
 
 **Discipline:** themes over threads; cite representative examples, don't dump feeds. Respect rate limits and TOS. Mark anything paywalled/private as an Open question.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the changelog / issue / release payloads **as fetched** — JSON wherever an API exists (GitHub API, RSS, Featurebase/Canny), not only a themed digest.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/deployed-client-bundle.toml

@@ -50,4 +50,28 @@ Then Method / Findings (framework, build tool, route count, endpoint count — t
 Return a one-paragraph headline of what the deployed shell reveals — framework + build tool, route count, the shape of the API surface it calls, whether source maps were shipped (and the confidence that implies). **Cross-checks:** flag that `dimensions/_shared/api-path-catalog.md` and `dimensions/_shared/feature-flags.md` are the SHARED seam artifacts (§6, one physical file each) — `session`/`wire`/`distribution` append to the same files with `source: session | wire | distribution`, and evaluation owns the adaptive static-vs-observed diff. Surface any endpoint or flag that looks authed/internal but is statically declared in the unauth bundle — that gap is the dimension's highest-value output.
 
 **Discipline:** breadth over depth; digest large chunks, never paste them; check for a source map before string-mining (it upgrades confidence); REDACT every env value before any `raw/` write and log it in `_meta.redactions`; obey the seam rule — one canonical shared catalog name, never a private fork. An absent bundle, obfuscated route table, or missing source map is an Open question, not a guess.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the entry bundle itself (`curl -o raw/bundle.js`, gzip is fine) and any `.map` — the route table, API-path catalog and flag extracts are written **in addition**, never instead.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/distribution-artifacts.toml

@@ -55,4 +55,28 @@ Then write the per-type raw files that apply — `raw/{extension-manifest.md, el
 Return a **one-paragraph headline** of what the shipped client reveals — its declared hosts, permission surface, embedded vendor SDKs, and how much richer (or not) it is than the web app. The API paths and feature flags you appended feed the **seam rule (§6)**: your `dimensions/_shared/api-path-catalog.md` rows carry `source: distribution` so evaluation can run its adaptive diff against `deployed-client-bundle` (`source: bundle`), `session`, and `wire-capture`. The hosts and SDK list cross-check **infra-backend-fingerprint** (a host the binary calls that DNS/CT didn't surface is a finding); the runtime hosts also seed **wire-capture** targets (the binary says what it _might_ call; the capture says what it _does_).
 
 **Discipline:** EULA before extraction — restrictive license ⇒ Open question, never silent decompile. Manifests/strings only; no protected-logic reversing. Redact every embedded key before any `raw/` write (§7 rule 3). Digest large bundles (§5). A missing artifact type is a recorded gap, not a guess.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the manifests verbatim (`manifest.json`, `Info.plist`, `AndroidManifest.xml`) and the extracted file listing.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/docs.toml

@@ -32,5 +32,31 @@ You collect a target's docs into `research/<target>/dimensions/docs/`. Read `.cl
 
 A one-paragraph headline (the product's documented surface in a sentence) + the section list with page counts + anything that overlaps the api/packages dimensions (flag it so synthesis can cross-check).
 
-**Discipline:** distill, don't mirror. A 300-page docs site becomes a navigable map + the load-bearing content, not 300 verbatim files. Record paywalled/gated docs as Open questions.
+**Discipline:** distill **in addition to**, never instead of. Save each captured page's source form under `raw/pages/` (md or html, as fetched) — that is the evidence layer — and build the navigable map + load-bearing content as the narrative layer beside it (ingestion §5.1). A distilled section whose source page was never saved is unverifiable by the next run (§5.3).
+
+**Do not mirror the SITE:** A 300-page docs site becomes a navigable map + the load-bearing content, not 300 verbatim files. Record paywalled/gated docs as Open questions.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+each captured page's source form under `raw/pages/` (md or html, as fetched).
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/infra-backend-fingerprint.toml

@@ -61,4 +61,28 @@ Return a **one-paragraph headline** of the reconstructed backend — origin clou
 **Discipline:** read-only public recon — never scan, brute-force, or hit a non-public host; respect crt.sh/WHOIS rate limits and back off; redact any credential-shaped value before writing (contract §7 rule 3 — DSNs, verification tokens, embedded keys surfaced in headers/TXT). An unresolvable host or a missing sub-processor page is an Open question, not a guess.
 
 **Verify an absence before asserting it (contract §7 rule 10).** Before reporting any host as **NXDOMAIN / absent** — especially `api.<target>` or any host a sibling dimension (bundle / session / wire) reports actually hitting — re-resolve via a **second resolver** (`dig @1.1.1.1 <host>`, `dig @8.8.8.8 <host>`) **and** a direct `curl -sI https://<host>`. An HTTP 4xx/5xx response means the host **resolves** → report it **present**, not absent. A single negative resolver result is recorded as _tentative_, never stated as fact and never used to instruct sibling dimensions. Likewise, an _inferred_ backend engine (e.g. "looks like Hasura/Supabase from the CNAME") is phrased as an inference and yields to a runtime-observing dimension (`session`/`deployed-client-bundle`) that names the engine directly.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the raw `dig`, `crt.sh` and HTTP header responses as returned; the decoded table is the narrative layer beside them.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/packages.toml

@@ -27,4 +27,28 @@ You collect a target's installable artifacts into `research/<target>/dimensions/
 A one-paragraph headline (the package family in a sentence) + the package table + which packages are the core public API (so synthesis can anchor the SDK surface). Flag overlap with the docs api-reference and the codebase dimensions for cross-check.
 
 **Discipline:** the exports map + type defs are the load-bearing artifact — prioritize them over download-count trivia. Digest huge `.d.ts` to signatures. Redact any registry tokens.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+per package: the registry metadata JSON (`npm view <pkg> --json > raw/<pkg>.registry.json`, PyPI `/pypi/<pkg>/json`) and the `.d.ts` / exports surface as fetched.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/session.toml

@@ -38,4 +38,44 @@ Under `research/<target>/dimensions/session/`:
 A one-paragraph headline (the auth model + transport + the single most load-bearing wire finding) + the phase coverage + which passes ran. Flag drift between the _observed_ wire surface and the _published_ api/packages surface — that drift is the highest-value synthesis input. If Pass 2 was needed but not authorized, list the open write-side questions; never fabricate request bodies.
 
 **Discipline:** ethics first, always. Redact before writing. Confirm before any state change. No destructive actions. No exfiltration. A gap is an Open question, never a guess.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+≥3 verbatim envelopes as `raw/*.json` — the identity read, one canonical list read, and the primary write (request + response) — per ingestion §8.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
+
+## Visual capture (ingestion §5.5) — screenshot generously
+
+You drive a real browser, so you carry the visual-evidence obligation. **Capture continuously, not
+one-image-per-surface:** every surface, plus every materially different state within it — empty vs
+populated, modal/drawer open, dropdown expanded, error and validation states, permission/plan walls,
+loading/in-flight, and the before/after pair around any authorized state change.
+
+This is **not** scored — `screenshot_coverage` is a narrow Mode-5 floor. The beneficiary is the human
+reading this corpus weeks later for a purpose nobody anticipated. The product's past state is the one thing
+a later run genuinely cannot reproduce.
+
+**Redact in the DOM before the shutter** (`tradecraft.md` §1c) — a leaked pixel is undetectable afterwards.
+**Check the corners of the frame**, not just the content: support-chat widgets, toasts, presence avatars and
+member lists routinely carry *another human's* name and message. Then look at the saved image, and record
+`redacted: <what>` in `screens/_index.md` rather than a blanket zero-PII claim.
 '''

package/data/harnesses/discover/codex/agents/website.toml

@@ -33,4 +33,28 @@ You collect a target's public-facing site into `research/<target>/dimensions/web
 A one-paragraph headline (the positioning in a sentence) + the pricing tiers + the headline feature claims. Flag claims that should be cross-checked against the codebase/docs (marketing often over-claims) so synthesis can reconcile.
 
 **Discipline:** quote positioning verbatim; capture pricing precisely (numbers + limits); separate _claims_ from verified capability — the reconciliation happens in synthesis. Respect robots.txt and rate limits; this is read-only public crawling, not scraping at scale.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the raw HTML or extracted text per captured page, and the pricing table as structured data.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
 '''

package/data/harnesses/discover/codex/agents/wire-capture.toml

@@ -42,4 +42,44 @@ Then the captures + raw artifacts (per `discovery` Part C (wire-capture)):
 Return a **one-paragraph headline** of what the wire reveals — the real hosts contacted, the envelope/auth scheme, and the rung used (so the reader knows how much to trust it). Then a compact table of observed endpoints. **Flag the seam rule (§6):** every `api-path-catalog.md` row is `source: wire`, so evaluation can diff _actually-called_ (wire) against _statically-declared_ (`bundle` / `distribution-artifacts`) and _browser-observed_ (`session`) — a host or path the binary declares but the wire never hits is a finding, not noise; the inverse (called but undeclared) is a stronger one. If only rung 1 was authorized, say so and name what rungs 2/3 would unlock so the main session can request authorization.
 
 **Discipline:** lowest privilege first; never self-escalate the ladder; never install a CA or tap third-party traffic; never run Wireshark; redact every body before disk and log it in `_meta`. An unauthorized higher rung is an Open question, not an excuse to guess what the wire would show.
+
+---
+
+## Dump manifest (ingestion §5.3–5.4) — evidence before narrative
+
+**MUST land in `raw/` as verbatim, redacted files before this dimension may be `status: complete`:**
+the flow log itself (HAR or the tap's JSON export), not only the decoded narrative.
+
+Three rules bind this, and they override any instinct to summarise:
+
+1. **If you cite it, dump it (§5.3).** Every value that reaches your `_summary.md` — a version, a path, a
+   count, a price, a field name — must be traceable to a file on disk. **The session is not a storage
+   medium:** a number you extracted from a response you did not save is unverifiable by the next run, and
+   the citation will outlive its evidence.
+2. **Digest IN ADDITION, never INSTEAD (§5.1).** `raw/` is the evidence layer and may be unreadable;
+   `_summary.md` is the narrative layer. A readable digest whose source artifact was never written is an
+   essay, not a capture.
+3. **Size is a routing problem (§5.2).** Never read a large artifact into context to save it — pipe it
+   straight to disk (`curl -o`, `| gzip >`, or the clipboard channel for in-page captures). If you must
+   bound an unbounded source, record the bound in `_meta.sampling`. Context budget is never a reason to
+   discard evidence.
+
+**Self-check before returning:** count the verbatim files in `raw/`. Zero ⇒ the dimension is `partial`,
+regardless of how good the prose is.
+
+## Visual capture (ingestion §5.5) — screenshot generously
+
+You drive a real browser, so you carry the visual-evidence obligation. **Capture continuously, not
+one-image-per-surface:** every surface, plus every materially different state within it — empty vs
+populated, modal/drawer open, dropdown expanded, error and validation states, permission/plan walls,
+loading/in-flight, and the before/after pair around any authorized state change.
+
+This is **not** scored — `screenshot_coverage` is a narrow Mode-5 floor. The beneficiary is the human
+reading this corpus weeks later for a purpose nobody anticipated. The product's past state is the one thing
+a later run genuinely cannot reproduce.
+
+**Redact in the DOM before the shutter** (`tradecraft.md` §1c) — a leaked pixel is undetectable afterwards.
+**Check the corners of the frame**, not just the content: support-chat widgets, toasts, presence avatars and
+member lists routinely carry *another human's* name and message. Then look at the saved image, and record
+`redacted: <what>` in `screens/_index.md` rather than a blanket zero-PII claim.
 '''

package/data/harnesses/discover/harness.json

@@ -1,11 +1,12 @@
 {
   "harness": "discover",
   "name": "discover",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "files": [
     ".prettierignore",
     ".prettierrc.json",
     ".vscode/settings.json"
   ],
-  "digest": "3272a670df3c"
+  "seeds": [],
+  "digest": "4ab9f67f0d67"
 }