wendkeep 0.65.0 → 0.66.1

package/CHANGELOG.md

@@ -4,6 +4,50 @@ 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.66.1] — 2026-07-29
+
+### Fixed
+
+- **A curadoria de candidates agora é durável e idempotente.** `memory promote` e
+  `memory reject` registram decisões causais no ledger; repair/replay não recriam o conflito
+  resolvido, retries não duplicam eventos, candidates sobrepostos permanecem isolados e a
+  promoção recupera o checkpoint divergente do attempt correspondente sem tocar attempt novo.
+- **Promoção de conflito exige escolha explícita.** `memory promote <candidate> --event
+  <event-id>` publica exatamente o evento escolhido, rejeita IDs externos ao candidate e não
+  permite que `blocked_by_core` sobrescreva a autoridade canônica de CORE.
+
+## [0.66.0] — 2026-07-29
+
+### Added
+
+- **O workspace privado Integrations passa a ter um kernel canônico para Claude Code e Codex.**
+  Catálogo/projeção de hooks, envelope e provider, filtros de conteúdo, normalização de uso,
+  parsers de transcript e identidade de sessão/turno agora vivem em módulos puros sob
+  `packages/integrations/src/`, sem filesystem, ambiente global, Vault ou registry no import.
+- **O tarball instalado prova a fronteira completa fora do checkout.** O teste executa `init` e
+  um hook `session-ensure` em consumidor temporário, valida estado persistido e as projeções
+  Claude/Codex contra o kernel empacotado, e confirma que Integrations permanece interno à
+  única publicação `wendkeep`.
+
+### Changed
+
+- **As fachadas históricas agora injetam efeitos no kernel de Integrations.** Taxonomia e hooks
+  preservam assinaturas e identidade dos exports enquanto stdin/stdout, `process.env`, leitura de
+  transcripts, acesso ao Vault e ao registry continuam nas bordas; paths, schemas, configs e
+  sessões existentes não exigem migração.
+- **Os workspaces privados deixaram de vazar por deep imports do wildcard raiz.** A allowlist de
+  exports mantém `wendkeep/harness`, `wendkeep/vault` e os caminhos históricos publicados, mas
+  bloqueia `packages/*`, inclusive variantes percent-encoded; MCP e Integrations seguem como
+  adapters irmãos sem dependência direta.
+
+### Fixed
+
+- **A reconexão de sessão por transcript agora respeita o provider.** Uma entrada do registry de
+  outro host é ignorada sem substituir uma identidade canônica válida já inspecionada.
+- **A suíte integral mantém determinismo sob carga de I/O no Windows.** O runner limita a duas as
+  files executadas em paralelo, preservando a concorrência multiprocesso dentro dos testes de
+  CAS/locks e todos os asserts, sem falsos vermelhos causados por starvation entre suítes.
+
 ## [0.65.0] — 2026-07-29
 
 ### Added

package/README.en.md

@@ -17,14 +17,24 @@
 
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
 `integrations`, and `pi` — without fragmenting installation. The private `cli`, `harness`,
-`vault`, and `mcp` workspaces now canonically own the executable runtime, Operating Profiles/the
-sensor engine, safe binding/the Shared Project Memory v2 kernel, and the MCP configuration kernel,
-respectively. The root package exposes Harness and Vault through `wendkeep/harness` and
-`wendkeep/vault`; CLI and MCP remain private surfaces, reached only through the binaries and the
-configuration effects of `init`. Historical imports keep working through compatibility facades
+`vault`, `mcp`, and `integrations` workspaces now canonically own the executable runtime,
+Operating Profiles/the sensor engine, safe binding/the Shared Project Memory v2 kernel, the MCP
+configuration kernel, and pure Claude/Codex integration rules, respectively. The root package
+exposes Harness and Vault through `wendkeep/harness` and `wendkeep/vault`; CLI, MCP, and
+Integrations remain private surfaces, reached only through the binaries, the configuration effects
+of `init`, and historical facades. Historical imports keep working through compatibility facades
 and no session data needs migration;
 see the [modular architecture](docs/en/architecture.md).
 
