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/cli/README.md

@@ -19,13 +19,13 @@ penguin chat --resume                                          # resume the late
 
 Tool calls go through an approval gate — `--approve allow-all` (default) `| deny-all | read-only | always-ask`. Data lives under `~/.penguin/data` (`PENGUIN_HOME` or `--root` override); model credentials come from the Project config or provider env vars (e.g. `DEEPSEEK_API_KEY`).
 
-Prefer a one-line install with a bundled Node runtime? See the [installation guide](https://prism-shadow.github.io/penguin-harness/docs/installation).
+Prefer a one-line install with a bundled Node runtime? See the [installation guide](https://penguin.ooo/docs/installation).
 
 ## Documentation
 
-- [Quickstart](https://prism-shadow.github.io/penguin-harness/docs/quickstart)
-- [CLI Reference](https://prism-shadow.github.io/penguin-harness/docs/cli)
-- [Configuration Reference](https://prism-shadow.github.io/penguin-harness/docs/configuration)
+- [Quickstart](https://penguin.ooo/docs/quickstart)
+- [CLI Reference](https://penguin.ooo/docs/cli)
+- [Configuration Reference](https://penguin.ooo/docs/configuration)
 
 ## Development
 

packages/core/README.md

@@ -23,11 +23,11 @@ A single `run` drives a complete Task: streaming output, per-call approvals, con
 
 ## Documentation
 
-- [Architecture](https://prism-shadow.github.io/penguin-harness/docs/architecture)
-- [The OmniMessage Protocol](https://prism-shadow.github.io/penguin-harness/docs/omni-message)
-- [Core Interfaces](https://prism-shadow.github.io/penguin-harness/docs/interfaces)
-- [The Agent Loop](https://prism-shadow.github.io/penguin-harness/docs/agent-loop)
-- [Sessions & Traces](https://prism-shadow.github.io/penguin-harness/docs/sessions-and-traces)
+- [Architecture](https://penguin.ooo/docs/architecture)
+- [The OmniMessage Protocol](https://penguin.ooo/docs/omni-message)
+- [Core Interfaces](https://penguin.ooo/docs/interfaces)
+- [The Agent Loop](https://penguin.ooo/docs/agent-loop)
+- [Sessions & Traces](https://penguin.ooo/docs/sessions-and-traces)
 
 ## Development
 

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.
  */

packages/landing/vite.config.ts

@@ -1,8 +1,8 @@
 /**
  * Vite config: static landing page (React SPA + Tailwind CSS 4).
  *
- * BASE_PATH is injected by the GitHub Pages workflow (e.g. "/penguin-harness/") so asset
- * URLs resolve under the project-pages subpath; local dev and previews default to "/".
+ * BASE_PATH is injected by the GitHub Pages workflow ("/" — the site is served from the
+ * custom apex domain https://penguin.ooo/); local dev and previews also default to "/".
  * Blog posts 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.
  */

packages/server/README.md

@@ -10,7 +10,7 @@ The PenguinHarness Web backend — the Web implementation of the SDK's Human bou
 - **SSE**: per-channel monotonic event ids with a bounded replay buffer (1000 events / 2MB); reconnects replay from `Last-Event-ID` or receive `resync_required`; heartbeat comment every 20s.
 - **Usage**: `token_usage` events are persisted row by row; costs are computed at query time from current per-model pricing.
 
-The full route tables and the SSE protocol are documented in the [Server API reference](https://prism-shadow.github.io/penguin-harness/docs/server-api). DTO types are exported for type-only import via `@prismshadow/penguin-server/api`.
+The full route tables and the SSE protocol are documented in the [Server API reference](https://penguin.ooo/docs/server-api). DTO types are exported for type-only import via `@prismshadow/penguin-server/api`.
 
 ## Environment
 

packages/skills/README.md

@@ -18,8 +18,8 @@ The first group powers the self-improvement loop: design a Benchmark, evaluate t
 
 ## Documentation
 
-- [Skills](https://prism-shadow.github.io/penguin-harness/docs/skills)
-- [Self-Improvement](https://prism-shadow.github.io/penguin-harness/docs/self-improvement)
+- [Skills](https://penguin.ooo/docs/skills)
+- [Self-Improvement](https://penguin.ooo/docs/self-improvement)
 
 ## Development
 

packages/web/README.md

@@ -1,6 +1,6 @@
 # @prismshadow/penguin-web
 
-The PenguinHarness Web App — a React 19 + Vite + Tailwind CSS 4 SPA that renders the OmniMessage stream (same protocol and statistics as the CLI) and manages Agents, Skills, Models, usage and Traces. Feature tour: [Web App Guide](https://prism-shadow.github.io/penguin-harness/docs/web-app).
+The PenguinHarness Web App — a React 19 + Vite + Tailwind CSS 4 SPA that renders the OmniMessage stream (same protocol and statistics as the CLI) and manages Agents, Skills, Models, usage and Traces. Feature tour: [Web App Guide](https://penguin.ooo/docs/web-app).
 
 ## Layout