v5.2

diff --git a/developer/authored/Manuscript.copy/Element/code.js b/developer/authored/Manuscript.copy/Element/code.js
index e9c2394..5a8e44d 100644 (file)
--- a/developer/authored/Manuscript.copy/Element/code.js
+++ b/developer/authored/Manuscript.copy/Element/code.js
@@ -111,15 +111,17 @@
       const overlay = is_text_light ? `rgba(255,255,255,${alpha})` : `rgba(0,0,0,${alpha})`;
       const text_color = is_text_light ? '#ffffff' : '#000000';
 
-      let exact_px = parseFloat(computed.fontSize) * metrics.ratio;
+      /* Two corrections, both applying to blocks and inline code alike. The ink
+         ratio corrects for the face; the size ratio corrects for the impression
+         a fixed pitch face makes at the same nominal size. Applying the second
+         only to blocks left inline code reading larger than the prose around
+         it, which is the more conspicuous of the two places to get it wrong,
+         since the comparison is immediate. */
+      const size_ratio = (RT.config && RT.config.code && RT.config.code.size_ratio) || 0.85;
+      let exact_px = parseFloat(computed.fontSize) * metrics.ratio * size_ratio;
       let offset_px = metrics.baseline_diff * (exact_px / 100);
 
       if(is_block){
-        /* A fixed pitch face reads larger than a proportional one at the same
-           size, since its widest glyphs set the measure. The tradition is a
-           point or two smaller: eleven against twelve, sometimes ten. The ink
-           ratio corrects for the face; this corrects for the impression. */
-        exact_px *= ((RT.config && RT.config.code && RT.config.code.size_ratio) || 0.85);
         let tagIndent = '';
         const prevNode = el.previousSibling;
         

diff --git a/developer/document/debug_vars.txt b/developer/document/debug_vars.txt
index ce01422..5a3bab6 100644 (file)
--- a/developer/document/debug_vars.txt
+++ b/developer/document/debug_vars.txt
@@ -1,2 +1,12 @@
 RT.Debug.enable('paginate')     // one line per element with its reason
 RT.Debug.enable('paginate_v')   // per-child measurement inside a split
+
+Pass 0 — survey, no changes. I read the manuscript and report: what tags it uses, where it diverges from current conventions, what's broken, how big it is, what it needs that the engine doesn't have yet. You get an inventory before committing to anything.
+
+Pass 1 — mechanical conformance. RT code format, tag spellings, heading capitalization, the may/just rule. Mostly scriptable, entirely verifiable, no judgement about content.
+
+Pass 2 — structure. Sections, counters, TOC, and whatever the book needs that we haven't built — figures and theorem numbering being the obvious candidates for a computation theory text. This is where the engine likely grows.
+
+Pass 3 — render and fix. The real test bed. Expect layout faults we haven't seen, since a book exercises depths and lengths the manuals don't.
+
+Pass 4 — copy editing, a chapter at a time. Slowest, most judgement-dependent, and best done once everything else is stable.

diff --git a/shared/tool/version b/shared/tool/version
index 7126e1f..c451632 100755 (executable)
--- a/shared/tool/version
+++ b/shared/tool/version
@@ -1,4 +1,4 @@
-echo "RT-Style v5.1 2026-08-04 16:37:01 Z"
+echo "RT-Style v5.2 2026-08-07 07:35:22 Z"
 echo "Harmony v3.3 2026-06-21 13:20:18 Z"