wendkeep 0.66.5 → 0.67.0

package/CHANGELOG.md

@@ -4,6 +4,34 @@ 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.67.0] — 2026-08-01
+
+### Added
+
+- **O harness da LLM pode selecionar uma rota Wend temporária por solicitação.**
+  `profile route <FLOW|GUIDE|GOVERN|ASSURE> --session <id> --reason <texto>` grava uma lease
+  auditável ligada ao prompt atual, sem alterar o perfil persistente do projeto ou da sessão.
+  `OFF` permanece exclusivamente humano e é rejeitado na seleção adaptativa. Contexto sem prompt
+  causal completo e coincidente no registry falha antes de mutar, e `profile status --session`
+  mostra perfil-base e estado da lease também na saída humana.
+- **A lease expira causalmente sem interromper implementações longas.** Um Stop aceito a consome
+  por CAS; bloqueio/retry a preserva, e o próximo prompt restaura o perfil-base mesmo depois de
+  crash ou hook ausente. Skills e AGENTS gerados ensinam a matriz FLOW/GUIDE/GOVERN/ASSURE.
+
+### Fixed
+
+- **Sessões Obsidian não renderizam envelopes internos do assistente como HTML.** A captura remove
+  metadata completa ou truncada de citação somente das respostas do assistente e escapa tags
+  XML-like nas linhas geradas, preservando relatos do usuário e autolinks HTTP(S). Reimport e
+  `SessionStop` convergem no mesmo normalizador idempotente, e o encerramento migra somente campos
+  gerados reconhecíveis de notas antigas sem reescrever prosa autoral.
+- **README e guias bilíngues explicam as letras `P/R/E/V/C` e a duração das escolhas.** A
+  documentação distingue `profile use` persistente de `profile route` por solicitação e deixa
+  explícito que a classificação semântica pertence ao harness, não a heurísticas do runtime.
+- **Sensores vermelhos deixam diagnóstico acionável sem persistir logs verdes.** O runner captura
+  stdout/stderr com limite, redige segredos e grava no máximo 2.000 caracteres apenas na entrada
+  vermelha de `evidencia.json`, em vez de descartar a causa da falha.
+
 ## [0.66.5] — 2026-08-01
 
 ### Fixed

package/README.en.md

@@ -15,6 +15,10 @@
 
 **Persistent memory for AI coding agents, built on your Obsidian vault.** Every Claude Code **and Codex** session is captured turn by turn into local Markdown — `init` wires both (Codex asks you to approve its hooks once; `import` backfills past sessions either way) — with token/cost tracking and automatically extracted decisions, bugs, and learnings. That always-on plane is **Keep Core**. On top of it, **Wend Runtime** provides a native, zero-dependency lifecycle (spec → change → TDD → sensor-gated archive), selected through the `OFF`, `FLOW`, `GUIDE`, `GOVERN`, and `ASSURE` Operating Profiles. 100% local, open-core.
 
+When projecting sessions, trailing internal metadata is removed only from assistant responses;
+user reports remain intact. XML-like tags are written as escaped text so Obsidian Reading view
+does not interpret them as HTML.
+
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
 `integrations`, and `pi` — without fragmenting installation. The private `cli`, `harness`,
 `vault`, `mcp`, and `integrations` workspaces now canonically own the executable runtime,
@@ -235,13 +239,82 @@ deliberate opt-in and runs that command's own validations:
 | `GOVERN` | P → R → E → V | Current a2 loop and compatible fallback. |
 | `ASSURE` | P → R → E → V → C | Governance with confirmation and handoff. |
 
