Bug: Agent reads memory/YYYY-MM-DD.md even with session-memory hook disabled

[G9Pedro]

Reported by: ForaDoPadrao (Discord, Feb 25)

Description:
When the session-memory hook is disabled in openclaw.json and AGENTS.md explicitly says Do NOT read memory/YYYY-MM-DD.md, the agent still attempts to read daily notes on /new and gets ENOENT errors.

Likely cause: Something in OpenClaw's internal system prompt instructs the agent to read daily notes independently of the hook.

Repro:

1. Disable session-memory hook in openclaw.json
2. Start new session with /new
3. Agent still attempts Read memory/YYYY-MM-DD.md

Expected: With hook disabled, agent should not attempt to read daily notes.

Environment: OpenClaw 2026.2.24, ClawVault 3.1.0

Note: This may be an OpenClaw issue rather than ClawVault, but documenting here since it affects the plugin behavior.

[G9Pedro]

This is a known separation-of-concerns issue. The daily memory file reading is likely triggered by the AGENTS.md or HEARTBEAT.md boot sequence instructions in the workspace files, which are injected into the system prompt independently of the session-memory hook.

The hook controls whether ClawVault writes memory entries on session start — but if AGENTS.md says 'read memory/YYYY-MM-DD.md in Boot Sequence', the agent follows that instruction from the workspace context regardless of hook config.

Workaround: Remove the memory read instruction from AGENTS.md/HEARTBEAT.md, or add a conditional guard in those files (e.g. 'if session-memory hook is enabled, read...').

Proper fix would be a ClawVault config flag like readDailyNotes: false that gets passed to the system prompt injector to suppress the instruction, separate from the hook that controls writes. Worth tracking as an enhancement.