+In the **0.66 Integrations Kernel** phase, `packages/integrations/src/` becomes the canonical
+authority for the hook catalog and projection, the envelope/provider, transcript content and usage
+filters and parsers, and session identity. These rules are pure: stdin/stdout, environment,
+filesystem, Vault, and registry effects remain in the historical facades. MCP and Integrations are
+sibling adapters with no dependency between them, and the direction remains
+`cli/mcp/integrations/pi → Harness → Vault`. Hooks, sessions, paths, configuration, and schemas
+remain equivalent; the private `@wendkeep/integrations` workspace stays inside the single
+published `wendkeep` package, with no public `wendkeep/integrations` subpath. Pi is the next phase.
+
 In the **0.65 MCP Configuration Kernel** phase, `packages/mcp/src/config.mjs` becomes the
 canonical authority for the MCPVault entry, catalog-described server selection, and `.mcp.json`
 merging. `src/taxonomy.mjs` supplies descriptors while `src/init.mjs` retains only filesystem
@@ -284,7 +294,10 @@ backup/audit; divergent mirrors fail closed. A demonstrably superseded
 ambiguity uses `memory reconcile <session> --by-session <successor>
 --reason <reason>` as a dry run and requires `--apply`; the decision is backed up and audited
 without rewriting ledger, CORE, or notes. Run `status --gate` again afterwards. Conflicts require
-explicit curation with `memory promote <id>` or `memory reject <id>`; doctor only diagnoses.
+explicit, durable curation: `memory promote <id> --event <event-id>` selects one event from the
+candidate, while `memory reject <id>` keeps the current value. Decisions are idempotent and
+survive repair/replay; `blocked_by_core` cannot override CORE. Doctor only diagnoses. See
+[memory and curation](docs/en/commands/memory.md).
 
 Session notes use one live `## Agentes, tokens e custos` snapshot. Main-agent and subagent hooks recompose it atomically, with costs, token dimensions, reasoning tokens and effort per model/source. Every hook that rewrites a session note takes a per-file lock and writes through a temp file + rename, so the `SubagentStop` fan-out (one hook run per subagent) can never leave a note half-written; a note whose frontmatter reads back damaged is left untouched rather than patched.
 

package/README.md

@@ -17,14 +17,24 @@
 
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
 `integrations`, and `pi` — without fragmenting installation. The private `cli`, `harness`,
-`vault`, and `mcp` workspaces now canonically own the executable runtime, Operating Profiles/the
-sensor engine, safe binding/the Shared Project Memory v2 kernel, and the MCP configuration kernel,
-respectively. The root package exposes Harness and Vault through `wendkeep/harness` and
-`wendkeep/vault`; CLI and MCP remain private surfaces, reached only through the binaries and the
-configuration effects of `init`. Historical imports keep working through compatibility facades
+`vault`, `mcp`, and `integrations` workspaces now canonically own the executable runtime,
+Operating Profiles/the sensor engine, safe binding/the Shared Project Memory v2 kernel, the MCP
+configuration kernel, and pure Claude/Codex integration rules, respectively. The root package
+exposes Harness and Vault through `wendkeep/harness` and `wendkeep/vault`; CLI, MCP, and
+Integrations remain private surfaces, reached only through the binaries, the configuration effects
+of `init`, and historical facades. Historical imports keep working through compatibility facades
 and no session data needs migration;
 see the [modular architecture](docs/en/architecture.md).
 
+In the **0.66 Integrations Kernel** phase, `packages/integrations/src/` becomes the canonical
+authority for the hook catalog and projection, the envelope/provider, transcript content and usage
+filters and parsers, and session identity. These rules are pure: stdin/stdout, environment,
+filesystem, Vault, and registry effects remain in the historical facades. MCP and Integrations are
+sibling adapters with no dependency between them, and the direction remains
+`cli/mcp/integrations/pi → Harness → Vault`. Hooks, sessions, paths, configuration, and schemas
+remain equivalent; the private `@wendkeep/integrations` workspace stays inside the single
+published `wendkeep` package, with no public `wendkeep/integrations` subpath. Pi is the next phase.
+
 In the **0.65 MCP Configuration Kernel** phase, `packages/mcp/src/config.mjs` becomes the
 canonical authority for the MCPVault entry, catalog-described server selection, and `.mcp.json`
 merging. `src/taxonomy.mjs` supplies descriptors while `src/init.mjs` retains only filesystem
@@ -284,7 +294,10 @@ backup/audit; divergent mirrors fail closed. A demonstrably superseded
 ambiguity uses `memory reconcile <session> --by-session <successor>
 --reason <reason>` as a dry run and requires `--apply`; the decision is backed up and audited
 without rewriting ledger, CORE, or notes. Run `status --gate` again afterwards. Conflicts require
