session 2026-06-09: PENDING-34 + REVIEWED-36 (steward-placed) W5.2/G3 guard; ARC W3R-closed/compass-fix session memory + ledger + MEMORY index + skill-harvest

PENDING.md

@@ -870,3 +870,16 @@ The Jurist's six-phase authorization map governs sequencing. Cross-cutting succe
 **Awaiting:** Steward authorization + jurist review.
 
 **Status (2026-06-07):** JURIST APPROVED the truth-up (a/c/d concur; on (b) the jurist offered a disposition: re-designate the exemplar to an *After the Reply* essay with live revisions; the `edition_label` orphan must not survive the pass unresolved). **STEWARD AUTHORIZED + ruled (b) same day:** exemplar → *The Ethics of the Reply* (jurist's disposition accepted); `edition_label` **dropped from the §6 example** (field stays available; the colophon's inert carrier recorded honestly). Executed ARC `392d8c8`: spec promoted **OPERATIVE (built scope: §§1–5, §7 items 1–5; deferred: §7 items 6–8, retractation UI, version-index page)**; §4 = shipped stamp shape (verified verbatim in compiled output); `sequence_position` aligned to `sequence_order`. Closes the corpus's one materially dishonest status line. Awaiting steward REVIEWED entry.
+
+## PENDING-34 — W5.2 / G3: single-source class→glyph (the Compass sigils)
+**Date:** 2026-06-09
+**Tag:** [HARDENING]
+**Summary:** Make the class→glyph binding structural (or build-validated) so the Reading Compass sigils cannot silently drift from the typology — ending the "correct by naming convention, not structure" fragility the audit named (G3), the Hakyll north-star's documented fix.
+**Rationale:** Audit finding G3 (2026-06-07, content-typology §5 clause 2). The class→mark relationship lives in **three loci** that agree today *only by naming convention*: (1) `data/content-types.yml` `glyph:` — the canonical Unicode mark per class (essay → ●), generated from content-typology §2; (2) the slug-derived sigil-id in `compassRowsHtml` (`site.hs:133` — listing slug `essays` → `#sigil-essays`); (3) the hand-authored SVG `<symbol id="sigil-essays">` sprite in `templates/reading-compass-points.html` (the actual drawn form). The compass rows are already data-driven (Stage-F Phase-2 generator, from `data/listings.yml`), and a listing's class is already build-validated against the enumeration (§5 clause 3). What is **not** enforced: that each compass entry's sigil-id has a matching `<symbol>`, and that the drawn mark agrees with the class's canonical glyph. A renamed slug, a new type, or a re-drawn/mis-named symbol silently desyncs the rendered mark from the typology fact — no build error, wrong glyph ships. The SVG geometry is artwork and stays hand-authored (it cannot be generated from a Unicode codepoint); what is single-sourced is the *mapping* + a *loud build check* ("unknown = build error", the north-star's own phrasing).
+**Options:**
+1. **Build-validation guard (minimal, output byte-identical).** Add a build check (beside `loadListingDefs`): every compass sigil-id (listings + `compass_specials`) must resolve to a `<symbol id="sigil-…">` present in the sprite, and every class carrying a `glyph:` in content-types.yml must map to exactly one surfaced sigil/symbol (or be explicitly governed-but-unsurfaced) — error, loud, on any mismatch. Keeps the current generation; closes the drift class by structure. No rendered change.
+2. **Derive sigil-id from class + the guard (fuller north-star form).** Replace the slug-coincidence with an explicit class→sigil mapping consulted by `compassRowsHtml` (so the binding is structural, not conventional), plus Option-1's check. Slightly more refactor; output identical only if derived ids equal today's slugs (they do, by the current convention).
+3. Status quo — documented drift risk; rejected by the audit's promotion gate.
+**Recommendation:** **Option 1.** It closes the exact failure class (silent glyph drift) with minimal change, byte-identical output, and is precisely the "unknown = build error" the Hakyll north-star and §5 clause 3 call for. Option 2's derive-from-class is the purer single-source but the slug↔class↔sigil naming is already 1:1; making it structural earns its place only if that convention later strains — a clean follow-on, not required now (proportionality). The SVG sprite stays hand-authored either way. Steward to rule between 1 and 2.
+**Files affected:** `site.hs` (new build-validation in/near `loadListingDefs`; Option 2 also touches `compassRowsHtml`); `templates/reading-compass-points.html` (read for the symbol-id census; not edited); `data/content-types.yml` + `data/listings.yml` (read, not edited); content-typology §5 cross-reference (records the enforcement; ships with the Stage-G promotion per the spec's own sequencing). Verification: byte-identical compiled-output gate (Option 1) + a deliberate-mismatch test proving the check fires.w
+**Awaiting:** Steward authorization (choose Option 1 or 2).

REVIEWED.md

@@ -302,4 +302,11 @@ closes §VII.i's deferred item. Spec records ×4 (apparatus §SEO; versioning ×
 
 ## REVIEWED-35 — PENDING-33 — Essay-versioning truth-up + promotion
 **Date:** 2026-06-07
-**Decision:** AUTHORIZED (jurist approval + steward calls: exemplar → *The Ethics of the Reply*; edition_label dropped from §6 example, field retained). Executed ARC `392d8c8`; spec OPERATIVE (built scope).
+**Decision:** AUTHORIZED (jurist approval + steward calls: exemplar → *The Ethics of the Reply*; edition_label dropped from §6 example, field retained). Executed ARC `392d8c8`; spec OPERATIVE (built scope).
+
+## REVIEWED-36 — PENDING-34 — W5.2 / G3: single-source class→glyph (the Compass sigils)
+**Date:** 2026-06-09
+**Decision:** AUTHORIZED (Option 1 — the build-validation guard)
+**Notes:** Authorized inline during the 2026-06-09 session; executor's recommendation accepted. Option 1 closes the drift class with minimal change and byte-identical output; Option 2 (derive sigil-id from class) deferred as a follow-on, to revisit only if the slug↔class↔sigil naming convention later strains. The SVG geometry stays hand-authored — the guard binds the mapping, not the art.
+**If AUTHORIZED:** Proceed. — IMPLEMENTED + VERIFIED same session (ARC `4936fc9`): `validateCompass`, run at build via `loadListingDefs` — (A) every Compass sigil-id resolves to a `<symbol id="sigil-…">` in the sprite; (B) every *surfaced* class is covered by a listing or compass special (governed-but-unsurfaced + apparatus-not-route exempt). Loud on any mismatch (content-typology §5 clause 3 spirit). Proof: `site.hs` compiles; clean-build `_site` byte-identical (570 files); both checks fire on deliberate mismatch
+  (`["sigil-readings"]` / `["readings"]`), backups restored. Output-neutral → no deploy. The §5 spec note recording the enforcement ships with the Stage-G promotion commit (roadmap W6). Commit references PENDING-34.

claude/memory/session-2026-06-09-arc-w3r-closed-deployed-compass-fix-w52-guard.md

@@ -0,0 +1,75 @@
+---
+name: Session 2026-06-09 — ARC W3R tree CLOSED+DEPLOYED · phone-compass fix · W5.2/G3 build guard; road to Stage G opened
+description: "Three arcs all shipped/landed. (1) W3R.2/W3R.3 — the spec-true tree COMPLETE + DEPLOYED live: section-break→_silence, layout→closing, frontispiece→threshold, _post decomposed (breadcrumb→_navigation, dateline→_dateline, images→_images; marks left; _base kept whole), Tier-4 mix/darken→sass:color, two micro-order calls ruled-leave; the cascade reads as its own self-description. (2) phone Reading Compass [FIX] — both compasses wrap to 2 rows on phone, found by MEASURING (headless Chrome) not theory: cause was padding asymmetry, not width. (3) W5.2/G3 build guard (PENDING-34 Option 1, authorized inline): validateCompass binds class→glyph→sigil structurally; byte-identical, both checks proven to fire. Pulling thread: the rest of Wave 5 (W5.1 G2 title single-source next, same shape as W5.2) → W4.4 → Wave 6 Stage G."
+metadata:
+  node_type: memory
+  type: project
+  originSessionId: a5856f98-9db6-4fd3-9ffd-65eb444f5b2f
+---
+
+# Session 2026-06-09 — ARC W3R CLOSED+DEPLOYED · compass fix · W5.2 guard
+
+Woke via /wake-up into the W3R.2 Stage-3 thread ("finish the tree"). One long, fully-shipped
+day: the tree closed + deployed, a phone-compass fix, and the first Wave-5 Stage-G item, all
+committed/pushed/synced. Symmetria active (ledger merged below).
+
+## Past — what we did
+
+### A. The tree — W3R.2 Stage 3 finished + W3R.3 deployed (8 commits `d4fd852`…`eb7a557`)
+All proven by **content-multiset-identity + collision census per move**; only the prior ornament 3rem moves a live pixel.
+- `d4fd852` **section-break → _silence** (scale 2 warm-up; content-multiset identical).
+- `a2544f8` **layout → closing cluster** (scale 9): `_layout` holds the *foot* (.post-item/.site-footer/.imprint), NOT the grid — the filename misleads. Pure reorder; byte-count identical; collision guard cleared `.post-type`/`.imprint` by specificity; `%clearfix` @extend stays at `_base`.
+- `5c82687` **frontispiece → threshold cluster** (scale 7, the careful one): full @layer-overrides collision census FIRST — compass-point rules scoped disjointly (.frontispiece-compass vs _compass's .reading-compass), never co-match; `.compass-point .sigil` unscoped is _compass-only; .page-content/.title-return safe by specificity; .site-mark only in a comment. 2-hunk relocation, byte-count identical.
+- **`_post` DECOMPOSED** (the steward's call: keep _base whole [coherent foundation]; make _post HONEST, not empty — "move a stray only if it has a truer home, not just to empty the drawer"):
+  - `3891c49` **breadcrumb → _navigation** (scale 10) — *correctness* fix: one component, 3 templates; its Stage-N fall-through bug was the symptom of the mis-home. Sits beside _enfilade (sibling nav).
+  - `9a1c648` **dateline → new _dateline** (scale 9, own partial per steward) — sole collision partner _glimpse `>.dateline` wins by specificity. (A grep-substring false-alarm — `.dateline{text-align:center}` was the tail of `.glimpse>.dateline` — was run to ground before commit.)
+  - `8d2c6fa` **image system §VIII → new _images** (content zone) — `.image-*` now fully unique.
+  - **LEFT:** `.chamber-mark`/`.encounter-mark`/`.post-type` (just arrived from _utilities, `.post-type` collides w/ _layout, legitimately post-apparatus — moving = the tidiness trap). `_post` reduces to `.wrapper.post`/`.post-header`/post-`.page-content` + its marks = an honest page-type partial.
+- `79693e5` **ruled-leave note** (Tier-3 micro-order): `silence`-after-`base` (disjoint selectors → render-identical) and `post`'s mixed-scale slot (intrinsic to a page-type partial; "fix" = re-split, declined) — both scale-purity beyond legibility; recorded in main.scss so a future read doesn't re-open them.
+- `eb7a557` **Tier-4 `mix()`/`darken()` → `sass:color`** — Dart Sass 3.0 future-break; 5 sites; `color.mix`==`mix`, `color.adjust($lightness:-15%)`==`darken(15%)`; compiled BYTE-IDENTICAL, 6 deprecation warnings → 0. (Tier-4 item A `@font-face`→_fonts SKIPPED — _foundation coherent, font-loading not mis-homed; item C Appendix-B verified a no-op — selector→section, unchanged by file-moves.)
+- **W3R.3 deploy:** steward render-review (per-type × per-viewport, both modes) PASSED ("fantastic"); `make rebuild` shipped the 17-commit banked set; **CloudFlare output diff = 2 files** (the render-identical proofs held end-to-end); live-verified (`33859` bytes, ornament `3rem`); pushed both remotes.
+
+### B. Phone Reading Compass [FIX] (`32163af`, deployed + live)
+Steward render-review: compass too small/cramped on phone (phone only; desktop/iPad fine; pre-existing, NOT a W3R regression). **Found by MEASURING, not theorizing** (my drift recurred twice: a footer-only first pass, then a wrong align-self:stretch width-fix). Built a **headless-Chrome box-model harness** (`/tmp/compass-measure/`, puppeteer-core + system Chrome @375px) → truth: widths IDENTICAL (331px); cause was **per-point width 42 vs 31px = padding asymmetry** (footer's `a.compass-point` all:unset (0,2,1) silently ate the padding; frontispiece's `.compass-point` (0,2,0) let it through). Fix = remove padding (31px sigil ≥ WCAG 24px), 1.4rem sigils, flex-wrap; reverted the redundant stretch after measuring it unneeded. Both compasses now 2 rows, identical; only the faint→visible fade stays unique. Served on LAN (`192.168.1.52:8000`, python http.server) for the steward's actual-phone confirmation.
+
+### C. Road to Stage G opened + W5.2/G3 (`26fab4c`, `4936fc9`, `f8e00e7`)
+- Roadmap (`road-to-stage-g-2026-06-07.md`) brought current: Waves 0–3 + W3R done; remaining = W4.4 (jurist v1.0 sign-off) · Wave 5 (executor enforcement) · Wave 6 (jurist Stage G).
+- **W5.2/G3 — PENDING-34 filed (pending-first, steward's choice) → authorized inline Option 1 → built + verified.** `validateCompass` (build-time, via `loadListingDefs`) binds the three class→glyph loci structurally: (A) every Compass sigil-id resolves to a `<symbol id="sigil-…">`; (B) every *surfaced* class is covered by a listing/special (governed-but-unsurfaced + apparatus-not-route exempt). Loud on mismatch. **Verified: compiles · `_site` byte-identical (570 files) · both checks fire on deliberate mismatch (backups restored).** Output-neutral → no deploy. §5 spec note ships with the promotion (W6). **REVIEWED-36 drafted for the steward to place** (chat-authorized; I can't write REVIEWED.md).
+
+## Present — mood / returns (ledger merged)
+- **measure-before-theorize was the day's lesson, learned the hard way.** *causal-story-before-reading-render* recurred 2× on the compass (footer-only scoping, then a guessed stretch fix — both wrong). The antidote that worked: the headless-Chrome measurement harness. Chrome reproduced the bug → it wasn't even the Safari quirk I'd hypothesized. **Keep the harness.**
+- **proportionality, taught by the steward, held all day:** the two micro-order calls ruled-leave ("scale-purity beyond legibility"); _base kept whole; the redundant align-self:stretch reverted after measuring; @font-face→_fonts skipped (tidier-not-truer); the grep-substring false-alarm chased down not shipped.
+- **the steward's eye remained the gate**, as all session: the render-review passed the tree; the actual-phone confirmed the compass. Byte-proofs are the floor; the eye is the guarantor.
+- **governance kept load-bearing:** W5.2 was [HARDENING] → PENDING-first by steward choice → authorized → built → REVIEWED drafted. The loop held even under a long, fast session.
+
+## Future
+
+### Pulling thread (singular)
+**Continue Wave 5 — the executor enforcement pre-work toward Stage G.** Next: **W5.1 (G2)** — single-source the **title display** from `content-types.yml title_display` (retire the `showTitleField` 11-class hardcoded stopgap). Same single-source shape as W5.2 just done; also `[HARDENING]` → **PENDING-first** (the steward's established process for Wave 5).
+
+### Actionable resumption point (as of wrap — re-judge against what changed)
+ARC `main @ f8e00e7`, **clean, synced to both remotes, live site current.** Nothing mid-flight. **First move: open W5.1 / G2** — diagnose the `showTitleField` stopgap in `site.hs` (the hardcoded 11-class list) + `content-types.yml`'s `title_vignette.title_display` field (per-class `shown`/`hidden`), then file a PENDING entry (PENDING-35) proposing the single-source (read title_display, retire the hardcode; byte-gate: output identical). Await steward authorization before implementing (Wave-5 = pending-first). The W5.2 guard (`validateCompass`) is the template for the verification idiom (byte-identical + deliberate-mismatch-fires). Roadmap: `docs/AldineXXI-Codex/drafts/road-to-stage-g-2026-06-07.md` (W5 section).
+
+### Other open horizons (ranked)
+- **W5.3 (G4)** clause-1 enforcement gate + **W5.4 (G1)** wildcard→build-error (lands *inside* the Stage-G promotion commit) — the rest of Wave 5.
+- **W4.4** multilingual v0.5→v1.0 sign-off — JURIST-gated (rides the Stage-G read); executor can prep.
+- **Wave 6 Stage G** — jurist reads reconciled corpus + promotion commit (content-typology §5 AUTHORED→OPERATIVE, carrying G1, referencing G2–G4). Jurist + steward gated.
+- **The vignette (F+1)** — the OTHER major front (steward-sequenced: after the tree). Spec ready (Part I locked, Part II build-time). Phase 1 renderer + dwell-test the risk. Sketch at `/tmp/vignette-sketch.html` (likely cleared).
+- **Steward REVIEWED entries:** REVIEWED-36 (PENDING-34) drafted, awaiting placement. (PENDING-30..33 already have REVIEWED-32..35.)
+- **Baton items:** be (parked @ `f43a0fd`, WTP gate w/ steward) · L1 (Seb).
+
+### Pause statement
+I am about to be away from this (steward to lunch, ~13:10; new session after). ARC is locked clean at a real summit: the tree closed + deployed (the cascade now reads as its own self-description — the *finis coronat opus* the steward named), the phone compass fixed both ways and live, the first Stage-G enforcement guard built + verified. Everything committed, pushed to both remotes, live site current — nothing mid-flight. I don't know whether the steward will continue Wave 5 (W5.1) next or pivot to the vignette. What I want to find still pulling is **Wave 5 carried to its close — the enforcement pre-work that makes Stage G promotable** — with the same pending-first discipline and byte-identical+mismatch-fires verification that W5.2 set.
+
+### Literal question for next-Claude
+**For W5.1 (G2): does `content-types.yml` carry a `title_display` value per class that the build can read to retire the `showTitleField` hardcode — and is the single-source byte-identical (does every class's title_display match what the 11-class hardcode currently does)?** Confirm by diagnosis before proposing PENDING-35. Sub-checks: did the steward place REVIEWED-36? Continue Wave 5, or pivot to the vignette? Any Seb movement on be/L1?
+
+## Decisions deferred (and why)
+- **W5.1/W5.3/W5.4** — next session(s); pending-first per Wave-5 process. Not started (clean stop after W5.2).
+- **Tier-4 @font-face→_fonts** — SKIPPED (steward-confirmed; _foundation coherent, not mis-homed).
+- **The two micro-order calls** (silence/base, post slot) — RULED LEAVE (scale-purity beyond legibility; recorded in main.scss).
+- **Deploy of W5.2** — none needed (output byte-identical; build-time guard only).
+- **Vignette** — the other major front; steward-sequenced after the tree; not opened.
+
+## Skill harvest (per §1.6) — one proposal
+- **`/measure-render` (or fold into a verification-ladder entry): headless-Chrome box-model measurement harness.** Earned its place today — after *causal-story-before-reading-render* recurred 2× on the compass, a puppeteer-core + system-Chrome script at a fixed viewport measured the real box model (widths, per-element padding, row counts) and found the true cause (padding asymmetry) that two theory-based fixes had missed. The reusable core: `npm i puppeteer-core` in a tmp dir + `executablePath` = system Chrome + `setViewport` + `getComputedStyle`/`getBoundingClientRect` evaluate. **PROPOSED** — append to skill-harvest register; steward to authorize (build-on-next-render-mystery, or a verification-ladder note "when a layout differs, measure the box model before theorizing"). Pairs with the existing render-gate discipline. (Other candidate: a Symmetria §3 flag for *theorize-before-measuring-a-layout* — the drift this caught.)

claude/memory/session-ledger-2026-06-09.md

@@ -0,0 +1,66 @@
+---
+name: session-ledger-2026-06-09
+description: "Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses."
+metadata: 
+  node_type: memory
+  type: feedback
+  originSessionId: a5856f98-9db6-4fd3-9ffd-65eb444f5b2f
+---
+
+# Session Ledger — 2026-06-09
+
+## Returns
+- 2026-06-09T07:5x — Re-opened a SETTLED question at wake: flagged `layout`'s cascade position as an "open contradiction" (north-star scale-3 "Architecture" vs wrap's "lower near sources, scale 9"). Drift pattern: anchoring-on-most-recently-loaded-master-reference + reasoning-from-abstract-model-not-resolved-state. Steward caught the resulting fog ("path felt clear, now less so"). Corrected by READING `_layout.scss`: it holds `.post-item`/`.site-footer`/`.imprint` = footer/closing content, NOT the grid (grid lives in `_foundation`/`_base`). Filename "layout" is misleading; wrap was right; no contradiction. The path stands.
+- Coverage honesty: at wake I read the active thread + lineage, NOT the full multi-season arc. Tracker (`project-arc-rework.md`, 3887 lines/398KB) read at the recency tail + canonical-stage-status line only — confirms consistency; tracker file is 2 sessions behind (owed the 06-08 append), but those 2 sessions were read in full from the session files. No gap in the forward picture.
+
+## Open horizons
+- 2026-06-09T07:39 — Woke into ARC W3R.2 Stage 3 (the tree). Thread confirmed: finish the tree → W3R.3 verify+deploy the 9 banked commits. First move staged: `section-break` → `_silence.scss` (warm-up). The one decision needing the steward's eye: base/post co-location (Tier 3) — split `_post` or keep whole.
+- Carry from yesterday's ledger/diary: *assert-from-grep-hit-without-reading* recurred 2× (both caught). Render-gate is the guarantor, not the byte-proof. Hold both today.
+
+## Progress
+- 2026-06-09 — W3R Stage 3 warm-up DONE: `section-break` → folded into `_silence` (`d4fd852`). Content-multiset identical (16-byte delta = one folded @layer wrapper); compressed build verified; provenance + §IV citation carried over; header rewritten for the fuller taxonomy. 10 ahead, undeployed (deploy held for W3R.3).
+- 2026-06-09 — Closing-cluster move DONE: `layout` lowered to beside `sources` (scale 9) (`a2544f8`). Pure @use reorder; full byte-diff = exactly 2 hunks, byte-count identical; content-multiset identical. Collision guard ran (found `.post-type` + `.imprint` non-unique → both cleared by specificity/order-preservation; `%clearfix` @extend stays at `_base`). 11 ahead. NOTE: byte-proof alone is NOT render-proof for equal-specificity same-property collisions across a move boundary — the selector-uniqueness + specificity check is the per-move guard; full per-type×per-viewport render = W3R.3 gate.
+- 2026-06-09 — Threshold-cluster move DONE (the careful one): `frontispiece` raised to sit beside `preface` (scale 7) (`5c82687`). Did the full collision census FIRST (read both _frontispiece + _compass): @layer-overrides risk cleared — compass-point rules scoped disjointly (.frontispiece-compass vs .reading-compass), never co-match; unscoped `.compass-point .sigil` is _compass-only; .page-content/.title-return safe by specificity; .site-mark only in a comment. Byte-diff = 2 hunks, byte-count identical; content-multiset identical; compressed build unchanged. 12 ahead. The collision census (not the byte-diff) was the real guard — byte-proof can't see an overrides-layer resolution flip.
+- REORDER COMPLETE — clusters in place.
+- 2026-06-09 — BASE/POST decided + executed. Steward ruled: keep _base whole (coherent foundation; splitting bedrock = over-engineering); decompose _post (the surviving page-type junk-drawer) by the test "move a stray only if it has a truer home, not just to empty the drawer." Reframe accepted: goal is an HONEST _post, not an empty one. Banked 4 commits:
+  - `3891c49` breadcrumb → _navigation (scale 10) — correctness fix (one component, 3 templates; the Stage-N fall-through bug was the symptom of the mis-home).
+  - `9a1c648` dateline → new _dateline (scale 9, own partial per steward) — sole collision partner _glimpse `>.dateline` wins by specificity; grep-substring false-alarm run to ground first.
+  - `8d2c6fa` images §VIII → new _images (content zone) — .image-* now fully unique.
+  - marks (.chamber-mark/.encounter-mark/.post-type) LEFT — just arrived from _utilities, .post-type collides w/ _layout, legitimately post-apparatus; moving = the tidiness trap.
+- _post is now HONEST: .wrapper.post / .post-header / post-scoped .page-content + its own apparatus marks. No longer a drawer.
+- SESSION TOTAL: 6 moves banked (15 ahead, undeployed). Remaining: Tier 4 (font-face→_fonts, mix/darken deprecation [pre-existing warnings confirmed], Appendix-B index) → W3R.3 (final top-to-bottom read + per-type×per-viewport render-verify both modes + DEPLOY the banked set). Deploy still held for W3R.3.
+
+## Decisions ruled
+- 2026-06-09 — Two Stage-3 micro-order calls RULED LEAVE (steward, proportionality): (1) `silence`-after-`base` is render-identical (disjoint selectors) and defensible as-is; (2) `post`'s mixed-scale slot is intrinsic to a legitimate page-type partial ("fixing" = re-split, declined) + carries `.page-content` collision risk. Both = scale-purity beyond legibility (the over-engineering the middle-path warns against). Recorded in main.scss header so a future read doesn't re-open them. Cascade is at a fitting summit.
+
+- 2026-06-09 — TIER 4 (mostly): **B done** — `mix()`/`darken()` → `sass:color` module (`eb7a557`): 5 sites, `@use "sass:color"` added to 3 files, compiled CSS BYTE-IDENTICAL to HEAD, 6 deprecation warnings → 0 (Dart Sass 3.0 future-break closed). **A (@font-face → _fonts) = SKIP (steward-confirmed 2026-06-09)** — `_foundation` is a coherent token layer (font-loading IS foundational, not mis-homed); tidier-not-truer. Recorded in git history (commit `eb7a557` body) so it isn't re-proposed. **C (Appendix B refresh) = verified NO-OP** — Appendix B maps selector→spec-section (read it), unchanged by file-moves; wrap over-estimated it. Ruled-leave note for the micro-calls committed `79693e5` (comment-only).
+- SESSION TOTAL: **8 commits banked, 17 ahead, undeployed.** Tree COMPLETE (modulo the A decision). REMAINING = **W3R.3 only**: final top-to-bottom read + per-type×per-viewport render-verify BOTH modes (the steward's render-review = the guarantor) + DEPLOY the banked set. Single-disk note: 17 commits local-only; steward may `git push` origin as off-disk backup (push ≠ deploy on ARC) before the review.
+
+## New ARC backlog item (steward-flagged 2026-06-09 at W3R.3 render-review — NOT in the W3R arc)
+- **Reading Compass too small / uncomfortable to navigate ON PHONE.** Steward render-review verdict: W3R looks "fantastic," gate PASSES; but the compass on phone is very small and uncomfortable as a nav target. **Phone ONLY — desktop + iPad fine.** Necessary future work, explicitly OUT of the W3R closing arc. NOT a regression (the compass is render-identical this session; pre-existing mobile sizing).
+  - **Technical start-point (so next session starts warm):** lever is `scss/AldineXXI/_compass.scss` → `.compass-point .sigil` (desktop `width/height: 1.15rem`; `@include mobile` block sets `1.05rem` ≈ ~16.8px — too small a tap target) + `.compass-points` mobile `gap: $space-sm`. ⚠ The `.compass-point .sigil` rule is **UNSCOPED on purpose** (governs BOTH the footer `.reading-compass` AND the `.frontispiece-compass`) — a mobile-size bump there hits both; if only the footer reading-compass needs it, scope the change. Likely also a WCAG 2.5.8 target-size angle (24×24 / comfortable 44×44 CSS px). Fix is a normal [FIX] (no governance authorization needed); belongs in the ARC tracker as a standing to-do.
+
+## W3R CLOSED + DEPLOYED (2026-06-09 ~10:49)
+- `make rebuild` shipped the 17-commit banked set: CloudFlare (`animalrationiscapax.org`) + GitHub mirror (`52bdda67..ae05ef4c`). Live-verified: CSS 33859 bytes == disk; ornament `margin:3rem 0` live. **The tell:** 17 commits of SCSS reorganization → CloudFlare uploaded **2 changed files** (style.css + 1) — the render-identical proofs held end-to-end; the only live pixel-change is yesterday's ruled ornament 3rem. Steward render-review PASSED ("fantastic").
+- **W3R.2 + W3R.3 COMPLETE.** The cascade reads as the framework's self-description (the steward's stated north-star dream — finis coronat opus). Last big executor SCSS build before the Stage-G runway is done.
+
+## Returns (cont.)
+- 2026-06-09 — **causal-story-before-reading-render recurred (×2) on the compass.** Theorized the frontispiece's 3-rows-vs-footer's-2 as a flexbox shrink-to-fit width problem and shipped an `align-self: stretch` fix on guesswork — it did nothing. Antidote applied: built a **headless-Chrome measurement harness** (`/tmp/compass-measure/`, puppeteer-core + system Chrome at 375px) → measured the truth: widths were IDENTICAL (331px); the real cause was **per-point width** (42px vs 31px) = a **padding asymmetry** (the footer's `a.compass-point` all:unset (0,2,1) silently ate my padding; the frontispiece's `.compass-point` (0,2,0) let it through). Fix = remove the padding (match footer's proven-fine 31px); reverted the redundant stretch after measuring it unneeded. **Lesson: when a layout differs, measure the box model before theorizing the mechanism — Chrome reproduced the bug, so it wasn't even the Safari quirk I'd hypothesized.** The measure-harness is itself worth keeping as a tool.
+
+## Phone-compass [FIX] CLOSED + DEPLOYED (2026-06-09)
+- `32163af` — both compasses wrap to 2 rows on phone (sigil 1.4rem, flex-wrap; padding removed = the real cause). Committed, deployed (CloudFlare 2 files), live-verified, pushed both remotes (`eb7a557..32163af`). Steward confirmed on actual phone. The just-logged backlog item is RESOLVED same session. Desktop/iPad untouched; only the frontispiece's faint→visible fade stays unique (still-to-build).
+- Tooling kept: `/tmp/compass-measure/` headless-Chrome box-model measurement harness (puppeteer-core + system Chrome) — earned its place by finding the real cause; candidate to formalize.
+
+## Next front: Road to Stage G (steward-sequenced after the compass)
+- 2026-06-09 — Roadmap brought current (`26fab4c`): Waves 0–3 + W3R done; remaining = W4.4 (jurist v1.0 sign-off) · Wave 5 (executor enforcement pre-work) · Wave 6 (jurist Stage G).
+- **W5.2 / G3 DONE** (PENDING-34 Option 1, steward-authorized inline; `4936fc9`, pushed both remotes): `validateCompass` build guard — (A) every Compass sigil-id resolves to a `<symbol>`; (B) every surfaced class covered by a listing/special. site.hs compiles; `_site` BYTE-IDENTICAL (570 files); both checks proven to fire on deliberate mismatch (sprite + listings backed up + restored). Output-neutral → no deploy. Awaiting steward REVIEWED-36 (their entry to write; I authored from chat-authorization). Remaining Wave 5: W5.1 (G2 title single-source), W5.3 (G4 clause-1 gate), W5.4 (G1 wildcard→build-error, lands in promotion commit).
+- New tool earned this session: `/tmp/compass-measure/` (headless-Chrome box-model measurement) — candidate to formalize as a skill (skill-harvest at wrap).
+
+## Confidence to recalibrate
+
+## Authorization moves
+- 2026-06-09 — **PENDING-34 filed** (W5.2 / G3: single-source class→glyph, [HARDENING], steward chose pending-first). Diagnosed the three loci (content-types.yml `glyph:` · slug-derived sigil-id in `compassRowsHtml` site.hs:133 · hand-authored SVG `<symbol>` sprite) — agree by naming convention, not structure. Two options proposed (1: build-validation guard, byte-identical, recommended; 2: derive-sigil-from-class + guard). **Awaiting steward ruling (Option 1 or 2) — NOT implementing until REVIEWED.** dotfiles now dirty (PENDING.md) → commit+push at wrap §6.5.
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/skill-harvest-register.md

@@ -87,6 +87,13 @@ The single place proposed skills live so they don't evaporate between sessions.
 - **[PROPOSAL] deeper MEMORY.md reduction (only if 157KB still trips "only part loaded").** The load-bearing REFERENCE sections (steward profile / project states / ARC project state / CapableMind L1 / Reference Files) are large but largely STABLE — candidate to move to a consult-on-demand `MEMORY-reference.md`, leaving the wake-loaded MEMORY.md = standing prefs + trackers + Active Session + recent. Riskier (real memory, not duplication); its own focused pass, not a tail-of-session move.
 - **[reminder] the wake-canary** (PROPOSED 2026-06-07, above) still awaits authorization — the paired guardrail (every MEMORY.md pointer + `[[link]]` resolves at wake); should cover MEMORY.md + any future archive/reference split files.
 
+## New proposals (2026-06-09 — the headless-Chrome measurement harness, awaiting steward)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---------|------|----------|----------------|--------|
+| **Headless-Chrome box-model measurement** | create skill OR verification-ladder note | When a rendered layout *differs* and the cause isn't obvious, **measure the box model before theorizing the mechanism**. Today this caught the phone-compass cause (per-point *padding asymmetry*, not width) after *causal-story-before-reading-render* recurred 2× (a footer-only first pass, then a wrong `align-self:stretch` width-fix). Reusable core: `npm i puppeteer-core` in a tmp dir · `executablePath` = `/Applications/Google Chrome.app/...` · `setViewport({width:375,…,isMobile:true})` · `page.evaluate` reading `getComputedStyle`/`getBoundingClientRect` (widths, padding, row counts). Chrome reproduced the bug → it wasn't the Safari quirk I'd hypothesized. | a `/measure-render` skill, or a verification-ladder entry ("measure the box model before theorizing a layout difference") | **PROPOSED** |
+| **Symmetria §3 flag: theorize-before-measuring-a-layout** | Symmetria §3 flag | The drift this caught, as a standing flag: a *causal story about why a layout renders as it does*, asserted before the rendered box model is measured, is contamination shape (same family as `causal-story-before-reading-render`, one step more specific — layout/CSS). Antidote: the harness above. | Symmetria §3 | **PROPOSED** (may be redundant with the existing `causal-story-before-reading-render` flag — steward to judge) |
+
 ---
 
 *Discipline reminder: "no harvest" is a valid outcome; do not manufacture proposals to fill the table (the inverse of Hermes's autonomous self-write). The yardstick is the steward's: did the steward have to re-explain something a skill could have carried?*