Feature: Automatic knowledge/memory sharing to git

Problem

During CPSEARCH-10981 multi-agent refactor, we discovered that Claude Code's memory system is not automatically shared to the repository. This means learnings from complex sessions don't get captured in version control for team knowledge.

• Claude Code memory saves locally (persists across sessions)
• But NOT automatically pushed to git/repo
• Team doesn't benefit from discovered patterns, lessons learned, or best practices
• Only discoverable if manually documented in commit messages or docs

Use Case

CPSEARCH-10981 cursorMark refactor discovered:

• Best practices for large multi-file refactors
• Process improvements (test-compile gates, domain review before multi-review)
• Common pitfalls (breaking API changes, test file updates, state semantics)
• These insights are only in local memory, not accessible to team

Desired Capability

Automatically save important learnings, patterns, and decisions to a repo file (e.g., docs/SESSION_LEARNINGS.md or .claude/learnings/) so that:

• Team knowledge accumulates in version control
• Future sessions can reference prior session findings
• Complex refactors leave a knowledge trail for the team

Suggested Implementation

Provide either:

1. Automatic push of significant learnings to a git-tracked file when refactors complete
2. Explicit tool to push memory to repo file with user approval