#22141: Create ContextMemory documentation

Added documentation for ContextMemory, including installation, usage, commands, and integration. ## Summary Describe the problem and fix in 2–5 bullets: - Problem: - Why it matters: - What changed: - What did NOT change (scope boundary): ## Change Type (select all) - [ ] Bug fix - [ ] Feature - [ ] Refactor - [x] Docs - [ ] Security hardening - [ ] Chore/infra ## Scope (select all touched areas) - [ ] Gateway / orchestration - [ ] Skills / tool execution - [ ] Auth / tokens - [x] Memory / storage - [ ] Integrations - [ ] API / contracts - [ ] UI / DX - [ ] CI/CD / infra ## Linked Issue/PR - Closes # - Related # ## User-visible / Behavior Changes List user-visible changes (including defaults/config). If none, write `None`. ## Security Impact (required) - New permissions/capabilities? (`Yes/No`) - Secrets/tokens handling changed? (`Yes/No`) - New/changed network calls? (`Yes/No`) - Command/tool execution surface changed? (`Yes/No`) - Data access scope changed? (`Yes/No`) - If any `Yes`, explain risk + mitigation: ## Repro + Verification ### Environment - OS: - Runtime/container: - Model/provider: - Integration/channel (if any): - Relevant config (redacted): ### Steps 1. 2. 3. ### Expected - ### Actual - ## Evidence Attach at least one: - [ ] Failing test/log before + passing after - [ ] Trace/log snippets - [ ] Screenshot/recording - [ ] Perf numbers (if relevant) ## Human Verification (required) What you personally verified (not just CI), and how: - Verified scenarios: - Edge cases checked: - What you did **not** verify: ## Compatibility / Migration - Backward compatible? (`Yes/No`) - Config/env changes? (`Yes/No`) - Migration needed? (`Yes/No`) - If yes, exact upgrade steps: ## Failure Recovery (if this breaks) - How to disable/revert this change quickly: - Files/config to restore: - Known bad symptoms reviewers should watch for: ## Risks and Mitigations List only real risks for this PR. Add/remove entries as needed. If none, write `None`. - Risk: - Mitigation: <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a single markdown file (`docs/contextmemory/contextmemory.md`) that documents `@akashkobal/contextmemory`, an external third-party npm package authored by the PR contributor. The package has no relationship to the OpenClaw project — it is not a dependency, not referenced in any source file, and not part of OpenClaw's feature set. - The documentation promotes a personal npm package (`@akashkobal/contextmemory`) with installation instructions, usage guides, and the author's GitHub profile — none of which relate to OpenClaw - The file is not added to `docs/docs.json` (Mintlify navigation), so even if merged it would be an orphan page unreachable through the docs site - The PR template is entirely unfilled — no problem statement, no change type selected, no security impact assessment, and no verification steps - **Recommendation**: This PR should not be merged. The OpenClaw docs directory is for documenting OpenClaw itself, not for hosting documentation for unrelated third-party packages <h3>Confidence Score: 1/5</h3> - This PR should not be merged — it adds promotional documentation for an unrelated third-party package to the OpenClaw docs directory. - Score of 1 because the PR introduces content that is entirely unrelated to the OpenClaw project. The added file documents a personal npm package (@akashkobal/contextmemory) with no connection to OpenClaw's codebase, features, or ecosystem. The PR template is completely unfilled, and the file is not integrated into the docs navigation. - docs/contextmemory/contextmemory.md — this entire file documents an unrelated third-party package and should not be included in this repository _{Last reviewed commit: adb5231} <!-- greptile_other_comments_section --> _{(4/5) You can add custom instructions or style guidelines for the agent [here](https://app.greptile.com/review/github)!} <!-- /greptile_comment -->