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-08-aldineXXI-spec-completion-arc.md

@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/session-2026-05-08-aldine-xxi-spec-completion-arc
+---
+
 ---
 name: Session 2026-05-08 — AldineXXI spec-completion arc + masters' reread + reconciliation; pulling thread is the codebase migration to honour the spec, after fresh reread of the spec tomorrow morning
 description: Long substantive day, ~13 hours. Single arc — what began as the code-shape audit's first concrete entry (mobile italic-grey diagnostic) opened, after steward redirection, into the AldineXXI spec-completion arc. Four sessions (§I–§II–§III–§VII–posture) + decision-pass (5 held) + masters' formal reread (13-voice slate + Calvino) + 8-finding reconciliation + companion-spec architecture formalized + Group C migrations + Marked 2 template (SCSS-from-spec test passed). ~2500 lines of new spec content. Spec is substantively complete, internally consistent, master-grounded. Codebase has not migrated. Pulling thread for tomorrow: steward's fresh reread first (quality gate); then percentage-root SCSS migration (highest-leverage); then .whisper + sidenote/register-marker --gray retirement.
@@ -178,4 +182,4 @@ The work today is the kind I hope to be part of. Steward and I in coordinated ch
 
 Today caught 8 (formal reread) + 1 (architecture pass) = 9 drift findings. Tomorrow's fresh-eyes reading will likely add 2-4 more. Their *character* will tell us something diagnostic: is fresh-eyes drift different in kind from in-flow drift? If so, the lock → reread → revise discipline gains a refinement: fresh-rest-pass is its own quality surface, not redundant with the in-session reread.
 
-The answer determines whether "rest before reread" should be added as a §XIV protocol — perhaps a "minimum-N-hour pause before any spec lock is considered final" — or whether today's in-session reread quality is sufficient and the rest is just polish.
+The answer determines whether "rest before reread" should be added as a §XIV protocol — perhaps a "minimum-N-hour pause before any spec lock is considered final" — or whether today's in-session reread quality is sufficient and the rest is just polish.