-explicit curation with `memory promote <id>` or `memory reject <id>`; doctor only diagnoses.
+explicit, durable curation: `memory promote <id> --event <event-id>` selects one event from the
+candidate, while `memory reject <id>` keeps the current value. Decisions are idempotent and
+survive repair/replay; `blocked_by_core` cannot override CORE. Doctor only diagnoses. See
+[memory and curation](docs/en/commands/memory.md).
 
 Session notes use one live `## Agentes, tokens e custos` snapshot. Main-agent and subagent hooks recompose it atomically, with costs, token dimensions, reasoning tokens and effort per model/source. Every hook that rewrites a session note takes a per-file lock and writes through a temp file + rename, so the `SubagentStop` fan-out (one hook run per subagent) can never leave a note half-written; a note whose frontmatter reads back damaged is left untouched rather than patched.
 

package/docs/en/commands/getting-started.md

@@ -78,6 +78,14 @@ When MCP is enabled, `init` preserves existing properties and servers in `.mcp.j
 and the reconciled proposal is written to `.mcp.json.new`. Since version 0.65, this composition is
 owned by the private MCP kernel without changing commands, flags, or the public npm surface.
 
+Pure rules that project Claude/Codex hooks and interpret envelopes, transcripts, usage, and
+identity belong to the private `@wendkeep/integrations` workspace. Historical facades retain
+stdin/stdout, environment, filesystem, Vault, and registry effects. This adds no commands or flags,
+changes neither hooks nor sessions, and requires no Vault, configuration, path, or schema migration.
+MCP and Integrations remain sibling adapters with no dependency between them, and the direction
+remains `cli/mcp/integrations/pi → Harness → Vault`. Everything stays inside the single published
+`wendkeep` package; there is no public `wendkeep/integrations` surface. Pi is the next modular phase.
+
 ## Common errors and diagnosis
 
 - Wrong vault: inspect `.wendkeep.json` and run `wendkeep doctor --vault <path>`.

package/docs/en/commands/memory-migration.md

@@ -64,7 +64,8 @@ to revision 1. Replaying that prompt or Stop does not duplicate the event/revisi
 - Partial/corrupt v2 bundle: use status and repair; migration is not a corruption tool.
 - First post-migration Stop is `ambiguous`: verify that its `turn_id` belongs to the transcript and
   that `UserPromptSubmit` opened/advanced the recovery activation.
-- Many candidates: curate gradually with `memory promote`/`memory reject`.
+- Many candidates: curate gradually with `memory promote`/`memory reject`; conflicts require
+  `memory promote <candidate> --event <event-id>` to choose the winner explicitly.
 - Legacy warning remains after apply: verify the selected vault and project binding.
 
 ## Next steps

package/docs/en/commands/memory.md

@@ -26,7 +26,7 @@ Pass the vault explicitly in automation. Preserve backups and evidence before re
 npx wendkeep memory status [--gate] --vault <vault>
 npx wendkeep memory repair --vault <vault>
 npx wendkeep memory reconcile <ambiguous-session> --by-session <successor-session> --reason <reason> [--apply] --vault <vault>
-npx wendkeep memory promote <candidate> --vault <vault>
+npx wendkeep memory promote <candidate> [--event <event-id>] --vault <vault>
 npx wendkeep memory reject <candidate> --vault <vault>
 npx wendkeep validate-memory [CORE-path]
 npx wendkeep validate-memory --vault <v2-vault>
@@ -63,7 +63,14 @@ npx wendkeep validate-memory --vault <v2-vault>
   Junctions, symlinks, reparse points, or hardlinks fail closed without touching external bytes.
   Locks publish owner and lease atomically, never reap a live PID by age alone, and release only
   the lease they acquired.
-- `promote`/`reject` append auditable decisions and never rewrite the ledger in place.
+- `promote`/`reject` append an auditable, idempotent decision to the ledger. Replay and repair
+  preserve that decision and do not recreate the resolved candidate. For a `conflict` candidate,
+  `promote` requires an `--event <event-id>` that belongs to the candidate; date or random ID
+  never picks an implicit winner. `reject` preserves the current operational value. A
+  `blocked_by_core` candidate can only be rejected: promotion first requires canonical CORE
+  curation. If the selected event still belongs to the matching latest `projected` attempt,
+  promotion also refreshes its checkpoint and mirror causally; JSON reports
+  `checkpointRefreshed`, and a newer concurrent attempt remains untouched.
 - `validate-memory <CORE.md>` checks the 25-line cap, required sections, and secrets.
 - `validate-memory --vault` requires a complete v2 bundle and is not the legacy-vault gate.
 
@@ -74,7 +81,8 @@ npx wendkeep memory status --gate --vault .MyApp-vault
 npx wendkeep memory reconcile old --by-session current --reason "delivery continued" --vault .MyApp-vault
 npx wendkeep memory reconcile old --by-session current --reason "delivery continued" --apply --vault .MyApp-vault
 npx wendkeep validate-memory .MyApp-vault/.brain/CORE.md
-npx wendkeep memory promote candidate-123 --vault .MyApp-vault
+npx wendkeep memory promote candidate-123 --event mem-selected --vault .MyApp-vault
+npx wendkeep memory reject candidate-456 --vault .MyApp-vault
 ```
 
 ## Expected result