+A route is a sequence of work stages, not a list of command names:
+
+- `P` = **Plan/Propose** — understand the request, bound the scope, and record the approach when a change is needed.
+- `R` = **Review** — inspect the proposal/design before execution; this is the formal a2-loop review.
+- `E` = **Execute** — edit the permitted code or artifacts.
+- `V` = **Validate** — run tests, sensors, and checks and record evidence.
+- `C` = **Confirm/hand off** — obtain explicit confirmation and complete the handoff.
+
+Thus, `P → R → E → V` means “plan/propose, review, execute, and validate”. `FLOW` starts at the
+execution/validation microcontract; `OFF` applies no automatic Wend route and returns process
+ownership to the native LLM harness.
+
+### Who selects the profile, and for how long?
+
+The LLM harness (Codex, Claude, or another agent) **classifies the current implementation** and can
+record a temporary choice with `wendkeep profile route`. Wend Runtime does not interpret prompt
+text or use diff size, heuristics, or environment variables: it validates the choice, applies the
+route in hooks, and expires the lease when the request ends. With no recorded route, the configured
+base profile remains effective.
+
+Resolution follows this order:
+
+1. a valid lease for the current request in `SESSION_REGISTRY.json`;
+2. a persistent session override in that registry;
+3. `harness.profile` in the project's `.wendkeep.json`;
+4. `GOVERN` when no valid setting exists.
+
+Without `--session`, `profile use` changes the **project default** for conversations/hooks that do
+not have a session override. With `--session <id>`, it changes only that session and leaves the
+project default untouched. Therefore, `profile use OFF` without `--session` is not an isolated
+test: it writes the project binding and can be shared if `.wendkeep.json` is committed.
+
+`profile route` is different: it requires `--session` and `--reason`, accepts only `FLOW`, `GUIDE`,
+`GOVERN`, or `ASSURE`, does not rewrite the project/persistent override, and applies only to the
+current causal prompt. An accepted `Stop` consumes the lease; if the process dies first, the next
+prompt advances the sequence and makes the old lease ineffective. `OFF` is never selected
+automatically.
+
+```bash
+npx wendkeep profile status
+npx wendkeep profile use GUIDE                 # project default
+npx wendkeep profile use FLOW --session <id>   # one session only
+npx wendkeep profile route FLOW --session <id> --reason "local fix"  # current request
+npx wendkeep profile status --session <id>     # session-effective profile
+```
+
+In human `status --session` output, `base=<profile>/<source>` and `lease=<state>` accompany the
+effective profile; `--json` exposes the same data as `base_profile`, `base_source`, and
+`task_lease`. `profile route` only accepts a session after `UserPromptSubmit` has recorded a
+positive causal turn and sequence that agree in the registry.
+
+### Which profile fits a simple request?
+
+“Small” describes size, not risk. The harness uses this matrix to choose and record a temporary
+route; semantic inference remains in the agent, not Wend Runtime:
+
+| Situation | Suggested profile |
+|---|---|
+| Question, inspection, or diagnosis with no mutation | No profile transition |
+| Local, reversible fix with an allowlist and no contract/spec change | `FLOW` (`E → V`) |
+| Small behavior change that needs a change but not formal Wend Runtime review | `GUIDE` (`P → E → V`) |
+| Normal, ambiguous, public-contract, security, dependency, CI/release, or policy change | `GOVERN` (`P → R → E → V`) |
+| Work requiring explicit confirmation and handoff | `ASSURE` (`P → R → E → V → C`) |
+
+If the harness does not record a lease, a small fix remains under the configured profile —
+`GOVERN` by default. `OFF` does not mean “simple task”: it is a persistent human choice that hands
+governance to the native harness. The LLM may temporarily elevate an `OFF` base to a Wend route,
+but it can never select `OFF` on its own.
+
 A corrupt binding never selects `OFF`: with one unambiguous explicit or legacy Vault, Keep Core
 remains active under `GOVERN`, the error stays visible, and mutation guards fail closed. Additional
 roots that FLOW must protect can be declared as project-relative paths under
 `harness.flow.protectedRoots` in `.wendkeep.json`; any change below them requires promotion.
 Invalid local config, marker, or identity never silently falls back to a parent/global Vault.
 
