Initialize repository with harness code and assets
Initial import of all source code, config, and README assets: the packages workspace (cli, core, server, web, docs, landing, skills), build scripts, tooling config, and CI workflows. Includes the data-layout revision made on this branch: the local data root defaults to ~/.penguin/data (PENGUIN_HOME still overrides; the installer keeps its binaries in ~/.penguin), and every Agent lives under <project>/agents/<agent>/ — path helpers, the three agent-enumeration scans, the system prompt, built-in Skills, tests and docs all follow the new layout. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018ihk8iQuo3kv2aPjAYEPuR
This commit is contained in:
1 parent
056bed7aeb
commit
45bfae6e94
543 files changed
+92949
No files matched your search
@@ -0,0 +1,17 @@
|
||||
/**
|
||||
* 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 "/".
|
||||
* 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.
|
||||
*/
|
||||
import react from "@vitejs/plugin-react";
|
||||
import tailwindcss from "@tailwindcss/vite";
|
||||
import { defineConfig } from "vite";
|
||||
|
||||
export default defineConfig({
|
||||
base: process.env.BASE_PATH ?? "/",
|
||||
plugins: [react(), tailwindcss()],
|
||||
server: { port: 7366 },
|
||||
});
|
||||
Reference in new issue
Block a user