Serve the site from the penguin.ooo apex domain

Set the Pages workflow BASE_PATH to / (assets 404ed on the custom domain under the /<repo>/ subpath) and point all hardcoded site links at https://penguin.ooo.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ihk8iQuo3kv2aPjAYEPuR

packages/docs/README.md

@@ -2,7 +2,7 @@
 
 The PenguinHarness documentation site (React + Vite + Tailwind CSS 4). Its own package, sharing the landing page's visual language: bilingual pages (zh/en), light/dark themes, a sidebar + per-page table of contents, and a "Copy Markdown" button on every page.
 
-Live at <https://prism-shadow.github.io/penguin-harness/docs/>.
+Live at <https://penguin.ooo/docs/>.
 
 ## Content model
 

packages/docs/vite.config.ts

@@ -2,9 +2,10 @@
  * Vite config: static docs site (React SPA + Tailwind CSS 4), a sibling of the
  * landing page but its own package so either site can evolve independently.
  *
- * BASE_PATH is injected by the GitHub Pages workflow as "/<repo>/docs/" — the docs
- * build is copied into the landing dist under docs/ so both sites ship as one Pages
- * artifact (see scripts/build-site.mjs at the repo root). Local dev defaults to "/".
+ * BASE_PATH is injected by the GitHub Pages workflow as "/docs/" (the site lives at the
+ * custom apex domain https://penguin.ooo/) — the docs build is copied into the landing
+ * dist under docs/ so both sites ship as one Pages artifact (see scripts/build-site.mjs
+ * at the repo root). Local dev defaults to "/".
  * Doc pages are local Markdown files imported at build time via import.meta.glob
  * (?raw), so the built site is fully static — no server or CMS involved.
  */