chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized
live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds
long YAML description lines, strips final newlines. Bodies untouched —
verified via full diff classification. From this commit forward, any diff in
claude/memory shows only what Basic Memory or the session writes.

Trial design: MemPalace untouched as incumbent; git status check on this dir
at every wrap; end-of-day evaluation (recall quality, sync robustness,
rebuild-from-files, malformed-file behavior).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
David F Glidden
2026-06-06 09:52:17 +02:00
co-authored by Claude Opus 4.8
parent 161fad7ae2
commit 3f9a89b00c
283 changed files with 2055 additions and 620 deletions
@@ -1,9 +1,13 @@
---
name: General-purpose Python CLI tools install via pipx, not per-tool venvs
description: For Python tools the steward uses as commands (docling, ruff, black, ansible, etc.), prefer pipx over creating dedicated venvs. pipx isolates dependencies under the hood while putting the CLI on PATH globally — same shape as Homebrew tools.
description: For Python tools the steward uses as commands (docling, ruff, black,
ansible, etc.), prefer pipx over creating dedicated venvs. pipx isolates dependencies
under the hood while putting the CLI on PATH globally — same shape as Homebrew tools.
type: feedback
originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
permalink: claude-memory/feedback-tool-installation-pipx-default
---
For Python CLI tools that belong in the steward's general toolset, **install via pipx**, not in a per-tool venv:
```
@@ -23,4 +27,4 @@ End state: tool is a regular shell command (`docling input.epub -o output.md`) a
- **System Python (`pip install --user`)** — rarely the right answer; pollutes system site-packages and is hard to clean up. Avoid.
- **Homebrew direct** — if the tool has a Homebrew formula (e.g., `pandoc`, `pipx` itself), that's the cleanest. Check `brew search <tool>` before defaulting to pipx.
When unsure, the question to ask: *"Is the steward going to invoke this as a command from outside any specific project?"* If yes → pipx. If the answer is "only inside the project source tree, while modifying that source tree" → per-project venv.
When unsure, the question to ask: *"Is the steward going to invoke this as a command from outside any specific project?"* If yes → pipx. If the answer is "only inside the project source tree, while modifying that source tree" → per-project venv.