fix(overview): restore truncated tails on pages 01-12

docs/taskplane-overview/01-origin-timeline.html

@@ -147,4 +147,14 @@ <h1>The road to Taskplane</h1>
           <div class="card-title">Taskplane</div>
           <div class="card-meta">today · deterministic orchestration</div>
           <div class="card-desc">Four agents. Verbose packets. File-backed state. Worktree isolation. Cross-model reviews. Semantic merges. A web-based dashboard to drive observability.</div>
-          <div class="lesson"><span class="lk">rule →</span> <
+          <div class="lesson"><span class="lk">rule →</span> <span class="lv">Autonomy is fine. Inspectable autonomy is the goal.</span></div>
+        </div>
+      </div>
+    </div>
+
+    <div class="footer-tag">
+      vibe → ralph → parallel ralph → <span class="hl">taskplane</span> · ~1M lines of AI-generated code along the way
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/02-light-factory-vs-dark.html

@@ -130,4 +130,15 @@ <h1>Light factory vs dark factory</h1>
           <li class="trait"><div class="glyph">✓</div><div class="trait-text">File-backed state. <span class="dim">.DONE, STATUS.md, batch-state.json. Resume from any crash.</span></div></li>
           <li class="trait"><div class="glyph">✓</div><div class="trait-text">Worktree isolation. <span class="dim">Every lane is its own checkout. No collisions, ever.</span></div></li>
           <li class="trait"><div class="glyph">✓</div><div class="trait-text">Cross-model reviews. <span class="dim">Different family on the other side. Independent quality gate.</span></div></li>
-          <li class="trait"><div class="glyph">✓</div><div class="trait-text">Dashboard reads disk. <span class="dim">SSE-streamed truth. Cannot lie. Doesn't decide.</
+          <li class="trait"><div class="glyph">✓</div><div class="trait-text">Dashboard reads disk. <span class="dim">SSE-streamed truth. Cannot lie. Doesn't decide.</span></div></li>
+        </ul>
+        <div class="floor-banner">visibility → full · recoverability → atomic · operator clarity → first-class</div>
+      </div>
+    </div>
+
+    <div class="footer-note">
+      autonomy is fine — <span class="hl">inspectable autonomy is the goal</span>
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/03-agent-quartet.html

@@ -189,4 +189,8 @@ <h1>The agent quartet</h1>
     </div>
 
     <div class="flow-band">
-      <span class="hl-p">supervisor</span> <span class="arrow">→</span> spawns <span class="hl-g">worker</span
+      <span class="hl-p">supervisor</span> <span class="arrow">→</span> spawns <span class="hl-g">worker</span> per lane <span class="arrow">→</span> worker calls <span class="hl-a">reviewer</span> at step boundaries <span class="arrow">→</span> wave completes <span class="arrow">→</span> <span class="hl-b">merger</span> combines lanes <span class="arrow">→</span> next wave
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/04-task-packet-anatomy.html

@@ -190,4 +190,3 @@ <h1>Anatomy of a Taskplane task packet</h1>
   </div>
 </body>
 </html>
-

docs/taskplane-overview/05-determinism-spectrum.html

@@ -176,4 +176,15 @@ <h1>Where Taskplane sits on the determinism spectrum</h1>
           <li class="item">Supervisor steering<span class="sub">when / what to inject</span></li>
           <li class="item">Discovery hydration<span class="sub">checkbox expansion at runtime</span></li>
           <li class="item">Verify-then-fix<span class="sub">test failures post-merge</span></li>
-          <li class="item">Exit inter
+          <li class="item">Exit interception<span class="sub">supervisor re-steer up to 2×</span></li>
+        </ul>
+      </div>
+    </div>
+
+    <div class="principle">
+      Two runs of the same batch produce the same waves, the same lanes, the same branch names —<br>
+      <span class="hl">only the contents of the model's tokens differ.</span>
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/06-cross-model-review.html

@@ -258,4 +258,15 @@ <h1>Cross-model reviews</h1>
       </div>
       <div class="verdict unavail">
         <div class="verdict-name">UNAVAILABLE</div>
