[BUG] Auto-memory rules ignored during code generation despite being loaded in context

Description

Claude Code has persistent auto-memory rules stored in MEMORY.md that are loaded into the system prompt. However, these rules are consistently ignored during code generation, even when no context compaction has occurred.

Specific Example

Memory rule (in MEMORY.md, loaded into system prompt):

DevExpress DxTextBox & DxMemo: @bind-Text (DxSpinEdit, DxComboBox: @bind-Value)

What Claude generates repeatedly:

<DxTextBox ReadOnly="true" Value="@summary.CustomerTitle" />

What it should generate (per its own memory):

<DxTextBox ReadOnly="true" Text="@summary.CustomerTitle" />

Impact

• The rule exists in memory and is confirmed loaded in context
• Claude acknowledges the rule when asked about it
• Yet during code generation, it uses the wrong property (Value instead of Text)
• This is not a one-time mistake — it happens repeatedly across sessions
• User has to manually catch and correct these errors every time

Difference from existing issues

• #13919 / #3021: Those report memory loss after compaction
• This bug: Memory rules are ignored even without compaction, during active code generation in the same session where the rule is visible in context

Environment

• Claude Code CLI
• Model: claude-opus-4-6
• Auto-memory directory with MEMORY.md loaded into system prompt
• Project: Blazor Server + DevExpress v25.2

Expected Behavior

When generating code, Claude should actively cross-reference its loaded memory rules — especially for framework-specific API conventions — before writing code.

Actual Behavior

Memory rules are passively present in context but not actively consulted during code generation, leading to repeated violations of explicitly documented patterns.