wendkeep 0.73.0 → 0.75.0

package/CHANGELOG.md

@@ -4,6 +4,72 @@ 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.75.0] — 2026-08-20
+
+### Added
+
+- **Identidades SQL escopadas por projeto.** Sessões, agentes, rollups, chamadas e transcripts
+  mantêm chaves internas derivadas de `project_id` + identificador externo, constraints compostas
+  e foreign keys que carregam o projeto. Colisões deliberadas entre projetos ficam isoladas.
+- **Migrações comprováveis.** Cada arquivo de schema recebe checksum; uma migração estrutural de
+  base existente cria backup consistente antes da transação e pode ser retomada com segurança.
+- **Reconciliação explícita.** `observer reconcile` reserva a varredura integral para bootstrap,
+  reparo e comprovação de paridade por hash, localmente ou contra o serviço.
+- **Outbox observável.** `doctor` informa lotes, eventos, bytes e idade; uma lease admite apenas um
+  publisher e batches do mesmo escopo são coalescidos.
+
+### Changed
+
+- **Publicação incremental nos hooks.** `SessionStart` apenas drena, `Stop` lê uma sessão e
+  `SubagentStop` somente o transcript afetado. `note new` e `change archive` enfileiram diretamente
+  os documentos que escreveram. O file store antigo deixa de receber publicação viva e permanece
+  apenas como fonte de migração.
+- **Schema SQL 5.** O mesmo `session_id`, `agent_id`, `call_id`, `transcript_id` ou `rollup_key`
+  pode existir em projetos diferentes sem disputar uma linha global.
+
+### Fixed
+
+- **Ingest atômico por evento.** Cada evento usa `SAVEPOINT ingest_one`; qualquer falha reverte o
+  registro de ingestão e todas as projeções antes de o batch continuar. Retry permanece idempotente.
+- **Chamadas incrementais estáveis.** Turnos concluídos usam identidade causal estável, evitando
+  duplicação quando um transcript cresce após a primeira publicação.
+
+### Performance
+
+- O caminho de hook não varre mais o Vault. A fixture de publicação incremental comprova
+  `p95 < 200 ms`, uma sessão lida por `Stop` e zero documentos lidos por `SessionStart`.
+
+## [0.74.0] — 2026-08-20
+
+### Added
+
+- **Registradores de memória escopados.** Eventos novos declaram escopo de projeto, work session,
+  change, branch ou worktree. HEADs de branches paralelas coexistem, enquanto decisões,
+  constraints e blockers realmente incompatíveis continuam sob curadoria humana.
+- **Migração append-only de escopo.** `memory rescope` mostra uma prévia sem valores e
+  `memory rescope --apply` anexa eventos de reescopo sem reescrever o ledger histórico; retry é
+  idempotente e candidates ambíguos não recebem vencedor automático.
+- **Recall baseado em evidências.** O índice `.brain/EVIDENCE_INDEX.jsonl` divide Markdown por
+  headings, parágrafos, decisões, tarefas, requisitos e evidências, preservando origem, heading,
+  autoridade, validade, sessão, work session, change e hash.
+- **Context broker por prompt.** `UserPromptSubmit` consulta o índice local, aplica ranking lexical
+  BM25 com frase exata, peso por campo, autoridade, validade, recência limitada e diversidade, e
+  injeta somente os melhores trechos dentro de um budget explícito.
+- **FTS5 no Observer.** O schema SQL 4 mantém chunks por projeto, faz feature probe de FTS5 e usa o
+  mesmo ranking/proveniência do Keep Core com fallback lexical quando a extensão não está disponível.
+
+### Changed
+
+- **Ambiguidade fica isolada.** Uma chave conflitante é omitida da projeção operacional e recebe
+  marcador de revisão; CORE e registros independentes continuam disponíveis.
+- **`/brain-recall` retorna passagens.** Resultados agora apontam para o trecho do match e incluem
+  arquivo, heading, autoridade, data e validade, em vez de retornar somente nomes de sessões.
+
+### Performance
+
+- Documentos excepcionalmente grandes usam amostragem distribuída limitada a 4 MiB no índice de
+  chunks, preservando o transporte gzip e evitando trabalho proporcional a transcripts gigantes.
+
 ## [0.73.0] — 2026-08-20
 
 ### Added

package/README.en.md

@@ -84,11 +84,11 @@ Decisions, dead ends, the reason you chose X over Y — gone next session. The p
 |---|---|
 | **Capture** — every turn, on disk | `SessionStart` / `Stop` hooks write each session to a dated Markdown note: prompts, iterations, files touched, wikilinks. |
 | **Derive** — decisions, bugs, learnings | Pulled from the transcript into their own notes, backlinked to the session. Your history becomes navigable, not archival. |
-| **Recall** — injected back | Canonical `CORE` + operational `SHARED_MEMORY`, with explicit budgets, are injected on `startup`, `/clear`, and `/compact`; `DIGEST` remains a deep-recall index and legacy fallback. |
+| **Recall** — injected back | Canonical `CORE` + operational `SHARED_MEMORY` enter on `startup`, `/clear`, and `/compact`; on every prompt, the local chunk index selects a few passages with source, authority, and validity under an explicit budget. |
 | **Cost** — what it all cost | Per‑model, cache‑aware token pricing per session — plus `cost --trend` with a run‑rate projection across the whole vault; research previews without a final rate remain unestimated. |
 | **Multi‑agent** — one vault, both agents | `init` wires the session hooks into `.claude/settings.json` *and* `.codex/hooks.json`, and every note is tagged with the agent that wrote it: Claude Code is detected from its environment, anything else is recorded as Codex. One shared graph, whichever agent you are in. |
 | **Local‑first** — no cloud, no account | Everything is plain Markdown on your disk. An optional MCP server (`@bitbonsai/mcpvault`) lets the agent read/write the vault. |
-| **Local Observer** — many projects, one view | `wendkeep observer` keeps documents, sessions, agents, tokens, costs, calls, and transcripts in the Docker volume SQLite database; every project gets a **Consumption** tab in the read-only dashboard at `http://127.0.0.1:8787/`, loopback has no token, and unavailable hooks use a gzip outbox without blocking the session, including large transcripts. |
+| **Local Observer** — many projects, one view | `wendkeep observer` keeps documents, FTS5 chunks, sessions, agents, tokens, costs, calls, and transcripts in SQLite. Identities and foreign keys are project-scoped; each event is atomic. Hooks publish only what changed, while `observer reconcile` reserves full scans for explicit recovery. |
 
 During historical migration, the Observer preserves differences between frontmatter totals and the
 ledger as explicit reconciliation rows, and disambiguates duplicate `session_id` values per file
@@ -100,7 +100,7 @@ The Codex scope guard treats `commit`, `push`, `pull`, `merge`, `publish`, and d
 operations as independent capabilities, including inside compound commands.
 
 - Node.js ≥ 18
