wendkeep 0.61.0 → 0.62.0

package/CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to **wendkeep** are documented here. Format based on
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); this project follows
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.62.0] — 2026-07-28
+
+### Added
+
+- **`wendkeep/harness` passa a expor o policy kernel reutilizável.** Os contratos dos cinco
+  Perfis de Operação e a engine de sensores podem ser importados pela superfície pública do pacote
+  raiz, com identidade validada a partir de um tarball realmente instalado.
+
+### Changed
+
+- **As implementações canônicas de perfis e sensores agora pertencem a
+  `packages/harness/src`.** `src/operating-profile.mjs` e `hooks/sensors-core.mjs` permanecem como
+  fachadas de reexport, preservando funções, constantes, objetos congelados e consumidores atuais.
+- **A direção modular do Harness virou contrato estrutural.** O workspace aceita somente built-ins,
+  módulos internos e a superfície pública do Vault; Vault continua proibido de depender do
+  Harness, e CLI, MCP, Integrations e Pi permanecem adaptadores superiores.
+- **OFF preserva a semântica publicada:** Keep Core/Vault continua ativo e a governança automática
+  fica desligada; comandos explícitos do operador não ganham bloqueios novos nesta extração.
+
 ## [0.61.0] — 2026-07-28
 
 ### Added

package/README.en.md

@@ -16,11 +16,11 @@
 **Persistent memory for AI coding agents, built on your Obsidian vault.** Every Claude Code **and Codex** session is captured turn by turn into local Markdown — `init` wires both (Codex asks you to approve its hooks once; `import` backfills past sessions either way) — with token/cost tracking and automatically extracted decisions, bugs, and learnings. That always-on plane is **Keep Core**. On top of it, **Wend Runtime** provides a native, zero-dependency lifecycle (spec → change → TDD → sensor-gated archive), selected through the `OFF`, `FLOW`, `GUIDE`, `GOVERN`, and `ASSURE` Operating Profiles. 100% local, open-core.
 
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
-`integrations`, and `pi` — without fragmenting installation. The private `vault` workspace now
-canonically owns safe binding and the Shared Project Memory v2 kernel (schema, mode, handoff,
-ledger, projection, and validation), exposed by the root package through `wendkeep/vault`.
-Historical imports, including installed bare subpaths such as `wendkeep/hooks/...`, keep working
-through compatibility facades and no session data needs migration;
+`integrations`, and `pi` — without fragmenting installation. The private `harness` and `vault`
+workspaces now canonically own Operating Profiles/the sensor engine and safe binding/the Shared
+Project Memory v2 kernel, respectively. The root package exposes those surfaces through
+`wendkeep/harness` and `wendkeep/vault`; historical imports keep working through compatibility
+facades and no session data needs migration;
 see the [modular architecture](docs/en/architecture.md).
 
 ```bash
@@ -189,8 +189,9 @@ Operations that deserve step-by-step guidance: [verify and exits 0/1/2](https://
 ## Operating Profiles — Keep Core is always active
 
 **Keep Core is always active**: the Vault, sessions, identity, CORE/SHARED, lessons, costs,
-and persistence do not turn off with the harness. **Wend Runtime** controls only the governance
-layer:
+and persistence do not turn off with the harness. **Wend Runtime** controls only the automatic
+governance layer. Even under `OFF`, explicit WendKeep commands remain available; invoking one is a
+deliberate opt-in and runs that command's own validations:
 
 | Profile | Route | Use |
 |---|---|---|

package/README.md

@@ -16,11 +16,11 @@
 **Persistent memory for AI coding agents, built on your Obsidian vault.** Every Claude Code **and Codex** session is captured turn by turn into local Markdown — `init` wires both (Codex asks you to approve its hooks once; `import` backfills past sessions either way) — with token/cost tracking and automatically extracted decisions, bugs, and learnings. That always-on plane is **Keep Core**. On top of it, **Wend Runtime** provides a native, zero-dependency lifecycle (spec → change → TDD → sensor-gated archive), selected through the `OFF`, `FLOW`, `GUIDE`, `GOVERN`, and `ASSURE` Operating Profiles. 100% local, open-core.
 
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
-`integrations`, and `pi` — without fragmenting installation. The private `vault` workspace now
-canonically owns safe binding and the Shared Project Memory v2 kernel (schema, mode, handoff,
-ledger, projection, and validation), exposed by the root package through `wendkeep/vault`.
-Historical imports, including installed bare subpaths such as `wendkeep/hooks/...`, keep working
-through compatibility facades and no session data needs migration;
+`integrations`, and `pi` — without fragmenting installation. The private `harness` and `vault`
+workspaces now canonically own Operating Profiles/the sensor engine and safe binding/the Shared
+Project Memory v2 kernel, respectively. The root package exposes those surfaces through
+`wendkeep/harness` and `wendkeep/vault`; historical imports keep working through compatibility
+facades and no session data needs migration;
 see the [modular architecture](docs/en/architecture.md).
 
 ```bash
