diff --git a/site/astro.config.mjs b/site/astro.config.mjs
index de87a12..c47254b 100644
--- a/site/astro.config.mjs
+++ b/site/astro.config.mjs
@@ -93,7 +93,18 @@ export default defineConfig({
         useStarlightUiThemeColors: false,
         styleOverrides: {
           borderColor: "var(--kit-line)",
-          borderRadius: "0.5rem",
+          // The panel step, taken from the same token the stylesheet uses
+          // rather than repeated as a number here. Expressive Code emits this
+          // straight into --ec-brdRad and draws the frame at that plus its
+          // border width, so a block's outer edge measures 9px and its content
+          // measures the 8px the scale asks for. That pixel is the border, not
+          // a fifth radius.
+          //
+          // Changing this needs the Astro cache cleared to see the effect. The
+          // dev server keeps serving the previously generated Expressive Code
+          // stylesheet, and the stale one renders every block at 0px, which
+          // reads as a broken value rather than as a stale build.
+          borderRadius: "var(--kit-radius-panel)",
           frames: { frameBoxShadowCssValue: "none" },
         },
       },
diff --git a/site/scripts/generate.mjs b/site/scripts/generate.mjs
index e675e41..f7b7835 100755
--- a/site/scripts/generate.mjs
+++ b/site/scripts/generate.mjs
@@ -84,6 +84,19 @@ export function parseRules(text) {
   })
 }
 
+/**
+ * The first sentence of a rule's Check, for the two homepage panels that are
+ * too small to hold the whole clause. Quoting a prefix is the only abridgement
+ * that cannot say something the standard does not: the panel used to carry a
+ * hand-written summary of R-CI-01's Check, and it dropped the `branches:`
+ * filter condition, so it told a repository carrying one that it passed.
+ * @param {string} check
+ */
+export function leadClause(check) {
+  const end = check.indexOf(". ")
+  return end === -1 ? check : check.slice(0, end + 1)
+}
+
 /** @param {Record<string,unknown>} fields @param {string} body */
 export function frontmatter(fields, body) {
   const head = Object.entries(fields)
diff --git a/site/src/components/FaIcon.astro b/site/src/components/FaIcon.astro
index 3c91e6e..5e234c6 100644
--- a/site/src/components/FaIcon.astro
+++ b/site/src/components/FaIcon.astro
@@ -40,7 +40,10 @@ if (!glyph) throw new Error(`FaIcon: no icon mapped for "${name}"`)
 const svg = icon(glyph, {
   attributes: {
     "aria-hidden": label ? "false" : "true",
-    "aria-label": label,
+    // Spread rather than assigned: an undefined label serialized to the literal
+    // string aria-label="undefined" on every icon the site draws. Masked while
+    // the icon stays hidden, and live the moment one is given a name.
+    ...(label && { "aria-label": label }),
     focusable: "false",
   },
 }).html.join("")
diff --git a/site/src/components/HomeHero.astro b/site/src/components/HomeHero.astro
index 9dd4bc0..9e9761d 100644
--- a/site/src/components/HomeHero.astro
+++ b/site/src/components/HomeHero.astro
@@ -9,7 +9,7 @@ FORM: user-pinned lateral control surface based on approved composition A; no co
 import DomainIcon from "./FaIcon.astro"
 import InlineCode from "./InlineCode.astro"
 import InstallCommand from "./InstallCommand.astro"
-import { domains, sampleRule } from "../lib/content.mjs"
+import { domains, leadClause, sampleRule } from "../lib/content.mjs"
 ---
 
 <section class="kit-hero" aria-labelledby="kit-hero-title">
@@ -31,12 +31,17 @@ import { domains, sampleRule } from "../lib/content.mjs"
   </div>
 
   <div class="maintenance-map" aria-label="How oss-kit connects repository maintenance domains">
-    <div class="maintenance-map__rail">
-      <span>Cross-domain scan</span>
-      <a href="/skills/oss-audit/">oss-audit</a>
+    {/* The rail named oss-audit and never said what it produces. Its two
+        captions read "Cross-domain scan" and "Every standard domain", both were
+        hidden below 34rem, and the definition a reader needed sat a thousand
+        pixels down the page in the domain rack. It says it here now, and the
+        whole strip is the link rather than the one word inside it. */}
+    <a class="maintenance-map__rail" href="/skills/oss-audit/">
+      <strong>oss-audit</strong>
       <span class="maintenance-map__pulse" aria-hidden="true"></span>
-      <span>Every standard domain</span>
-    </div>
+      <span class="maintenance-map__rail-note">Evidence and gaps across every standard domain</span>
+      <DomainIcon name="arrow" />
+    </a>
 
     <div class="maintenance-map__body">
       <article class="repo-hub">
@@ -67,11 +72,14 @@ import { domains, sampleRule } from "../lib/content.mjs"
                 <span class="domain-bay__count">
                   {/* The lit bay used to say so in green and in nothing else. The
                       marker is a shape rather than a second tint, and the word
-                      behind it is what a reader who cannot see either one gets. */}
+                      behind it is what a reader who cannot see either one gets.
+                      That word said "Scanning now.", which described an activity
+                      no visitor had started on a repository none had supplied.
+                      The bay is lit because the route below expands it. */}
                   {domain.area === "SEC" && (
                     <>
                       <i aria-hidden="true" />
-                      <span class="sr-only">Scanning now. </span>
+                      <span class="sr-only">Example domain. </span>
                     </>
                   )}
                   {domain.rules.length} rules
