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>

claude/memory/user-care-over-traffic-skills-as-accountability.md

@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/user-care-over-traffic-skills-as-accountability
+---
+
 ---
 name: Care over traffic — work answers to itself; skills as accountability not productivity
 description: Steward correction 2026-04-28 of an earlier "fix carelessness so I can just write" framing. The corrected posture: even with no traffic, the few who find ARC see craft; quality work matters whether or not it's read; skills/agent-circles serve consistency and accountability, not scale.
@@ -18,4 +22,4 @@ originSessionId: e5a1fa7c-cae6-49c4-8678-e27ce379639b
 - Cousin to the **Non-Convergence Principle** in `~/CLAUDE.md`: *"the system should be inhabitable, dignified, and sufficient at any point along the way"*; no step depending on a future step to be meaningful.
 - Cousin to **"Would Alexander do it?"** feedback (2026-04-27): each pattern at a time, not bulk-scaffold; the cramped will of the maker is the failure mode.
 - The audience-building diagnosis from the jurist (find the right 50 people; address RSS / email-capture gaps) sits *next to* this principle — practical, not prerequisite. The work answers to itself first; audience-building is a separate concern.
-- When time pressure surfaces (e.g., 2026-04-28 jurist's "publish today"), don't compromise care for speed; the publish-today imperative still operates within the care-frame, not against it.
+- When time pressure surfaces (e.g., 2026-04-28 jurist's "publish today"), don't compromise care for speed; the publish-today imperative still operates within the care-frame, not against it.