-`wendkeep profile status/use` makes the choice observable; `wendkeep flow
+`wendkeep profile status/use/route` makes the choice observable; `wendkeep flow
 start/finish/promote` handles local adjustments without manufacturing an ADR and fails closed on
 physical escapes, Git metadata/hidden flags, mutating sensors, protected surfaces, or incomplete
 session projection. Bounded no-follow discovery sees empty/ignored protected aliases; Vault writes
@@ -379,7 +452,7 @@ explore → propose → apply (TDD) → verify → archive
 
 - **Propose** — `wendkeep change new <slug>` scaffolds `08-Mudanças/<slug>/` (`proposta.md`, `design.md`, `tarefas.md`; `--simple` skips the design). It becomes the global *current* change. When the change declares `spec_impact: required`, you author the delta yourself at `specs/<capability>/spec.md` — there is no placeholder to delete. Multiple changes may remain open: `change list`/`status` and the hooks show every pending one, while commands without `--change` act on the current one alone. `change use <slug>` changes focus and `change continue <archived> <new>` creates an auditable continuation.
 - **Apply** — implement each `tarefas.md` task. Mark machine proof with one or more `[sensor:<id>]` tags on the same task: every distinct ID enters the gate once, in declaration order. Also mark satisfied requirements with one or more `[req:<ID>]` tags.
-- **Verify** — `wendkeep verify` runs the sensors your tasks declared (from `wendkeep.sensors.json` at the project root) and writes `evidencia.json`. A red `critical` fails the gate; a red `warning` is advisory. `verify --deep` builds a self-contained package with complete effective requirements (living contract + this change's delta), so the independent verifier never needs to reconstruct unarchived requirements from `07-Specs`. Every change needs a `verdict.json` to archive; `verify --deep` writes a trivial one automatically when the change declares no `[req:]`.
+- **Verify** — `wendkeep verify` runs the sensors your tasks declared (from `wendkeep.sensors.json` at the project root) and writes `evidencia.json`. A red `critical` fails the gate; a red `warning` is advisory. Failures retain only a bounded, sanitized diagnostic; green output is not persisted. `verify --deep` builds a self-contained package with complete effective requirements (living contract + this change's delta), so the independent verifier never needs to reconstruct unarchived requirements from `07-Specs`. Every change needs a `verdict.json` to archive; `verify --deep` writes a trivial one automatically when the change declares no `[req:]`.
 - **Archive** — `wendkeep change archive <slug>` **gates** on the evidence (blocks unless every declared critical sensor is green), promotes each capability's spec delta (`ADDED`/`MODIFIED`/`REMOVED`) into the living `07-Specs/<capability>.md`, moves the change to `_arquivo/`, and mints an ADR in `04-Decisões/`.
 
 > The gate blocks unless the scaffold is filled, no task is open, evidence is fresh, and every declared requirement is covered. **`--force` waives exactly one of those — the open-task check — and is the human's call, never the agent's.** An unfilled scaffold, a red critical sensor, stale evidence, an orphan requirement or a missing verdict block regardless.

package/README.md

@@ -15,6 +15,10 @@
 
 **Persistent memory for AI coding agents, built on your Obsidian vault.** Every Claude Code **and Codex** session is captured turn by turn into local Markdown — `init` wires both (Codex asks you to approve its hooks once; `import` backfills past sessions either way) — with token/cost tracking and automatically extracted decisions, bugs, and learnings. That always-on plane is **Keep Core**. On top of it, **Wend Runtime** provides a native, zero-dependency lifecycle (spec → change → TDD → sensor-gated archive), selected through the `OFF`, `FLOW`, `GUIDE`, `GOVERN`, and `ASSURE` Operating Profiles. 100% local, open-core.
 
+When projecting sessions, trailing internal metadata is removed only from assistant responses;
+user reports remain intact. XML-like tags are written as escaped text so Obsidian Reading view
+does not interpret them as HTML.
+
 The runtime is being separated into six physical boundaries — `cli`, `harness`, `vault`, `mcp`,
 `integrations`, and `pi` — without fragmenting installation. The private `cli`, `harness`,
 `vault`, `mcp`, and `integrations` workspaces now canonically own the executable runtime,
@@ -235,13 +239,82 @@ deliberate opt-in and runs that command's own validations:
 | `GOVERN` | P → R → E → V | Current a2 loop and compatible fallback. |
 | `ASSURE` | P → R → E → V → C | Governance with confirmation and handoff. |
 
+A route is a sequence of work stages, not a list of command names:
+
+- `P` = **Plan/Propose** — understand the request, bound the scope, and record the approach when a change is needed.
+- `R` = **Review** — inspect the proposal/design before execution; this is the formal a2-loop review.
+- `E` = **Execute** — edit the permitted code or artifacts.
+- `V` = **Validate** — run tests, sensors, and checks and record evidence.
+- `C` = **Confirm/hand off** — obtain explicit confirmation and complete the handoff.
+
+Thus, `P → R → E → V` means “plan/propose, review, execute, and validate”. `FLOW` starts at the
+execution/validation microcontract; `OFF` applies no automatic Wend route and returns process
+ownership to the native LLM harness.
+
+### Who selects the profile, and for how long?
+
+The LLM harness (Codex, Claude, or another agent) **classifies the current implementation** and can
+record a temporary choice with `wendkeep profile route`. Wend Runtime does not interpret prompt
+text or use diff size, heuristics, or environment variables: it validates the choice, applies the
+route in hooks, and expires the lease when the request ends. With no recorded route, the configured
+base profile remains effective.
+
+Resolution follows this order:
+
+1. a valid lease for the current request in `SESSION_REGISTRY.json`;
+2. a persistent session override in that registry;
+3. `harness.profile` in the project's `.wendkeep.json`;
+4. `GOVERN` when no valid setting exists.
+
+Without `--session`, `profile use` changes the **project default** for conversations/hooks that do
+not have a session override. With `--session <id>`, it changes only that session and leaves the
+project default untouched. Therefore, `profile use OFF` without `--session` is not an isolated
+test: it writes the project binding and can be shared if `.wendkeep.json` is committed.
+
+`profile route` is different: it requires `--session` and `--reason`, accepts only `FLOW`, `GUIDE`,
+`GOVERN`, or `ASSURE`, does not rewrite the project/persistent override, and applies only to the
+current causal prompt. An accepted `Stop` consumes the lease; if the process dies first, the next
+prompt advances the sequence and makes the old lease ineffective. `OFF` is never selected
+automatically.
+
+```bash
+npx wendkeep profile status
+npx wendkeep profile use GUIDE                 # project default
+npx wendkeep profile use FLOW --session <id>   # one session only
+npx wendkeep profile route FLOW --session <id> --reason "local fix"  # current request
+npx wendkeep profile status --session <id>     # session-effective profile
+```
+
+In human `status --session` output, `base=<profile>/<source>` and `lease=<state>` accompany the
+effective profile; `--json` exposes the same data as `base_profile`, `base_source`, and
+`task_lease`. `profile route` only accepts a session after `UserPromptSubmit` has recorded a
+positive causal turn and sequence that agree in the registry.
+
+### Which profile fits a simple request?
+
+“Small” describes size, not risk. The harness uses this matrix to choose and record a temporary
+route; semantic inference remains in the agent, not Wend Runtime:
+
+| Situation | Suggested profile |
+|---|---|
+| Question, inspection, or diagnosis with no mutation | No profile transition |
+| Local, reversible fix with an allowlist and no contract/spec change | `FLOW` (`E → V`) |
+| Small behavior change that needs a change but not formal Wend Runtime review | `GUIDE` (`P → E → V`) |
+| Normal, ambiguous, public-contract, security, dependency, CI/release, or policy change | `GOVERN` (`P → R → E → V`) |
+| Work requiring explicit confirmation and handoff | `ASSURE` (`P → R → E → V → C`) |
+
+If the harness does not record a lease, a small fix remains under the configured profile —
+`GOVERN` by default. `OFF` does not mean “simple task”: it is a persistent human choice that hands
+governance to the native harness. The LLM may temporarily elevate an `OFF` base to a Wend route,
+but it can never select `OFF` on its own.
+
 A corrupt binding never selects `OFF`: with one unambiguous explicit or legacy Vault, Keep Core
 remains active under `GOVERN`, the error stays visible, and mutation guards fail closed. Additional
 roots that FLOW must protect can be declared as project-relative paths under
 `harness.flow.protectedRoots` in `.wendkeep.json`; any change below them requires promotion.
 Invalid local config, marker, or identity never silently falls back to a parent/global Vault.
 
-`wendkeep profile status/use` makes the choice observable; `wendkeep flow
+`wendkeep profile status/use/route` makes the choice observable; `wendkeep flow
 start/finish/promote` handles local adjustments without manufacturing an ADR and fails closed on
 physical escapes, Git metadata/hidden flags, mutating sensors, protected surfaces, or incomplete
 session projection. Bounded no-follow discovery sees empty/ignored protected aliases; Vault writes