-        <div class="verdict-desc">Reviewer crashed / timed out. Worker proceeds cautiously. Logged for the operator.</div
+        <div class="verdict-desc">Reviewer crashed / timed out. Worker proceeds cautiously. Logged for the operator.</div>
+      </div>
+    </div>
+
+    <div class="footer-line">
+      review levels per task → <span class="hl-g">0</span> none · <span class="hl-g">1</span> plan · <span class="hl-a">2</span> plan + code · <span class="hl-a">3</span> plan + code + test
+      <br />step 0 (preflight) and the final step (docs) always skip
+    </div>
+
+  </div>
+</body>
+</html>

docs/taskplane-overview/07-mailbox-protocol.html

@@ -203,4 +203,13 @@ <h1>The file-based mailbox</h1>
       </div>
       <div class="prop">
         <div class="prop-name">bidirectional</div>
-        <div class="prop-desc">agents reply into 
+        <div class="prop-desc">agents reply into outbox/ — the engine polls and surfaces alerts to the supervisor.</div>
+      </div>
+      <div class="prop">
+        <div class="prop-name">portable</div>
+        <div class="prop-desc">windows, macOS, linux — same protocol. no sockets, no named pipes, no daemon.</div>
+      </div>
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/08-waves-lanes-worktrees.html

@@ -297,4 +297,13 @@ <h1>Batch, waves, lanes, worktrees, tasks</h1>
       </div>
       <div class="rule r2">
         <div class="rule-name">Lanes are parallel</div>
-        <div class="rule-desc">Up to <code>max_lanes</code> within a 
+        <div class="rule-desc">Up to <code>max_lanes</code> within a wave. Each lane is one subprocess worker against one worktree against one branch.</div>
+      </div>
+      <div class="rule r3">
+        <div class="rule-name">Tasks share lanes when scopes overlap</div>
+        <div class="rule-desc">Affinity-first assignment. Overlapping <code>## File Scope</code> entries collapse onto the same lane and run serially.</div>
+      </div>
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/09-branching-lifecycle.html

@@ -244,4 +244,21 @@ <h1>How Taskplane uses branches</h1>
         <div class="step-title">wave merge</div>
         <div class="step-desc">After each wave, a merge agent combines lane branches back into orch. Next wave sees the previous wave's merged changes.</div>
       </div>
-      <div class="step
+      <div class="step s4">
+        <div class="step-num">4</div>
+        <div class="step-title">all waves complete</div>
+        <div class="step-desc">Orch branch now holds the full batch result. Your working branch is still untouched.</div>
+      </div>
+      <div class="step s5">
+        <div class="step-num">5</div>
+        <div class="step-title">/orch-integrate</div>
+        <div class="step-desc">Fast-forward, merge commit, or open a PR. Your choice. Always an explicit step.</div>
+      </div>
+    </div>
+
+    <div class="rule">
+      your <span class="pink">working branch</span> is sacred — <span class="hl">never touched</span> until <code style="font-family:var(--mono); color:var(--green); background:var(--bg); padding:1px 5px; border-radius:3px;">/orch-integrate</code>
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/10-semantic-merge.html

@@ -200,4 +200,14 @@ <h1>Semantic merge vs git merge</h1>
         <div class="ms">
           <div class="ms-num">5</div>
           <div class="ms-name">result.json</div>
-          <div class="ms-desc">Engine polls. Counters u
+          <div class="ms-desc">Engine polls. Counters update. Next wave provisions.</div>
+        </div>
+      </div>
+    </div>
+
+    <div class="monitor">
+      merge health monitor polls every 2 min · <span class="hl-a">stale at 10</span> · <span class="hl-r">stuck at 20</span> · emits events, never kills autonomously
+    </div>
+  </div>
+</body>
+</html>

docs/taskplane-overview/11-polyrepo-segments.html

@@ -274,4 +274,12 @@ <h1>Polyrepo: tasks decompose into segments</h1>
       <div class="rule k2">
         <div class="rule-name">Segment isolation</div>
         <div class="rule-desc">Workers <em>read</em> across all repos for planning. They <em>write</em> only to the active segment repo + the packet home.</div>
-      </div>
+      </div>
+      <div class="rule k3">
+        <div class="rule-name">Per-repo orch branches</div>
+        <div class="rule-desc">An <code>orch/…</code> branch is created in <em>every</em> repo with work. <code>/orch-integrate</code> loops over all of them.</div>
+      </div>
+    </div>
+  </div>
+</body>
+</html>