@@ -189,8 +189,9 @@ Operations that deserve step-by-step guidance: [verify and exits 0/1/2](https://
 ## Operating Profiles — Keep Core is always active
 
 **Keep Core is always active**: the Vault, sessions, identity, CORE/SHARED, lessons, costs,
-and persistence do not turn off with the harness. **Wend Runtime** controls only the governance
-layer:
+and persistence do not turn off with the harness. **Wend Runtime** controls only the automatic
+governance layer. Even under `OFF`, explicit WendKeep commands remain available; invoking one is a
+deliberate opt-in and runs that command's own validations:
 
 | Profile | Route | Use |
 |---|---|---|

package/docs/en/commands/operating-profiles.md

@@ -8,6 +8,10 @@ Choose how much Wend Runtime governance an execution needs without disabling **K
 Keep Core is always active: the Vault, session, identity, CORE/SHARED, lessons, costs, and
 persistence integrations continue working under every profile.
 
+The `OFF` profile disables automatic governance activation, not the CLI: explicit commands such as
+`profile`, `flow`, `change`, `verify`, and `sensors` remain available. Invoking one is a deliberate
+opt-in and runs that command's own validations and gates.
+
 ## When to use
 
 Use `profile` to inspect or explicitly select an Operating Profile. Use `FLOW` for local,
@@ -44,11 +48,28 @@ Every FLOW subcommand also accepts `--project <path>`, `--vault <path>`, and `--
 provided, `--session` scopes ID-based reads and mutations to the session that owns the FLOW; an
 ID from another session fails without mutation.
 
+## Ownership and programmatic surface
+
+The private `packages/harness` workspace canonically owns Operating Profile resolution/policy and
+the sensor engine. Programmatic consumers use the public root-package subpath:
+
+```js
+import {
+  resolveOperatingProfile,
+  runSensors,
+  evaluateGate,
+} from 'wendkeep/harness';
+```
+
+`src/operating-profile.mjs` and `hooks/sensors-core.mjs` are compatibility facades only. Dependency
+direction is `adapters (cli/mcp/integrations/pi) -> Harness -> Vault`; Vault never depends on
+Harness. The workspaces remain private and are not published as independent npm packages.
+
 ## Options and exit codes
 
 | Profile | Route | Contract |
 |---|---|---|
-| `OFF` | LLM-native harness | Wend Runtime off; Keep Core intact. |
+| `OFF` | LLM-native harness | Automatic governance off; Keep Core and explicit commands available. |
 | `FLOW` | E → V | Microcontract with Git baseline, allowlist, sensors, and receipt, without a change. |
 | `GUIDE` | P → E → V | Compact change; policy recognized for compatible evolution. |
 | `GOVERN` | P → R → E → V | Current a2 loop and conservative fallback. |
@@ -145,9 +166,10 @@ npx wendkeep flow promote $flowId --change-slug another-slug
 ## Expected result
 
 Changing profile neither creates a new session nor interrupts the Vault. In `OFF`, memory and
-lessons are still injected and Stop still persists the session/memory lifecycle, while the
-router, skill gate, change context/warn/nag/guard, and plan capture are inactive. A completed FLOW
-leaves a durable, inspectable receipt; a promoted FLOW enters the normal change lifecycle.
+lessons are still injected and Stop still persists the session/memory lifecycle, while automatic
+router, skill gate, change context/warn/nag/guard, and plan capture are inactive. Explicit commands
+remain available and run their own contracts. A completed FLOW leaves a durable, inspectable
+receipt; a promoted FLOW enters the normal change lifecycle.
 
 ## Common errors and diagnosis
 

package/docs/pt-BR/commands/operating-profiles.md

@@ -8,6 +8,10 @@ Escolher quanta governança do Wend Runtime uma execução precisa sem desligar
 O Keep Core permanece sempre ativo: Vault, sessão, identidade, CORE/SHARED, lessons, custos e
 integrações de persistência continuam funcionando em todos os perfis.
 
+O perfil `OFF` desativa a ativação automática da governança, não a CLI: comandos explícitos como
+`profile`, `flow`, `change`, `verify` e `sensors` continuam disponíveis. Invocá-los é um opt-in
+deliberado e executa as validações e gates próprios daquele comando.
+
 ## Quando usar
 
 Use `profile` para consultar ou selecionar explicitamente um Perfil de Operação. Use `FLOW` para
@@ -44,11 +48,29 @@ Todos os subcomandos FLOW também aceitam `--project <path>`, `--vault <path>` e
 Quando informado, `--session` restringe inclusive consultas e mutações por ID à sessão dona do
 FLOW; um ID de outra sessão falha sem mutação.
 
+## Ownership e superfície programática
+
+O workspace privado `packages/harness` é o dono canônico da resolução/política dos Perfis de
+Operação e da engine de sensores. Consumidores programáticos usam o subpath público do pacote raiz:
+
+```js
+import {
+  resolveOperatingProfile,
+  runSensors,
+  evaluateGate,
+} from 'wendkeep/harness';
+```
+
+`src/operating-profile.mjs` e `hooks/sensors-core.mjs` são somente fachadas de compatibilidade. A
+direção de dependências é `adapters (cli/mcp/integrations/pi) -> Harness -> Vault`; o Vault nunca
+depende do Harness. Os workspaces continuam privados e não são publicados como pacotes npm
+independentes.
+
 ## Opções e códigos de saída
 
 | Perfil | Rota | Contrato |
 |---|---|---|
-| `OFF` | harness nativo da LLM | Wend Runtime desligado; Keep Core integral. |
+| `OFF` | harness nativo da LLM | Governança automática desligada; Keep Core e comandos explícitos disponíveis. |
 | `FLOW` | E → V | Microcontrato com baseline Git, allowlist, sensores e recibo, sem change. |
 | `GUIDE` | P → E → V | Change compacta; política reconhecida para evolução compatível. |
 | `GOVERN` | P → R → E → V | Loop a2 atual e fallback conservador. |
@@ -144,8 +166,9 @@ npx wendkeep flow promote $flowId --change-slug outro-slug
 
 Trocar o perfil não cria outra sessão nem interrompe o Vault. Em `OFF`, a memória e as lessons
 continuam injetadas e o Stop continua persistindo sessão/memória, mas router, skill gate,
-change context/warn/nag/guard e captura de plano ficam inativos. Um FLOW concluído deixa recibo
-durável e consultável; um FLOW promovido passa a seguir o lifecycle normal de change.
+change context/warn/nag/guard e captura de plano automáticos ficam inativos. Os comandos explícitos
+continuam disponíveis e executam seus próprios contratos. Um FLOW concluído deixa recibo durável e
+consultável; um FLOW promovido passa a seguir o lifecycle normal de change.
 
 ## Erros comuns e diagnóstico
 

package/hooks/sensors-core.mjs

@@ -1,102 +1 @@
-// hooks/sensors-core.mjs — native sensor runner + evidence gate (Pilar C).
-// Pure-ish: `spawn` is injectable so runs are testable without a shell. Config lives
-// at the PROJECT ROOT (wendkeep.sensors.json); evidence lives per-change in the vault.
-import { spawnSync } from 'node:child_process';
-import { existsSync, readFileSync } from 'node:fs';
-import { dirname, join, resolve } from 'node:path';
-
-export const SENSOR_VAULT_ENV = 'WENDKEEP_SENSOR_VAULT';
-
-export function sensorProcessEnv(vaultBase, inherited = process.env) {
-  return {
-    ...inherited,
-    OBSIDIAN_VAULT_PATH: vaultBase,
-    [SENSOR_VAULT_ENV]: vaultBase,
-  };
-}
-
-export function loadSensors(projectRoot, file = 'wendkeep.sensors.json') {
-  return loadSensorsDetailed(projectRoot, file).sensors;
-}
-
-// Missing config and broken config are different failures: absent file usually means
-// wrong cwd (subdirectory), broken JSON means the config itself needs fixing. Collapsing
-// both into [] made every sensor report "sensor não definido" — a misleading diagnosis.
-export function loadSensorsDetailed(projectRoot, file = 'wendkeep.sensors.json') {
-  const path = join(projectRoot, file);
-  if (!existsSync(path)) return { sensors: [], missing: true, error: null, path };
-  try {
-    const data = JSON.parse(readFileSync(path, 'utf8'));
-    return { sensors: Array.isArray(data.sensors) ? data.sensors : [], missing: false, error: null, path };
-  } catch (e) {
-    return { sensors: [], missing: false, error: e.message, path };
-  }
-}
-
-// Climb the directory tree looking for a project marker (wendkeep.sensors.json or
-// .wendkeep.json), like git does with .git — shells in agent harnesses keep their cwd
-// across commands, so verify is often run from a subdirectory.
-export function findProjectRoot(startDir) {
-  let dir = resolve(startDir);
-  for (;;) {
-    if (existsSync(join(dir, 'wendkeep.sensors.json')) || existsSync(join(dir, '.wendkeep.json'))) return dir;
-    const parent = dirname(dir);
-    if (parent === dir) return null;
-    dir = parent;
-  }
-}
-
-export function requiredSensors(tasks) {
-  return [...new Set((tasks || []).flatMap((task) => (
-    Array.isArray(task.sensors) && task.sensors.length ? task.sensors : [task.sensor]
-  )).filter(Boolean))];
-}
-
-export function runSensors(sensors, ids, { spawn = spawnSync, cwd, env, now } = {}) {
-  const byId = Object.fromEntries((sensors || []).map((s) => [s.id, s]));
-  const ts = now || new Date().toISOString();
-  const evidence = [];
-  for (const id of ids) {
-    const s = byId[id];
-    if (!s) { evidence.push({ id, status: 'red', ts, severity: 'critical', note: 'sensor não definido' }); continue; }
-    const r = spawn(s.command, [], { cwd, shell: true, stdio: 'ignore', ...(env ? { env } : {}) });
-    const entry = { id, status: (r.status ?? 1) === 0 ? 'green' : 'red', ts, severity: s.severity || 'critical' };
-    if (s.type === 'mutation' && s.report) {
-      // Delegated mutation (Wave B): read the tool's mutation-testing-elements report and
-      // attach surviving mutants so verify can turn them into fix tasks.
-      try { entry.survivors = parseMutationReport(JSON.parse(readFileSync(join(cwd || '.', s.report), 'utf8'))); }
-      catch { /* report ausente/ilegível — segue só com o exit code */ }
-    }
-    evidence.push(entry);
-  }
-  return evidence;
-}
-
-// Parse a mutation-testing-elements report (Stryker et al.): return surviving mutants
-// (Survived | NoCoverage) as {file, line, mutator}.
-export function parseMutationReport(json) {
-  const out = [];
-  const files = json && json.files ? json.files : {};
-  for (const [file, data] of Object.entries(files)) {
-    for (const m of (data && data.mutants) || []) {
-      if (m.status === 'Survived' || m.status === 'NoCoverage') {
-        out.push({ file, line: m.location && m.location.start ? m.location.start.line : null, mutator: m.mutatorName || 'unknown' });
-      }
-    }
-  }
-  return out;
-}
-
-// A required sensor blocks the gate when it is missing (never verified) or red at a
-// non-warning severity. Warnings are advisory: a red warning does not block archive.
-// Severity comes from the evidence entry (written by runSensors); absent -> critical.
-export function evaluateGate(evidence, requiredIds) {
-  const byId = Object.fromEntries((evidence || []).map((e) => [e.id, e]));
-  const failing = (requiredIds || []).filter((id) => {
-    const e = byId[id];
-    if (!e) return true; // never verified
-    if (e.status === 'green') return false;
-    return (e.severity || 'critical') !== 'warning';
-  });
-  return { ok: failing.length === 0, failing };
-}
+export * from '../packages/harness/src/sensors-core.mjs';

package/package.json

@@ -1,12 +1,13 @@
 {
   "name": "wendkeep",
-  "version": "0.61.0",
+  "version": "0.62.0",
   "description": "Vault-first persistent memory for AI coding agents, with an optional profile-aware governance runtime: OFF, FLOW, GUIDE, GOVERN, or ASSURE. Local-first and agent-agnostic (Claude Code, Codex, Cursor…).",
   "type": "module",
   "workspaces": [
     "packages/*"
   ],
   "exports": {
+    "./harness": "./packages/harness/src/index.mjs",
     "./vault": "./packages/vault/src/index.mjs",
     "./*": "./*"
   },
@@ -30,7 +31,7 @@
     "node": ">=18"
   },
   "scripts": {
-    "check": "node --check bin/wendkeep.mjs && node --check src/init.mjs && node --check src/doctor.mjs && node --check src/project-vault.mjs && node --check src/operating-profile.mjs && node --check src/profile.mjs && node --check src/flow.mjs && node --check hooks/operating-profile-runtime.mjs && node --check hooks/flow-core.mjs && node --check hooks/flow-protected-policy.mjs && node --check hooks/git-snapshot.mjs && node --check hooks/vault-path-safety.mjs && node --check hooks/vault-runtime-store.mjs && node --check packages/vault/src/index.mjs && node --check packages/vault/src/project-vault.mjs && node --check packages/vault/src/vault-path-safety.mjs && node --check packages/vault/src/memory-schema.mjs && node --check packages/vault/src/memory-mode.mjs && node --check packages/vault/src/memory-handoff.mjs && node --check packages/vault/src/memory-store.mjs && node --check packages/vault/src/validate-core.mjs && node --check packages/vault/src/validate-memory.mjs",
+    "check": "node --check bin/wendkeep.mjs && node --check src/init.mjs && node --check src/doctor.mjs && node --check src/project-vault.mjs && node --check src/operating-profile.mjs && node --check src/profile.mjs && node --check src/flow.mjs && node --check hooks/operating-profile-runtime.mjs && node --check hooks/flow-core.mjs && node --check hooks/flow-protected-policy.mjs && node --check hooks/git-snapshot.mjs && node --check hooks/vault-path-safety.mjs && node --check hooks/vault-runtime-store.mjs && node --check packages/harness/src/index.mjs && node --check packages/harness/src/operating-profile.mjs && node --check packages/harness/src/sensors-core.mjs && node --check packages/vault/src/index.mjs && node --check packages/vault/src/project-vault.mjs && node --check packages/vault/src/vault-path-safety.mjs && node --check packages/vault/src/memory-schema.mjs && node --check packages/vault/src/memory-mode.mjs && node --check packages/vault/src/memory-handoff.mjs && node --check packages/vault/src/memory-store.mjs && node --check packages/vault/src/validate-core.mjs && node --check packages/vault/src/validate-memory.mjs",
     "test": "node --test",
     "release": "node scripts/release.mjs",
     "release:dry": "node scripts/release.mjs --dry-run",
@@ -59,6 +60,7 @@
     "url": "https://github.com/rogersialves/wendkeep/issues"
   },
   "devDependencies": {
+    "acorn": "^8.18.0",
     "wendkeep": "^0.57.2"
   }
 }

package/packages/harness/package.json

@@ -1,5 +1,6 @@
 {
   "name": "@wendkeep/harness",
   "private": true,
-  "type": "module"
+  "type": "module",
+  "exports": "./src/index.mjs"
 }

package/packages/harness/src/index.mjs

@@ -0,0 +1,2 @@
+export * from './operating-profile.mjs';
+export * from './sensors-core.mjs';

package/packages/harness/src/operating-profile.mjs

@@ -0,0 +1,133 @@
+export const OPERATING_PROFILES = Object.freeze([
+  'OFF',
+  'FLOW',
+  'GUIDE',
+  'GOVERN',
+  'ASSURE',
+]);
+export const DEFAULT_OPERATING_PROFILE = 'GOVERN';
+
+const PROFILE_SET = new Set(OPERATING_PROFILES);
+
+function policy(profile, route, options) {
+  return Object.freeze({
+    profile,
+    route: Object.freeze(route),
+    keepCore: true,
+    ...options,
+  });
+}
+
+export const OPERATING_PROFILE_POLICIES = Object.freeze({
+  OFF: policy('OFF', ['LLM'], {
+    harness: false,
+    contract: 'native',
+    requiresChange: false,
+    requiresReview: false,
+    requiresConfirmation: false,
+  }),
+  FLOW: policy('FLOW', ['E', 'V'], {
+    harness: true,
+    contract: 'flow',
+    requiresChange: false,
+    requiresReview: false,
+    requiresConfirmation: false,
+  }),
+  GUIDE: policy('GUIDE', ['P', 'E', 'V'], {
+    harness: true,
+    contract: 'simple-change',
+    requiresChange: true,
+    requiresReview: false,
+    requiresConfirmation: false,
+  }),
+  GOVERN: policy('GOVERN', ['P', 'R', 'E', 'V'], {
+    harness: true,
+    contract: 'change',
+    requiresChange: true,
+    requiresReview: true,
+    requiresConfirmation: false,
+  }),
+  ASSURE: policy('ASSURE', ['P', 'R', 'E', 'V', 'C'], {
+    harness: true,
+    contract: 'change',
+    requiresChange: true,
+    requiresReview: true,
+    requiresConfirmation: true,
+  }),
+});
+
+function invalidProfileError(value) {
+  const rendered = typeof value === 'string' ? `"${value}"` : String(value);
+  const error = new Error(
+    `Perfil de Operação inválido: ${rendered}. Use ${OPERATING_PROFILES.join(', ')}.`,
+  );
+  error.code = 'WENDKEEP_OPERATING_PROFILE_INVALID';
+  return error;
+}
+
+function canonicalProfile(value) {
+  if (typeof value !== 'string') return '';
+  return value.trim().toUpperCase();
+}
+
+export function normalizeOperatingProfile(value, { strict = false } = {}) {
+  const normalized = canonicalProfile(value);
+  if (PROFILE_SET.has(normalized)) return normalized;
+  if (strict) throw invalidProfileError(value);
+  return DEFAULT_OPERATING_PROFILE;
+}
+
+export function resolveOperatingProfile(config = {}) {
+  const harness = config && typeof config === 'object' && !Array.isArray(config)
+    && config.harness && typeof config.harness === 'object' && !Array.isArray(config.harness)
+    ? config.harness
+    : null;
+  const configured = !!harness && Object.prototype.hasOwnProperty.call(harness, 'profile');
+  if (!configured) {
+    return {
+      profile: DEFAULT_OPERATING_PROFILE,
+      source: 'default',
+      valid: true,
+      configured: false,
+      raw: null,
+    };
+  }
+
+  const raw = harness.profile;
+  const normalized = canonicalProfile(raw);
+  if (PROFILE_SET.has(normalized)) {
+    return {
+      profile: normalized,
+      source: 'project-binding',
+      valid: true,
+      configured: true,
+      raw,
+    };
+  }
+  return {
+    profile: DEFAULT_OPERATING_PROFILE,
+    source: 'default-invalid',
+    valid: false,
+    configured: true,
+    raw,
+  };
+}
+
+export function operatingProfilePolicy(value) {
+  return OPERATING_PROFILE_POLICIES[normalizeOperatingProfile(value)];
+}
+
+export function setOperatingProfile(config = {}, value) {
+  const profile = normalizeOperatingProfile(value, { strict: true });
+  const base = config && typeof config === 'object' && !Array.isArray(config) ? config : {};
+  const harness = base.harness && typeof base.harness === 'object' && !Array.isArray(base.harness)
+    ? base.harness
+    : {};
+  return {
+    ...base,
+    harness: {
+      ...harness,
+      profile,
+    },
+  };
+}

package/packages/harness/src/sensors-core.mjs

@@ -0,0 +1,102 @@
+// hooks/sensors-core.mjs — native sensor runner + evidence gate (Pilar C).
+// Pure-ish: `spawn` is injectable so runs are testable without a shell. Config lives
+// at the PROJECT ROOT (wendkeep.sensors.json); evidence lives per-change in the vault.
+import { spawnSync } from 'node:child_process';
+import { existsSync, readFileSync } from 'node:fs';
+import { dirname, join, resolve } from 'node:path';
+
+export const SENSOR_VAULT_ENV = 'WENDKEEP_SENSOR_VAULT';
+
+export function sensorProcessEnv(vaultBase, inherited = process.env) {
+  return {
+    ...inherited,
+    OBSIDIAN_VAULT_PATH: vaultBase,
+    [SENSOR_VAULT_ENV]: vaultBase,
+  };
+}
+
+export function loadSensors(projectRoot, file = 'wendkeep.sensors.json') {
+  return loadSensorsDetailed(projectRoot, file).sensors;
+}
+
+// Missing config and broken config are different failures: absent file usually means
+// wrong cwd (subdirectory), broken JSON means the config itself needs fixing. Collapsing
+// both into [] made every sensor report "sensor não definido" — a misleading diagnosis.
+export function loadSensorsDetailed(projectRoot, file = 'wendkeep.sensors.json') {
+  const path = join(projectRoot, file);
+  if (!existsSync(path)) return { sensors: [], missing: true, error: null, path };
+  try {
+    const data = JSON.parse(readFileSync(path, 'utf8'));
+    return { sensors: Array.isArray(data.sensors) ? data.sensors : [], missing: false, error: null, path };
+  } catch (e) {
+    return { sensors: [], missing: false, error: e.message, path };
+  }
+}
+
+// Climb the directory tree looking for a project marker (wendkeep.sensors.json or
+// .wendkeep.json), like git does with .git — shells in agent harnesses keep their cwd
+// across commands, so verify is often run from a subdirectory.
+export function findProjectRoot(startDir) {
+  let dir = resolve(startDir);
+  for (;;) {
+    if (existsSync(join(dir, 'wendkeep.sensors.json')) || existsSync(join(dir, '.wendkeep.json'))) return dir;
+    const parent = dirname(dir);
+    if (parent === dir) return null;
+    dir = parent;
+  }
+}
+
+export function requiredSensors(tasks) {
+  return [...new Set((tasks || []).flatMap((task) => (
+    Array.isArray(task.sensors) && task.sensors.length ? task.sensors : [task.sensor]
+  )).filter(Boolean))];
+}
+
+export function runSensors(sensors, ids, { spawn = spawnSync, cwd, env, now } = {}) {
+  const byId = Object.fromEntries((sensors || []).map((s) => [s.id, s]));
+  const ts = now || new Date().toISOString();
+  const evidence = [];
+  for (const id of ids) {
+    const s = byId[id];
+    if (!s) { evidence.push({ id, status: 'red', ts, severity: 'critical', note: 'sensor não definido' }); continue; }
+    const r = spawn(s.command, [], { cwd, shell: true, stdio: 'ignore', ...(env ? { env } : {}) });
+    const entry = { id, status: (r.status ?? 1) === 0 ? 'green' : 'red', ts, severity: s.severity || 'critical' };
+    if (s.type === 'mutation' && s.report) {
+      // Delegated mutation (Wave B): read the tool's mutation-testing-elements report and
+      // attach surviving mutants so verify can turn them into fix tasks.
+      try { entry.survivors = parseMutationReport(JSON.parse(readFileSync(join(cwd || '.', s.report), 'utf8'))); }
+      catch { /* report ausente/ilegível — segue só com o exit code */ }
+    }
+    evidence.push(entry);
+  }
+  return evidence;
+}
+
+// Parse a mutation-testing-elements report (Stryker et al.): return surviving mutants
+// (Survived | NoCoverage) as {file, line, mutator}.
+export function parseMutationReport(json) {
+  const out = [];
+  const files = json && json.files ? json.files : {};
+  for (const [file, data] of Object.entries(files)) {
+    for (const m of (data && data.mutants) || []) {
+      if (m.status === 'Survived' || m.status === 'NoCoverage') {
+        out.push({ file, line: m.location && m.location.start ? m.location.start.line : null, mutator: m.mutatorName || 'unknown' });
+      }
+    }
+  }
+  return out;
+}
+
+// A required sensor blocks the gate when it is missing (never verified) or red at a
+// non-warning severity. Warnings are advisory: a red warning does not block archive.
+// Severity comes from the evidence entry (written by runSensors); absent -> critical.
+export function evaluateGate(evidence, requiredIds) {
+  const byId = Object.fromEntries((evidence || []).map((e) => [e.id, e]));
+  const failing = (requiredIds || []).filter((id) => {
+    const e = byId[id];
+    if (!e) return true; // never verified
+    if (e.status === 'green') return false;
+    return (e.severity || 'critical') !== 'warning';
+  });
+  return { ok: failing.length === 0, failing };
+}

package/src/operating-profile.mjs

@@ -1,133 +1 @@
-export const OPERATING_PROFILES = Object.freeze([
-  'OFF',
-  'FLOW',
-  'GUIDE',
-  'GOVERN',
-  'ASSURE',
-]);
-export const DEFAULT_OPERATING_PROFILE = 'GOVERN';
-
-const PROFILE_SET = new Set(OPERATING_PROFILES);
-
-function policy(profile, route, options) {
-  return Object.freeze({
-    profile,
-    route: Object.freeze(route),
-    keepCore: true,
-    ...options,
-  });
-}
-
-export const OPERATING_PROFILE_POLICIES = Object.freeze({
-  OFF: policy('OFF', ['LLM'], {
-    harness: false,
-    contract: 'native',
-    requiresChange: false,
-    requiresReview: false,
-    requiresConfirmation: false,
-  }),
-  FLOW: policy('FLOW', ['E', 'V'], {
-    harness: true,
-    contract: 'flow',
-    requiresChange: false,
-    requiresReview: false,
-    requiresConfirmation: false,
-  }),
-  GUIDE: policy('GUIDE', ['P', 'E', 'V'], {
-    harness: true,
-    contract: 'simple-change',
-    requiresChange: true,
-    requiresReview: false,
-    requiresConfirmation: false,
-  }),
-  GOVERN: policy('GOVERN', ['P', 'R', 'E', 'V'], {
-    harness: true,
-    contract: 'change',
-    requiresChange: true,
-    requiresReview: true,
-    requiresConfirmation: false,
-  }),
-  ASSURE: policy('ASSURE', ['P', 'R', 'E', 'V', 'C'], {
-    harness: true,
-    contract: 'change',
-    requiresChange: true,
-    requiresReview: true,
-    requiresConfirmation: true,
-  }),
-});
-
-function invalidProfileError(value) {
-  const rendered = typeof value === 'string' ? `"${value}"` : String(value);
-  const error = new Error(
-    `Perfil de Operação inválido: ${rendered}. Use ${OPERATING_PROFILES.join(', ')}.`,
-  );
-  error.code = 'WENDKEEP_OPERATING_PROFILE_INVALID';
-  return error;
-}
-
-function canonicalProfile(value) {
-  if (typeof value !== 'string') return '';
-  return value.trim().toUpperCase();
-}
-
-export function normalizeOperatingProfile(value, { strict = false } = {}) {
-  const normalized = canonicalProfile(value);
-  if (PROFILE_SET.has(normalized)) return normalized;
-  if (strict) throw invalidProfileError(value);
-  return DEFAULT_OPERATING_PROFILE;
-}
-
-export function resolveOperatingProfile(config = {}) {
-  const harness = config && typeof config === 'object' && !Array.isArray(config)
-    && config.harness && typeof config.harness === 'object' && !Array.isArray(config.harness)
-    ? config.harness
-    : null;
-  const configured = !!harness && Object.prototype.hasOwnProperty.call(harness, 'profile');
-  if (!configured) {
-    return {
-      profile: DEFAULT_OPERATING_PROFILE,
-      source: 'default',
-      valid: true,
-      configured: false,
-      raw: null,
-    };
-  }
-
-  const raw = harness.profile;
-  const normalized = canonicalProfile(raw);
-  if (PROFILE_SET.has(normalized)) {
-    return {
-      profile: normalized,
-      source: 'project-binding',
-      valid: true,
-      configured: true,
-      raw,
-    };
-  }
-  return {
-    profile: DEFAULT_OPERATING_PROFILE,
-    source: 'default-invalid',
-    valid: false,
-    configured: true,
-    raw,
-  };
-}
-
-export function operatingProfilePolicy(value) {
-  return OPERATING_PROFILE_POLICIES[normalizeOperatingProfile(value)];
-}
-
-export function setOperatingProfile(config = {}, value) {
-  const profile = normalizeOperatingProfile(value, { strict: true });
-  const base = config && typeof config === 'object' && !Array.isArray(config) ? config : {};
-  const harness = base.harness && typeof base.harness === 'object' && !Array.isArray(base.harness)
-    ? base.harness
-    : {};
-  return {
-    ...base,
-    harness: {
-      ...harness,
-      profile,
-    },
-  };
-}
+export * from '../packages/harness/src/operating-profile.mjs';