@nurix/etna 0.19.42 → 0.19.43

package/bin/etna.js

@@ -488,6 +488,20 @@ async function installHarness(harnessName, harnesses) {
         installed.push(`${rel} → ./${rel}`);
     }
 
+    // Seed files listed in harness.json's `seeds` (e.g. a pre-baked docs/ scaffold). Same
+    // project-root landing as `files`, opposite ownership: a seed is written only when its
+    // path is absent. Once present it is the project's living copy — a refresh never
+    // overwrites it and never prunes it.
+    for (const rel of harnessMeta.seeds || []) {
+        const src = join(bundledHarnessDir, rel);
+        if (!existsSync(src)) continue;
+        const dest = join(targetDir, rel);
+        if (existsSync(dest)) continue;
+        mkdirSync(dirname(dest), { recursive: true });
+        cpSync(src, dest, { recursive: true });
+        installed.push(`${rel} → ./${rel} (seeded)`);
+    }
+
     // Retire hooks earlier harness versions shipped before merging, so the additive merge
     // never resurrects an entry pointing at a script this bundle no longer carries.
     for (const r of retireOldHooks(targetDir)) notices.push(`removed ${r}`);

package/data/harness-index.json

@@ -1,6 +1,10 @@
 {
-    "fingerprint": "e47ee7aac58b",
+    "fingerprint": "4d6e06e37895",
     "harnesses": {
+        "apollo": {
+            "plugin": "apollo",
+            "description": "the pre-baked `code` harness, built for Apollo Studio exports"
+        },
         "code": {
             "plugin": "code",
             "description": "the foundation every Nurix project starts with"

package/data/harnesses/apollo/.prettierignore

@@ -0,0 +1,29 @@
+# Dependencies & build output
+node_modules
+dist
+build
+
+# Lockfiles
+pnpm-lock.yaml
+package-lock.json
+yarn.lock
+
+# Harness-managed — the installer overwrites all of these, so formatting them is churn
+# that comes straight back on the next `npx @nurix/etna`.
+.claude
+.codex
+.agents
+CLAUDE.md
+AGENTS.md
+
+# Frozen records — a plan, changelog entry, or migration runbook is a point-in-time
+# artifact that is never edited after it freezes. Reformatting one is an edit, and the
+# `maintenance` agent is forbidden from making it — so a format gate over this tree is
+# a demand nothing in the repo is allowed to satisfy.
+docs/history
+
+# Source catalogs — authored markdown; prettier collapses template/example blocks
+skills
+rules
+agents
+harness

package/data/harnesses/apollo/.prettierrc.json

@@ -0,0 +1,3 @@
+{
+  "proseWrap": "never"
+}

package/data/harnesses/apollo/.vscode/settings.json

@@ -0,0 +1,19 @@
+{
+  // Markdown: Prettier unwraps prose to one logical line per paragraph
+  // (see .prettierrc → proseWrap:never) on save; the editor soft-wraps for
+  // reading, so no hard line breaks get baked into the source.
+  "[markdown]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode",
+    "editor.formatOnSave": true,
+    "editor.wordWrap": "on"
+  },
+  // Hide harness-authoring scaffolding from the file explorer
+  "files.exclude": {
+    ".claude": true,
+    ".vscode": true,
+    ".agents": true,
+    ".codex": true,
+    "**/node_modules": true,
+    "**/apollo.service.json": true
+  }
+}

package/data/harnesses/apollo/CLAUDE.md

@@ -0,0 +1,162 @@
+# Agent Instructions
+
+How AI coding agents — any vendor, any runtime — work on this project. Rules are runtime-neutral: a rule that depends on a capability (sub-agent dispatch, browser tools, context injection, slash commands) applies only if the runtime has it, and states its fallback. Rules marked **[override]** deliberately replace a runtime default — in a conflict, the rule here wins.
+
+---
+
+## Maintenance
+
+**Baseline first**: if `docs/structure.md` lacks a `harness-version` frontmatter marker, or it is behind the `version` in `.claude/harness.json`, invoke the `maintenance` agent before taking up the user's first ask — tell the user, let the agent run, then proceed.
+
+Invoke the `maintenance` agent whenever the docs look like they need it — not just at first setup: a missing `docs/structure.md` (the repo isn't reconciled — baseline before applying anything below), a `harness-version` marker behind the installed version, docs contradicting code, unowned source paths, or drift noticed while working. Never reconcile these by hand — the agent auto-selects its mode (baseline when the marker is missing or behind, coherence audit otherwise) and hands back; if it returns a follow-up (typically the module proposal), re-invoke it to finish. Each component's internals live in the component, not here.
+
+---
+
+## Getting Started
+
+- Read **[`docs/structure.md`](docs/structure.md)** for the documentation map and folder authority (architecture, features, operations)
+- Read **[`docs/memory/`](docs/memory/)** for agent memory files (one per agent)
+- Prefer `docs/` over `README.md` — docs/ is canonical for agents; check the README only when docs/ lacks a setup detail
+- Check **[`package.json`](package.json)** for available scripts. Detect the package manager from the lockfile — see `.claude/rules/general.md`; don't hardcode one.
+
+---
+
+## Workflows
+
+Three peer modes, then a verification gate and a Completion step — enter wherever the user's thinking already is. Each mode is implemented by an agent + skill; the behavioural detail lives in those files, not here.
+
+| Mode | Enter when | Implemented by | Exits to |
+| --- | --- | --- | --- |
+| **Brainstorming** | explicit ask (`/brainstorm start`); or offer a session — never auto-enter — when the user brings a large piece of work (name what makes it big) or an utterance contradicts a recorded pillar (name the principle) | `brainstorm` agent + skill | LLD, Plan, or close + harvest |
+| **LLD** (low-level design) | new feature work | `lld-mode` agent + `documentation` skill | Plan |
+| **Plan** | an LLD is approved | `documentation` skill → `docs/history/plans/YYYY-MM-DD-{slug}.md` | Verification gate → Completion |
+
+> Brainstorm entry needs a **basis** — a reference document or a one-shot brain dump; drip-sized asks (a bug fix, one button) are too small and get redirected. A **pillar** is a recorded strategic principle from a past brainstorm: in-progress sessions live under `docs/research/`, harvested ones under `docs/history/brainstorms/`, harvested doctrine under `docs/architecture/`. The LLD is the feature doc itself — `docs/features/{feature}.md`, design intent first, extended in place at Completion.
+
+**On Plan Completion:**
+
+1. **The verification gate passes first** — user-triggered: when implementation completes, report it and offer the gate; never run it unbidden. It requires the plan's Test Obligations ledger to exist (proof the plan gates ran) and discharges every row, driving the real surface before pinning tests — `.claude/rules/verification.md`. A plan with outstanding obligations stays open, whatever the code does.
+2. Freeze the plan — `Status: Complete`, fill the Completed date. The file is now frozen.
+3. Flip the feature LLD to `status: active`; extend it in place with the how-it-works sections; confirm its `owns:` globs against the actual code.
+4. Record the gate's results in the changelog entry, and confirm every section of `docs/tests/{feature}.md` carries its `Pinned:` trace — the checklist itself is authored at the gate (step 1), not written up afterwards.
+
+**On Brainstorm Close** (when a session ends, not when a plan completes): close + harvest is the skill's `stop` procedure — converge, a user-approved harvest manifest, apply, then a uselessness test; conclusions disperse by scope (architecture docs, decision records, backlog), the record moves from `docs/research/{topic}-brainstorm/` to `docs/history/brainstorms/{topic}/`, and the user decides whether the moved folder is deleted or committed.
+
+---
+
+## Ownership, Boundaries, Verification & Documentation
+
+These four mechanisms work in tandem to keep the repo self-updating and to prevent half-finished changes: **ownership** routes an edit to the canonical doc before the code is touched, the **boundary** check reads both sides of every contract a change participates in so one side never ships alone, **verification** proves the change works in the product before it is called done, and **documentation** updates close the loop so the next session inherits the truth. Skipping any leg breaks the others.
+
+### Ownership — route before editing
+
+Which doc is canonical for which code paths is the **feature doc's own frontmatter**. A feature doc (flat in `docs/features/`) carries `owns:` (code-path globs — the only ownership key), `module:` (a bounded-context label, omitted when cross-cutting), `keywords:` (discovery), and `status:`. Code → doc ownership is the union of every feature doc's `owns:` globs, surfaced as the generated ownership index at session start. A module is tied to code by the `owns:` globs of the docs carrying its `module:` label — not a folder, not a separate map. Architecture docs describe cross-cutting patterns and own no files; operations docs describe procedures.
+
+Before modifying code in an unfamiliar area:
+
+1. Consult the **injected ownership index** (`glob → doc · module · keywords · status`). Match the path or topic to the owning feature doc and read it before changes. (No index in context ⇒ either the repo isn't reconciled — see Maintenance — or the runtime doesn't inject it — see Runtime Notes.)
+2. If a `docs/memory/` file exists for the domain, read it for domain knowledge and failure modes.
+
+The `lld-mode` agent checks for ownership conflicts during LLD research — feature docs whose `owns:` globs overlap at equal specificity. Resolve them in the LLD before proceeding.
+
+### Boundaries — check while changing
+
+Boundaries are **diagnosed, not documented** — the `boundary` skill derives them fresh from source on every run (the definition and mechanism catalog live in the skill), so nothing is persisted that could go stale.
+
+**Invoke the `boundary` skill after a plan is approved and before its first implementation step.** It parses the plan's Proposed Changes, reads the touched source, traces the consumers on the other side, and reports severity-ranked violations with suggested amendments and a pass/block verdict — in chat, read-only. Fold the amendments into the plan before coding. For non-plan edits in contract-heavy code (db schema, wire envelopes, auth, events, env/config), run the same diagnostic scoped to the diff.
+
+### Test obligations — specify before implementing
+
+**After `boundary` passes and its amendments are folded, invoke the `test-plan` skill** — same plan gate, ordered second. It derives the tests the plan owes from its Proposed Changes and the owning LLD, and writes the **Test Obligations** ledger into the plan (one row per promised behavior: layer · target file · oracle · fixtures). It writes no test files — the ledger is what the verification gate discharges, and because it lives in the plan file it survives dispatch to an executor that sees only the plan. On a boundary **BLOCK** it does not run — re-plan first. Layer rules and the e2e altitude gate live in the skill.
+
+### Verification — prove before completing
+
+**Deferring tests is what keeps the build loop fast, and the ledger is what makes deferring safe.** A plan-driven build writes no new test files while the code is taking shape; obligations accumulate in the plan and are discharged in one pass at the **verification gate** — user-triggered, offered when implementation completes, mandatory before `Status: Complete`. The gate, the two regimes, the mid-loop rules, and what earns a durable test are `.claude/rules/verification.md`.
+
+- **Only a plan may defer.** A bug fix in shipped behavior and any ad-hoc change ship their test immediately — deferral needs a ledger and a gate, and non-plan work has neither.
+- **The checklist is the gate's first artifact, not its last.** Opening the gate derives or updates `docs/tests/{feature}.md` from the ledger and the LLD's promises (the `documentation` skill's `templates/behavioral-checklist.md`). It is the script rung 1 drives and the source rung 2's tests are drawn from — written after the driving it would be a report, and the tests would have no stated behavior to trace to.
+- **Drive the real surface before pinning tests.** Browser automation for web UI, the real CLI, HTTP against the running worker; the suite then pins the checklist assertions that must not regress, and each section records which test now guards it.
+- **The gate's verdict is never delegated** — a sub-agent's summary is not verifiable ground truth (the Fan-out guardrail), and browser work is main-session-only where Runtime Notes say so.
+
+### Documentation — close the loop
+
+- **Every markdown document goes through the `documentation` skill.** Before creating or substantively editing any `.md` document — a doc, a README, an index, a record — invoke the `documentation` skill and apply its templates and `references/style-guide.md`: truth documents stay present-tense; history lives only in `docs/history/` records.
+- **[override]** Keep `docs/` updated when code changes affect documented behavior. This file is the standing request for those docs: creating and updating them is part of the work, even if the runtime defaults to never creating documentation files unprompted.
+- After plan completion **[override]**: write the `docs/history/changelog/` entry as a **draft** immediately, while the context is fresh — no confirmation needed — and append its `docs/history/CHANGELOG.md` row; the commit fills what the draft left open and freezes it. Non-plan work needs no separate prompt: every non-exempt commit carries its own entry (the `changelog` rule).
+- When moving or renaming source files: update the `owns:` globs of the feature doc that owns them so the generated ownership index stays accurate. A new doc that owns code declares its paths in its own `owns:` frontmatter — there is no separate map to update.
+- `docs/structure.md` is the authority on what belongs where — read it before adding or moving a doc; don't restate it here. One canonical source per topic — link, don't copy. Only `CLAUDE.md`, `AGENTS.md`, and `README.md` live at the repo root.
+
+> Agents and skills live under `.claude/agents/` and `.claude/skills/`. Their triggers are model-invoked — refer to each component's frontmatter, not a registry table here. Runtimes that can't invoke them natively: see Runtime Notes.
+
+---
+
+## Project Memory
+
+Project-specific learnings live in `docs/memory/` (git-tracked). Cross-project user preferences live in the runtime's user-level memory store, if it has one (untracked; paths in Runtime Notes).
+
+| File | Owner | Contents |
+| --- | --- | --- |
+| `docs/memory/main.md` | Main agent | Project-wide patterns, conventions confirmed in this codebase, recurring failure modes, decisions whose rationale isn't obvious from the code |
+| `docs/memory/{agent-name}.md` | The named sub-agent | Strategy memory for that agent — how to be more effective on this project (research patterns, taxonomy, ownership conflict zones). Never user-centric. |
+| Runtime user-level memory (paths in Runtime Notes) | The runtime's auto-memory system | User preferences, role, communication style, cross-project habits |
+
+When recording a learning, ask: _is this true of this project, or true of this user?_ Project facts → `docs/memory/` (overriding any auto-memory default location); user facts → the runtime's user-level store. `docs/memory/main.md` is created on first write; append entries dated `## YYYY-MM-DD — {topic}`.
+
+---
+
+## Changelog
+
+The working session is the last holder of the refinement context that produced a change — asks, iterations, rejections, skill outcomes, discoveries. The changelog captures it; the `retro` agent distills it on demand. A commit marks the user's acceptance of the work it carries — for plan work, behavioral verification is the gate's job, and a mid-plan commit is a checkpoint (the `verification` rule). The `changelog` rule carries the trigger and the lifecycle; this is the policy:
+
+- **Every non-mechanical commit is covered by an entry** at `docs/history/changelog/YYYY-MM-DD-{three-words}.md`, staged inside the commit it describes — whatever tool or session performs the commit — plus a row in `docs/history/CHANGELOG.md`. Format, required fields, and the closed exemption list are the `documentation` skill's `templates/changelog-entry.md`; the failure fields (rejected attempts, overridden skill output) and verbatim taste quotes are required, not optional — the entry's value concentrates there.
+- **An entry may exist before its commit.** A plan reaching `Status: Complete` writes its entry as a **draft** immediately, while the context is fresh; the commit fills what the draft left open. **Immutability begins at commit, not creation** — a draft is mutable, a committed entry never is, and a correction is a new entry that links back. Doc-health passes skip the genre.
+- **A commit is the smallest unit an entry may describe**; above that the mapping is judgment. Work exceeding a draft's scope gets a *second* entry rather than stretching the first.
+- **Distillation is the `retro` agent** — run on demand (before a brainstorm or LLD, before a new project, after a refinement arc), it converts accumulated entries into a typed punch list (doc content, doc structure, skill evolution, pins, harness rules), appends actionable items to the backlog, and proposes only — application runs through the normal documentation loop.
+
+**One-shot migrations are a different genre.** Work that runs **once** against a live system — a data backfill, a schema cutover, a dependency or harness upgrade rolled across repos — is a **migration runbook** at `docs/history/migrations/YYYY-MM-DD-{slug}.md` (template: the `documentation` skill's `templates/migration-runbook.md`), authored **before** execution and outcome-stamped after. A changelog entry says what changed in the repo; a runbook says what was executed against the world and how to verify or undo it. A repeatable procedure is neither — that is `docs/operations/`. When a runbook defers targets, it records **why** and the **trigger to re-evaluate them**, so the next run re-checks rather than inheriting the skip.
+
+---
+
+## Out-of-Scope Discovery
+
+When a plan's implementation surfaces work that is important but outside the plan's scope and is not being done now (a pre-existing bug being fixed on the spot is the bug-fix regime — the `verification` rule — not a backlog item):
+
+- Append it to `docs/history/backlog.md` under the appropriate priority (P0-P3)
+- Format: `- **[P1]** Description — discovered by [plan-name or agent-name]`
+- Do NOT ask permission. Just append and mention it in the reply.
+
+---
+
+## Guardrails & Defaults
+
+Defaults — ❌ prohibitions hold unless the user explicitly asks otherwise; ✅ and ⚠️ items are standing policy:
+
+- ✅ **Verification — batched at a gate, not continuous.** A plan-driven build loop ships code without new test files; the tests and the driven checks land together at the **verification gate** — user-triggered, offered when implementation completes, mandatory before a plan reaches `Status: Complete`. The gate, the regimes, and the mechanism ladder are `.claude/rules/verification.md`; framework, test-tree placement, and shared fixtures are `.claude/rules/testing.md` — the repo's existing runner and layout always win.
+  - **Only a plan defers**: a bug fix in shipped behavior and any ad-hoc change ship their test immediately — a regression test that fails before the change and passes after.
+  - **Drive before pinning**: prove the change in the real product first — browser automation for web UI, the real CLI, HTTP against the running worker — then pin as suite tests only the behaviors that must not regress.
+  - **Discipline**: run the affected part of the suite at the gate and report results honestly. Never weaken, skip, or delete a test to mask an unexplained failure — when a plan or LLD intentionally changes behavior, updating the affected tests to the new contract is part of the change.
+  - **Throwaway checks are not tests**: temporary verification scripts go to scratch space and are deleted, never committed into the test tree.
+- ❌ **Dependencies** – Never upgrade frameworks, libraries, or dependencies.
+- ❌ **Compatibility** – Never maintain backward compatibility unless specified.
+- ❌ **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** – Before editing, if `docs/operations/protected-files.md` exists, read it and never modify any path it lists; also never modify `AGENTS.md` or the `protected-files.md` file 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.
+- ✅ **Fan-out is a tool, not a default** — the main session does the work and its own reasoning; a delegated result comes back as a summary, not verifiable ground truth. Delegate **only when** the work is large, independent, or repetitive enough that a self-contained hand-off (the sub-agent sees none of the conversation) costs less than the work — broad research, wide sweeps, audits — and run independent delegations in parallel. **Never delegate judgment by reflex**: a second opinion is for a high-stakes call or an explicit request. No dispatch mechanism ⇒ inline.
+- ⚠️ **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 `verification` rule). If scope changes after completion, write a new dated plan that links back to the old one.
+- ⚠️ **Tool Issues** – If any CLI tool, shell alias, or MCP tool behaves unexpectedly (syntax errors, silent failures, wrong defaults), report the exact tool name, command, and error to the user so they can fix or remove the underlying library.
+
+---
+
+## File Structure
+
+- Add a file-path header comment at the top of each source file, in the file's native comment syntax — `// src/modules/example.js - Module for handling user authentication`. Place it below any shebang line; skip formats with no comment syntax (JSON, lockfiles) and generated files.
+- Add a 1-line description above each function whose purpose isn't fully evident from its name and signature: `// Extract JWT token from request based on endpoint type`. A comment that restates the name is noise. No inline comments that restate obvious code; no commented-out code — if a block needs a comment to be understandable, refactor for clarity instead.
+
+---
+
+## Runtime Notes
+
+Everything above is runtime-neutral. This section is the only place runtime- or vendor-specific facts may live; re-audit it whenever a runtime ships new models or tools. Lint: nothing outside this section may name a model, a vendor product, or a runtime-built-in tool — exempt are repo-relative `.claude/**` component paths (shipped in this repo, readable by any runtime) and protocol names (e.g. MCP).
+
+- **Claude Code**: sub-agent dispatch is the Agent tool; sub-agents can run skills and spawn their own sub-agents (probe-verified; re-verify on runtime updates), but cannot reliably hold the browser connection (the "can't hold the browser connection" condition the Browser Automation guardrail refers to) — browser work is Chrome CDP ("Claude in Chrome"), main session only. The user-level memory store is `~/.claude/` (auto-memory under `~/.claude/projects/...`). The ownership index and skill/agent descriptions are injected at session start; skills are invoked as slash commands (e.g. `/brainstorm start`). Dispatch tiers: mechanical fan-out runs on the cheapest capable tier; a user-requested second opinion takes the strongest — pick by capability at dispatch, since model names go stale.
+- **Runtimes without native component support** (AGENTS.md readers, etc.): read `.claude/agents/<name>.md` and each skill's `.claude/skills/<name>/SKILL.md` (plus its `references/`) and follow them inline; derive the ownership index by scanning `docs/features/` frontmatter.

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

@@ -0,0 +1,144 @@
+---
+name: brainstorm
+description: The brainstorm twin — the paper-owning half of the brainstorm capability. Dispatched at session gates (start, on demand, pause, stop) by the `brainstorm` skill, never self-triggered and never conversing with the user. Scribe (distills the ops capture ledger into the working surface), editor (recomposes the thesis whole, diffs surfaced), harvester (drives the stop pipeline — manifest, apply, uselessness test, move), blindspot analyst (cold-reads the surface for unknown unknowns behind a four-test quality gate — grounded, material, new, answerable). Consumes the detector script for mechanical integrity and audits the five semantic sources the detector cannot judge. Writes every working-surface file; the facilitator writes only ops/capture.md and sync-log dispatch lines.
+tools: Read, Glob, Grep, Write, Edit, Bash, Task, Skill
+model: opus
+---
+
+# Brainstorm Twin
+
+You own the **paper** of a brainstorm session; the facilitator (the main loop running the
+`brainstorm` skill) owns the conversation. You are dispatched at gates with a session-folder path,
+a gate name, and a scope. You never talk to the user — anything needing their judgment goes back
+in your final report for the facilitator to relay.
+
+The format contract is the skill's `references/session-schema.md` (resolve it beside this harness:
+`.claude/skills/brainstorm/references/` in a consumer repo, `skills/brainstorm/references/` in
+etna; also read `references/doctrine.md` for the epistemics). The mechanical half is the detector:
+
+```
+node <skill>/scripts/detector.mjs <session-folder> [--gate=manifest|move] [--json]
+```
+
+Run it at the start of every dispatch and again before you return. If node or the script is
+unavailable, say so loudly in your report and run the checks by hand from the schema — a missing
+detector is a flagged fact, never a silent skip.
+
+## The write protocol you enforce
+
+One writer per file. You write `state.md`, `thesis.md`, `forks.md`, `ledger.md`, `fragments/`,
+manifest, and your own sync-log **result** lines. You never write `ops/capture.md` (the
+facilitator's) or sync-log dispatch lines. The user may hand-edit anything: before rewriting any
+file, read its current state in full and treat content you did not write as **first-class user
+signal — fold it forward, never clobber it**. A hand-edit that contradicts the ledger is a design
+question: file a fork, don't "fix" the file.
+
+## Every dispatch, in order
+
+1. **Detector first** — `--gate=session`. Fix what is yours to fix (scribe-calls, below); report
+   what isn't.
+2. **Read the whole surface** plus every `ops/capture.md` entry since the last reconciled sync.
+3. **Scribe pass** — distill new capture into the surface, per the doctrine's epistemic rules
+   (distilled never verbatim; examples as examples; no naked pointers; both sides captured).
+   Residue that doesn't warrant filing stays in ops — that is what ops is for.
+4. **Semantic audit** — the five sources the detector cannot judge:
+   - **Cross-pillar contradiction** — across any two session files, `state.md` included (a state
+     file describing a session the pillars contradict is the historically strongest signal).
+   - **Aspect adequacy** — the detector checks that every mapped aspect *links* to content; you judge
+     whether the content actually covers it. Covered-in-name-only → a fork.
+   - **Basis drift** — decided divergence from `basis/` is fine; accidental divergence → a fork.
+   - **Tech conflicts** — anything violating the tech fragment (or the repo's `.claude/rules/`)
+     without a recorded deviation → a fork.
+   - **Self-containment** — read as the stranger you are (you were dispatched context-free; use
+     that): undefined terms, naked pointers, enumerations cited but never printed.
+5. **The scribe-call / design-call line** — an edit whose resolution doesn't change the design
+   (wording, bookkeeping, printing an enumeration, glossing a term) you apply directly and list.
+   An edit whose resolution changes the idea becomes a fork (`Raised by: twin (S#)` — cite your
+   own sync id). Never route a design question through a direct edit.
+6. **Editor pass** — recompose `thesis.md` whole (claim → argument → what changed), stamp
+   `Current as of:`, mirror the stamp into state.md `Last compose`, update the posture line.
+   Filing an insight must never push the session away from coherent: orphan evidence is a
+   scribe-note in your report, never a fork; free-floating insight may feed a thesis aspect.
+7. **Close the log** — append your result line to `ops/sync-log.md`:
+   `S# → reconciled | <ISO datetime> | N edits · M new forks · K open · untouched: <aspects>`
+   (or `S# → failed | <ts> | <reason>` — never omit the line; an unlogged dispatch reads as a
+   fabricated one). The one-line report is also the last line of your reply, plus anything the
+   facilitator must relay (design questions raised, what the recompose changed). When several
+   audit sources fire at once, rank integrity findings (attribution without evidence, files
+   contradicting the state) above coverage and staleness — a record that lies about its own
+   process is worse than one that merely stalled.
+
+## The blindspot pass (gate: on demand, scope: blindspot)
+
+Dispatched when the user asks what they're missing, when the facilitator self-initiates at a
+frame-settling moment (usually widening a reconcile dispatch's scope), or on the accepted
+pre-converge offer. Run the standard dispatch order first so the surface is current, then
+re-read the whole surface plus `basis/` cold, measured against the thesis's claim — the stated goal — never against
+a generic checklist. The species that pay: an assumption the design rests on but never states; a
+concern no aspect owns; two required properties that pull against each other with nothing
+designing for either; a rule or path that can never fire; an ambiguity two files resolve
+differently; a shape matching a failure already recorded in the basis or ledger.
+
+**The quality gate — a candidate passes all four tests or dies unsurfaced.** The gate exists so
+the user never over-replies to noise:
+
+1. **Grounded** — it cites the specific surface or basis content that creates it. Raisable
+   against any project of this type without reading this folder → generic → dead.
+2. **Material** — some plausible answer changes the thesis, a commitment, or the aspect map.
+   Every answer leaves the design unchanged → dead.
+3. **New** — not a restatement of an open fork, a ledger decision or Declined line, or an
+   explicit park.
+4. **Answerable** — resolvable by a decision or a named investigation, not "think harder
+   about X".
+
+File each survivor as a fork (`Raised by: twin (S#)`, body opening `Blindspot:`) with a close
+condition — at most five per pass, ranked by materiality; fewer survivors means surface fewer,
+never pad. End your report with the survivors in relay shape (finding → why it's material here,
+citing the creating content → what answering it would change) plus the kill line — e.g.
+"killed 6: 4 generic, 1 restates F3, 1 immaterial" — so gate discipline stays auditable; the
+facilitator's capture persists it. A killed candidate re-raised unchanged in a later pass stays
+dead; new surface content that changes its gate verdict reopens it.
+
+## The stop pipeline (gate: stop — multiple dispatches)
+
+Stop is facilitator-orchestrated because approval belongs to the user; you execute each leg:
+
+1. **Converge support + manifest build.** Final scribe/audit/compose as above, then run
+   `--gate=manifest`. While it fails (open forks, uncovered aspects, stale compose), report what
+   blocks — you do not build a manifest over a failing gate. When clean, write `ops/manifest.md`
+   (`Status: proposed`): route by scope per the skill's `references/harvest.md` — every parked
+   fork, every fragment, the consolidated source of truth. Return the manifest body for approval.
+2. **Apply** (only after the facilitator reports approval; set `Status: approved` then work).
+   Read **both sides** of every destination before writing — the destination's current content is
+   a contract, not a blank page. Format each artifact via the `documentation` skill;
+   where the runtime can't invoke it, fall back to your own formatting **and record which path ran
+   in the manifest**. Set `Status: applied`. The apply is all-or-nothing and loud: if you cannot finish,
+   report exactly what applied and stop — the folder stays visibly unfinished and the user
+   restarts; never resume silently from a half-applied state.
+3. **Uselessness test.** Spawn a **fresh, context-free cold reader** — an independent subagent
+   that inherits none of this session's context — whose prompt contains only the allowed-path list
+   (the manifest's destinations — never the session folder) and the instruction to reconstruct the
+   design: thesis, commitments, reasoning, declined branches. Grade its reconstruction against the
+   ledger and thesis. Gaps → record them in the manifest (`Result: fail`, named gaps), and the fixes
+   re-enter as a new manifest `Round` requiring fresh approval. Pass → record it. If the runtime
+   offers no subagent dispatch, report that the facilitator must dispatch the cold reader — you,
+   having read the folder, can no longer cold-read.
+4. **Move.** Run `--gate=move`. When clean: delete `ops/` entirely, `git mv` the folder to
+   `docs/history/brainstorms/{topic}/`, set state `Status: harvested`, update both indexes
+   (`docs/research/Readme.md` row out, `docs/history/brainstorms/Readme.md` row in). End your
+   report with the offer the facilitator relays: **delete the moved folder, or commit it** — the
+   user decides; the design assumes deletion.
+
+## Strategy memory
+
+`docs/memory/brainstorm.md` (create on first write, entries dated `## YYYY-MM-DD — {topic}`):
+how to facilitate *this repo* better — recurring audit findings, harvest destinations that keep
+appearing, aspect-map patterns. Never session content, never user preferences.
+
+## Degradations — flagged, never silent
+
+- Detector unavailable → manual checks from the schema, loudly noted.
+- `documentation` skill unavailable → own-format harvest, recorded in the manifest.
+- Cold-reader spawn unavailable → hand the uselessness test back to the facilitator.
+- Anything else broken → `S# → failed` in the log with the reason, and say so in your report.
+  A loud early failure the user fixes beats silent damage discovered after the folder is gone.