penguin-harness-dev

# Developing PenguinHarness PenguinHarness is a TypeScript monorepo: an Agent SDK (`packages/core`), an HTTP server (`packages/server`), a Web App (`packages/web`), a CLI (`packages/cli`), an Electron shell (`packages/desktop`), the landing and docs sites, and the shipped plugin library — one npm package per plugin under the repo root's `plugins/`, with `packages/plugins` as the loader that depends on them all. It **consumes** LLM providers through `@prismshadow/agenthub` and implements no provider clients of its own. This page is the part that applies to every change. Four reference files carry the detail, read them when the task reaches them: | Read | When | | --- | --- | | `reference/verification.md` | A test fails oddly, CI reads green when it should not, or the user asks you to run the suite on another machine | | `reference/changelog.md` | Writing or auditing a changelog entry | | `reference/model-catalog.md` | Touching `model-catalog.ts`, pricing, provider groups or glyphs | | `reference/authoring.md` | Writing a blog post, auditing prose, or proposing a simplification | ## Repo shape — read before your first edit Two repositories sit side by side: the implementation repo (`penguin-harness`) and the design repo (`penguin-harness-design`). Three paths inside the implementation repo are symlinks into the design repo and are gitignored here: - `design/` → the design repo, so specs are reachable as `design/specs/…` - `AGENTS.md` → `design/AGENTS.md` - `CLAUDE.md` → `...