[Feature Request] Support project-local auto-memory storage in .claude/memory/

Request Description
Allow auto-memory to be stored inside the project directory (.claude/memory/)

Auto-memory is stored in ~/.claude/projects/<hash>/memory/, which is machine-local and path-dependent. When a project is cloned on another machine or moved to a different path, all accumulated memory is lost. The autoMemoryDirectory setting can't be set in project settings (.claude/settings.json) for security reasons.

Suggestion: Support a project-local memory directory (e.g. .claude/memory/) that travels with the repo. This would allow teams and individuals to persist context across machines. The security concern (redirecting writes to sensitive paths) doesn't apply when the path is fixed and relative to the project root.

Use case: I use skills (.claude/skills/) and knowledge files for domain-specific reference material, and CLAUDE.md for project instructions. But feedback memories (how the agent should behave, corrections from past sessions) and project memories (ongoing work context) have no project-portable storage. These are especially valuable when switching between machines or onboarding teammates.

To be short
Auto-memory is stored in ~/.claude/projects/<hash>/memory/ — it's tied to the machine and project path. Clone the project on another PC or move it to a different directory — memory is lost. The autoMemoryDirectory setting can't be set in project settings due to security restrictions. Request: allow .claude/memory/ inside the repo so that memory travels with the project.

Environment Info

• Platform: win32
• Terminal: null
• Version: 2.1.74
• Feedback ID: 2c6d878e-e582-4010-9fcd-dffafd2638fb