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/session-2026-05-14-readings-spec-and-l1-handoff.md

@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/session-2026-05-14-readings-spec-and-l1-handoff
+---
+
 ---
 name: Session 2026-05-14 — Readings spec landed (15th content type, commit 5792286), PDF/Print posture session planned, chamber cruft audit revealed 47% needs work, mempalace mine still running through Phase 5, context clearing with L1 recall-fix as pulling thread
 description: Substantial morning session continuing from yesterday's bge-m3 mine. Resolved gloss/commentary form question with Readings as 15th ARC type, ratified by Genette + Carruthers (read directly). Audited chamber: 186/399 files need work. Built dedicated session plan for both PDF/Print postures. Disabled Stop + PreCompact mempalace hooks (settings.json backup preserved) before context clear, so the running mine isn't interrupted. Pulling thread for cleared context: L1 recall-fix focused session per the saved plan.
@@ -112,4 +116,4 @@ The L1 work doesn't touch mempalace; the still-running mine is unaffected by L1
 1. **Will PR #442's branch hold through the rest of the continental-theory tail** (heavy files: Habermas, Foucault, Derrida, Mauss, Bourdieu, Lévi-Strauss arriving now) without HNSW corruption? The 20+ hours so far suggest yes, but the load increases as Phase 5 hits the heaviest files.
 2. **Did the H2 vector-recall issue still reproduce in current main**, or has some adjacent change silently fixed/changed it since April 19? The L1 session's investigation phase answers this.
 3. **What does the chamber-queryability audit actually find** when run post-mine? Specifically: is the KG populated for chamber content entities (i.e., does `kg_query("Saenger")` return rich facts), or is the KG mostly session-level entities? The answer determines whether the multi-modal-tool approach pays off.
-4. **For the PDF posture session: which Van de Graaf ratio variant?** Classic canon (1:1:2:2) or Tschichold-refined? Chamber masters (Tschichold's *Form of the Book*, Bringhurst's *Elements*) have the answer.
+4. **For the PDF posture session: which Van de Graaf ratio variant?** Classic canon (1:1:2:2) or Tschichold-refined? Chamber masters (Tschichold's *Form of the Book*, Bringhurst's *Elements*) have the answer.