@@ -97,6 +105,9 @@ of a global projection that has already advanced with concurrent events.
   `memory reconcile` dry run before authorizing `--apply`; the command fails when the ambiguous
   attempt already contains event IDs.
 - Ordinary pending candidate: recoverable warning, requiring human choice when appropriate.
+- `promote` reports that `--event` is required: inspect the candidate `event_ids`, compare their
+  provenance/value, and name the winner explicitly. An ID outside the candidate fails without
+  mutating the ledger or projections.
 - Missing `event_cursor` or mismatched v2 hash: preserve the bundle and assess `memory repair`.
 - `validate-memory --vault` fails on legacy: validate CORE only or migrate first.
 

package/docs/pt-BR/commands/getting-started.md

@@ -79,6 +79,14 @@ e adiciona `wendkeep-vault`. Se o JSON existente for inválido, o arquivo origin
 a byte intacto e a proposta reconciliada é gravada em `.mcp.json.new`. Desde a versão 0.65, essa
 composição pertence ao kernel MCP privado, sem alterar comandos, flags ou a superfície npm pública.
 
+As regras puras que projetam os hooks de Claude/Codex e interpretam envelopes, transcripts, uso e
+identidade pertencem ao workspace privado `@wendkeep/integrations`. As fachadas históricas mantêm
+os efeitos de stdin/stdout, ambiente, filesystem, Vault e registry. Isso não acrescenta comandos ou
+flags, não altera hooks ou sessões e não exige migração de cofre, config, paths ou schemas. MCP e
+Integrations permanecem adapters irmãos sem dependência, e a direção continua
+`cli/mcp/integrations/pi → Harness → Vault`. Tudo permanece dentro do único pacote publicado
+`wendkeep`; não existe `wendkeep/integrations` público. A próxima fase modular é Pi.
+
 ## Erros comuns e diagnóstico
 
 - Cofre errado: confira `.wendkeep.json` e rode `wendkeep doctor --vault <path>`.

package/docs/pt-BR/commands/memory-migration.md

@@ -64,7 +64,8 @@ revision 1. Repetir esse prompt ou Stop não duplica evento/revision.
 - Bundle v2 parcial/corrompido: use status e repair; migração não é ferramenta de corrupção.
 - Primeiro Stop pós-migração fica `ambiguous`: confirme que o `turn_id` pertence ao transcript e
   que `UserPromptSubmit` abriu/avançou a activation de recuperação.
-- Candidates numerosos: curate gradualmente com `memory promote`/`memory reject`.
+- Candidates numerosos: curate gradualmente com `memory promote`/`memory reject`; conflitos
+  exigem `memory promote <candidate> --event <event-id>` para escolher o vencedor explicitamente.
 - Warning legado após apply: confirme o vault efetivamente selecionado e o vínculo do projeto.
 
 ## Próximos passos

package/docs/pt-BR/commands/memory.md

@@ -26,7 +26,7 @@ Informe o vault explicitamente em automações. Preserve backups e evidências a
 npx wendkeep memory status [--gate] --vault <cofre>
 npx wendkeep memory repair --vault <cofre>
 npx wendkeep memory reconcile <sessão-ambígua> --by-session <sessão-sucessora> --reason <motivo> [--apply] --vault <cofre>
-npx wendkeep memory promote <candidate> --vault <cofre>
+npx wendkeep memory promote <candidate> [--event <event-id>] --vault <cofre>
 npx wendkeep memory reject <candidate> --vault <cofre>
 npx wendkeep validate-memory [caminho-do-CORE]
 npx wendkeep validate-memory --vault <cofre-v2>
@@ -61,7 +61,13 @@ npx wendkeep validate-memory --vault <cofre-v2>
   candidates, registry, notas, backups, temporários e sidecars antes de ler ou escrever. Junction,
   symlink, reparse point ou hardlink falham fechados sem tocar bytes externos. Locks publicam owner
   e lease atomicamente, não colhem PID vivo apenas por idade e só liberam a lease adquirida.
