#16657: feat(memory-lancedb): add memory CLI command alias

## Summary - feat(memory-lancedb): add memory CLI command alias - Split from our `v2026.2.13` patch train as a single-purpose change for easier review. ## Why - Keep the diff focused and low-risk so it can be merged or reverted independently. ## Scope - Branch: `feat/memory-lancedb-memory-cli-command-en` - Files changed: 2 - Key files: - `extensions/memory-lancedb/index.test.ts` - `extensions/memory-lancedb/index.ts` ## Test Plan - Suggested local command: - `./node_modules/.bin/vitest run extensions/memory-lancedb/index.test.ts` - Validation status: - [ ] CI checks pass - [ ] Maintainer re-ran local tests ## Risk & Rollback - Risk: low to medium; impact limited to touched module(s). - Rollback: revert this PR commit(s) cleanly. ## Co-authorship - Co-authored by @ciberponk and Codex (GPT-5). <!-- greptile_comment --> <h3>Greptile Summary</h3> Added `memory` CLI command alias to the memory-lancedb plugin alongside the existing `ltm` command. Both commands now invoke `api.runtime.tools.registerMemoryCli(program)` to provide consistent CLI access patterns. - Registered new CLI command alias `memory` that uses the same implementation as memory-core plugin - Existing `ltm` command with custom subcommands (list, search, stats) remains unchanged - Test coverage added to verify both commands are registered correctly - No conflicts expected since only one memory plugin can be active at a time (memory slot mechanism) <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The changes are minimal and well-tested. The PR adds a simple CLI command alias without modifying any existing logic. Test coverage verifies both commands are registered. The memory slot mechanism ensures no conflicts between plugins. The implementation follows existing patterns from memory-core plugin. - No files require special attention _{Last reviewed commit: 696c160} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->