@@ -379,7 +452,7 @@ explore → propose → apply (TDD) → verify → archive
 
 - **Propose** — `wendkeep change new <slug>` scaffolds `08-Mudanças/<slug>/` (`proposta.md`, `design.md`, `tarefas.md`; `--simple` skips the design). It becomes the global *current* change. When the change declares `spec_impact: required`, you author the delta yourself at `specs/<capability>/spec.md` — there is no placeholder to delete. Multiple changes may remain open: `change list`/`status` and the hooks show every pending one, while commands without `--change` act on the current one alone. `change use <slug>` changes focus and `change continue <archived> <new>` creates an auditable continuation.
 - **Apply** — implement each `tarefas.md` task. Mark machine proof with one or more `[sensor:<id>]` tags on the same task: every distinct ID enters the gate once, in declaration order. Also mark satisfied requirements with one or more `[req:<ID>]` tags.
-- **Verify** — `wendkeep verify` runs the sensors your tasks declared (from `wendkeep.sensors.json` at the project root) and writes `evidencia.json`. A red `critical` fails the gate; a red `warning` is advisory. `verify --deep` builds a self-contained package with complete effective requirements (living contract + this change's delta), so the independent verifier never needs to reconstruct unarchived requirements from `07-Specs`. Every change needs a `verdict.json` to archive; `verify --deep` writes a trivial one automatically when the change declares no `[req:]`.
+- **Verify** — `wendkeep verify` runs the sensors your tasks declared (from `wendkeep.sensors.json` at the project root) and writes `evidencia.json`. A red `critical` fails the gate; a red `warning` is advisory. Failures retain only a bounded, sanitized diagnostic; green output is not persisted. `verify --deep` builds a self-contained package with complete effective requirements (living contract + this change's delta), so the independent verifier never needs to reconstruct unarchived requirements from `07-Specs`. Every change needs a `verdict.json` to archive; `verify --deep` writes a trivial one automatically when the change declares no `[req:]`.
 - **Archive** — `wendkeep change archive <slug>` **gates** on the evidence (blocks unless every declared critical sensor is green), promotes each capability's spec delta (`ADDED`/`MODIFIED`/`REMOVED`) into the living `07-Specs/<capability>.md`, moves the change to `_arquivo/`, and mints an ADR in `04-Decisões/`.
 
 > The gate blocks unless the scaffold is filled, no task is open, evidence is fresh, and every declared requirement is covered. **`--force` waives exactly one of those — the open-task check — and is the human's call, never the agent's.** An unfilled scaffold, a red critical sensor, stale evidence, an orphan requirement or a missing verdict block regardless.

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

@@ -14,9 +14,9 @@ opt-in and runs that command's own validations and gates.
 
 ## When to use
 
-Use `profile` to inspect or explicitly select an Operating Profile. Use `FLOW` for local,
-reversible `spec_impact:none` maintenance that fits an Execute → Validate microcontract without a
-change.
+Use `profile use` for a persistent human selection and `profile route` for the harness to record
+the temporary route for the current implementation. Use `FLOW` for local, reversible
+`spec_impact:none` maintenance that fits an Execute → Validate microcontract without a change.
 
 ## When not to use
 
@@ -28,7 +28,8 @@ change.
 ## Prerequisites
 
 - An initialized project whose `.wendkeep.json` is bound to the correct Vault.
-- For a session override, one unambiguous session in `SESSION_REGISTRY.json`.
+- For an override or temporary route, one unambiguous session in `SESSION_REGISTRY.json`; `route`
+  also requires the current prompt to have a recorded causal frontier.
 - For FLOW, a Git repository, a path allowlist, a reason, and at least one existing sensor in
   `wendkeep.sensors.json`.
 
@@ -37,6 +38,7 @@ change.
 ```bash
 npx wendkeep profile status [--project <path>] [--vault <path>] [--session <id>] [--json]
 npx wendkeep profile use <profile> [--project <path>] [--vault <path>] [--session <id>] [--json]
+npx wendkeep profile route <FLOW|GUIDE|GOVERN|ASSURE> --session <id> --reason <text> [--project <path>] [--vault <path>] [--json]
 npx wendkeep flow start <slug> --allow <path> [--allow <path>...] --sensor <id> [--sensor <id>...] --reason <text> [--session <id>]
 npx wendkeep flow status [<id>]
 npx wendkeep flow show <id> [--session <id>]
@@ -75,15 +77,42 @@ Harness. The workspaces remain private and are not published as independent npm
 | `GOVERN` | P → R → E → V | Current a2 loop and conservative fallback. |
 | `ASSURE` | P → R → E → V → C | Governance plus confirmation and handoff. |
 
-- Resolution is explicit session override → project `harness.profile` → `GOVERN`. Heuristics,
-  diff size, prompt text, environment variables, or read failures never select `OFF`.
-- `profile status` prints the effective profile and source; `--json` emits structured output. When
-  an explicit Vault preserves the selection despite a corrupt binding, output includes
+### Route legend
+
+The letters are work stages, not individual commands:
+
+- `P` = **Plan/Propose** — understand the request, bound the scope, and record the approach.
+- `R` = **Review** — inspect the proposal/design before execution; this is the formal a2-loop review.
+- `E` = **Execute** — edit the permitted paths and artifacts.
+- `V` = **Validate** — run tests, sensors, and checks and record evidence.
+- `C` = **Confirm/hand off** — obtain explicit confirmation and complete the handoff.
+
+So, `P → R → E → V` means “plan/propose, review, execute, and validate”. `FLOW` starts at the
+execution/validation microcontract; `OFF` imposes no automatic Wend route and returns process
+ownership to the native LLM harness.
+
+- The LLM harness semantically classifies the request and records `profile route`; Wend Runtime
+  does not classify text, diff size, heuristics, or environment variables. It validates and applies
+  the deterministic lease.
+- For a local, reversible fix with no contract/spec change, choose `FLOW`. For a compact behavior
+  change that needs a change but no formal review, choose `GUIDE`. For uncertainty, risk, security,
+  public contracts, dependencies, CI/release, or policy, choose `GOVERN`. Use `ASSURE` when
+  confirmation and handoff are part of the contract.
+- `OFF` can never be an adaptive route; only a human persists it explicitly through
+  `profile use OFF`. An `OFF` base may still receive a temporary elevation to a Wend route.
+
+- Resolution is active prompt lease → persistent session override → project
+  `harness.profile` → `GOVERN`. Invalid/expired leases and read failures never select `OFF`.
+- `profile status` prints the effective profile and source. With `--session`, human output adds
+  `base=<profile>/<source>` and `lease=<state>`; `--json` emits the same data structurally. When an
+  explicit Vault preserves the selection despite a corrupt binding, output includes
   `binding_error` and the diagnostic is also written to stderr.
 - `profile use` validates names and flags strictly; a duplicate/incomplete singleton option or a
   value beginning with `--` fails before I/O. Without `--session`, it atomically changes the
   project binding; with `--session`, it records override, source, and timestamp without changing
   session identity.
+- `profile route` requires `--session` and `--reason`, accepts only the four adaptive profiles,
+  and records lease id, reason, turn/sequence, and timestamp without touching persistent profiles.
 - `.wendkeep.json` stays on `schemaVersion: 1`; the additive field is, for example,
   `"harness": { "profile": "GOVERN" }`. A legacy binding without it also resolves to `GOVERN`.
 - A corrupt binding never means `OFF`. When the payload or legacy integration identifies one
@@ -127,13 +156,39 @@ Harness. The workspaces remain private and are not published as independent npm
 - Exit `0` means a successful query or transition; exit `1` means a policy/red-sensor block; exit
   `2` means invalid profile, session, flow, or arguments, with no partial mutation.
 
+### Selection scope
+
+Without `--session`, `profile use` writes `harness.profile` to `.wendkeep.json` and changes the
+project default for conversations/hooks that have no session override. With `--session <id>`, it
+writes an override only to that session's `SESSION_REGISTRY.json` and leaves the project default
+unchanged. Therefore, `profile use OFF` without `--session` is not an isolated test; if
+`.wendkeep.json` is committed, that choice is shared with other checkouts as well.
+
+`profile route` creates a lease only for the current request. An accepted `Stop` consumes it by
+CAS; if cleanup does not run, the next `UserPromptSubmit` advances the sequence and the lease is no
+longer effective. A blocked Stop preserves it for a retry of the same request. There is no
+wall-clock TTL that can interrupt long work. A session with no causal prompt recorded yet (missing
+turn, zero sequence, or missing/mismatched causal map entry) is rejected before any mutation.
+`status --session` includes the base profile and lease state in both human and `--json` output; in
+JSON the fields are `base_profile`, `base_source`, and `task_lease.state` (`active`, `consumed`,
+`expired`, `invalid`, or `absent`).
+
+```bash
+npx wendkeep profile status                       # project default
+npx wendkeep profile use GUIDE                   # change the project default
+npx wendkeep profile use FLOW --session <id>     # one session only
+npx wendkeep profile route FLOW --session <id> --reason "local adjustment"  # current request
+npx wendkeep profile status --session <id>       # session-effective profile
+```
+
 ## Examples
 
-Inspect the effective default and apply an override only to the current session:
+Inspect the effective default and route only the current implementation:
 
 ```bash
 npx wendkeep profile status
-npx wendkeep profile use OFF --session 019abc-session-id --json
+npx wendkeep profile route FLOW --session 019abc-session-id --reason "fix local typo" --json
+npx wendkeep profile status --session 019abc-session-id --json
 ```
 
 Run FLOW maintenance while capturing the `flow_id` returned by `start`:

package/docs/en/commands/sessions-and-import.md

@@ -81,7 +81,13 @@ Each canonical session points to the matching provider, transcript, note file, a
 registry keeps one `SessionStart` epoch per activation plus the latest native turn; multiple
 `Stop` events may acknowledge turns in that epoch without closing it. Repeated imports of the
 same `session_id` deduplicate; human focus does not close or re-identify live hooks. Every
-automatic iteration remains valid Markdown even when a message must be truncated.
+automatic iteration remains valid Markdown even when a message must be truncated. Complete or
+truncated trailing internal metadata is removed only from assistant messages; a reproduction
+written by the user remains in the transcript. In the note, XML-like tags are encoded as visible
+text — including placeholders such as `<session>` — without changing `<https://...>` autolinks.
+Reimport and `SessionStop` share the same idempotent normalizer; when an older note is finalized,
+only recognized generated fields under `Iterações` and `Encerramento` are migrated, without rewriting
+authored prose.
 Duplicate/stale hooks converge on the same frontier, and imports may refresh only observability
 without creating a new turn block.
 

package/docs/en/commands/verify.md

@@ -73,15 +73,17 @@ npx wendkeep memory status --gate --vault .MyApp-vault
 ## Expected result
 
 `evidencia.json` contains sensor results and a seal binds proof to the current `tarefas.md` hash.
-Deep mode packages requirements, tasks, and evidence for read-only review; the verdict covers every
-`[req:]` before archive.
+When a sensor is red, its entry receives only a local, sanitized diagnostic bounded to 2,000
+characters; stdout/stderr from green sensors is not persisted. Deep mode packages requirements,
+tasks, and evidence for read-only review; the verdict covers every `[req:]` before archive.
 
 ## Common errors and diagnosis
 
 - `no change`: this is exit 2 and a valid idle state; create/use a change or skip verify.
 - Zero/missing sensors: inspect every same-line tag and `sensors list`; multiple tags on one task
   are valid and all of them enter the gate.
-- Red gate: fix the cause and rerun; never choose `archive --force` on your own.
+- Red gate: inspect the bounded `note` field on the `evidencia.json` entry, fix the cause, and
+  rerun; never choose `archive --force` on your own.
 - Missing/stale verdict: regenerate `--deep` and request a fresh independent pass.
 - Surviving mutants: strengthen the discriminating test; after three rounds, review manually.
 

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

@@ -14,9 +14,9 @@ deliberado e executa as validações e gates próprios daquele comando.
 
 ## Quando usar
 
-Use `profile` para consultar ou selecionar explicitamente um Perfil de Operação. Use `FLOW` para
-manutenção local, reversível e com `spec_impact:none` que caiba num microcontrato Executar →
-Validar, sem change.
+Use `profile use` para uma seleção humana persistente e `profile route` para o harness registrar a
+rota temporária da implementação atual. Use `FLOW` para manutenção local, reversível e com
+`spec_impact:none` que caiba num microcontrato Executar → Validar, sem change.
 
 ## Quando não usar
 
@@ -28,7 +28,8 @@ gates/policies do WendKeep; promova o trabalho para uma change.
 ## Pré-requisitos
 
 - Projeto inicializado, com `.wendkeep.json` vinculado ao Vault correto.
-- Para override de sessão, uma sessão inequívoca no `SESSION_REGISTRY.json`.
+- Para override ou rota temporária, uma sessão inequívoca no `SESSION_REGISTRY.json`; `route`
+  também exige que o prompt atual já tenha fronteira causal registrada.
 - Para FLOW, repositório Git, allowlist de paths, motivo e ao menos um sensor existente em
   `wendkeep.sensors.json`.
 
@@ -37,6 +38,7 @@ gates/policies do WendKeep; promova o trabalho para uma change.
 ```bash
 npx wendkeep profile status [--project <path>] [--vault <path>] [--session <id>] [--json]
 npx wendkeep profile use <perfil> [--project <path>] [--vault <path>] [--session <id>] [--json]
+npx wendkeep profile route <FLOW|GUIDE|GOVERN|ASSURE> --session <id> --reason <texto> [--project <path>] [--vault <path>] [--json]
 npx wendkeep flow start <slug> --allow <path> [--allow <path>...] --sensor <id> [--sensor <id>...] --reason <texto> [--session <id>]
 npx wendkeep flow status [<id>]
 npx wendkeep flow show <id> [--session <id>]
@@ -76,15 +78,42 @@ independentes.
 | `GOVERN` | P → R → E → V | Loop a2 atual e fallback conservador. |
 | `ASSURE` | P → R → E → V → C | Governança acrescida de confirmação e handoff. |
 
-- A resolução segue override explícito da sessão → `harness.profile` do projeto → `GOVERN`.
-  Heurística, tamanho do diff, texto do prompt, variável de ambiente ou erro de leitura nunca
+### Legenda da rota
+
+As letras são etapas do trabalho, não comandos individuais:
+
+- `P` = **Planejar/Propor** — entender o pedido, delimitar o escopo e registrar a abordagem.
+- `R` = **Revisar** — revisar proposta/design antes da execução; é a revisão formal do loop a2.
+- `E` = **Executar** — editar os paths e artefatos permitidos.
+- `V` = **Validar** — rodar testes, sensores e verificações e registrar evidência.
+- `C` = **Confirmar/entregar** — obter confirmação explícita e fazer handoff.
+
+Logo, `P → R → E → V` é “planejar/propor, revisar, executar e validar”. `FLOW` começa no
+microcontrato de execução/validação; `OFF` não impõe rota Wend automática e entrega o processo ao
+harness nativo da LLM.
+
+- O harness da LLM classifica semanticamente o pedido e registra `profile route`; o Wend Runtime
+  não classifica texto, tamanho do diff, heurística ou variável de ambiente. Ele valida e aplica a
+  lease determinística.
+- Para correção local, reversível e sem contrato/spec, escolha `FLOW`. Para mudança compacta de
+  comportamento que precisa de change sem revisão formal, escolha `GUIDE`. Em dúvida, risco,
+  segurança, contrato público, dependências, CI/release ou policy, escolha `GOVERN`. Use `ASSURE`
+  quando confirmação e handoff forem parte do contrato.
+- `OFF` nunca pode ser uma rota adaptativa; somente uma pessoa o persiste explicitamente por
+  `profile use OFF`. Uma base `OFF` ainda pode receber uma elevação temporária para rota Wend.
+
+- A resolução segue lease ativa do prompt → override persistente da sessão →
+  `harness.profile` do projeto → `GOVERN`. Lease inválida/expirada e erro de leitura nunca
   selecionam `OFF`.
-- `profile status` mostra perfil efetivo e origem; `--json` produz saída estruturada. Quando um
-  Vault explícito preserva a escolha apesar de binding corrompido, a saída inclui `binding_error`
-  e o diagnóstico também vai para stderr.
+- `profile status` mostra perfil efetivo e origem. Com `--session`, a saída humana acrescenta
+  `base=<perfil>/<origem>` e `lease=<estado>`; `--json` produz os mesmos dados estruturados. Quando
+  um Vault explícito preserva a escolha apesar de binding corrompido, a saída inclui
+  `binding_error` e o diagnóstico também vai para stderr.
 - `profile use` valida nome e flags estritamente; opção singleton duplicada, incompleta ou com
   valor iniciado por `--` falha antes de I/O. Sem `--session`, altera atomicamente o binding do
   projeto; com `--session`, grava override, origem e timestamp sem trocar a identidade da sessão.
+- `profile route` exige `--session` e `--reason`, aceita somente os quatro perfis adaptativos e
+  grava `lease_id`, motivo, turno/sequência e timestamp sem tocar no perfil persistente.
 - `.wendkeep.json` continua em `schemaVersion: 1`; o campo aditivo usa, por exemplo,
   `"harness": { "profile": "GOVERN" }`. Binding legado sem o campo também resolve `GOVERN`.
 - Binding corrompido nunca equivale a `OFF`. Quando o payload ou a integração legada identifica
@@ -126,13 +155,39 @@ independentes.
 - Exit `0` indica consulta ou transição concluída; exit `1` indica política/sensor vermelho; exit
   `2` indica perfil, sessão, flow ou argumentos inválidos, sem mutação parcial.
 
+### Escopo da escolha
+
+Sem `--session`, `profile use` grava `harness.profile` no `.wendkeep.json` e muda o padrão do
+projeto para as conversas/hooks que não tenham override de sessão. Com `--session <id>`, grava o
+override somente no `SESSION_REGISTRY.json` daquela sessão e preserva o padrão do projeto. Por
+isso, `profile use OFF` sem `--session` não é um teste isolado; se o `.wendkeep.json` for commitado,
+essa escolha também será compartilhada com outros checkouts.
+
+`profile route` cria uma lease apenas para a solicitação atual. Um `Stop` aceito a consome por
+CAS; se o cleanup não rodar, o próximo `UserPromptSubmit` avança a sequência e a lease deixa de ser
+efetiva. Stop bloqueado preserva a lease para o retry do mesmo pedido. Não há TTL de relógio que
+interrompa trabalho longo. Sessão ainda sem prompt causal registrado (turno ausente, sequência
+zero, mapa causal ausente ou divergente) é rejeitada antes de qualquer mutação. `status --session`
+inclui o perfil-base e o estado da lease tanto na saída humana quanto em `--json`; neste, os campos
+são `base_profile`, `base_source` e `task_lease.state` (`active`, `consumed`, `expired`, `invalid` ou
+`absent`).
+
+```bash
+npx wendkeep profile status                       # padrão do projeto
+npx wendkeep profile use GUIDE                   # altera o padrão do projeto
+npx wendkeep profile use FLOW --session <id>     # altera somente uma sessão
+npx wendkeep profile route FLOW --session <id> --reason "ajuste local"  # pedido atual
+npx wendkeep profile status --session <id>       # consulta a sessão efetiva
+```
+
 ## Exemplos
 
-Consultar o padrão efetivo e aplicar override somente à sessão atual:
+Consultar o padrão efetivo e rotear somente a implementação atual:
 
 ```bash
 npx wendkeep profile status
-npx wendkeep profile use OFF --session 019abc-session-id --json
+npx wendkeep profile route FLOW --session 019abc-session-id --reason "corrige typo local" --json
+npx wendkeep profile status --session 019abc-session-id --json
 ```
 
 Executar uma manutenção FLOW capturando o `flow_id` retornado por `start`:

package/docs/pt-BR/commands/sessions-and-import.md

@@ -80,7 +80,13 @@ Cada sessão canônica aponta para provider, transcript, arquivo de nota e custo
 O registry mantém um epoch de `SessionStart` por activation e o turno nativo mais recente; vários
 `Stop` podem confirmar turnos do mesmo epoch sem fechá-lo. Importações repetidas do mesmo
 `session_id` são deduplicadas; o foco humano não encerra nem altera a identidade dos hooks. Cada
-iteração automática permanece Markdown válido mesmo quando uma fala precisa ser truncada. Hooks
+iteração automática permanece Markdown válido mesmo quando uma fala precisa ser truncada.
+Metadados internos terminais completos ou truncados são removidos somente das mensagens do
+assistente; uma reprodução escrita pelo usuário permanece no transcript. Na nota, tags XML-like
+são codificadas como texto visível — inclusive placeholders como `<session>` — sem alterar
+autolinks `<https://...>`. Reimport e `SessionStop` compartilham o mesmo normalizador idempotente;
+ao finalizar uma nota antiga, somente campos gerados reconhecíveis em `Iterações` e
+`Encerramento` são migrados, sem reescrever a prosa autoral. Hooks
 duplicados/stale convergem no mesmo frontier, e importações podem atualizar só a observabilidade
 sem criar um novo bloco de turno.
 

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

@@ -74,15 +74,18 @@ npx wendkeep memory status --gate --vault .MeuApp-vault
 ## Resultado esperado
 
 `evidencia.json` contém resultados dos sensores e um selo liga a prova ao hash atual de
-`tarefas.md`. No deep, o pacote contém requisitos, tarefas e evidência suficientes para revisão
-read-only; o verdict cobre cada `[req:]` antes do archive.
+`tarefas.md`. Quando um sensor fica vermelho, sua entrada recebe somente um diagnóstico local
+sanitizado e limitado a 2.000 caracteres; stdout/stderr de sensores verdes não é persistido. No
+deep, o pacote contém requisitos, tarefas e evidência suficientes para revisão read-only; o
+verdict cobre cada `[req:]` antes do archive.
 
 ## Erros comuns e diagnóstico
 
 - `no change`: isso é exit 2 e estado ocioso válido; crie/use uma change ou não rode verify.
 - Zero/sensores ausentes: confira todas as tags na mesma linha e `sensors list`; várias tags na
   mesma tarefa são válidas e todas entram no gate.
-- Gate vermelho: corrija a causa e repita; não use `archive --force` por conta própria.
+- Gate vermelho: consulte o campo `note` limitado da entrada em `evidencia.json`, corrija a causa
+  e repita; não use `archive --force` por conta própria.
 - Verdict stale/ausente: regenere `--deep` e peça novo passe independente.
 - Mutantes sobreviventes: fortaleça o teste discriminante; após três rodadas, revise manualmente.
 

package/hooks/change-nag.mjs

@@ -13,6 +13,7 @@ import {
   profileSentinelId,
   resolveHookOperatingProfile,
 } from './operating-profile-runtime.mjs';
+import { consumeSessionTaskOperatingProfile } from './operating-profile-task-store.mjs';
 
 export function nagDecision(input, vaultBase, { profile = 'GOVERN' } = {}) {
   if (input && input.stop_hook_active) return null; // anti-loop: sempre primeiro
@@ -39,6 +40,13 @@ if (process.argv[1] && import.meta.url === pathToFileURL(process.argv[1]).href)
       : runtime.bindingError
         ? { decision: 'block', reason: profileRuntimeError(runtime.bindingError) }
         : nagDecision(input, runtime.vaultBase, { profile: runtime.profile });
+    if (!decision && runtime.taskLease?.state === 'active') {
+      consumeSessionTaskOperatingProfile(
+        runtime.vaultBase,
+        runtime.identity?.canonicalConversationId || input?.session_id || input?.sessionId || '',
+        runtime.taskLease.lease_id,
+      );
+    }
     writeHookOutput(decision || {});
   } catch {
     writeHookOutput({});