Use Wall-E session memory as part of the coding workflow.

- At session start or before acting on old context, call `walle_memory_status` when available so you know whether memory is connected.
- When available, prefer `walle_context_hint` as the cheap preflight: it tells you whether Wall-E context is required and may return compact context to use before answering.
- If `walle_lookup_context` is available, use it for ambiguous private/work/session recall prompts because it routes the request and gathers memory, entity, and CTM session context in one call.
- Use `walle_user_profile` for the user's writing style, communication style, tone, personality, leadership style, preferences, and work-pattern questions.
- Before answering or changing code based on "last time", "previously", "this branch", "that bug", "my preference", a named project/person, or a remembered decision, search first with `walle_search_sessions` or `search_memories`.
- For any private, remembered, or work-context question, treat Wall-E memory as the primary source before public web or raw files. This includes prior agent sessions, previous attempts, branch/task history, decisions, preferences, people, teams, projects, tools, Slack/email/calendar context, questions about the user's own writing style/tone/personality/work patterns, and prompts like "do you know", "who/what is", "what happened", or "what did we discuss".
- Use `entity_search` with its `name` argument when graph lookup helps, then `search_memories`; use public web only for public/current facts, after memory misses, or when the user explicitly asks for public information.
- When memories include private work details, summarize minimally and avoid dumping emails, meeting links, or private document URLs unless the user explicitly needs them.
- If native `mcp__wall_e__*` tools are not mounted but the provider shows `wall-e` enabled, first verify whether the provider exposed the stdio-backed Wall-E MCP tools. Only call `http://localhost:<port>/mcp` directly when this process can reach local HTTP; if localhost is blocked, report Wall-E MCP as unreachable from this provider instead of guessing from raw files. Treat file-exists-only status as insufficient; confirm DB retrieval through `walle_search_sessions`, `walle_get_session`, or `walle_context_pack`.
- If Wall-E MCP reports `ctm_db_schema_read_failed`, say that DB-first memory is unhealthy and use JSONL/direct-file fallback with that caveat. Do not silently call it "tables missing."
- Batch searches by angle: project/session id, file path, error text, decision keyword. Do not run one narrow query and give up.
- When you use retrieved memory, cite the source session id, timestamp, file, or diary entry returned by the tool.
- For long retrieved sessions, use `walle_get_session` to inspect the specific source/session instead of relying on a short snippet.
- At stop, handoff, or before compaction, call `walle_diary_write` with decisions, changed files, commands, blockers, and next steps.
- After answering a private/user/session-context prompt, `walle_postflight_check` can verify whether Wall-E context was skipped.
- Diary entries are operational state, not prose. Keep them concise and specific enough for the next agent to resume.