-- An AI coding agent with hooks. `init` wires **Claude Code** and **Codex** automatically — Codex gets eight compatible hooks, including the scoped `PreToolUse` guard, and enumerates them untrusted, so approve its “Hooks need review” prompt once at startup (see [Notes & roadmap](#notes--roadmap))
+- An AI coding agent with hooks. `init` wires **Claude Code** and **Codex** automatically — Codex gets twelve compatible hooks, including per-prompt recall and the scoped `PreToolUse` guard, and enumerates them untrusted, so approve its “Hooks need review” prompt once at startup (see [Notes & roadmap](#notes--roadmap))
 - Obsidian (to view the graph) — optional but the point
 
 ## Install & set up
@@ -115,7 +115,7 @@ npx wendkeep init
 
 1. Create the vault folder taxonomy and a templated `README.md` (default vault: `<project>/.<project-name>-vault`, e.g. `.MyApp-vault`; override with `--vault`).
 2. Write a provider-neutral **`.wendkeep.json`** binding at the project root and a matching `.brain/PROJECT.json` marker in the vault, then merge the session hooks into **`.claude/settings.json`**. The binding is provider-neutral by design: any agent resolves the same vault from its session `cwd`, with no machine-global environment variable. Older registrations already in `.claude/settings.json` are adopted automatically.
-3. Wire the Codex hooks in **`.codex/hooks.json`** — eleven compatible entries: `brain-inject` + `session-start` + `observer-publish` on `SessionStart`, `session-ensure` + `change-context` on `UserPromptSubmit`, `session-stop` + `observer-publish` + `change-nag` on `Stop`, `subagent-stop` + `observer-publish` on `SubagentStop`, and `change-guard` on `PreToolUse` for `Bash`, `exec_command`, `apply_patch`, and mutable MCP tools, always in the `npx wendkeep hook <name>` form. `observer-publish` keeps the sanitized index projection and also sends the local SQL authority with documents, consumption, and transcripts; it does not replace the local lifecycle. The guard accepts object, raw-string, and argv Codex payloads; before a mutation it compares the session with the project, Git root, remote, branch, and worktree, denying missing or divergent targets. The other four stay out because Codex offers no equivalent payload, tool, or event: `change-warn` (no reliable `tool_input.file_path`), `plan-capture` (no `ExitPlanMode`), `decision-capture` (`AskUserQuestion` is Claude-only), and `task-log` (`TaskCompleted` is not in Codex's event enum). Codex scope blocks use `permissionDecision: "deny"`; `ask` is never emitted in `PreToolUse`. The merge remains non-destructive, preserves third-party hooks, and migrates legacy `timeout` to `timeoutSec`. **Codex enumerates every hook as untrusted and runs none until you approve the “Hooks need review” prompt at startup — `init` cannot pre-approve them**.
+3. Wire the Codex hooks in **`.codex/hooks.json`** — twelve compatible entries: `brain-inject` + `session-start` + `observer-publish` on `SessionStart`, `session-ensure` + `evidence-context` + `change-context` on `UserPromptSubmit`, `session-stop` + `observer-publish` + `change-nag` on `Stop`, `subagent-stop` + `observer-publish` on `SubagentStop`, and `change-guard` on `PreToolUse` for `Bash`, `exec_command`, `apply_patch`, and mutable MCP tools, always in the `npx wendkeep hook <name>` form. For the Observer, `SessionStart` only drains the outbox, `Stop` enqueues the changed session, and `SubagentStop` enqueues only the affected transcript; full scanning is explicit through `observer reconcile`. The guard accepts object, raw-string, and argv Codex payloads; before a mutation it compares the session with the project, Git root, remote, branch, and worktree, denying missing or divergent targets. The other four stay out because Codex offers no equivalent payload, tool, or event: `change-warn` (no reliable `tool_input.file_path`), `plan-capture` (no `ExitPlanMode`), `decision-capture` (`AskUserQuestion` is Claude-only), and `task-log` (`TaskCompleted` is not in Codex's event enum). Codex scope blocks use `permissionDecision: "deny"`; `ask` is never emitted in `PreToolUse`. The merge remains non-destructive, preserves third-party hooks, and migrates legacy `timeout` to `timeoutSec`. **Codex enumerates every hook as untrusted and runs none until you approve the “Hooks need review” prompt at startup — `init` cannot pre-approve them**.
 4. Add the **`wendkeep-vault`** MCP server to `.mcp.json` so the agent can read/write the vault. Skip with `--no-mcp` — e.g. when the agent already has a vault MCP. (`--no-mcp` skips *only wendkeep's own* MCP; companion MCPs still follow `--companions`.)
 5. Offer to pin **companion** plugins/MCP (multi-choice; **none** pre-checked — wendkeep is a neutral harness and presumes no third-party plugin). Each is wired the most agent-agnostic way it supports:
    - **`context-mode`** — context optimizer + FTS5 memory, wired as a Claude Code plugin. It ships its own MCP server, so wendkeep deliberately adds no `.mcp.json` entry (registering both cold-started two servers at once). On non-Claude agents, add the MCP by hand: `npx -y context-mode`.
@@ -125,7 +125,7 @@ npx wendkeep init
 
    Control with `--companions <csv>` or `--no-companions`. The Claude Code plugin layer (`extraKnownMarketplaces` + `enabledPlugins`) is wired as a bonus where the companion has one.
 6. Install a **color system** into the vault's `.obsidian/`: a CSS snippet that accents notes by type (session/decision/bug/learning, via the `cssclasses` the hooks emit) plus graph color groups by folder. Non-destructive merge into `appearance.json`/`graph.json`; skip with `--no-colors`. Re-apply it any time on an existing vault with `wendkeep theme sync` — Obsidian owns `graph.json` and can drop the color groups (a grey graph); the re-sync restores them without a full re-`init`.
-7. Seed **Shared Project Memory v2** without overwriting existing artifacts: `.brain/CORE.md` (hand-curated canonical truth), `.brain/SHARED_MEMORY.md` (generated operational state), `.brain/MEMORY_EVENTS.jsonl` (append-only ledger), `.brain/MEMORY_CANDIDATES.jsonl` (curation queue), and `.brain/COMPACTION_PROTOCOL.md`. The durable outbox appears under `.brain/memory-outbox/` when events exist; `DIGEST.md` and `index.jsonl` remain deep recall. Everything stays local to the vault.
+7. Seed **Shared Project Memory v2** without overwriting existing artifacts: `.brain/CORE.md`, `.brain/SHARED_MEMORY.md`, `.brain/MEMORY_EVENTS.jsonl`, `.brain/MEMORY_CANDIDATES.jsonl`, and `.brain/COMPACTION_PROTOCOL.md`. The durable outbox appears under `.brain/memory-outbox/`; `EVIDENCE_INDEX.jsonl` is rebuilt locally from chunks while `DIGEST.md`/`index.jsonl` remain compatible. Everything stays in the vault.
 8. Seed the **definitions + skills layer**: `.brain/agents/` + `.brain/skills/` (versioned source of truth), including the native process skills `wk-workflow` / `wk-tdd` / `wk-debugging` / `wk-brainstorming` / `wk-planning` / `wk-verify` (some ship templates — e.g. `wk-verify`'s `verdict-template.json` + reviewer prompt). `init` runs `wendkeep sync-defs` for you, delivering the skills to `.claude/skills/` and `.agents/skills/`, and the agent definitions (`.brain/agents/*.toml`) to `.codex/agents/`, plus a managed section in `AGENTS.md` that indexes the skills for Codex; `sync-defs --check` detects stale copies (re-run `sync-defs` after editing `.brain`).
 9. Seed the **change/spec lifecycle**: the `07-Specs/` + `08-Mudanças/` folders and a native `wendkeep.sensors.json` — critical memory validation/health sensors plus one for each of `typecheck` / `test` / `lint` / `build` found in your `package.json`. `memory-health` blocks delivery on corruption or projection divergence; semantic conflicts degrade only the affected keys and await curation. Pending outbox events and ordinary candidates are warnings. Add sensors with `wendkeep sensors add`. Drives `wendkeep change` / `wendkeep verify` — see **Change lifecycle** below.
 
@@ -240,7 +240,7 @@ The README is the map; the guides provide syntax, options, exit codes, examples,
 | **Notes and knowledge** | BUG/APR/ADR, repairs, renumbering, lessons, and dashboard | [Notes and knowledge](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/notes-and-knowledge.md) |
 | **Costs and observability** | safe dry-run, tri-state, aggregation, trends, and historical rebuild | [Costs and observability](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/costs-and-observability.md) |
 | **Maintenance and diagnostics** | doctor, frontier/manifest freshness, drift, version, and help | [Maintenance and diagnostics](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/maintenance-and-diagnostics.md) |
-| **Local Observer** | `observer serve`, registration, snapshots, outbox, and multi-project index | [Local Observer](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/observer.md) |
+| **Local Observer** | `observer serve`, registration, incremental publication, `reconcile`, outbox, and multi-project index | [Local Observer](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/observer.md) |
 
 Operations that deserve step-by-step guidance: [verify and exits 0/1/2](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/verify.md),
 [legacy-memory migration](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/memory-migration.md), and
@@ -332,9 +332,9 @@ spec, or ADR. If delivery requires a code/config edit, it pauses and work return
 `implementation`:
 
 ```bash
-npx wendkeep delivery start release-0-73-0 --allow git:merge --allow git:push --allow publish --source-change <slug> --source-commit <sha>
-npx wendkeep delivery status release-0-73-0
-npx wendkeep delivery finish release-0-73-0 --target main --ci-url <url> --version 0.73.0 --npm-integrity <sha512> --release-url <url>
+npx wendkeep delivery start release-0-74-0 --allow git:merge --allow git:push --allow publish --source-change <slug> --source-commit <sha>
+npx wendkeep delivery status release-0-74-0
+npx wendkeep delivery finish release-0-74-0 --target main --ci-url <url> --version 0.74.0 --npm-integrity <sha512> --release-url <url>
 ```
 
 If the harness does not record a lease, a small fix remains under the configured profile —
@@ -369,6 +369,8 @@ Hot memory now separates human authorship, operational state, and evidence:
 - **`SHARED_MEMORY.md` is generated operational state.** The `Stop` hook turns the session handoff into sanitized events; the projector deterministically reduces the ledger and publishes a verifiable revision, cursor, and hash. Facts are `verified` only with local evidence; unsupported reports remain `reported`, and disagreements become candidates for human judgment.
 - **`MEMORY_EVENTS.jsonl` is the append-only authority.** `Stop` makes events durable in the outbox before acknowledging the attempt; the projector runs outside the registry lock and retries reuse the same IDs. Repeating an identical `event_id`/payload is a no-op; reusing the ID with different bytes is observable corruption.
 - **`MEMORY_CANDIDATES.jsonl` is the curation queue.** Conflicts and legacy content are never silently promoted. `promote` and `reject` record the decision as a new event; promotion preserves the selected event's JSON type, session, activation/epoch, and source turn.
+- **Registers are scoped.** `git.local-head`, handoffs, verdicts, and change status carry project, work-session, change, branch, or worktree scope. Two branches do not create a global conflict; only events in the same scope and causal lineage may advance automatically.
+- **`EVIDENCE_INDEX.jsonl` is local recall.** Markdown is chunked by headings and blocks without requiring the Observer. Ranking combines BM25, exact phrases, field weights, authority, validity, bounded recency, and source diversity; `UserPromptSubmit` injects only relevant passages with provenance.
 
 Artifacts stay under `.brain/` only. Sanitization strips secrets, tokens, local paths, transcripts, and harness payloads both before persistence and before injection. Events carry a `project_id`, and one vault never accepts another project's events.
 
@@ -390,6 +392,8 @@ Codex uses `session_id`/`turn_id` plus transcript order, with no artificial caus
 npx --no-install wendkeep memory status --gate --vault .MyApp-vault
 npx --no-install wendkeep memory migrate --vault .MyApp-vault          # preview, zero writes
 npx --no-install wendkeep memory migrate --apply --vault .MyApp-vault  # backup + candidates + v2 bundle
+npx --no-install wendkeep memory rescope --vault .MyApp-vault          # preview without values
+npx --no-install wendkeep memory rescope --apply --vault .MyApp-vault  # append-only and idempotent
 ```
 
 ### Health and recovery

package/README.md

@@ -84,11 +84,11 @@ Decisions, dead ends, the reason you chose X over Y — gone next session. The p
 |---|---|
 | **Capture** — every turn, on disk | `SessionStart` / `Stop` hooks write each session to a dated Markdown note: prompts, iterations, files touched, wikilinks. |
 | **Derive** — decisions, bugs, learnings | Pulled from the transcript into their own notes, backlinked to the session. Your history becomes navigable, not archival. |
-| **Recall** — injected back | Canonical `CORE` + operational `SHARED_MEMORY`, with explicit budgets, are injected on `startup`, `/clear`, and `/compact`; `DIGEST` remains a deep-recall index and legacy fallback. |
+| **Recall** — injected back | Canonical `CORE` + operational `SHARED_MEMORY` enter on `startup`, `/clear`, and `/compact`; on every prompt, the local chunk index selects a few passages with source, authority, and validity under an explicit budget. |
 | **Cost** — what it all cost | Per‑model, cache‑aware token pricing per session — plus `cost --trend` with a run‑rate projection across the whole vault; research previews without a final rate remain unestimated. |
 | **Multi‑agent** — one vault, both agents | `init` wires the session hooks into `.claude/settings.json` *and* `.codex/hooks.json`, and every note is tagged with the agent that wrote it: Claude Code is detected from its environment, anything else is recorded as Codex. One shared graph, whichever agent you are in. |
 | **Local‑first** — no cloud, no account | Everything is plain Markdown on your disk. An optional MCP server (`@bitbonsai/mcpvault`) lets the agent read/write the vault. |
-| **Local Observer** — many projects, one view | `wendkeep observer` keeps documents, sessions, agents, tokens, costs, calls, and transcripts in the Docker volume SQLite database; every project gets a **Consumption** tab in the read-only dashboard at `http://127.0.0.1:8787/`, loopback has no token, and unavailable hooks use a gzip outbox without blocking the session, including large transcripts. |
+| **Local Observer** — many projects, one view | `wendkeep observer` keeps documents, FTS5 chunks, sessions, agents, tokens, costs, calls, and transcripts in SQLite. Identities and foreign keys are project-scoped; each event is atomic. Hooks publish only what changed, while `observer reconcile` reserves full scans for explicit recovery. |
 
 During historical migration, the Observer preserves differences between frontmatter totals and the
 ledger as explicit reconciliation rows, and disambiguates duplicate `session_id` values per file
@@ -100,7 +100,7 @@ The Codex scope guard treats `commit`, `push`, `pull`, `merge`, `publish`, and d
 operations as independent capabilities, including inside compound commands.
 
 - Node.js ≥ 18
-- An AI coding agent with hooks. `init` wires **Claude Code** and **Codex** automatically — Codex gets eight compatible hooks, including the scoped `PreToolUse` guard, and enumerates them untrusted, so approve its “Hooks need review” prompt once at startup (see [Notes & roadmap](#notes--roadmap))
+- An AI coding agent with hooks. `init` wires **Claude Code** and **Codex** automatically — Codex gets twelve compatible hooks, including per-prompt recall and the scoped `PreToolUse` guard, and enumerates them untrusted, so approve its “Hooks need review” prompt once at startup (see [Notes & roadmap](#notes--roadmap))
 - Obsidian (to view the graph) — optional but the point
 
 ## Install & set up
@@ -115,7 +115,7 @@ npx wendkeep init
 
 1. Create the vault folder taxonomy and a templated `README.md` (default vault: `<project>/.<project-name>-vault`, e.g. `.MyApp-vault`; override with `--vault`).
 2. Write a provider-neutral **`.wendkeep.json`** binding at the project root and a matching `.brain/PROJECT.json` marker in the vault, then merge the session hooks into **`.claude/settings.json`**. The binding is provider-neutral by design: any agent resolves the same vault from its session `cwd`, with no machine-global environment variable. Older registrations already in `.claude/settings.json` are adopted automatically.
-3. Wire the Codex hooks in **`.codex/hooks.json`** — eleven compatible entries: `brain-inject` + `session-start` + `observer-publish` on `SessionStart`, `session-ensure` + `change-context` on `UserPromptSubmit`, `session-stop` + `observer-publish` + `change-nag` on `Stop`, `subagent-stop` + `observer-publish` on `SubagentStop`, and `change-guard` on `PreToolUse` for `Bash`, `exec_command`, `apply_patch`, and mutable MCP tools, always in the `npx wendkeep hook <name>` form. `observer-publish` keeps the sanitized index projection and also sends the local SQL authority with documents, consumption, and transcripts; it does not replace the local lifecycle. The guard accepts object, raw-string, and argv Codex payloads; before a mutation it compares the session with the project, Git root, remote, branch, and worktree, denying missing or divergent targets. The other four stay out because Codex offers no equivalent payload, tool, or event: `change-warn` (no reliable `tool_input.file_path`), `plan-capture` (no `ExitPlanMode`), `decision-capture` (`AskUserQuestion` is Claude-only), and `task-log` (`TaskCompleted` is not in Codex's event enum). Codex scope blocks use `permissionDecision: "deny"`; `ask` is never emitted in `PreToolUse`. The merge remains non-destructive, preserves third-party hooks, and migrates legacy `timeout` to `timeoutSec`. **Codex enumerates every hook as untrusted and runs none until you approve the “Hooks need review” prompt at startup — `init` cannot pre-approve them**.
+3. Wire the Codex hooks in **`.codex/hooks.json`** — twelve compatible entries: `brain-inject` + `session-start` + `observer-publish` on `SessionStart`, `session-ensure` + `evidence-context` + `change-context` on `UserPromptSubmit`, `session-stop` + `observer-publish` + `change-nag` on `Stop`, `subagent-stop` + `observer-publish` on `SubagentStop`, and `change-guard` on `PreToolUse` for `Bash`, `exec_command`, `apply_patch`, and mutable MCP tools, always in the `npx wendkeep hook <name>` form. For the Observer, `SessionStart` only drains the outbox, `Stop` enqueues the changed session, and `SubagentStop` enqueues only the affected transcript; full scanning is explicit through `observer reconcile`. The guard accepts object, raw-string, and argv Codex payloads; before a mutation it compares the session with the project, Git root, remote, branch, and worktree, denying missing or divergent targets. The other four stay out because Codex offers no equivalent payload, tool, or event: `change-warn` (no reliable `tool_input.file_path`), `plan-capture` (no `ExitPlanMode`), `decision-capture` (`AskUserQuestion` is Claude-only), and `task-log` (`TaskCompleted` is not in Codex's event enum). Codex scope blocks use `permissionDecision: "deny"`; `ask` is never emitted in `PreToolUse`. The merge remains non-destructive, preserves third-party hooks, and migrates legacy `timeout` to `timeoutSec`. **Codex enumerates every hook as untrusted and runs none until you approve the “Hooks need review” prompt at startup — `init` cannot pre-approve them**.
 4. Add the **`wendkeep-vault`** MCP server to `.mcp.json` so the agent can read/write the vault. Skip with `--no-mcp` — e.g. when the agent already has a vault MCP. (`--no-mcp` skips *only wendkeep's own* MCP; companion MCPs still follow `--companions`.)
 5. Offer to pin **companion** plugins/MCP (multi-choice; **none** pre-checked — wendkeep is a neutral harness and presumes no third-party plugin). Each is wired the most agent-agnostic way it supports:
    - **`context-mode`** — context optimizer + FTS5 memory, wired as a Claude Code plugin. It ships its own MCP server, so wendkeep deliberately adds no `.mcp.json` entry (registering both cold-started two servers at once). On non-Claude agents, add the MCP by hand: `npx -y context-mode`.
@@ -125,7 +125,7 @@ npx wendkeep init
 
    Control with `--companions <csv>` or `--no-companions`. The Claude Code plugin layer (`extraKnownMarketplaces` + `enabledPlugins`) is wired as a bonus where the companion has one.
 6. Install a **color system** into the vault's `.obsidian/`: a CSS snippet that accents notes by type (session/decision/bug/learning, via the `cssclasses` the hooks emit) plus graph color groups by folder. Non-destructive merge into `appearance.json`/`graph.json`; skip with `--no-colors`. Re-apply it any time on an existing vault with `wendkeep theme sync` — Obsidian owns `graph.json` and can drop the color groups (a grey graph); the re-sync restores them without a full re-`init`.
-7. Seed **Shared Project Memory v2** without overwriting existing artifacts: `.brain/CORE.md` (hand-curated canonical truth), `.brain/SHARED_MEMORY.md` (generated operational state), `.brain/MEMORY_EVENTS.jsonl` (append-only ledger), `.brain/MEMORY_CANDIDATES.jsonl` (curation queue), and `.brain/COMPACTION_PROTOCOL.md`. The durable outbox appears under `.brain/memory-outbox/` when events exist; `DIGEST.md` and `index.jsonl` remain deep recall. Everything stays local to the vault.
+7. Seed **Shared Project Memory v2** without overwriting existing artifacts: `.brain/CORE.md`, `.brain/SHARED_MEMORY.md`, `.brain/MEMORY_EVENTS.jsonl`, `.brain/MEMORY_CANDIDATES.jsonl`, and `.brain/COMPACTION_PROTOCOL.md`. The durable outbox appears under `.brain/memory-outbox/`; `EVIDENCE_INDEX.jsonl` is rebuilt locally from chunks while `DIGEST.md`/`index.jsonl` remain compatible. Everything stays in the vault.
 8. Seed the **definitions + skills layer**: `.brain/agents/` + `.brain/skills/` (versioned source of truth), including the native process skills `wk-workflow` / `wk-tdd` / `wk-debugging` / `wk-brainstorming` / `wk-planning` / `wk-verify` (some ship templates — e.g. `wk-verify`'s `verdict-template.json` + reviewer prompt). `init` runs `wendkeep sync-defs` for you, delivering the skills to `.claude/skills/` and `.agents/skills/`, and the agent definitions (`.brain/agents/*.toml`) to `.codex/agents/`, plus a managed section in `AGENTS.md` that indexes the skills for Codex; `sync-defs --check` detects stale copies (re-run `sync-defs` after editing `.brain`).
 9. Seed the **change/spec lifecycle**: the `07-Specs/` + `08-Mudanças/` folders and a native `wendkeep.sensors.json` — critical memory validation/health sensors plus one for each of `typecheck` / `test` / `lint` / `build` found in your `package.json`. `memory-health` blocks delivery on corruption or projection divergence; semantic conflicts degrade only the affected keys and await curation. Pending outbox events and ordinary candidates are warnings. Add sensors with `wendkeep sensors add`. Drives `wendkeep change` / `wendkeep verify` — see **Change lifecycle** below.
 
@@ -240,7 +240,7 @@ The README is the map; the guides provide syntax, options, exit codes, examples,
 | **Notes and knowledge** | BUG/APR/ADR, repairs, renumbering, lessons, and dashboard | [Notes and knowledge](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/notes-and-knowledge.md) |
 | **Costs and observability** | safe dry-run, tri-state, aggregation, trends, and historical rebuild | [Costs and observability](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/costs-and-observability.md) |
 | **Maintenance and diagnostics** | doctor, frontier/manifest freshness, drift, version, and help | [Maintenance and diagnostics](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/maintenance-and-diagnostics.md) |
-| **Local Observer** | `observer serve`, registration, snapshots, outbox, and multi-project index | [Local Observer](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/observer.md) |
+| **Local Observer** | `observer serve`, registration, incremental publication, `reconcile`, outbox, and multi-project index | [Local Observer](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/observer.md) |
 
 Operations that deserve step-by-step guidance: [verify and exits 0/1/2](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/verify.md),
 [legacy-memory migration](https://github.com/rogersialves/wendkeep/blob/main/docs/en/commands/memory-migration.md), and
@@ -332,9 +332,9 @@ spec, or ADR. If delivery requires a code/config edit, it pauses and work return
 `implementation`:
 
 ```bash
-npx wendkeep delivery start release-0-73-0 --allow git:merge --allow git:push --allow publish --source-change <slug> --source-commit <sha>
-npx wendkeep delivery status release-0-73-0
-npx wendkeep delivery finish release-0-73-0 --target main --ci-url <url> --version 0.73.0 --npm-integrity <sha512> --release-url <url>
+npx wendkeep delivery start release-0-74-0 --allow git:merge --allow git:push --allow publish --source-change <slug> --source-commit <sha>
+npx wendkeep delivery status release-0-74-0
+npx wendkeep delivery finish release-0-74-0 --target main --ci-url <url> --version 0.74.0 --npm-integrity <sha512> --release-url <url>
 ```
 
 If the harness does not record a lease, a small fix remains under the configured profile —
@@ -369,6 +369,8 @@ Hot memory now separates human authorship, operational state, and evidence:
 - **`SHARED_MEMORY.md` is generated operational state.** The `Stop` hook turns the session handoff into sanitized events; the projector deterministically reduces the ledger and publishes a verifiable revision, cursor, and hash. Facts are `verified` only with local evidence; unsupported reports remain `reported`, and disagreements become candidates for human judgment.
 - **`MEMORY_EVENTS.jsonl` is the append-only authority.** `Stop` makes events durable in the outbox before acknowledging the attempt; the projector runs outside the registry lock and retries reuse the same IDs. Repeating an identical `event_id`/payload is a no-op; reusing the ID with different bytes is observable corruption.
 - **`MEMORY_CANDIDATES.jsonl` is the curation queue.** Conflicts and legacy content are never silently promoted. `promote` and `reject` record the decision as a new event; promotion preserves the selected event's JSON type, session, activation/epoch, and source turn.
+- **Registers are scoped.** `git.local-head`, handoffs, verdicts, and change status carry project, work-session, change, branch, or worktree scope. Two branches do not create a global conflict; only events in the same scope and causal lineage may advance automatically.
+- **`EVIDENCE_INDEX.jsonl` is local recall.** Markdown is chunked by headings and blocks without requiring the Observer. Ranking combines BM25, exact phrases, field weights, authority, validity, bounded recency, and source diversity; `UserPromptSubmit` injects only relevant passages with provenance.
 
 Artifacts stay under `.brain/` only. Sanitization strips secrets, tokens, local paths, transcripts, and harness payloads both before persistence and before injection. Events carry a `project_id`, and one vault never accepts another project's events.
 
@@ -390,6 +392,8 @@ Codex uses `session_id`/`turn_id` plus transcript order, with no artificial caus
 npx --no-install wendkeep memory status --gate --vault .MyApp-vault
 npx --no-install wendkeep memory migrate --vault .MyApp-vault          # preview, zero writes
 npx --no-install wendkeep memory migrate --apply --vault .MyApp-vault  # backup + candidates + v2 bundle
+npx --no-install wendkeep memory rescope --vault .MyApp-vault          # preview without values
+npx --no-install wendkeep memory rescope --apply --vault .MyApp-vault  # append-only and idempotent
 ```
 
 ### Health and recovery

package/docs/en/commands/memory.md

@@ -30,6 +30,7 @@ Pass the vault explicitly in automation. Preserve backups and evidence before re
 npx wendkeep memory status [--gate] --vault <vault>
 npx wendkeep memory curate --vault <vault>
 npx wendkeep memory candidates [--active] --vault <vault>
+npx wendkeep memory rescope [--apply] --vault <vault>
 npx wendkeep memory repair --vault <vault>
 npx wendkeep memory recover-attempt <session> [--apply] --vault <vault>
 npx wendkeep memory reconcile <ambiguous-session> --by-session <successor-session> --reason <reason> [--apply] --vault <vault>
@@ -51,7 +52,7 @@ npx wendkeep validate-memory --vault <v2-vault>
   non-TTY environment it exits `2` without changing bytes and recommends the advanced fallback
   `memory candidates --active`.
 - `memory candidates` is read-only and prints deterministic JSON containing only `candidate_id`,
-  `reason`, `status`, `memory_key`, and `event_ids`; it does not expose memory values or content and
+  `reason`, `status`, `memory_key`, scope when present, and `event_ids`; it does not expose memory values or content and
   does not create a lock or mutate the bundle. `--active` omits terminal candidates (`resolved`,
   `rejected`, and `superseded`). A missing status is normalized to `active`.
 - For `memory candidates`, exit `0` means a valid inventory (including empty or conflicted), exit
@@ -95,6 +96,18 @@ npx wendkeep validate-memory --vault <v2-vault>
   and its successor. Replay is CORE-aware, checkpoints use the physical ledger cursor, and the
   command neither rewrites ledger/CORE/notes nor consumes the outbox. Retrying the same applied
   decision is idempotent.
+- `memory rescope` is a dry run by default and lists only planned IDs, keys, and scopes. With
+  `--apply`, it appends explicit project, work-session, change, branch, or worktree events while
+  preserving historic bytes as the ledger prefix. Ambiguous candidates are neither migrated nor
+  assigned a winner; retry returns `unchanged`.
+- Registers such as `git.local-head`, `handoff.latest`, `quality.latest-*`, and
+  `change.<slug>.status` compete only inside the same scope. Automatic resolution still requires
+  the same project and causal lineage; incompatible decisions, constraints, and blockers remain
+  human-curated. An ambiguous key is omitted from SHARED without removing CORE or independent keys.
+- `.brain/EVIDENCE_INDEX.jsonl` chunks documents by heading and block and records file, heading,
+  type, change, session, work session, authority, date, validity, and hash. `/brain-recall` and the
+  `UserPromptSubmit` hook use BM25, exact phrase, field weights, authority, validity, bounded
+  recency, and diversity to return the matching passage with provenance.
 - Every memory path validates the physical topology of `.brain`, ledger, outbox, CORE, SHARED,
   candidates, registry, notes, backups, temporary files, and sidecars before reading or writing.
   Junctions, symlinks, reparse points, or hardlinks fail closed without touching external bytes.
@@ -136,6 +149,8 @@ npx wendkeep validate-memory --vault <v2-vault>
 npx wendkeep memory status --gate --vault .MyApp-vault
 npx wendkeep memory curate --vault .MyApp-vault
 npx wendkeep memory candidates --active --vault .MyApp-vault
+npx wendkeep memory rescope --vault .MyApp-vault
+npx wendkeep memory rescope --apply --vault .MyApp-vault
 npx wendkeep memory recover-attempt session-123 --vault .MyApp-vault
 npx wendkeep memory recover-attempt session-123 --apply --vault .MyApp-vault
 npx wendkeep memory reconcile old --by-session current --reason "delivery continued" --vault .MyApp-vault

package/docs/en/commands/observer.md

@@ -34,6 +34,7 @@ loopback reads remain open, while every mutation requires a Bearer token.
 npx wendkeep observer status --data-dir <directory> --json
 npx wendkeep observer register --project <project> --vault <vault> --data-dir <directory>
 npx wendkeep observer publish --project <project> --vault <vault> --data-dir <directory>
+npx wendkeep observer reconcile --project <project> --vault <vault> --data-dir <directory> [--url http://127.0.0.1:8787]
 npx wendkeep observer memory import --project <project> --vault <vault> --url http://127.0.0.1:8787 --token <token> --json
 npx wendkeep observer serve --host 127.0.0.1 --port 8787 --data-dir <directory> --token <token>
 ```
@@ -42,7 +43,7 @@ npx wendkeep observer serve --host 127.0.0.1 --port 8787 --data-dir <directory>
 
 - `--data-dir` selects the local event and index directory; the default is
   `WENDKEEP_OBSERVER_DATA_DIR` or `~/.wendkeep-observer`.
-- `--project` and `--vault` identify a project for `register`, `publish`, and `memory import`.
+- `--project` and `--vault` identify a project for `register`, `publish`, `reconcile`, and `memory import`.
 - `--host` accepts only `127.0.0.1`, `localhost`, or `::1`; other hosts are rejected before
   listening.
 - `--token` or `WENDKEEP_OBSERVER_TOKEN` authenticates mutations; `--allow-non-loopback` fails without one.
@@ -84,8 +85,8 @@ If the browser shows the shell but the list fails, check the service health at
 
 ## Expected result
 
-`register` stores `project_id`, name, version, and registration time. `publish` reads the local
-vault, produces the snapshot, and sends idempotent events to SQLite containing the complete content
+`register` stores `project_id`, name, version, and registration time. `publish` and `reconcile`
+perform an explicit full-vault scan and send idempotent events to SQLite containing the complete content
 of sessions, decisions, bugs, learnings, specs, changes, CORE, DIGEST, SHARED_MEMORY, brain state,
 agent sessions, cost rollups, and calls. Messages and transcripts are only sent by capture levels
 that explicitly enable them. The container stores everything in
@@ -96,10 +97,26 @@ cost/token total recorded in frontmatter is preserved through an explicit reconc
 the detailed ledger does not add up; that row does not invent calls. Historical sessions sharing
 one `session_id` receive a canonical per-file identity so one rollup cannot overwrite the other.
 
+In schema 5, sessions, agents, rollups, calls, and transcripts use internal identities derived from
+`project_id` plus the external identifier, with project-scoped constraints and foreign keys. The
+same `session_id`, `agent_id`, `call_id`, or `rollup_key` can exist in separate projects without a
+collision. Every event runs inside its own savepoint; an intermediate failure rolls back the ingest
+row and all projections before the batch continues. Migrations are checksummed and an existing
+database receives a consistent backup before every structural migration.
+
+Each ingested document is also projected into chunks carrying path, heading,
+authority, time, and validity. The Observer feature-probes FTS5 and uses the index when the
+extension is available; otherwise it preserves the same semantics through a lexical fallback.
+Search returns the passage containing the match and its provenance rather than only the beginning
+of the document.
+
 `init` projects `observer-publish` into `SessionStart`, `Stop`, and `SubagentStop` after the primary
-hooks. When the server is unavailable, it writes snapshots to `.brain/observer-outbox/` and SQL
-events to `.brain/observer-sql-outbox/` without blocking the session; a later run retries the
-batches. SQL batches use gzip so complete transcripts larger than 64 MB as plain JSON remain within
+hooks. `SessionStart` only drains the queue; `Stop` reads the changed session alone, and
+`SubagentStop` reads only the affected subagent transcript. `note new` and `change archive` enqueue
+the documents they wrote. Events are coalesced by scope and one lease admits a single publisher.
+When the server is unavailable, `.brain/observer-sql-outbox/` remains durable without blocking the
+session; full-vault scanning is reserved for `observer reconcile`. `doctor` reports queue batches,
+events, bytes, and age. SQL batches use gzip so complete transcripts larger than 64 MB as plain JSON remain within
 the transport limit; the Observer decompresses and validates the body before ingesting it. The
 outbox is temporary transport, not authority.
 
@@ -107,12 +124,12 @@ outbox is temporary transport, not authority.
 
 - `project_not_registered`: run `observer register` before publishing.
 - `host loopback`: replace `0.0.0.0` or a LAN address with `127.0.0.1`.
-- Pending outbox: the service was unavailable; preserve `.brain/observer-outbox/` and
-  `.brain/observer-sql-outbox/`, then rerun the publisher. Also ignore
-  `.brain/observer-sql-state.json` and `.brain/observer-sql-outbox/` in a versioned vault. Do not delete events manually.
+- Pending outbox: the service was unavailable; preserve `.brain/observer-sql-outbox/` and let a
+  later hook drain it or run `observer reconcile`. Also ignore
+  `.brain/observer-sql-state.json`, `.brain/observer-sql-outbox/`, and `.brain/observer-sql-publisher.lock` in a versioned vault. Do not delete events manually.
 - `WENDKEEP_OBSERVER_NODE_UNSUPPORTED`: run the Observer on Node.js 22.13 or newer.
 - If memory or usage is incomplete, check the Sync screen, preserve the outbox, and run
-  `observer memory import` to rebuild the load from the vault.
+  `observer reconcile` to rebuild the load and prove hash parity.
 
 ## Next steps
 
@@ -139,7 +156,8 @@ complete, archive, repair, or promote state.
   rollups, calls, and transcripts.
 - `GET /v1/projects/:project_id/memory/tree` — document tree and metadata.
 - `GET /v1/projects/:project_id/memory/document?path=...` — complete Markdown content.
-- `GET /v1/projects/:project_id/memory/search?q=...` — path and body search.
+- `GET /v1/projects/:project_id/memory/search?q=...` — ranked chunk search with matching passage
+  and provenance; uses a lexical fallback when FTS5 is unavailable.
 - `GET /v1/projects/:project_id/sync` — mode, counts, conflicts, and latest event.
 - `PUT /v1/projects/:project_id/sync` — compatibility configuration; SQL remains authoritative.
 - `GET /v1/projects/:project_id/memory/export` — read-only export with complete content.

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

@@ -248,7 +248,7 @@ Deliver an approved version without manufacturing another change:
 ```bash
 npx wendkeep delivery start release-0-73-0 --source-change proportional-governance --allow git:merge --allow git:push --allow publish
 npx wendkeep delivery status release-0-73-0
-npx wendkeep delivery finish release-0-73-0 --target v0.73.0 --ci-url <run> --version 0.73.0 --npm-integrity <sha512> --release-url <release>
+npx wendkeep delivery finish release-0-74-0 --target v0.74.0 --ci-url <run> --version 0.74.0 --npm-integrity <sha512> --release-url <release>
 ```
 
 ## Expected result

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

@@ -30,6 +30,7 @@ Informe o vault explicitamente em automações. Preserve backups e evidências a
 npx wendkeep memory status [--gate] --vault <cofre>
 npx wendkeep memory curate --vault <cofre>
 npx wendkeep memory candidates [--active] --vault <cofre>
+npx wendkeep memory rescope [--apply] --vault <cofre>
 npx wendkeep memory repair --vault <cofre>
 npx wendkeep memory recover-attempt <sessão> [--apply] --vault <cofre>
 npx wendkeep memory reconcile <sessão-ambígua> --by-session <sessão-sucessora> --reason <motivo> [--apply] --vault <cofre>
@@ -51,7 +52,7 @@ npx wendkeep validate-memory --vault <cofre-v2>
   não-TTY/terminal não interativo, ele retorna exit `2` sem alterar bytes e orienta usar o fallback
   avançado `memory candidates --active`.
 - `memory candidates` é read-only e imprime JSON determinístico com somente `candidate_id`,
-  `reason`, `status`, `memory_key` e `event_ids`; não expõe valores nem conteúdo da memória e não
+  `reason`, `status`, `memory_key`, escopo quando presente e `event_ids`; não expõe valores nem conteúdo da memória e não
   cria lock nem altera o bundle. `--active` omite candidates terminais (`resolved`, `rejected` e
   `superseded`). Status ausente é normalizado para `active`.
 - Em `memory candidates`, exit `0` indica inventário válido (inclusive vazio ou com conflitos),
@@ -95,6 +96,18 @@ npx wendkeep validate-memory --vault <cofre-v2>
   do attempt exato, salva backup do registry e limita a mutação ao attempt ambíguo e à sucessora.
   O replay é CORE-aware, usa cursor físico do ledger no checkpoint e não reescreve ledger, CORE ou
   notas, nem consome a outbox. Repetir a mesma decisão aplicada é idempotente.
+- `memory rescope` é dry-run por padrão e lista somente IDs, chaves e escopos planejados. Com
+  `--apply`, anexa eventos explícitos de projeto, work session, change, branch ou worktree e mantém
+  os bytes históricos como prefixo do ledger. Candidates ambíguos não são migrados nem recebem
+  vencedor; uma repetição retorna `unchanged`.
+- Registradores como `git.local-head`, `handoff.latest`, `quality.latest-*` e
+  `change.<slug>.status` só competem dentro do mesmo escopo. Resolução automática ainda exige o
+  mesmo projeto e linhagem causal; decisões, constraints e blockers incompatíveis permanecem sob
+  curadoria. Uma chave ambígua é omitida de SHARED sem remover CORE ou chaves independentes.
+- `.brain/EVIDENCE_INDEX.jsonl` divide documentos por headings e blocos e registra arquivo,
+  heading, tipo, change, sessão, work session, autoridade, data, validade e hash. `/brain-recall`
+  e o hook `UserPromptSubmit` usam BM25, frase exata, pesos por campo, autoridade, validade,
+  recência limitada e diversidade para retornar o trecho do match com proveniência.
 - Toda rota de memória valida a topologia física de `.brain`, ledger, outbox, CORE, SHARED,
   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
@@ -134,6 +147,8 @@ npx wendkeep validate-memory --vault <cofre-v2>
 npx wendkeep memory status --gate --vault .MeuApp-vault
 npx wendkeep memory curate --vault .MeuApp-vault
 npx wendkeep memory candidates --active --vault .MeuApp-vault
+npx wendkeep memory rescope --vault .MeuApp-vault
+npx wendkeep memory rescope --apply --vault .MeuApp-vault
 npx wendkeep memory recover-attempt sessao-123 --vault .MeuApp-vault
 npx wendkeep memory recover-attempt sessao-123 --apply --vault .MeuApp-vault
 npx wendkeep memory reconcile antiga --by-session atual --reason "entrega continuada" --vault .MeuApp-vault

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

@@ -34,6 +34,7 @@ continuam compatíveis com Node.js 18 ou mais recente. Registre explicitamente c
 npx wendkeep observer status --data-dir <diretório> --json
 npx wendkeep observer register --project <projeto> --vault <vault> --data-dir <diretório>
 npx wendkeep observer publish --project <projeto> --vault <vault> --data-dir <diretório>
+npx wendkeep observer reconcile --project <projeto> --vault <vault> --data-dir <diretório> [--url http://127.0.0.1:8787]
 npx wendkeep observer memory import --project <projeto> --vault <vault> --url http://127.0.0.1:8787 --token <token> --json
 npx wendkeep observer serve --host 127.0.0.1 --port 8787 --data-dir <diretório> --token <token>
 ```
@@ -42,7 +43,7 @@ npx wendkeep observer serve --host 127.0.0.1 --port 8787 --data-dir <diretório>
 
 - `--data-dir` escolhe o diretório local de eventos e índice; o padrão é
   `WENDKEEP_OBSERVER_DATA_DIR` ou `~/.wendkeep-observer`.
-- `--project` e `--vault` identificam o projeto nos comandos `register`, `publish` e `memory import`.
+- `--project` e `--vault` identificam o projeto nos comandos `register`, `publish`, `reconcile` e `memory import`.
 - `--host` aceita somente `127.0.0.1`, `localhost` ou `::1`; outros hosts são recusados antes do
   listen.
 - `--token` ou `WENDKEEP_OBSERVER_TOKEN` autentica mutações; `--allow-non-loopback` falha sem token.
@@ -85,8 +86,8 @@ Se o navegador mostrar a tela mas a lista falhar, confirme a saúde em
 
 ## Resultado esperado
 
-`register` grava `project_id`, nome, versão e data de registro. `publish` lê o vault local,
-produz o snapshot e envia eventos idempotentes para o SQLite com o conteúdo integral das sessões,
+`register` grava `project_id`, nome, versão e data de registro. `publish` e `reconcile` fazem a
+varredura integral explícita do vault e enviam eventos idempotentes para o SQLite com o conteúdo integral das sessões,
 decisões, bugs, aprendizados, specs, changes, CORE, DIGEST, SHARED_MEMORY, estado do brain,
 sessões de agentes, rollups de custo e chamadas. Mensagens e transcripts só são enviados nos
 níveis de captura que os habilitam. O container grava tudo em
@@ -98,10 +99,25 @@ reconciliação quando o ledger detalhado não fecha com ele; essa linha não in
 Sessões históricas com o mesmo `session_id` recebem uma identidade canônica por arquivo para
 evitar que um rollup sobrescreva o outro.
 
+No schema 5, sessões, agentes, rollups, chamadas e transcripts usam identidades internas derivadas
+de `project_id` + identificador externo, com constraints e foreign keys escopadas. O mesmo
+`session_id`, `agent_id`, `call_id` ou `rollup_key` pode existir em projetos diferentes sem colisão.
+Cada evento é aplicado em um savepoint próprio; falha intermediária reverte ingest e todas as
+projeções antes de o batch continuar. Migrações têm checksum e toda migração estrutural de uma base
+existente cria backup consistente antes da transação.
+
+Cada documento ingerido também é projetado em chunks com caminho, heading,
+autoridade, data e validade. O Observer faz um feature probe de FTS5 e usa o índice quando a
+extensão está disponível; caso contrário, mantém a mesma semântica por fallback lexical. A busca
+retorna o trecho em que houve o match e sua proveniência, não apenas o começo do documento.
+
 O `init` projeta `observer-publish` para `SessionStart`, `Stop` e `SubagentStop` depois dos hooks
-principais. Sem servidor disponível, ele grava snapshots em `.brain/observer-outbox/` e eventos
-SQL em `.brain/observer-sql-outbox/`, sem bloquear a sessão; uma execução posterior tenta
-reenviar os lotes. Os lotes SQL são enviados com gzip para que transcripts completos maiores que
+principais. `SessionStart` apenas drena a fila; `Stop` lê somente a sessão alterada e
+`SubagentStop` somente o transcript do subagente afetado. `note new` e `change archive` enfileiram
+diretamente os documentos que escreveram. Os eventos são coalescidos por escopo e uma lease garante
+um único publisher. Sem servidor disponível, a outbox `.brain/observer-sql-outbox/` é preservada
+sem bloquear a sessão; a varredura integral fica reservada a `observer reconcile`. O `doctor`
+mostra lotes, eventos, bytes e idade da fila. Os lotes SQL são enviados com gzip para que transcripts completos maiores que
 64 MB em JSON puro continuem dentro do limite do transporte; o Observer descomprime e valida o
 corpo antes de ingerir. O outbox é transporte temporário, não autoridade.
 
@@ -109,12 +125,12 @@ corpo antes de ingerir. O outbox é transporte temporário, não autoridade.
 
 - `project_not_registered`: rode `observer register` antes de publicar.
 - `host loopback`: troque `0.0.0.0` ou endereço LAN por `127.0.0.1`.
-- Outbox pendente: o serviço estava indisponível; preserve `.brain/observer-outbox/` e
-  `.brain/observer-sql-outbox/` e repita o publisher. Adicione também
-  `.brain/observer-sql-state.json` e `.brain/observer-sql-outbox/` ao ignore do Vault. Não apague eventos manualmente.
+- Outbox pendente: o serviço estava indisponível; preserve `.brain/observer-sql-outbox/` e deixe
+  um hook posterior drená-la ou rode `observer reconcile`. Adicione também
+  `.brain/observer-sql-state.json`, `.brain/observer-sql-outbox/` e `.brain/observer-sql-publisher.lock` ao ignore do Vault. Não apague eventos manualmente.
 - `WENDKEEP_OBSERVER_NODE_UNSUPPORTED`: execute o Observer em Node.js 22.13 ou mais recente.
 - Se a memória ou o consumo ficarem incompletos, verifique a tela Sincronização, preserve o
-  outbox e rode `observer memory import` para reconstruir a carga a partir do vault.
+  outbox e rode `observer reconcile` para reconstruir e comprovar paridade por hash.
 
 ## Próximos passos
 
@@ -140,7 +156,8 @@ corte. As telas do Observer não concluem, arquivam, reparam ou promovem estado.
   chamadas e transcripts.
 - `GET /v1/projects/:project_id/memory/tree` — árvore e metadados dos documentos.
 - `GET /v1/projects/:project_id/memory/document?path=...` — conteúdo Markdown integral.
-- `GET /v1/projects/:project_id/memory/search?q=...` — busca no caminho e no corpo.
+- `GET /v1/projects/:project_id/memory/search?q=...` — busca ranqueada por chunks, com trecho do
+  match e proveniência; usa fallback lexical quando FTS5 não está disponível.
 - `GET /v1/projects/:project_id/sync` — modo, contagem, conflitos e último evento.
 - `PUT /v1/projects/:project_id/sync` — compatibilidade de configuração; a autoridade continua SQL.
 - `GET /v1/projects/:project_id/memory/export` — exportação read-only com conteúdo completo.

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

@@ -247,7 +247,7 @@ Entregar uma versão já aprovada sem fabricar outra change:
 ```bash
 npx wendkeep delivery start release-0-73-0 --source-change governanca-proporcional --allow git:merge --allow git:push --allow publish
 npx wendkeep delivery status release-0-73-0
-npx wendkeep delivery finish release-0-73-0 --target v0.73.0 --ci-url <run> --version 0.73.0 --npm-integrity <sha512> --release-url <release>
+npx wendkeep delivery finish release-0-74-0 --target v0.74.0 --ci-url <run> --version 0.74.0 --npm-integrity <sha512> --release-url <release>
 ```
 
 ## Resultado esperado

package/hooks/brain-core.mjs

@@ -5,6 +5,7 @@ import { basename, join } from 'node:path';
 import { ensureDir, stripYamlQuotes, toVaultRelative } from './obsidian-common.mjs';
 import { getLocale } from './locale.mjs';
 import { sanitizeMemoryText } from './memory-schema.mjs';
+import { buildEvidenceIndex } from './evidence-recall.mjs';
 
 export function brainDir(vaultBase) {
   return join(vaultBase, '.brain');
@@ -85,6 +86,7 @@ export function buildBrainIndex(vaultBase) {
   ensureDir(brainDir(vaultBase));
   const out = rows.map((r) => JSON.stringify(r)).join('\n') + (rows.length ? '\n' : '');
   writeFileSync(join(brainDir(vaultBase), 'index.jsonl'), out, 'utf8');
+  buildEvidenceIndex(vaultBase);
   return rows;
 }
 

package/hooks/brain-recall.mjs

@@ -4,10 +4,12 @@
 import { pathToFileURL } from 'node:url';
 import { getVaultBase } from './obsidian-common.mjs';
 import { loadIndex } from './brain-core.mjs';
+import { loadEvidenceIndex, recallEvidence } from './evidence-recall.mjs';
 
 export { loadIndex };
 
 export function scoreRows(rows, query, topK = 5) {
+  if (rows.some((row) => row?.chunk_id)) return recallEvidence(rows, query, { topK });
   const terms = String(query).toLowerCase().split(/\s+/).filter(Boolean);
   if (!terms.length) return [];
   return rows
@@ -27,6 +29,8 @@ export function scoreRows(rows, query, topK = 5) {
 
 if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href) {
   const vaultBase = getVaultBase();
-  const hits = scoreRows(loadIndex(vaultBase), process.argv.slice(2).join(' '));
+  const query = process.argv.slice(2).join(' ');
+  const evidence = loadEvidenceIndex(vaultBase);
+  const hits = evidence.length ? recallEvidence(evidence, query, { topK: 5 }) : scoreRows(loadIndex(vaultBase), query);
   process.stdout.write(JSON.stringify(hits, null, 2) + '\n');
 }