-- `promote`/`reject` acrescentam decisão auditável; nunca reescrevem o ledger no lugar.
+- `promote`/`reject` acrescentam uma decisão auditável e idempotente ao ledger. Replay e repair
+  preservam a decisão e não recriam o candidate resolvido. Para candidate `conflict`, `promote`
+  exige `--event <event-id>` pertencente ao candidate; não há vencedor implícito por data ou ID.
+  `reject` preserva o valor operacional atual. Candidate `blocked_by_core` só pode ser rejeitado:
+  promover exige antes alterar CORE pela curadoria canônica. Se o evento escolhido ainda pertence
+  ao último attempt `projected` correspondente, a promoção também atualiza causalmente checkpoint
+  e espelho; o JSON retorna `checkpointRefreshed`, e um attempt concorrente mais novo não é tocado.
 - `validate-memory <CORE.md>` valida cap de 25 linhas, seções e segredos.
 - `validate-memory --vault` exige bundle v2 completo; não é o gate correto para vault legado.
 
@@ -72,7 +78,8 @@ npx wendkeep memory status --gate --vault .MeuApp-vault
 npx wendkeep memory reconcile antiga --by-session atual --reason "entrega continuada" --vault .MeuApp-vault
 npx wendkeep memory reconcile antiga --by-session atual --reason "entrega continuada" --apply --vault .MeuApp-vault
 npx wendkeep validate-memory .MeuApp-vault/.brain/CORE.md
