docs: add logo to README, GitHub Pages, and mdBook

Logo: layered translucent pages with cryptographic hash arc,
indigo (#4f46e5) and rose (#e11d48) palette matching the site theme.

- README: centered logo (200px) above title and badges
- GitHub Pages: 24px logo in nav bar, 96px logo in hero section
- mdBook: centered logo (160px) on introduction page
- Logo file placed at root, docs/, and book/src/ for all contexts

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: copyleftdev

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <em>Place logo here</em>
+  <img src="logo.png" alt="Palimpsest" width="200">
 </p>
 
 <h1 align="center">Palimpsest</h1>

book/src/introduction.md

@@ -1,5 +1,9 @@
 # Introduction
 
+<p align="center">
+  <img src="logo.png" alt="Palimpsest" width="160">
+</p>
+
 Palimpsest is a **deterministic crawl kernel** — not a crawler, not a Wayback clone, not a scraping framework. It is the foundational memory layer of the web: a system where the same input and the same seed produce an identical crawl, identical artifacts, and identical replay. Every design decision bends around this property.
 
 ## What Makes This Different

book/src/logo.png

@@ -179,6 +179,10 @@ <h1 class="menu-title">Palimpsest Documentation</h1>
                 <div id="mdbook-content" class="content">
                     <main>
                         <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h1>
+<p align="center">
+  <img src="logo.png" alt="Palimpsest" width="160">
+</p>
+
 <p>Palimpsest is a <strong>deterministic crawl kernel</strong> — not a crawler, not a Wayback clone, not a scraping framework. It is the foundational memory layer of the web: a system where the same input and the same seed produce an identical crawl, identical artifacts, and identical replay. Every design decision bends around this property.</p>
 <h2 id="what-makes-this-different"><a class="header" href="#what-makes-this-different">What Makes This Different</a></h2>
 <p>Traditional web archiving tools (Heritrix, wget, Scrapy, Brozzler) treat crawling as an inherently non-deterministic process. Network jitter, DNS resolution timing, thread scheduling, and random retry backoff all introduce entropy. Two runs of the same crawl produce different results. This makes verification impossible, replay approximate, and auditing meaningless.</p>

docs/book/index.html

@@ -179,6 +179,10 @@ <h1 class="menu-title">Palimpsest Documentation</h1>
                 <div id="mdbook-content" class="content">
                     <main>
                         <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h1>
+<p align="center">
+  <img src="logo.png" alt="Palimpsest" width="160">
+</p>
+
 <p>Palimpsest is a <strong>deterministic crawl kernel</strong> — not a crawler, not a Wayback clone, not a scraping framework. It is the foundational memory layer of the web: a system where the same input and the same seed produce an identical crawl, identical artifacts, and identical replay. Every design decision bends around this property.</p>
 <h2 id="what-makes-this-different"><a class="header" href="#what-makes-this-different">What Makes This Different</a></h2>
 <p>Traditional web archiving tools (Heritrix, wget, Scrapy, Brozzler) treat crawling as an inherently non-deterministic process. Network jitter, DNS resolution timing, thread scheduling, and random retry backoff all introduce entropy. Two runs of the same crawl produce different results. This makes verification impossible, replay approximate, and auditing meaningless.</p>

docs/book/introduction.html

@@ -180,6 +180,10 @@ <h1 class="menu-title">Palimpsest Documentation</h1>
                 <div id="mdbook-content" class="content">
                     <main>
                         <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h1>
+<p align="center">
+  <img src="logo.png" alt="Palimpsest" width="160">
+</p>
+
 <p>Palimpsest is a <strong>deterministic crawl kernel</strong> — not a crawler, not a Wayback clone, not a scraping framework. It is the foundational memory layer of the web: a system where the same input and the same seed produce an identical crawl, identical artifacts, and identical replay. Every design decision bends around this property.</p>
 <h2 id="what-makes-this-different"><a class="header" href="#what-makes-this-different">What Makes This Different</a></h2>
 <p>Traditional web archiving tools (Heritrix, wget, Scrapy, Brozzler) treat crawling as an inherently non-deterministic process. Network jitter, DNS resolution timing, thread scheduling, and random retry backoff all introduce entropy. Two runs of the same crawl produce different results. This makes verification impossible, replay approximate, and auditing meaningless.</p>

docs/book/logo.png

@@ -1461,7 +1461,10 @@
 
 <nav>
   <div class="inner">
-    <div class="brand"><strong>Palimpsest</strong> &mdash; Technical Journey</div>
+    <div class="brand" style="display:flex;align-items:center;gap:0.6rem;">
+      <img src="logo.png" alt="" style="width:24px;height:24px;border-radius:4px;">
+      <span><strong>Palimpsest</strong></span>
+    </div>
     <div style="display:flex;gap:2rem;align-items:center;">
       <a href="./book/index.html">Documentation</a>
       <a href="https://github.com/copyleftdev/palimpsest" target="_blank">Repository</a>
@@ -1471,6 +1474,7 @@
 
 <!-- ─── HERO ─── -->
 <div class="hero">
+  <img src="logo.png" alt="Palimpsest" style="width:96px;height:96px;border-radius:12px;margin-bottom:1.5rem;">
   <div class="label">Built with Claude Code &mdash; One Session, Zero Compromise</div>
   <h1>The Web's Memory Layer <em>Should Be Provable</em></h1>
   <p class="subtitle">