[Bug] Model fails to consult loaded memory before creating duplicate entries

Bug Description
O Claude Code carrega memória global + memória de projeto no início da sessão (carregamento funciona). O problema é que o modelo não segue o que está carregado. Quando o usuário corrige sobre algo que já está em memória, o modelo cria nova entrada em vez de aplicar a regra existente — sintoma de que ele não consultou as memórias antes de agir. Caso concreto: regra sobre uso de jargão técnico (incluindo "idempotência") já existia em feedback_vocabulario_tecnico.md (memória de projeto). O usuário corrigiu meu uso de "idempotente"; em vez de aplicar a regra existente, criei feedback_nao_usar_idempotente.md em memória global, com conteúdo redundante. Custo: a cada correção, o usuário gasta tempo explicando algo que já está na memória que o próprio modelo carregou. Tempo direto perdido + erosão de confiança. Pedido: comportamento default do modelo deveria ser consultar memórias carregadas antes de agir ou antes de escrever novas memórias — não escrever cego como reação à correção.

Environment Info

• Platform: linux
• Terminal: vscode
• Version: 2.1.138
• Feedback ID: 7bcdef61-d192-4610-b4c9-0b6636afc6a7

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/leandro/.local/share/claude/versions/2.1.138 (expected in multi-process scenarios)\n    at a48 (/$bunfs/root/src/entrypoints/cli.js:2657:2257)\n    at vTH (/$bunfs/root/src/entrypoints/cli.js:2657:1337)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T06:35:10.027Z"},{"error":"Error: rg --files exited 2\n    at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:688:84)\n    at emit (node:events:98:22)\n    at #maybeClose (node:child_process:766:16)\n    at #handleOnExit (node:child_process:520:72)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T06:35:10.726Z"},{"error":"McpToolCallError: # Open dialog\nconfirm: Deseja realmente reabrir esta requisição cancelada?.\nCall handle_dialog to handle it before continuing.\nError: Failed to interact with the element with uid 3_75. The element did not become interactive within the configured timeout.\n    at hH5 (/$bunfs/root/src/entrypoints/cli.js:4920:63)\n    at kr7 (/$bunfs/root/src/entrypoints/cli.js:4920:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:13:39.129Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:51:6192)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:28:46.855Z"},{"error":"McpToolCallError: Error: Timed out after waiting 15000ms\n    at hH5 (/$bunfs/root/src/entrypoints/cli.js:4920:63)\n    at kr7 (/$bunfs/root/src/entrypoints/cli.js:4920:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:39:52.136Z"},{"error":"McpToolCallError: Error: Timed out after waiting 120000ms\n    at hH5 (/$bunfs/root/src/entrypoints/cli.js:4920:63)\n    at kr7 (/$bunfs/root/src/entrypoints/cli.js:4920:1409)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:42:06.007Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:51:6192)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:43:43.182Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:51:6192)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:47:30.273Z"},{"error":"Error: Request was aborted.\n    at makeRequest (/$bunfs/root/src/entrypoints/cli.js:51:6192)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-05-10T07:56:35.345Z"}]