-npx wendkeep memory promote candidate-123 --vault .MeuApp-vault
+npx wendkeep memory promote candidate-123 --event mem-escolhido --vault .MeuApp-vault
+npx wendkeep memory reject candidate-456 --vault .MeuApp-vault
 ```
 
 ## Resultado esperado
@@ -94,6 +101,9 @@ prefixo válido de uma projeção global que já avançou com eventos concorrent
   ambiguidade for comprovadamente substituída por uma sessão sucessora, revise o dry-run de
   `memory reconcile` antes de autorizar `--apply`; o comando falha se o attempt ambíguo tiver IDs.
 - Candidate pendente comum: warning recuperável, exige decisão humana quando apropriado.
+- `promote` informa que `--event` é obrigatório: leia os `event_ids` do candidate, compare a
+  proveniência/valor e indique explicitamente o vencedor. ID que não pertence ao candidate falha
+  sem mutar ledger ou projeções.
 - `event_cursor` ausente ou hash divergente em v2: preserve o bundle e avalie `memory repair`.
 - `validate-memory --vault` falha no legado: valide apenas CORE ou migre primeiro.
 

package/hooks/brain-core.mjs

@@ -1,159 +1,159 @@
-// .agent/hooks/brain-core.mjs
-// Camada fria do brain: indexa o frontmatter das notas de sessão (0 token LLM).
-import { existsSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
-import { basename, join } from 'node:path';
-import { ensureDir, stripYamlQuotes, toVaultRelative } from './obsidian-common.mjs';
-import { getLocale } from './locale.mjs';
-
-export function brainDir(vaultBase) {
-  return join(vaultBase, '.brain');
-}
-
-// Frontmatter YAML simples: escalares `k: v` + listas `k:` seguido de `  - item`.
-export function parseFrontmatter(content) {
-  const m = content.match(/^---\n([\s\S]*?)\n---/);
-  if (!m) return {};
-  const data = {};
-  const lines = m[1].split('\n');
-  for (let i = 0; i < lines.length; i++) {
-    const kv = lines[i].match(/^([\w-]+):\s*(.*)$/);
-    if (!kv) continue;
-    const key = kv[1];
-    const val = kv[2];
-    if (val === '') {
-      const list = [];
-      while (i + 1 < lines.length && /^\s+-\s+/.test(lines[i + 1])) {
-        list.push(stripYamlQuotes(lines[++i].replace(/^\s+-\s+/, '').trim()));
-      }
-      data[key] = list.length ? list : '';
-    } else {
-      data[key] = stripYamlQuotes(val.trim());
-    }
-  }
-  return data;
-}
-
-function walkMd(dir) {
-  const out = [];
-  let entries;
-  try { entries = readdirSync(dir, { withFileTypes: true }); } catch { return out; }
-  for (const e of entries) {
-    const fp = join(dir, e.name);
-    if (e.isDirectory()) out.push(...walkMd(fp));
-    else if (e.name.endsWith('.md')) out.push(fp);
-  }
-  return out;
-}
-
-const DERIVED_RE = /\[\[(0[456]-[^\]|]+?)(?:\|[^\]]*)?\]\]/g;
-function derivedLinks(content) {
-  const dec = new Set(), bug = new Set(), lea = new Set();
-  let m;
-  while ((m = DERIVED_RE.exec(content))) {
-    const t = m[1];
-    if (t.startsWith('04-')) dec.add(t);
-    else if (t.startsWith('05-')) bug.add(t);
-    else if (t.startsWith('06-')) lea.add(t);
-  }
-  return { decisions: [...dec], bugs: [...bug], learnings: [...lea] };
-}
-
-// Varre 02-Sessões/** e regrava .brain/index.jsonl inteiro. Provider-agnóstico.
-export function buildBrainIndex(vaultBase) {
-  const rows = [];
-  for (const fp of walkMd(join(vaultBase, getLocale(vaultBase).folders.sessions))) {
-    let content;
-    try { content = readFileSync(fp, 'utf8'); } catch { continue; }
-    const fm = parseFrontmatter(content);
-    if (fm.type && fm.type !== 'session') continue;
-    const der = derivedLinks(content);
-    rows.push({
-      session_id: fm.session_id || '',
-      date: fm.date || '',
-      provider: fm.provider || '',
-      status: fm.status || '',
-      summary: fm.summary || '',
-      file: toVaultRelative(vaultBase, fp),
-      tags: Array.isArray(fm.tags) ? fm.tags : (fm.tags ? [fm.tags] : []),
-      decisions: der.decisions,
-      bugs: der.bugs,
-      learnings: der.learnings,
-    });
-  }
-  rows.sort((a, b) => (a.date + a.file).localeCompare(b.date + b.file));
-  ensureDir(brainDir(vaultBase));
-  const out = rows.map((r) => JSON.stringify(r)).join('\n') + (rows.length ? '\n' : '');
-  writeFileSync(join(brainDir(vaultBase), 'index.jsonl'), out, 'utf8');
-  return rows;
-}
-
-// Lê o índice gravado (linhas JSONL). Usado pelo recall e pelo digest.
-export function loadIndex(vaultBase) {
-  try {
-    return readFileSync(join(brainDir(vaultBase), 'index.jsonl'), 'utf8')
-      .split('\n').filter(Boolean).map((l) => JSON.parse(l));
-  } catch {
-    return [];
-  }
-}
-
-const DIGEST_CAPS = { decisions: 5, sessions: 4, bugs: 2, learnings: 2 };
-
-function adrNumber(path) {
-  const m = path.match(/ADR-(\d+)/);
-  return m ? Number(m[1]) : -1;
-}
-
-// Destila index.jsonl em .brain/DIGEST.md (camada quente, determinístico, 0 token LLM).
-// Cap por construção: 1 header + 13 itens (5/4/2/2) + 1 pointer = máx 15 linhas.
-export function buildBrainDigest(vaultBase, rows = null) {
-  const data = rows ?? loadIndex(vaultBase);
-  const byDateDesc = [...data].sort((a, b) =>
-    String(b.date || '').localeCompare(String(a.date || '')) || String(b.file || '').localeCompare(String(a.file || '')));
-
-  const seen = new Set();
-  const pick = (kind, max) => {
-    const out = [];
-    for (const r of byDateDesc) {
-      for (const p of r[kind] || []) {
-        if (out.length >= max) return out;
-        if (!seen.has(p)) { seen.add(p); out.push(p); }
-      }
-    }
-    return out;
-  };
-
-  // The digest is INJECTED into every session, so a dead wikilink is dead weight in the model's
-  // context. Keep only targets that resolve to a real note (by vault-relative path or basename)
-  // and drop placeholder paths (a truncated `…` from a summary line). `pick` collects extra so
-  // caps still fill after filtering.
-  const known = new Set();
-  for (const r of data) {
-    const rel = String(r.file || '').replace(/\.md$/i, '');
-    if (rel) { known.add(rel); known.add(basename(rel)); }
-  }
-  const resolves = (p) => {
-    const t = String(p || '').replace(/\.md$/i, '').trim();
-    if (!t || t.includes('...') || t.includes('…')) return false;
-    return known.has(t) || known.has(basename(t)) || existsSync(join(vaultBase, `${t}.md`));
-  };
-  const pickLive = (kind, max) => pick(kind, max * 4).filter(resolves).slice(0, max);
-
-  const decisions = pickLive('decisions', DIGEST_CAPS.decisions).sort((a, b) => adrNumber(b) - adrNumber(a));
-  const sessions = byDateDesc.slice(0, DIGEST_CAPS.sessions);
-  const bugs = pickLive('bugs', DIGEST_CAPS.bugs);
-  const learnings = pickLive('learnings', DIGEST_CAPS.learnings);
-
-  const lines = ['<!-- AUTO-GERADO por brain-core.mjs (0 token LLM). NÃO editar. Rebuild: node .agent/hooks/brain-reindex.mjs -->'];
-  for (const d of decisions) lines.push(`- Decisão: [[${d}]]`);
-  for (const s of sessions) lines.push(`- Sessão ${s.date} (${s.provider || '?'}): ${s.summary || s.file} → [[${String(s.file || '').replace(/\.md$/, '')}]]`);
-  for (const b of bugs) lines.push(`- Bug: [[${b}]]`);
-  for (const l of learnings) lines.push(`- Aprendizado: [[${l}]]`);
-
-  const shown = sessions.length;
-  if (data.length > shown) lines.push(`- +${data.length - shown} mais no índice — use /brain-recall <tópico>`);
-
-  ensureDir(brainDir(vaultBase));
-  writeFileSync(join(brainDir(vaultBase), 'DIGEST.md'), lines.join('\n') + '\n', 'utf8');
-  return lines;
-}
+// .agent/hooks/brain-core.mjs
+// Camada fria do brain: indexa o frontmatter das notas de sessão (0 token LLM).
+import { existsSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { basename, join } from 'node:path';
+import { ensureDir, stripYamlQuotes, toVaultRelative } from './obsidian-common.mjs';
+import { getLocale } from './locale.mjs';
+
+export function brainDir(vaultBase) {
+  return join(vaultBase, '.brain');
+}
+
+// Frontmatter YAML simples: escalares `k: v` + listas `k:` seguido de `  - item`.
+export function parseFrontmatter(content) {
+  const m = content.match(/^---\n([\s\S]*?)\n---/);
+  if (!m) return {};
+  const data = {};
+  const lines = m[1].split('\n');
+  for (let i = 0; i < lines.length; i++) {
+    const kv = lines[i].match(/^([\w-]+):\s*(.*)$/);
+    if (!kv) continue;
+    const key = kv[1];
+    const val = kv[2];
+    if (val === '') {
+      const list = [];
+      while (i + 1 < lines.length && /^\s+-\s+/.test(lines[i + 1])) {
+        list.push(stripYamlQuotes(lines[++i].replace(/^\s+-\s+/, '').trim()));
+      }
+      data[key] = list.length ? list : '';
+    } else {
+      data[key] = stripYamlQuotes(val.trim());
+    }
+  }
+  return data;
+}
+
+function walkMd(dir) {
+  const out = [];
+  let entries;
+  try { entries = readdirSync(dir, { withFileTypes: true }); } catch { return out; }
+  for (const e of entries) {
+    const fp = join(dir, e.name);
+    if (e.isDirectory()) out.push(...walkMd(fp));
+    else if (e.name.endsWith('.md')) out.push(fp);
+  }
+  return out;
+}
+
+const DERIVED_RE = /\[\[(0[456]-[^\]|]+?)(?:\|[^\]]*)?\]\]/g;
+function derivedLinks(content) {
+  const dec = new Set(), bug = new Set(), lea = new Set();
+  let m;
+  while ((m = DERIVED_RE.exec(content))) {
+    const t = m[1];
+    if (t.startsWith('04-')) dec.add(t);
+    else if (t.startsWith('05-')) bug.add(t);
+    else if (t.startsWith('06-')) lea.add(t);
+  }
+  return { decisions: [...dec], bugs: [...bug], learnings: [...lea] };
+}
+
+// Varre 02-Sessões/** e regrava .brain/index.jsonl inteiro. Provider-agnóstico.
+export function buildBrainIndex(vaultBase) {
+  const rows = [];
+  for (const fp of walkMd(join(vaultBase, getLocale(vaultBase).folders.sessions))) {
+    let content;
+    try { content = readFileSync(fp, 'utf8'); } catch { continue; }
+    const fm = parseFrontmatter(content);
+    if (fm.type && fm.type !== 'session') continue;
+    const der = derivedLinks(content);
+    rows.push({
+      session_id: fm.session_id || '',
+      date: fm.date || '',
+      provider: fm.provider || '',
+      status: fm.status || '',
+      summary: fm.summary || '',
+      file: toVaultRelative(vaultBase, fp),
+      tags: Array.isArray(fm.tags) ? fm.tags : (fm.tags ? [fm.tags] : []),
+      decisions: der.decisions,
+      bugs: der.bugs,
+      learnings: der.learnings,
+    });
+  }
+  rows.sort((a, b) => (a.date + a.file).localeCompare(b.date + b.file));
+  ensureDir(brainDir(vaultBase));
+  const out = rows.map((r) => JSON.stringify(r)).join('\n') + (rows.length ? '\n' : '');
+  writeFileSync(join(brainDir(vaultBase), 'index.jsonl'), out, 'utf8');
+  return rows;
+}
+
+// Lê o índice gravado (linhas JSONL). Usado pelo recall e pelo digest.
+export function loadIndex(vaultBase) {
+  try {
+    return readFileSync(join(brainDir(vaultBase), 'index.jsonl'), 'utf8')
+      .split('\n').filter(Boolean).map((l) => JSON.parse(l));
+  } catch {
+    return [];
+  }
+}
+
+const DIGEST_CAPS = { decisions: 5, sessions: 4, bugs: 2, learnings: 2 };
+
+function adrNumber(path) {
+  const m = path.match(/ADR-(\d+)/);
+  return m ? Number(m[1]) : -1;
+}
+
+// Destila index.jsonl em .brain/DIGEST.md (camada quente, determinístico, 0 token LLM).
+// Cap por construção: 1 header + 13 itens (5/4/2/2) + 1 pointer = máx 15 linhas.
+export function buildBrainDigest(vaultBase, rows = null) {
+  const data = rows ?? loadIndex(vaultBase);
+  const byDateDesc = [...data].sort((a, b) =>
+    String(b.date || '').localeCompare(String(a.date || '')) || String(b.file || '').localeCompare(String(a.file || '')));
+
+  const seen = new Set();
+  const pick = (kind, max) => {
+    const out = [];
+    for (const r of byDateDesc) {
+      for (const p of r[kind] || []) {
+        if (out.length >= max) return out;
+        if (!seen.has(p)) { seen.add(p); out.push(p); }
+      }
+    }
+    return out;
+  };
+
+  // The digest is INJECTED into every session, so a dead wikilink is dead weight in the model's
+  // context. Keep only targets that resolve to a real note (by vault-relative path or basename)
+  // and drop placeholder paths (a truncated `…` from a summary line). `pick` collects extra so
+  // caps still fill after filtering.
+  const known = new Set();
+  for (const r of data) {
+    const rel = String(r.file || '').replace(/\.md$/i, '');
+    if (rel) { known.add(rel); known.add(basename(rel)); }
+  }
+  const resolves = (p) => {
+    const t = String(p || '').replace(/\.md$/i, '').trim();
+    if (!t || t.includes('...') || t.includes('…')) return false;
+    return known.has(t) || known.has(basename(t)) || existsSync(join(vaultBase, `${t}.md`));
+  };
+  const pickLive = (kind, max) => pick(kind, max * 4).filter(resolves).slice(0, max);
+
+  const decisions = pickLive('decisions', DIGEST_CAPS.decisions).sort((a, b) => adrNumber(b) - adrNumber(a));
+  const sessions = byDateDesc.slice(0, DIGEST_CAPS.sessions);
+  const bugs = pickLive('bugs', DIGEST_CAPS.bugs);
+  const learnings = pickLive('learnings', DIGEST_CAPS.learnings);
+
+  const lines = ['<!-- AUTO-GERADO por brain-core.mjs (0 token LLM). NÃO editar. Rebuild: node .agent/hooks/brain-reindex.mjs -->'];
+  for (const d of decisions) lines.push(`- Decisão: [[${d}]]`);
+  for (const s of sessions) lines.push(`- Sessão ${s.date} (${s.provider || '?'}): ${s.summary || s.file} → [[${String(s.file || '').replace(/\.md$/, '')}]]`);
+  for (const b of bugs) lines.push(`- Bug: [[${b}]]`);
+  for (const l of learnings) lines.push(`- Aprendizado: [[${l}]]`);
+
+  const shown = sessions.length;
+  if (data.length > shown) lines.push(`- +${data.length - shown} mais no índice — use /brain-recall <tópico>`);
+
+  ensureDir(brainDir(vaultBase));
+  writeFileSync(join(brainDir(vaultBase), 'DIGEST.md'), lines.join('\n') + '\n', 'utf8');
+  return lines;
+}