@@ -84,16 +92,32 @@ import { domains, sampleRule } from "../lib/content.mjs"
 
       {
         sampleRule && (
-          <article class="rule-route">
+          <article class="rule-route" aria-labelledby="rule-route-label">
             <div class="rule-route__head">
-              <span>Example route</span>
+              <span id="rule-route-label">Example route</span>
               <a href={`/rules/${sampleRule.id.toLowerCase()}/`}>{sampleRule.id}</a>
             </div>
-            <h2>{sampleRule.statement}</h2>
+            {/* A statement, not a section heading. As an h2 this was the second
+                heading on the site, ahead of every section, so anyone browsing
+                by heading met a SHA-pinning rule before the page's structure.
+                It renders at 11.5px, which is the size that gave it away. */}
+            <p class="rule-route__statement">{sampleRule.statement}</p>
             <dl>
               <div>
                 <dt>Check</dt>
-                <dd><InlineCode text={sampleRule.check} /></dd>
+                {/* The whole Check ran to nine wrapped lines of 11px monospace,
+                    the largest text mass in the map and its least readable
+                    panel, at the point the route was meant to arrive. Mono
+                    carries machine-facing facts here, not explanations. */}
+                <dd>
+                  <InlineCode text={leadClause(sampleRule.check)} />
+                  <a
+                    class="rule-route__more"
+                    href={`/rules/${sampleRule.id.toLowerCase()}/#${sampleRule.id.toLowerCase()}-check`}
+                  >
+                    Read the full check
+                  </a>
+                </dd>
               </div>
               <div>
                 <dt>Fixed by</dt>
diff --git a/site/src/content/docs/index.mdx b/site/src/content/docs/index.mdx
index 2b6e598..4f8f384 100644
--- a/site/src/content/docs/index.mdx
+++ b/site/src/content/docs/index.mdx
@@ -13,7 +13,7 @@ tableOfContents: false
 ---
 
 import DomainRack from "../../components/DomainRack.astro";
-import { rules, sampleRule } from "../../lib/content.mjs";
+import { FORGE_LABEL, contractRule, leadClause, rules, sampleRule } from "../../lib/content.mjs";
 
 <DomainRack />
 
@@ -50,10 +50,12 @@ import { rules, sampleRule } from "../../lib/content.mjs";
       <strong>Observable evidence</strong>
       {/* The rule's own Check line runs to 400 characters, which in a card this
           size is a wall nobody reads and which forced the other three cards to
-          match its height. The leading clause is quoted here and the link goes
-          to the whole thing. */}
-      <p>Every external <code>uses:</code> line resolves to a 40-character commit SHA.</p>
-      <a href="/rules/r-sec-01/#r-sec-01-check">Read the full check</a>
+          match its height. Its first sentence is quoted, and the link goes to
+          the whole thing. The sentence used to be written out here in a shorter
+          form of its own, which read as a quotation and was not one: it dropped
+          the composite actions the rule also covers. */}
+      <p>{leadClause(sampleRule.check)}</p>
+      <a href={`/rules/${sampleRule.id.toLowerCase()}/#${sampleRule.id.toLowerCase()}-check`}>Read the full check</a>
     </li>
     <li>
       <span className="workflow-trace__step">03 · Fix</span>
@@ -77,18 +79,25 @@ import { rules, sampleRule } from "../../lib/content.mjs";
     <p>The standard states every current opinion as a numbered rule with a reason, a check, one fixing skill, and forge scope.</p>
     <a className="kit-button kit-button--secondary" href="/standard/">Read all {rules.length} rules</a>
   </div>
+  {/* Every field here comes from the rule. The panel used to be transcribed by
+      hand, under a heading inviting the reader to check the bar before adopting
+      it, and its Check said "The workflow declares both trigger paths." The real
+      one turns on a `branches:` filter, which a configuration can carry and
+      still fail. Nothing failed when the two diverged, so the one element on the
+      page that offered verification was the one element nothing verified. */}
   <div className="standard-sheet" aria-label="Structure of an oss-kit rule">
     <div className="standard-sheet__head">
       <span>Rule contract</span>
-      <span>R-CI-01</span>
+      <a href={`/rules/${contractRule.id.toLowerCase()}/`}>{contractRule.id}</a>
     </div>
     <code>Statement</code>
-    <p>CI runs on every push to the default branch and on every change request.</p>
+    <p>{contractRule.statement}.</p>
     <code>Check</code>
-    <p>The workflow declares both trigger paths.</p>
+    <p>{leadClause(contractRule.check)}</p>
+    <a className="standard-sheet__more" href={`/rules/${contractRule.id.toLowerCase()}/#${contractRule.id.toLowerCase()}-check`}>Read the full check</a>
     <div className="standard-sheet__meta">
-      <span>Fixed by <strong>oss-ci</strong></span>
-      <span>GitHub and GitLab</span>
+      <span>Fixed by <strong>{contractRule.fixedBy}</strong></span>
+      <span>{FORGE_LABEL[contractRule.forges]}</span>
     </div>
   </div>
 </section>
diff --git a/site/src/lib/content.mjs b/site/src/lib/content.mjs
index cd62642..c835d59 100644
--- a/site/src/lib/content.mjs
+++ b/site/src/lib/content.mjs
@@ -6,6 +6,10 @@ import readmeText from "../../../README.md?raw"
 import standardText from "../../../skills/oss-audit/STANDARD.md?raw"
 import { FORGE_LABEL, parseRules, skillSummaries } from "../../scripts/generate.mjs"
 
+// Re-exported so a page quoting the standard reaches for one module rather than
+// two, and so nothing on the homepage has a reason to transcribe a rule by hand.
+export { FORGE_LABEL, leadClause } from "../../scripts/generate.mjs"
+
 export const rules = parseRules(standardText)
 
 export const domains = [...new Set(rules.map((rule) => rule.section))].map((section) => {
@@ -20,6 +24,11 @@ export const domains = [...new Set(rules.map((rule) => rule.section))].map((sect
 
 export const sampleRule = rules.find((rule) => rule.id === "R-SEC-01")
 
+// The rule the homepage's contract panel takes apart. A second area, so the page
+// does not show the same rule twice, and read from the standard rather than
+// transcribed: see leadClause for what the transcription cost.
+export const contractRule = rules.find((rule) => rule.id === "R-CI-01")
+
 /** @param {number} n */
 const plural = (n) => `${n} ${n === 1 ? "rule" : "rules"}`
 
diff --git a/site/src/styles/custom.css b/site/src/styles/custom.css
index b403a1c..3823e49 100644
--- a/site/src/styles/custom.css
+++ b/site/src/styles/custom.css
@@ -25,9 +25,28 @@
      carrying content goes below this. Marks that carry none, like the mono
      eyebrow rules, are not exempt either: they are words. */
   --kit-annotation: 0.7rem;
+  /* Four steps, and every rounded thing on the site takes one of them. There
+     used to be eleven values across 24 declarations, most of them a fraction of
+     a pixel apart: a control at 5.6px beside a control at 6px, a panel at 8px
+     beside a panel at 8.8px. Nothing documented a reason for any of the gaps,
+     and no two of the near-identical pairs ever appeared together, so the
+     spread was drift rather than a distinction. The one nesting that a reader
+     does see is kept: the map is the faceplate, and the panels inside it round
+     tighter than it does. Circles stay 50% and the mobile bay stays square,
+     because neither is a radius on this scale. */
+  --kit-radius-indicator: 2px;
+  --kit-radius-control: 6px;
+  --kit-radius-panel: 8px;
+  --kit-radius-faceplate: 12px;
   --kit-signal: #56f27b;
   --kit-signal-strong: #56f27b;
   --kit-signal-low: #102e19;
+  /* The step the primary control takes on hover. It lived as a hex literal in
+     the one rule that used it, which made the site's main action the only
+     colour on the page outside the palette. Light mode does not override it,
+     so hovering there still lifts toward this rather than deepening; that is
+     the behaviour as it stands, not a decision this token is making. */
+  --kit-signal-lift: #7af594;
   --kit-display: "Barlow Condensed", "Arial Narrow", sans-serif;
   --kit-body: "Public Sans", system-ui, sans-serif;
   --kit-mono: "Commit Mono", ui-monospace, monospace;
@@ -182,7 +201,7 @@ a {
   min-height: 2.85rem;
   padding: 0.75rem 1rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.375rem;
+  border-radius: var(--kit-radius-control);
   color: var(--kit-text);
   font-size: 0.9rem;
   font-weight: 650;
@@ -211,8 +230,8 @@ button.kit-button {
 }
 
 .kit-button--primary:hover {
-  border-color: #7af594;
-  background: #7af594;
+  border-color: var(--kit-signal-lift);
+  background: var(--kit-signal-lift);
   color: #080b0a;
 }
 
@@ -305,7 +324,7 @@ button.kit-button {
   width: clamp(10rem, 15vw, 16rem);
   height: 2.45rem;
   border-color: var(--kit-line);
-  border-radius: 0.375rem;
+  border-radius: var(--kit-radius-control);
   background: var(--kit-panel);
   color: var(--kit-muted);
 }
@@ -315,6 +334,41 @@ button.kit-button {
   color: var(--kit-text);
 }
 
+/* Starlight and Expressive Code round four things from their own component
+   styles, at 4px and 3.2px, which are the two values the scale does not carry.
+   Each takes the step its role names. The search shortcut hint and the rule ID
+   badge are small inline marks, and the badge is the case the Shapes section
+   names by hand: an area page prints 61 of them. The table of contents links
+   are navigation rows, so they match the sidebar links rather than the badges.
+   The code block's copy control is a button, and its inner layer follows it. */
+.kit-header__tools site-search kbd,
+.sl-badge {
+  border-radius: var(--kit-radius-indicator);
+}
+
+starlight-toc a,
+mobile-starlight-toc a {
+  border-radius: var(--kit-radius-control);
+}
+
+.expressive-code .copy button,
+.expressive-code .copy button div {
+  border-radius: var(--kit-radius-control);
+}
+
+/* A search result is one card split into a title and the matches beneath it.
+   Pagefind rounds each half to half its own radius, which lands at 4px, so the
+   card's outer corners came out tighter than any panel on the site. The two
+   halves take the panel step on the outer corners and stay square at the seam
+   they share, which is what makes them read as one card. */
+site-search .pagefind-ui__result-title {
+  border-radius: var(--kit-radius-panel) var(--kit-radius-panel) 0 0;
+}
+
+site-search .pagefind-ui__result-nested {
+  border-radius: 0 0 var(--kit-radius-panel) var(--kit-radius-panel);
+}
+
 /* The custom element is inline by default, so its line box added roughly 8px
    above and below the control and the flex gap measured from that rather than
    from the select. Flex removes the line box, and the height then matches the
@@ -328,7 +382,7 @@ button.kit-button {
   height: 2.45rem;
   padding-block: 0;
   border-color: var(--kit-line);
-  border-radius: 0.375rem;
+  border-radius: var(--kit-radius-control);
   background-color: var(--kit-panel);
 }
 
@@ -338,7 +392,7 @@ button.kit-button {
   min-height: 2.45rem;
   padding-inline: 0.9rem;
   border: 1px solid var(--kit-signal);
-  border-radius: 0.375rem;
+  border-radius: var(--kit-radius-control);
   background: var(--kit-signal);
   color: #080b0a;
   font-size: 0.8rem;
@@ -365,7 +419,7 @@ button.kit-button {
   min-height: 3.6rem;
   padding: 0.45rem 0.55rem 0.45rem 0.9rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
 }
 
@@ -440,7 +494,7 @@ button.kit-button {
   min-height: 2.5rem;
   padding-inline: 0.6rem;
   border: 1px solid transparent;
-  border-radius: 0.35rem;
+  border-radius: var(--kit-radius-control);
   background: transparent;
   color: var(--kit-muted);
   cursor: pointer;
@@ -556,7 +610,7 @@ button.kit-button {
 .maintenance-map {
   position: relative;
   border: 1px solid var(--kit-line);
-  border-radius: 0.75rem;
+  border-radius: var(--kit-radius-faceplate);
   background: var(--kit-surface);
   /* 50px of blur on a dark surface reads as haze rather than as lift. This is
      a machined panel, so the shadow is tight enough to look like one. */
@@ -598,7 +652,7 @@ html[data-theme="light"] .maintenance-map {
 
 .maintenance-map__rail {
   display: grid;
-  grid-template-columns: auto auto minmax(3rem, 1fr) auto;
+  grid-template-columns: auto minmax(3rem, 1fr) auto auto;
   gap: 0.8rem;
   align-items: center;
   min-height: 2.65rem;
@@ -606,20 +660,24 @@ html[data-theme="light"] .maintenance-map {
   border-bottom: 1px solid var(--kit-line);
   color: var(--kit-faint);
   font-size: var(--kit-annotation);
-  letter-spacing: 0.06em;
-  text-transform: uppercase;
+  text-decoration: none;
 }
 
-.maintenance-map__rail a {
-  display: inline-flex;
-  align-items: center;
-  min-height: 1.5rem;
+.maintenance-map__rail strong {
   color: var(--kit-signal-strong);
-  font-size: 0.82rem;
-  font-weight: 600;
-  letter-spacing: 0;
-  text-decoration: none;
-  text-transform: none;
+  font: 600 0.82rem/1 var(--kit-mono);
+}
+
+/* A sentence, so it takes the body face. The rail's other text is uppercase
+   annotation and this is not: an instrument label and a definition are two
+   different jobs, and the second one reads badly in tracked-out capitals. */
+.maintenance-map__rail-note {
+  color: var(--kit-muted);
+  font: 450 var(--kit-annotation)/1.4 var(--kit-body);
+}
+
+.maintenance-map__rail:hover .maintenance-map__rail-note {
+  color: var(--kit-text);
 }
 
 .maintenance-map__pulse {
@@ -646,7 +704,6 @@ html[data-theme="light"] .maintenance-map {
   grid-template-columns: minmax(8.5rem, 0.82fr) minmax(21rem, 1.55fr) minmax(10rem, 0.95fr);
   gap: 0.85rem;
   align-items: center;
-  min-height: 35rem;
   padding: 1rem;
 }
 
@@ -654,7 +711,7 @@ html[data-theme="light"] .maintenance-map {
 .rule-route {
   position: relative;
   border: 1px solid var(--kit-line);
-  border-radius: 0.55rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
 }
 
@@ -822,7 +879,7 @@ html[data-theme="light"] .maintenance-map {
   min-height: 3.65rem;
   padding: 0.5rem 0.65rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.45rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
   color: var(--kit-text);
   text-decoration: none;
@@ -840,6 +897,20 @@ html[data-theme="light"] .maintenance-map {
   box-shadow: 0 3px 18px rgba(86, 242, 123, 0.08);
 }
 
+/* The lit bay is a state, so its boundary is held to WCAG 1.4.11's 3:1 rather
+   than to nothing. Light mode's --kit-signal measures 2.66:1 on the white
+   panel and fails it; --kit-signal-strong is the same green three steps down,
+   already the light mode's text green, and measures 5.43:1. Dark mode passes
+   on --kit-signal and keeps it. */
+html[data-theme="light"] .domain-bay--active a {
+  border-color: var(--kit-signal-strong);
+}
+
+html[data-theme="light"] .repo-hub__state i,
+html[data-theme="light"] .domain-bay__count i {
+  background: var(--kit-signal-strong);
+}
+
 .domain-bay__number,
 .domain-bay__count {
   color: var(--kit-faint);
@@ -880,12 +951,13 @@ html[data-theme="light"] .maintenance-map {
   text-decoration: none;
 }
 
-.rule-route h2 {
+.rule-route__statement {
   margin: 0;
   padding: 0.8rem 0.7rem;
   border-bottom: 1px solid var(--kit-line);
   font-family: var(--kit-body);
   font-size: 0.72rem;
+  font-weight: 600;
   line-height: 1.35;
   letter-spacing: 0;
 }
@@ -911,10 +983,26 @@ html[data-theme="light"] .maintenance-map {
   color: var(--kit-signal-strong);
 }
 
+/* Its own line, because it follows a quotation and a link tucked against the
+   end of one reads as part of it. */
+.rule-route__more {
+  display: block;
+  margin-top: 0.45rem;
+  font-family: var(--kit-mono);
+}
+
+/* Where the route arrives. It read as one more line of annotation, which left
+   the one panel asserting a verified state looking like the two describing an
+   unfinished one. The border takes the strong signal in both themes: the plain
+   one measures 2.66:1 on the light panel, and this marks a state. */
 .rule-route__verified {
   display: inline-flex;
   gap: 0.4rem;
   align-items: center;
+  padding: 0.3rem 0.5rem;
+  border: 1px solid var(--kit-signal-strong);
+  border-radius: var(--kit-radius-indicator);
+  background: var(--kit-signal-low);
   color: var(--kit-signal-strong);
   font-family: var(--kit-mono);
 }
@@ -980,7 +1068,7 @@ html[data-theme="light"] .maintenance-map {
   min-height: 4.5rem;
   padding-inline: 1rem;
   border: 1px solid var(--kit-signal);
-  border-radius: 0.45rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-signal-low);
   color: var(--kit-text);
   text-decoration: none;
@@ -1139,7 +1227,7 @@ html[data-theme="light"] .maintenance-map {
   display: grid;
   grid-template-columns: repeat(4, minmax(0, 1fr));
   border: 1px solid var(--kit-line);
-  border-radius: 0.65rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-surface);
 }
 
@@ -1211,7 +1299,7 @@ html[data-theme="light"] .maintenance-map {
 
 .standard-sheet {
   border: 1px solid var(--kit-line);
-  border-radius: 0.65rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
 }
 
@@ -1226,8 +1314,23 @@ html[data-theme="light"] .maintenance-map {
   text-transform: uppercase;
 }
 
-.standard-sheet__head span:last-child {
+/* The rule ID is a link now. The panel invites a reader to check the bar, and
+   it used to be the one element on the page offering nothing to check it
+   against. */
+.standard-sheet__head a {
   color: var(--kit-signal-strong);
+  text-decoration: none;
+}
+
+.standard-sheet__more {
+  display: inline-block;
+  margin: 0 1.25rem 1.4rem;
+  color: var(--kit-signal-strong);
+  font: 500 var(--kit-annotation)/1.3 var(--kit-mono);
+}
+
+.standard-sheet > p:has(+ .standard-sheet__more) {
+  margin-bottom: 0.55rem;
 }
 
 /* Scoped under the markdown wrapper on purpose. Unscoped this is (0,1,1) and
@@ -1338,7 +1441,7 @@ html[data-theme="light"] .maintenance-map {
 
 .sl-markdown-content :where(code):not(pre code) {
   border: 1px solid var(--kit-line);
-  border-radius: 0.2rem;
+  border-radius: var(--kit-radius-indicator);
   background: var(--kit-panel-strong);
 }
 
@@ -1354,7 +1457,7 @@ html[data-theme="light"] .maintenance-map {
 
 #starlight__sidebar summary,
 #starlight__sidebar a {
-  border-radius: 0.25rem;
+  border-radius: var(--kit-radius-control);
 }
 
 #starlight__sidebar [aria-current="page"] {
@@ -1398,7 +1501,7 @@ html[data-theme="light"] .maintenance-map {
 
 .pagination-links a {
   border-color: var(--kit-line);
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
   box-shadow: none;
 }
@@ -1416,7 +1519,7 @@ html[data-theme="light"] .maintenance-map {
   overflow: hidden;
   margin: 0 0 2rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-line);
 }
 
@@ -1458,7 +1561,7 @@ html[data-theme="light"] .maintenance-map {
   margin-block: 2rem;
   padding: 1.2rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
 }
 
@@ -1515,7 +1618,7 @@ html[data-theme="light"] .maintenance-map {
   margin-block: 2rem;
   padding: 1.2rem;
   border: 1px solid var(--kit-line);
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   background: var(--kit-panel);
 }
 
@@ -1582,7 +1685,7 @@ html[data-theme="light"] .maintenance-map {
    Each variant keeps its own signal; none of them borrows a second hue. */
 .starlight-aside {
   border-inline-start-width: 1px;
-  border-radius: 0.5rem;
+  border-radius: var(--kit-radius-panel);
   padding: 1rem 1.15rem;
 }
 
@@ -1897,7 +2000,7 @@ html[data-theme="light"] .maintenance-map {
     min-height: 2.45rem;
     padding-inline: 0.72rem;
     border: 1px solid var(--kit-line);
-    border-radius: 0.375rem;
+    border-radius: var(--kit-radius-control);
     background: var(--kit-panel);
     color: var(--kit-text);
     cursor: pointer;
@@ -1924,14 +2027,14 @@ html[data-theme="light"] .maintenance-map {
     width: min(16rem, calc(100vw - 2rem));
     padding: 0.45rem;
     border: 1px solid var(--kit-line);
-    border-radius: 0.5rem;
+    border-radius: var(--kit-radius-panel);
     background: var(--kit-panel);
     box-shadow: 0 18px 42px rgba(0, 0, 0, 0.35);
   }
 
   .kit-mobile-nav nav a {
     padding: 0.78rem;
-    border-radius: 0.3rem;
+    border-radius: var(--kit-radius-control);
     color: var(--kit-text);
     font-size: 0.82rem;
     font-weight: 600;
@@ -2000,23 +2103,37 @@ html[data-theme="light"] .maintenance-map {
     white-space: nowrap;
   }
 
+  /* The middle column moves to a second row rather than being dropped. On the
+     domain rack it holds the skills that own the domain, which is the whole
+     claim the section headline makes, and hiding it left seven rows of name and
+     arrow restating the bays a reader had already scrolled past. Same treatment
+     the skills rack below has always had, for the same reason. */
+  .domain-rack a {
+    align-items: start;
+    padding-block: 0.9rem;
+  }
+
   .domain-rack__skills {
-    display: none;
+    grid-column: 3 / -1;
+    grid-row: 2;
+    margin-top: 0.3rem;
   }
 
-  /* On the skills rack the summary is the content, not an annotation, so it
-     moves to its own row rather than being dropped. */
   .domain-rack--skills a {
     grid-template-columns: 2.4rem 1.2rem minmax(0, 1fr) auto auto;
-    align-items: start;
-    padding-block: 0.9rem;
   }
 
   .domain-rack--skills .domain-rack__skills {
-    display: block;
-    grid-column: 3 / -1;
-    grid-row: 2;
-    margin-top: 0.3rem;
+    font: 400 0.85rem/1.45 var(--kit-body);
+  }
+
+  /* These two carry no icon, so their tracks are shifted and the row-2 span
+     above would land under the wrong column. Their meta is one skill name and
+     one ecosystem note beside a full rule statement, which is the annotation
+     the treatment above exists to spare. They stay dropped. */
+  .domain-rack--rules .domain-rack__skills,
+  .domain-rack--ecosystems .domain-rack__skills {
+    display: none;
   }
 
   .workflow-trace {
@@ -2114,7 +2231,7 @@ html[data-theme="light"] .maintenance-map {
 
   starlight-menu-button button {
     border: 1px solid var(--kit-line);
-    border-radius: 0.375rem;
+    border-radius: var(--kit-radius-control);
     background: var(--kit-panel);
     color: var(--kit-text);
     box-shadow: none;
@@ -2149,13 +2266,19 @@ html[data-theme="light"] .maintenance-map {
    between 529px and 543px; 34rem is the first width where one column is not
    needed. Check it against `.maintenance-map__body`, not the document. */
 @media (max-width: 34rem) {
+  /* The rail's caption used to be dropped here, which left a green line and a
+     word above the map and nothing saying what either meant. It wraps to a
+     second row instead: the name and the scan line keep row one, the sentence
+     that defines them takes the width of row two. */
   .maintenance-map__rail {
-    grid-template-columns: auto 1fr;
+    grid-template-columns: auto minmax(2rem, 1fr) auto;
+    row-gap: 0.35rem;
+    padding-block: 0.55rem;
   }
 
-  .maintenance-map__rail > span:first-child,
-  .maintenance-map__rail > span:last-child {
-    display: none;
+  .maintenance-map__rail-note {
+    grid-column: 1 / -1;
+    grid-row: 2;
   }
 
   .maintenance-map__body {
@@ -2295,8 +2418,11 @@ html[data-theme="light"] .maintenance-map {
     grid-column: 1 / -1;
   }
 
+  /* The count column stays. It reads "10 rules", it is four characters wider
+     than the arrow it sits beside, and dropping it left the rack claiming one
+     responsibility per skill while showing neither the skill nor the rules. */
   .domain-rack a {
-    grid-template-columns: 2rem 1.2rem minmax(0, 1fr) auto;
+    grid-template-columns: 2rem 1.2rem minmax(0, 1fr) auto auto;
     gap: 0.65rem;
     min-height: 4rem;
     padding-inline: 0.25rem;
@@ -2307,7 +2433,11 @@ html[data-theme="light"] .maintenance-map {
     grid-template-columns: auto minmax(0, 1fr) auto;
   }
 
-  .domain-rack__rules {
+  /* Three tracks above, so these two keep dropping their count. It holds a
+     forge scope rather than a rule count here, and "GitHub and GitLab" beside a
+     wrapped rule statement at this width is the column that has to go. */
+  .domain-rack--rules .domain-rack__rules,
+  .domain-rack--ecosystems .domain-rack__rules {
     display: none;
   }
 
diff --git a/tests/homepage-claims.test.ts b/tests/homepage-claims.test.ts
new file mode 100644
index 0000000..f102114
--- /dev/null
+++ b/tests/homepage-claims.test.ts
@@ -0,0 +1,107 @@
+import { describe, expect, test } from "bun:test"
+import { readFileSync } from "node:fs"
+import { leadClause, parseRules } from "../site/scripts/generate.mjs"
+
+// The homepage quotes the standard in three places: the hero's example route,
+// the workflow trace, and the rule-contract panel. Two of the three used to be
+// transcribed by hand, and one of those transcriptions was wrong. Under the
+// heading "Read the bar before you adopt it", the panel gave R-CI-01's Check as
+// "The workflow declares both trigger paths." The real Check turns on a
+// `pull_request` trigger carrying no `branches:` filter, and says outright that
+// a configuration carrying one fails the rule rather than passing it. So the
+// panel told a repository with `branches: [main]` that it passed. Nothing
+// failed: the page's factual accuracy was the one thing in this repository no
+// check covered, while the rest of it enforces R-DOC-04 against exactly this.
+//
+// These tests hold the page to deriving what it quotes. They do not compare
+// rendered output, which would need a build; they hold the sources to the
+// shape that makes rendered output correct by construction.
+const standard = readFileSync("skills/oss-audit/STANDARD.md", "utf8")
+const rules = parseRules(standard)
+
+const HOMEPAGE = ["site/src/content/docs/index.mdx", "site/src/components/HomeHero.astro"]
+const sources = HOMEPAGE.map((path) => ({ path, text: readFileSync(path, "utf8") }))
+
+// Comment bodies are stripped first. They quote the wrong old wording on
+// purpose, to record what went wrong, and a check that punished them would
+// teach the next person to delete the explanation instead of the defect.
+const withoutComments = (text: string) => text.replaceAll(/\{?\/\*[\s\S]*?\*\/\}?/g, "")
+
+describe("rule claims on the homepage", () => {
+  test("the standard supplies the two rules the homepage takes apart", () => {
+    // A guard on the guard: if either ID is renamed, the tests below would
+    // silently check an undefined rule and pass.
+    expect(rules.map((rule) => rule.id)).toContain("R-SEC-01")
+    expect(rules.map((rule) => rule.id)).toContain("R-CI-01")
+  })
+
+  for (const rule of rules) {
+    test(`${rule.id}'s lead clause is a verbatim prefix of its Check`, () => {
+      const lead = leadClause(rule.check)
+      expect(rule.check.startsWith(lead)).toBe(true)
+      expect(lead.length).toBeGreaterThan(0)
+      // A prefix that runs to the whole Check quotes correctly but abridges
+      // nothing, which is the failure the panels reach for it to avoid.
+      // R-SEC-01 and R-CI-01 are the two the homepage renders.
+      if (rule.id === "R-SEC-01" || rule.id === "R-CI-01") {
+        expect(lead.length).toBeLessThan(rule.check.length)
+      }
+    })
+  }
+
+  // A label naming a rule field, as the three quoting blocks write it: a bare
+  // Statement or Check, or one numbered by the workflow trace's step counter.
+  const FIELD = /<(?:code|dt|span[^>]*)>\s*(?:\d+\s*·\s*)?(Check|Statement)\s*<\/(?:code|dt|span)>/g
+
+  for (const { path, text } of sources) {
+    test(`${path} writes out no rule field by hand`, () => {
+      const body = withoutComments(text)
+      const handwritten: string[] = []
+      for (const label of body.matchAll(FIELD)) {
+        const after = body.slice(label.index + label[0].length).slice(0, 400)
+        const open = /<(p|dd)[^>]*>/.exec(after)
+        if (!open) continue
+        const value = after.slice(open.index + open[0].length).trimStart()
+        // The field's value has to be an expression: either the rule property
+        // directly, or a component handed one. A literal sentence here is the
+        // defect, whatever it says, because nothing downstream can tell whether
+        // it still matches the rule it claims to quote.
+        const derived = value.startsWith("{") || /^<[A-Z][^>]*\{/.test(value)
+        if (!derived) handwritten.push(`${label[1]}: ${value.slice(0, 72)}`)
+      }
+      expect(handwritten).toEqual([])
+    })
+
+    test(`${path} reads each rule field it renders from the rule`, () => {
+      const body = withoutComments(text)
+      // Rendering a rule means naming its fields as properties. A page that
+      // stopped doing this would pass the check above by having nothing left
+      // to check, so the derivation itself is asserted.
+      const rendered = /\{(contractRule|sampleRule)[?.]/.test(body)
+      if (!rendered) return
+      expect(body).toMatch(/\{(contractRule|sampleRule)\??\.statement\}/)
+      expect(body).toMatch(/leadClause\((contractRule|sampleRule)\.check\)/)
+    })
+  }
+
+  test("the contract panel reads every field of its rule, including forge scope", () => {
+    // The panel's Fixed by and forge scope were transcribed too, and they were
+    // right. Being right by luck is what this stops: the rule that changes a
+    // fixing skill changes nothing on the homepage today.
+    const body = withoutComments(readFileSync("site/src/content/docs/index.mdx", "utf8"))
+    expect(body).toMatch(/\{contractRule\.fixedBy\}/)
+    expect(body).toMatch(/FORGE_LABEL\[contractRule\.forges\]/)
+  })
+
+  test("both quoting panels link to the full check", () => {
+    // An abridgement is honest only where the whole clause is one click away.
+    for (const { path, text } of sources) {
+      const body = withoutComments(text)
+      if (!/leadClause\(/.test(body)) continue
+      expect({ path, linked: /#\$\{[a-zA-Z]+\.id\.toLowerCase\(\)\}-check/.test(body) }).toEqual({
+        path,
+        linked: true,
+      })
+    }
+  })
+})