Skip to content

A local-first multi-agent app development platform, built on PenguinHarness

feat(release): v0.2.0 源码版 —— README 写明 Adelie 是 PenguinHarness 的 fork

lmliheng42cc976b8a7f
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 00df2cca..cb3cd7ea 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -44,9 +44,13 @@
# every push to main; this workflow only decides when the release tags are published.
name: Release
+# Fork note (Adelie, 2026-10-05): upstream's release pipeline is dispatch-only here. On a tag push
+# it would build the penguin/ one-line-installer bundles and publish @penguinharness/* and
+# @prismshadow/penguin-* to npm -- the upstream product, out of our fork. None of that is Adelie's,
+# and an accidental `git push --tags` must not be able to start it. Adelie's own release pipeline is
+# still to be written (FORK-PROGRESS.md 4.2); until then this file is kept for reference and can
+# only be run by hand, from the Actions tab.
on:
- push:
- tags: ["v*"]
workflow_dispatch:
inputs:
tag:
diff --git a/FORK-PROGRESS.md b/FORK-PROGRESS.md
index cc0081c9..b6a882b3 100644
--- a/FORK-PROGRESS.md
+++ b/FORK-PROGRESS.md
@@ -51,8 +51,16 @@
(建议:变量名改成 `ADELIE_*`,并在 `resolveRoot()` 里兼容读一次旧名,方便旧数据迁过来)。
- [ ] 2.3 **端口与 profile 默认值**:服务器默认端口、CLI 默认端口(现在是 7369)与旧 Adelie 的
4000 / 7370 对齐,避免两个产品抢端口。
-- [ ] 2.4 **README 与包元数据**:根 `README.md` 换成 Adelie 自己的说明 + 「基于 PenguinHarness」的
- 来源声明(`FORK.md` 已有,README 里指过去即可)。
+- [x] 2.4 **README 与包元数据**(2026-10-05):根 `README.md` 与 `README.zh.md` 重写成 Adelie 自己的
+ 说明 + 「基于 PenguinHarness」的来源声明 —— 头部换成 Adelie 图标 / 名字 / `built on
+ PenguinHarness`、一张 `fork of PenguinHarness` 徽章,去掉上游的下载按钮、npm / Pages 徽章与
+ penguin.ooo 那一串渠道徽章,正文加 `> [!IMPORTANT]` 声明(来源、商标归属、上游渠道是上游的);
+ 「安装」一节改成**本仓库实测过的从源码运行方式** + 明确「Adelie 还没有自己的产物」,
+ `> [!WARNING]` 说明上游那些安装方式装出来的是 PenguinHarness;路线图 / 贡献者 / 引用 / 协议
+ 四节改标为「上游的」,引用里的 bibtex 名字改回 `PenguinHarness`。包元数据(`package.json`
+ 的 name / version)归 4.1,本版没动。
+ **发布说明**:`RELEASE-v0.2.0.md`(仓库根)是 v0.2.0 的发布正文(基于哪个上游 commit、
+ 这一版改了什么、怎么跑、许可证义务、待办)。
- [x] 2.5 **上游 `landing` / `docs` / `ui-gallery` / `hmr` 的去留(2026-10-05 定,用户「看你」)**:
- **删 `packages/landing`**(官网 + 博客 + 下载页,163 文件 / 3.0M):整站都是上游产品的宣传
与 `penguin.ooo` 链接,对 Adelie 没有一处价值。连带删掉只为它存在的
@@ -82,10 +90,45 @@
`adelie-core` / `adelie-server` / `adelie-web` / `adelie-desktop` 等)。**只和发布一起做** ——
内部改名 968 个文件、零功能收益,放到这里一次做完。`@prismshadow/agenthub` 是**外部**包
(见下),改名时不能碰。
-- [ ] 4.2 GitHub Pages(PWA)、设计站、Windows 安装包三条流水线按新仓库结构重写
- (上游那条 Pages 流水线已随 `landing` 删掉)。
+- [ ] 4.2 发布流水线重写:上游三条都还是上游的 —— `.github/workflows/release.yml`(tag 触发,
+ **已改成只能手动触发**,见下)负责安装包与 npm;`docker.yml` 的 `push: branches: [main]`
+ 会把镜像推到 Docker Hub `hiyouga/penguinharness`(现在不触发,因为默认分支还是旧 main;
+ **哪天把新基座变成默认分支,这条要先处理**);`desktop-build.yml` 的 `push: release/**`;
+ Pages 那条已随 `landing` 删掉。
- [ ] 4.3 **旧的四件产物要更新**(用户 2026-10-05 定:按新基座重发新版,不是下架)。
+## 发布 v0.2.0(2026-10-05)
+
+用户要求「先发布最新版本到 GitHub,说明是基于 penguin harness 做的」。这一版是**源码版**:
+
+| | |
+| --- | --- |
+| tag | `v0.2.0`(接在旧 Adelie 的 `v0.1.0` 之后;本地 `v0.1.0` 指向旧 Adelie 的 `ae9da1c9`) |
+| 分支 | `fork/penguin-base` |
+| 发布正文 | `RELEASE-v0.2.0.md`(仓库根,中英双语问题只在中文 —— 发布正文用中文) |
+| 产物 | **没有**。npm 包 / 安装包 / Docker 镜像 / 下载页都属于 4.x |
+
+**为发布做的一件安全动作**:`.github/workflows/release.yml` 原本 `on: push: tags: ["v*"]`,
+推任何 `v*` tag 都会去构建 `penguin/` 安装包并把 `@penguinharness/*`、`@prismshadow/penguin-*`
+发到 npm(上游产物,从我们的 fork 发出去是错的)。已把它改成只剩 `workflow_dispatch`
+(文件头加注释说明缘由),所以推 tag 不会触发任何工作流。其余工作流的触发面已逐份核对:
+`ci.yml` push/PR 只对 `main`,`docker.yml` push 只对 `main`,`desktop-build.yml` push 只对
+`release/**`,`oss-staging.yml` 与 `release.yml` 只有手动。
+
+**卡点:本会话没有 GitHub 凭证**,建不了 Release(Release 只能走 API;`gh` 没装、`~/.config/gh`
+与 `~/.netrc` 都没有、vault 里也没有 `GH_TOKEN`)。两条路:
+
+1. 用户把 token 放进 vault:`penguin config vault set GH_TOKEN <token>`(**下次对话才注入**),
+ 下一轮用 `POST /repos/lmliheng/Adelie/releases`(`tag_name: v0.2.0`、
+ `target_commitish: fork/penguin-base`、正文取 `RELEASE-v0.2.0.md`)建 Release。
+2. 用户自己在网页上建:`Draft a new release` → 选已存在的 tag `v0.2.0` → target
+ `fork/penguin-base` → 正文粘贴 `RELEASE-v0.2.0.md`。
+
+**待用户定**:新基座要不要变成默认分支(现在默认分支仍是旧 Adelie 的 `main`,仓库首页显示的
+是旧 README)。`main` 与新基座是两段不相干的历史(`main` = 旧 Adelie,`fork/penguin-base` =
+上游 PenguinHarness),不能直接 merge;要换之前先把旧 `main` 存成一条 `legacy/main` 分支
+(旧 `main` 尖端 `7fb74262`),再谈默认分支怎么切。
+
## 本机部署(2026-10-05)
| | |
@@ -138,3 +181,4 @@
| 2026-10-05 | 部署 | 新 Adelie 起在 **3004**(`adelie-app.service`,数据根 `/root/adelie-data`);上游设计规格页让到 3003 | `curl` 127.0.0.1 与外网地址都 200;Playwright 打开 3004 是 `Sign in · Adelie`、唯一 4xx 是登录前的 `/api/me` 401(预期);`ss` 确认 3004 绑 0.0.0.0;ufw 与运维面板端口表已登记 3003/3004 | 无(环境动作) |
| 2026-10-05 | 2.1b | 界面图标换成 Adelie 自己的标志(三份 `penguin-logo.svg` → `adelie-icon.svg`,组件 `PenguinLogo` → `AppLogo`,全部引用点跟上) | ui 999 / web 2886 全绿;ui / web / docs / ui-gallery typecheck 过;`pnpm format:check` 干净;重建 web 产物后 **3004 现网**已供新图标(favicon 200、`<title>Adelie</title>`),Playwright 看登录页:阿德利企鹅标志 + 标题 Adelie,唯一 4xx 仍是 `/api/me` 401 | 见本行提交 |
| 2026-10-05 | 2.1c | 产品名全仓统一成 Adelie(140 文件),并推进内核版本 `KERNEL_VERSION` → `2026-10-05` | `pnpm lint` 0 警告;八个包 typecheck 过;`pnpm format:check` 干净;`sh scripts/test-installer.sh` 通过;测试 **8485 通过 / 7 跳过 / 0 失败**(docs 62 · core 1346 · ui 999 · server 2552 · cli 509 · web 2886 · ui-gallery 131);3004 现网重建后登录页再无旧名字,Playwright 复核正常 | 见本行提交 |
+| 2026-10-05 | 2.4 + 发布 | 两份 README 重写成「Adelie 是 PenguinHarness 的 fork」的诚实版(来源声明、上游渠道与商标归属、从源码运行的安装节、上游路线图/贡献者/引用/协议改标);写 `RELEASE-v0.2.0.md` 当发布正文;把上游那条 tag 触发的 release 流水线改成只能手动触发 | `pnpm lint` 0 警告;`pnpm format:check` 干净;五份工作流用仓库自带 `yaml` 逐份解析通过,`release.yml` 的 `on` 只剩 `workflow_dispatch`;`git ls-remote` 复核远端分支与 tag | 见本行提交 |
diff --git a/README.md b/README.md
index db518d61..3d930a1b 100644
--- a/README.md
+++ b/README.md
@@ -4,42 +4,27 @@
<h1 align="center">Adelie</h1>
-<p align="center"><strong>Open-source, local-first multi-agent app development platform</strong><br />Fully automate <strong>building</strong> · <strong>optimizing</strong> · <strong>deploying</strong> AI applications</p>
+<p align="center"><strong>A local-first multi-agent app development platform, built on PenguinHarness</strong></p>
<p align="center">
- <a href="https://penguin.ooo/download">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="assets/readme/download-en-dark.svg" />
- <img src="assets/readme/download-en-light.svg" alt="Download App" height="44" />
- </picture>
- </a>
-</p>
-
-<p align="center">1000+ Models · Multi-Platform · Apache 2.0 · Agent Self-Evolution</p>
-
-<p align="center">
- <a href="https://www.npmjs.com/package/@prismshadow/penguin-core"><img src="https://img.shields.io/npm/v/@prismshadow/penguin-core" alt="npm version" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/ci.yml"><img src="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/pages.yml"><img src="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/pages.yml/badge.svg" alt="Deploy Site" /></a>
<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="License: Apache-2.0" /></a>
<img src="https://img.shields.io/badge/node-%E2%89%A5%2024-brightgreen" alt="Node >= 24" />
+ <a href="https://github.com/Prism-Shadow/penguin-harness"><img src="https://img.shields.io/badge/fork%20of-PenguinHarness-1f6feb" alt="Fork of PenguinHarness" /></a>
</p>
-<p align="center">
- <a href="https://penguin.ooo/"><img src="https://img.shields.io/badge/Website-penguin.ooo-1f6feb?logo=googlechrome&logoColor=white" alt="Website" /></a>
- <a href="https://penguin.ooo/docs/"><img src="https://img.shields.io/badge/Docs-penguin.ooo%2Fdocs-1f6feb?logo=readthedocs&logoColor=white" alt="Docs" /></a>
- <a href="https://penguin.ooo/blog"><img src="https://img.shields.io/badge/Blog-penguin.ooo%2Fblog-1f6feb?logo=rss&logoColor=white" alt="Blog" /></a>
-</p>
-
-<p align="center">
- <a href="https://discord.gg/eFHKqqcU3D"><img src="https://img.shields.io/badge/Discord-join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord" /></a>
- <a href="https://x.com/code_hiyouga"><img src="https://img.shields.io/badge/X-code%5Fhiyouga-000000?logo=x&logoColor=white" alt="X (Twitter)" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness-community/blob/main/wechat/group.jpg"><img src="https://img.shields.io/badge/WeChat-user%20group-07C160?logo=wechat&logoColor=white" alt="WeChat" /></a>
-</p>
-
-<p align="center">
- <a href="https://www.producthunt.com/products/penguinharness?embed=true&amp;utm_source=badge-featured&amp;utm_medium=badge&amp;utm_campaign=badge-penguinharness" target="_blank" rel="noopener noreferrer"><img alt="Adelie - Let Agents Autonomously Build Better Agents for $0.02 | Product Hunt" width="250" height="54" src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1202577&amp;theme=light&amp;t=1784804711946" /></a>
-</p>
+> [!IMPORTANT]
+> **Adelie is a fork of [PenguinHarness](https://github.com/Prism-Shadow/penguin-harness).** The code
+> tree, the engine, the Web frontend and the protocol all come from PenguinHarness (Apache-2.0);
+> Adelie is the productised line built on top of it — its own brand and interface, its own data root
+> and ports, its own release pipeline.
+>
+> - Where it came from, what the licence requires, what we changed: [`FORK.md`](FORK.md)
+> - How far the work has got: [`FORK-PROGRESS.md`](FORK-PROGRESS.md)
+> - The upstream project's own channels — repository, website, docs, blog, community, Discord, X,
+> WeChat, Product Hunt — are **theirs**, not Adelie's: <https://github.com/Prism-Shadow/penguin-harness> ·
+> <https://penguin.ooo/>
+> - The PenguinHarness and PrismShadow names and marks belong to upstream. Adelie does not use them
+> as its own name, icon or domain.
<p align="center">English | <a href="README.zh.md">简体中文</a></p>
@@ -84,7 +69,7 @@ https://github.com/user-attachments/assets/922d13a6-5ffc-4685-9a39-352f02f9afc0
## Built-in plugins
-Four plugin categories ship in the box ([docs](https://penguin.ooo/docs/skills)) — skills, plus the session hooks that drive goal mode and continual learning; agents can also write and optimize their own skills:
+Four plugin categories ship in the box (the docs live in [`packages/docs`](packages/docs) in this tree) — skills, plus the session hooks that drive goal mode and continual learning; agents can also write and optimize their own skills:
| Category | Plugins |
| -------------------- | ----------------------------------------------------------------------------- |
@@ -117,132 +102,62 @@ Each family's latest generation only — the app's **Models** page lists every b
| ------------ | -------------------------------------------------------------------------- |
| OS | Linux, macOS, Windows 10+ |
| Architecture | x64, arm64 |
-| Runtime | bundled by the one-line installer (npm installs need Node >= 24) |
+| Runtime | Node >= 24 (there is no Adelie installer yet — see Installation) |
| Model | an API key for at least one model |
-## Installation
-
-Start with the desktop app, or install the command line on a workstation or server. Both use the same `~/.penguin/data` root and can be mixed freely; a server is also one `docker run` away:
-
-- **🖥️ Desktop app** — a double-click install: it embeds the server and opens already signed in, no terminal involved.
-- **⌨️ CLI** — a one-line installer (or npm / offline package) puts the `penguin` command on the machine; `penguin web` then serves the full Web experience in your browser at `http://127.0.0.1:7364` (multi-session chat, agent / skill / model management, usage stats, Trace observability, evaluation center). The online installers bundle their own Node runtime — unpack and run; upgrades and reinstalls never touch your data.
-
-> [!NOTE]
-> On a CLI install, the server prints a first-login link as a framed notice on every start until a password is set — open it to claim the built-in `admin` account and choose one. Models are configured on the in-app **Models** page.
-
-### 🖥️ Desktop app
-
-The full Web experience as a standalone application: it embeds the server and opens already signed in — no terminal, no login page, no initial password to copy. It works on the same `~/.penguin/data` root as a CLI install, so the two can be used interchangeably (a data root only ever runs one server; if a CLI-started instance is already up, the app attaches to it).
-
-Download the desktop app from the [download page](https://penguin.ooo/download). The page serves the OSS-accelerated mirror when it is reachable, and every installer is also attached to each [GitHub Release](https://github.com/Prism-Shadow/penguin-harness/releases).
-
-| Platform | Installers |
-| ----------- | --------------------------- |
-| macOS 11+ | dmg (Apple Silicon / Intel) |
-| Windows 10+ | installer (.exe, x64) |
-| Linux (x64) | AppImage / deb |
-
-The macOS builds are Developer ID signed and notarized, and the Windows installers are Authenticode signed, so neither platform needs a first-launch unblock. Linux is the one exception:
-
-<details>
-<summary><b>🐧 Linux: double-clicking the AppImage does nothing</b></summary>
-
-Browsers download AppImages without the execute permission. Grant it once and the app starts normally from then on (the deb package installs through the package manager and is not affected):
-
-```bash
-chmod +x penguin-desktop-linux-x86_64.AppImage
-```
-
-</details>
-
-### 🐧🍎 Linux / macOS (online install)
-
-```bash
-curl -fsSL https://penguin.ooo/install.sh | sh
-penguin web # start the service and open http://127.0.0.1:7364
-```
-
-### 🪟 Windows (online install, PowerShell)
-
-```powershell
-irm https://penguin.ooo/install.ps1 | iex
-penguin web # start the service and open http://127.0.0.1:7364
-```
-
-### 📦 npm (any platform, Node >= 24)
-
-```bash
-npm install -g @prismshadow/penguin-cli
-penguin web # start the service and open http://127.0.0.1:7364
-```
-
-### 🐳 Docker
-
-```bash
-docker run -d --name penguin -p 127.0.0.1:7364:7364 -v penguin-data:/data hiyouga/penguinharness:latest
-docker logs penguin # the first-login link, openable as it stands on this machine
-```
-
-The official image runs the same server on `0.0.0.0:7364` with its data root on the `/data` volume, as an unprivileged user, for `linux/amd64` and `linux/arm64`. It is built from this repository's source: `latest` is rebuilt on every push to `main`, and each release is published under its exact version (`hiyouga/penguinharness:0.2.13`) — there is no moving `stable` tag. The example publishes the port on the host's loopback, so the Web App answers only on the machine running Docker (`http://localhost:7364`); to reach it from a network, publish on all interfaces instead (`-p 7364:7364`), preferably behind a reverse proxy that terminates TLS. Compose file and the full deployment notes — reverse proxies, upgrades, the rescue path — are in the [Docker quickstart](https://penguin.ooo/docs/quickstart-docker).
-
-<details>
-<summary><b>📴 Offline install (air-gapped machines)</b></summary>
-
-Every <a href="https://github.com/Prism-Shadow/penguin-harness/releases">GitHub Release</a> attaches exactly one package per target — Linux and macOS in x64 / arm64, Windows in x64, plus a runtime-less universal package — and the same file serves online and offline installation. Each package seals the program payload, its SHA256 checksum and the platform's installer: download the one file on a networked machine, copy it to the target, extract once and run the bundled installer — no network, no separate checksum file to carry (the sealed SHA256 is always verified).
-
-**Linux (on arm64, use `penguin-linux-arm64.tar.gz`):**
-
-```bash
-mkdir penguin-install
-tar -xzf penguin-linux-x64.tar.gz -C penguin-install
-./penguin-install/install.sh
-```
+## Installation — read this first
-**macOS (Apple silicon shown; on Intel, use `penguin-darwin-x64.tar.gz`):**
+**Adelie has not shipped release artifacts of its own yet.** There is no Adelie npm package, no
+Adelie installer, no Adelie Docker image and no Adelie download page: those are the last step of the
+plan ([`FORK-PROGRESS.md`](FORK-PROGRESS.md) §4). Today the only way to run Adelie is from this
+source tree:
```bash
-mkdir penguin-install
-tar -xzf penguin-darwin-arm64.tar.gz -C penguin-install
-./penguin-install/install.sh
+# dependencies (skip desktop/electron: it downloads a runtime and is not needed for the Web App)
+pnpm install --frozen-lockfile \
+ --filter @prismshadow/penguin-core --filter @prismshadow/penguin-ui \
+ --filter @prismshadow/penguin-server --filter @prismshadow/penguin-web \
+ --filter @prismshadow/penguin-cli --filter @prismshadow/penguin-hmr
+
+# build (core's exports point at dist/, so build before running anything)
+pnpm -r --filter @prismshadow/penguin-core --filter @prismshadow/penguin-server \
+ --filter @prismshadow/penguin-web run build
+
+# run the server together with the built Web App
+cd packages/server
+PENGUIN_HOME=<data root> HOST=0.0.0.0 PORT=<port> node dist/index.js
```
-**Windows (unzip, then double-click `install.cmd` — or run it in PowerShell):**
+The first start prints a first-login link as a framed notice on every start until a password exists —
+open it to claim the built-in `admin` account and set one (there is no initial password to copy).
+Models are configured on the in-app **Models** page, which is where a fresh instance needs an API key
+before it can run anything.
-```powershell
-Expand-Archive penguin-win32-x64.zip -DestinationPath penguin-install
-cd penguin-install
-.\install.cmd
-```
-
-</details>
+> [!WARNING]
+> Everything the upstream README offers — `curl https://penguin.ooo/install.sh | sh`,
+> `npm install -g @prismshadow/penguin-cli`, `docker run hiyouga/penguinharness`, the desktop
+> installer on <https://penguin.ooo/download> — installs **PenguinHarness**, not Adelie. Those
+> channels stay upstream's until Adelie publishes its own.
-### 🤖 CLI & SDK — for agents
+Package names, the data root and the command name still carry the upstream spelling
+(`@prismshadow/*`, `~/.penguin/data`, `penguin`) because the rename is a staged job — what is left
+of it is tracked in [`FORK-PROGRESS.md`](FORK-PROGRESS.md).
-The same engine, scriptable — made to be driven by agents (and agents building agents):
+## Development
```bash
-penguin config model add --provider deepseek --model-id deepseek-flash --api-key sk-... --set-default
-penguin run -m "Create hello.txt containing Hello, Penguin" # one-shot task
-penguin chat # interactive REPL (/compact, /clear, /exit, Ctrl-C to interrupt)
-penguin server # headless service (same API the Web App uses)
+pnpm install && pnpm build # build first: core's exports point at dist/
+pnpm dev # backend + web app together (prefixed logs, deps built once)
```
-```ts
-import { createAgent, isCompleteModelMessage, userText } from "@prismshadow/penguin-core";
-
-const agent = await createAgent({ agentId: "default_agent" });
-const session = await agent.createSession({ workspaceDir: process.cwd() });
+See [CONTRIBUTING.md](.github/CONTRIBUTING.md) for the workspace guide (the file is upstream's and
+largely still describes this tree accurately): dev commands, quality gates, repo layout, changelog
+rule. `packages/landing` (the upstream website) was removed in this fork.
-for await (const output of session.run([userText("Create hello.txt containing hi")], {
- approve: async () => "allow", // per-tool-call approval
-})) {
- if (isCompleteModelMessage(output) && output.payload.type === "text") {
- console.log(output.payload.text);
- }
-}
-```
+## Upstream roadmap
-## Roadmap
+This is the upstream project's roadmap, kept here as context for where
+the base is heading. Adelie's own plan is [`FORK-PROGRESS.md`](FORK-PROGRESS.md).
- [ ] Public release of the benchmark suite
- [x] Desktop app
@@ -252,31 +167,24 @@ for await (const output of session.run([userText("Create hello.txt containing hi
- [ ] OpenShell integration (permission-governed shell)
- More to come…
-## Development
-
-```bash
-pnpm install && pnpm build # build first: core's exports point at dist/
-pnpm dev # backend + web app together (prefixed logs, deps built once)
-```
-
-See [CONTRIBUTING.md](.github/CONTRIBUTING.md) for the full workspace guide: dev commands, quality gates, repo layout, and the changelog rule.
-
-## Contributors
+## Upstream contributors
-Thanks to everyone who has contributed to Adelie!
+Thanks to everyone who has contributed to PenguinHarness — the
+codebase this fork is built on.
<p align="center">
- <a href="https://github.com/Prism-Shadow/penguin-harness/graphs/contributors"><img src="https://contrib.rocks/image?repo=Prism-Shadow/penguin-harness" alt="Adelie contributors" /></a>
+ <a href="https://github.com/Prism-Shadow/penguin-harness/graphs/contributors"><img src="https://contrib.rocks/image?repo=Prism-Shadow/penguin-harness" alt="PenguinHarness contributors" /></a>
</p>
## Citation
-If you use Adelie in your research, please cite:
+If you use this codebase in your research, cite the upstream project it comes from (Adelie is a
+fork of it):
```bibtex
@software{penguinharness2026,
author = {{PrismShadow Team}},
- title = {Adelie: Efficient Self-Improving Harness for Everyone},
+ title = {PenguinHarness: Efficient Self-Improving Harness for Everyone},
year = {2026},
url = {https://github.com/Prism-Shadow/penguin-harness},
license = {Apache-2.0}
@@ -294,6 +202,7 @@ See [THIRD-PARTY-NOTICES.md](THIRD-PARTY-NOTICES.md) for their licenses.
## License
-[Apache-2.0](LICENSE) © 2026 Prism Shadow
+[Apache-2.0](LICENSE) © 2026 Prism Shadow — the upstream copyright. Adelie is a fork of it and
+is released under the same licence; see [`FORK.md`](FORK.md).
-Built with ❤️ by [Yaowei Zheng](https://github.com/hiyouga) (author of [LlamaFactory](https://github.com/hiyouga/LlamaFactory)), the [PrismShadow AI Team](https://github.com/Prism-Shadow), and [Fable 5](https://www.anthropic.com/news/claude-fable-5-mythos-5).
+The upstream PenguinHarness codebase is built with ❤️ by [Yaowei Zheng](https://github.com/hiyouga) (author of [LlamaFactory](https://github.com/hiyouga/LlamaFactory)), the [PrismShadow AI Team](https://github.com/Prism-Shadow), and [Fable 5](https://www.anthropic.com/news/claude-fable-5-mythos-5). Adelie is a fork of that work.
diff --git a/README.zh.md b/README.zh.md
index 6aaf3710..42deb06a 100644
--- a/README.zh.md
+++ b/README.zh.md
@@ -4,42 +4,24 @@
<h1 align="center">Adelie</h1>
-<p align="center"><strong>开源、本地的多 Agent 应用自动开发平台</strong><br />全自动<strong>创建</strong> · <strong>优化</strong> · <strong>部署</strong> AI 应用</p>
+<p align="center"><strong>本地优先的多智能体应用开发平台,构建在 PenguinHarness 之上</strong></p>
<p align="center">
- <a href="https://penguin.ooo/download">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="assets/readme/download-zh-dark.svg" />
- <img src="assets/readme/download-zh-light.svg" alt="下载应用" height="44" />
- </picture>
- </a>
-</p>
-
-<p align="center">1000+ 模型 · 多平台 · Apache 2.0 · Agent 自进化</p>
-
-<p align="center">
- <a href="https://www.npmjs.com/package/@prismshadow/penguin-core"><img src="https://img.shields.io/npm/v/@prismshadow/penguin-core" alt="npm 版本" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/ci.yml"><img src="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/pages.yml"><img src="https://github.com/Prism-Shadow/penguin-harness/actions/workflows/pages.yml/badge.svg" alt="Deploy Site" /></a>
- <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="License: Apache-2.0" /></a>
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue" alt="协议:Apache-2.0" /></a>
<img src="https://img.shields.io/badge/node-%E2%89%A5%2024-brightgreen" alt="Node >= 24" />
+ <a href="https://github.com/Prism-Shadow/penguin-harness"><img src="https://img.shields.io/badge/%E6%9D%A5%E6%BA%90-PenguinHarness%20%E7%9A%84%20fork-1f6feb" alt="PenguinHarness 的 fork" /></a>
</p>
-<p align="center">
- <a href="https://penguin.ooo/"><img src="https://img.shields.io/badge/%E5%AE%98%E7%BD%91-penguin.ooo-1f6feb?logo=googlechrome&logoColor=white" alt="官网" /></a>
- <a href="https://penguin.ooo/docs/"><img src="https://img.shields.io/badge/%E6%96%87%E6%A1%A3-penguin.ooo%2Fdocs-1f6feb?logo=readthedocs&logoColor=white" alt="文档" /></a>
- <a href="https://penguin.ooo/blog"><img src="https://img.shields.io/badge/%E5%8D%9A%E5%AE%A2-penguin.ooo%2Fblog-1f6feb?logo=rss&logoColor=white" alt="博客" /></a>
-</p>
-
-<p align="center">
- <a href="https://discord.gg/eFHKqqcU3D"><img src="https://img.shields.io/badge/Discord-%E5%8A%A0%E5%85%A5%E8%AE%A8%E8%AE%BA-5865F2?logo=discord&logoColor=white" alt="Discord" /></a>
- <a href="https://x.com/code_hiyouga"><img src="https://img.shields.io/badge/X-code%5Fhiyouga-000000?logo=x&logoColor=white" alt="X(Twitter)" /></a>
- <a href="https://github.com/Prism-Shadow/penguin-harness-community/blob/main/wechat/group.jpg"><img src="https://img.shields.io/badge/%E5%BE%AE%E4%BF%A1-%E4%BA%A4%E6%B5%81%E7%BE%A4-07C160?logo=wechat&logoColor=white" alt="微信群" /></a>
-</p>
-
-<p align="center">
- <a href="https://www.producthunt.com/products/penguinharness?embed=true&amp;utm_source=badge-featured&amp;utm_medium=badge&amp;utm_campaign=badge-penguinharness" target="_blank" rel="noopener noreferrer"><img alt="Adelie - Let Agents Autonomously Build Better Agents for $0.02 | Product Hunt" width="250" height="54" src="https://api.producthunt.com/widgets/embed-image/v1/featured.svg?post_id=1202577&amp;theme=light&amp;t=1784804711946" /></a>
-</p>
+> [!IMPORTANT]
+> **Adelie 是 [PenguinHarness](https://github.com/Prism-Shadow/penguin-harness) 的 fork。**
+> 这棵代码树、引擎、Web 前端与协议都来自 PenguinHarness(Apache-2.0);Adelie 是长在它上面的
+> 产品线 —— 自己的品牌与界面、自己的数据根与端口、自己的发布链路。
+>
+> - 来源、许可证义务、我们改了什么:[`FORK.md`](FORK.md)
+> - 改到哪一步了:[`FORK-PROGRESS.md`](FORK-PROGRESS.md)
+> - 上游自己的渠道(仓库、官网、文档、博客、社区、Discord、X、微信、Product Hunt)是**上游的**,
+> 不是 Adelie 的:<https://github.com/Prism-Shadow/penguin-harness> · <https://penguin.ooo/>
+> - PenguinHarness / PrismShadow 的名字与商标属于上游。Adelie 不拿它们当自己的名号、图标或域名。
<p align="center"><a href="README.md">English</a> | 简体中文</p>
@@ -84,7 +66,7 @@ https://github.com/user-attachments/assets/aec49ae9-b743-467b-b247-37bedfeaa36e
## 内置插件库
-开箱内置四类插件([文档](https://penguin.ooo/docs/skills))——Skill,以及驱动目标模式与持续学习的会话钩子;Agent 也能编写并优化自己的 Skill:
+开箱内置四类插件(文档在这个仓库的 [`packages/docs`](packages/docs) 里)——Skill,以及驱动目标模式与持续学习的会话钩子;Agent 也能编写并优化自己的 Skill:
| 分类 | 插件 |
| ----------- | ------------------------------------------------------------------------------- |
@@ -113,136 +95,61 @@ https://github.com/user-attachments/assets/aec49ae9-b743-467b-b247-37bedfeaa36e
## 系统需求
-| 需求项 | 支持情况 |
-| -------- | ------------------------------------------------- |
-| 操作系统 | Linux、macOS、Windows 10+ |
-| 架构 | x64、arm64 |
-| 运行时 | 一行安装器自带(经 npm 安装需 Node >= 24) |
-| 模型 | 至少一个模型的 API key |
-
-## 安装
-
-优先使用桌面端,也可以在本地电脑或服务器上安装命令行。两种方式共用 `~/.penguin/data` 目录,可自由混用;服务端也可以一条 `docker run` 起来:
-
-- **🖥️ 桌面端应用**——双击安装:内嵌服务端,打开即已登录,全程无需终端。
-- **⌨️ 命令行**——一行命令(或 npm / 离线包)装出 `penguin` 命令,`penguin web` 即在浏览器打开完整 Web 体验 `http://127.0.0.1:7364`(多会话对话、Agent / 技能 / 模型管理、用量统计、轨迹观测、评估中心)。在线安装器自带 Node 运行时,解压即用;升级与重装不触碰数据。
-
-> [!NOTE]
-> 命令行安装后,服务端会以边框提示打印一条首次登录链接(在密码被设置之前每次启动都会重新打印)——打开即可认领内置管理员 `admin` 并设置密码;模型在应用内「模型」页配置。
-
-### 🖥️ 桌面端应用
-
-完整的 Web 体验打包为独立应用:内嵌服务端,打开即已登录——无需终端、无登录页、也不用抄初始密码——并与 CLI 安装共用同一个 `~/.penguin/data` 数据目录,两者可以混用(一个数据目录同一时刻只运行一个服务端;CLI 已启动实例时,应用会直接接入它)。
-
-从[下载页](https://penguin.ooo/download)获取桌面端应用。下载页会自动选择可用的 OSS 加速源,安装包也附于每个 [GitHub Release](https://github.com/Prism-Shadow/penguin-harness/releases)。
-
-| 平台 | 安装包 |
-| ------------- | ---------------------------- |
-| macOS 11+ | dmg(Apple 芯片 / Intel) |
-| Windows 10+ | 安装程序(.exe,x64) |
-| Linux(x64) | AppImage / deb |
-
-macOS 安装包已由 Developer ID 签名并公证,Windows 安装程序已 Authenticode 签名,两个平台首次启动都无需额外放行;只有 Linux 是例外:
-
-<details>
-<summary><b>🐧 Linux 双击 AppImage 没有反应?</b></summary>
-
-浏览器下载的 AppImage 默认没有执行权限,赋权一次后即可正常启动(deb 包经包管理器安装,无此问题):
-
-```bash
-chmod +x penguin-desktop-linux-x86_64.AppImage
-```
-
-</details>
-
-### 🐧🍎 Linux / macOS(在线安装)
-
-```bash
-curl -fsSL https://penguin.ooo/install.sh | sh
-penguin web # 启动服务并打开 http://127.0.0.1:7364
-```
-
-### 🪟 Windows(在线安装,PowerShell)
-
-```powershell
-irm https://penguin.ooo/install.ps1 | iex
-penguin web # 启动服务并打开 http://127.0.0.1:7364
-```
-
-### 📦 npm(任意平台,需 Node >= 24)
-
-```bash
-npm install -g @prismshadow/penguin-cli
-penguin web # 启动服务并打开 http://127.0.0.1:7364
-```
-
-### 🐳 Docker
+| 需求项 | 支持情况 |
+| -------- | --------------------------------------------------- |
+| 操作系统 | Linux、macOS、Windows 10+ |
+| 架构 | x64、arm64 |
+| 运行时 | Node >= 24(Adelie 还没有安装包 —— 见「安装」一节) |
+| 模型 | 至少一个模型的 API key |
-```bash
-docker run -d --name penguin -p 127.0.0.1:7364:7364 -v penguin-data:/data hiyouga/penguinharness:latest
-docker logs penguin # 首次登录链接,在本机可原样打开
-```
-
-官方镜像以非特权用户在 `0.0.0.0:7364` 上运行同一个服务端,数据目录落在 `/data` 卷上,提供 `linux/amd64` 与 `linux/arm64`。镜像由本仓库源码构建:`latest` 在每次 push `main` 时重建,每个发布版以精确版本号发布(`hiyouga/penguinharness:0.2.13`),没有会移动的 `stable` 标签。示例把端口发布在宿主机回环上,因此 Web 应用只在运行 Docker 的那台机器上可达(`http://localhost:7364`);要从网络访问,改为发布到所有接口(`-p 7364:7364`),并尽量置于终结 TLS 的反向代理之后。compose 文件与完整部署说明(反向代理、升级、救援路径)见 [Docker 快速开始](https://penguin.ooo/docs/quickstart-docker)。
-
-<details>
-<summary><b>📴 离线安装(无网环境)</b></summary>
+## 安装 —— 先读这一节
-每个 <a href="https://github.com/Prism-Shadow/penguin-harness/releases">GitHub Release</a> 每个目标只附带一个安装包——Linux 与 macOS 各有 x64 / arm64 两种架构,Windows 为 x64,另有不带运行时的 universal 包——同一个文件同时服务在线与离线安装。包内封入程序负载、其 SHA256 校验文件与对应平台的安装器:在有网机器下载这一个文件,拷贝到目标机器,解压一次并运行包内安装器即可——全程无需联网,也不必另外携带校验文件(包内封入的 SHA256 始终强制校验)。
-
-**Linux(arm64 机器换用 `penguin-linux-arm64.tar.gz`):**
+**Adelie 还没有发布自己的产物。** 没有 Adelie 的 npm 包、安装包、Docker 镜像或下载页 —— 那是计划的
+最后一步([`FORK-PROGRESS.md`](FORK-PROGRESS.md) §4)。现在要跑 Adelie,只有从这棵源码树开始:
```bash
-mkdir penguin-install
-tar -xzf penguin-linux-x64.tar.gz -C penguin-install
-./penguin-install/install.sh
+# 装依赖(跳过 desktop / electron:它要下一个运行时,跑 Web 用不到)
+pnpm install --frozen-lockfile \
+ --filter @prismshadow/penguin-core --filter @prismshadow/penguin-ui \
+ --filter @prismshadow/penguin-server --filter @prismshadow/penguin-web \
+ --filter @prismshadow/penguin-cli --filter @prismshadow/penguin-hmr
+
+# 构建(core 的导出指向 dist/,不先构建就跑不起来)
+pnpm -r --filter @prismshadow/penguin-core --filter @prismshadow/penguin-server \
+ --filter @prismshadow/penguin-web run build
+
+# 起服务端 + 已构建的 Web 前端
+cd packages/server
+PENGUIN_HOME=<数据根> HOST=0.0.0.0 PORT=<端口> node dist/index.js
```
-**macOS(Apple 芯片用 arm64 包,Intel 芯片换用 `penguin-darwin-x64.tar.gz`):**
+首次启动会在输出里打印一条「首次登录链接」,在设密码之前每次启动都会打印:打开它认领内置的
+`admin` 账号并设置密码(没有可输入的初始密码)。模型在应用内的**模型库**页配置 —— 新实例要先配一个
+API key 才能跑任务。
-```bash
-mkdir penguin-install
-tar -xzf penguin-darwin-arm64.tar.gz -C penguin-install
-./penguin-install/install.sh
-```
+> [!WARNING]
+> 上游 README 里的那些方式 —— `curl https://penguin.ooo/install.sh | sh`、
+> `npm install -g @prismshadow/penguin-cli`、`docker run hiyouga/penguinharness`、
+> <https://penguin.ooo/download> 上的桌面安装包 —— 装出来的是 **PenguinHarness**,不是 Adelie。
+> 那些渠道在 Adelie 发布自己的产物之前,仍然属于上游。
-**Windows(解压后双击 `install.cmd`,或在 PowerShell 中运行):**
+包名、数据根与命令名还留着上游的拼写(`@prismshadow/*`、`~/.penguin/data`、`penguin`)—— 改名是
+分期做的,还没做完的部分记在 [`FORK-PROGRESS.md`](FORK-PROGRESS.md)。
-```powershell
-Expand-Archive penguin-win32-x64.zip -DestinationPath penguin-install
-cd penguin-install
-.\install.cmd
-```
-
-</details>
-
-### 🤖 CLI 与 SDK——面向 Agent
-
-同一引擎、可脚本化——为被 Agent 驱动而生(以及让 Agent 构建 Agent):
+## 参与开发
```bash
-penguin config model add --provider deepseek --model-id deepseek-flash --api-key sk-... --set-default
-penguin run -m "Create hello.txt containing Hello, Penguin" # 单次任务
-penguin chat # 交互式 REPL(/compact、/clear、/exit、Ctrl-C 中断)
-penguin server # 无界面服务(与 Web 应用同一套 API)
+pnpm install && pnpm build # 先构建:core 的导出指向 dist/
+pnpm dev # 后端 + Web 前端一起起(日志带前缀,依赖只构建一次)
```
-```ts
-import { createAgent, isCompleteModelMessage, userText } from "@prismshadow/penguin-core";
-
-const agent = await createAgent({ agentId: "default_agent" });
-const session = await agent.createSession({ workspaceDir: process.cwd() });
+完整的工作区指南见 [CONTRIBUTING.zh.md](.github/CONTRIBUTING.zh.md)(那份文件是上游的,大体仍准确):
+开发命令、质量门禁、仓库结构、变更日志规则。上游的官网站点 `packages/landing` 已在本 fork 中删除。
-for await (const output of session.run([userText("Create hello.txt containing hi")], {
- approve: async () => "allow", // 按工具调用逐个审批
-})) {
- if (isCompleteModelMessage(output) && output.payload.type === "text") {
- console.log(output.payload.text);
- }
-}
-```
+## 上游路线图
-## 路线图
+这里是上游项目的路线图,留作了解这个基座往哪走。Adelie 自己的计划在
+[`FORK-PROGRESS.md`](FORK-PROGRESS.md)。
- [ ] Benchmark 套件正式发布
- [x] 桌面端应用
@@ -252,31 +159,22 @@ for await (const output of session.run([userText("Create hello.txt containing hi
- [ ] 集成 OpenShell(带权限管控的 shell)
- 更多规划,敬请期待……
-## 参与开发
-
-```bash
-pnpm install && pnpm build # 先构建:core 的导出指向 dist/
-pnpm dev # 服务端 + Web 一起启动(带前缀日志,依赖只构建一次)
-```
-
-完整工作区指南见 [CONTRIBUTING.zh.md](.github/CONTRIBUTING.zh.md):开发命令、质量门禁、仓库结构与 changelog 规则。
-
-## 贡献者
+## 上游贡献者
-感谢每一位为 Adelie 作出贡献的开发者!
+感谢每一位为 PenguinHarness 作出贡献的开发者 —— 这个 fork 建在它的代码之上。
<p align="center">
- <a href="https://github.com/Prism-Shadow/penguin-harness/graphs/contributors"><img src="https://contrib.rocks/image?repo=Prism-Shadow/penguin-harness" alt="Adelie 贡献者" /></a>
+ <a href="https://github.com/Prism-Shadow/penguin-harness/graphs/contributors"><img src="https://contrib.rocks/image?repo=Prism-Shadow/penguin-harness" alt="PenguinHarness 贡献者" /></a>
</p>
## 引用
-如果 Adelie 对你的研究有帮助,请引用:
+如果你用到了这套代码,请引用它的上游项目(Adelie 是它的 fork):
```bibtex
@software{penguinharness2026,
author = {{PrismShadow Team}},
- title = {Adelie: Efficient Self-Improving Harness for Everyone},
+ title = {PenguinHarness: Efficient Self-Improving Harness for Everyone},
year = {2026},
url = {https://github.com/Prism-Shadow/penguin-harness},
license = {Apache-2.0}
@@ -294,6 +192,7 @@ pnpm dev # 服务端 + Web 一起启动(带前缀日志,
## 协议
-[Apache-2.0](LICENSE) © 2026 Prism Shadow
+[Apache-2.0](LICENSE) © 2026 Prism Shadow —— 这是上游的版权。Adelie 是它的 fork,
+以同一协议发布;见 [`FORK.md`](FORK.md)。
-由 [LlamaFactory](https://github.com/hiyouga/LlamaFactory) 作者 [Yaowei Zheng](https://github.com/hiyouga)、[PrismShadow AI Team](https://github.com/Prism-Shadow) 与 [Fable 5](https://www.anthropic.com/news/claude-fable-5-mythos-5) 共同用 ❤️ 构建。
+上游 PenguinHarness 由 [LlamaFactory](https://github.com/hiyouga/LlamaFactory) 作者 [Yaowei Zheng](https://github.com/hiyouga)、[PrismShadow AI Team](https://github.com/Prism-Shadow) 与 [Fable 5](https://www.anthropic.com/news/claude-fable-5-mythos-5) 共同用 ❤️ 构建。Adelie 是这份工作的 fork。
diff --git a/RELEASE-v0.2.0.md b/RELEASE-v0.2.0.md
new file mode 100644
index 00000000..c85abc5e
--- /dev/null
+++ b/RELEASE-v0.2.0.md
@@ -0,0 +1,85 @@
+# Adelie v0.2.0 —— 基于 PenguinHarness 的新基座(源码版)
+
+**这一版是 Adelie 换基座后的第一个版本:整棵代码树 fork 自
+[PenguinHarness](https://github.com/Prism-Shadow/penguin-harness)。** Adelie 自己的引擎从这一版
+起不再使用;引擎、Web 前端、协议都来自上游,Adelie 长在它上面做产品化。
+
+## 基于哪个版本
+
+| | |
+| --- | --- |
+| 上游 | [Prism-Shadow/penguin-harness](https://github.com/Prism-Shadow/penguin-harness)(Apache-2.0) |
+| 基座提交 | `18d7c137a1f1`(上游 `develop`,2026-10-04 取) |
+| 本版分支 | `fork/penguin-base` |
+| 上游与许可证义务的说明 | [`FORK.md`](FORK.md) |
+| 改到哪一步了 | [`FORK-PROGRESS.md`](FORK-PROGRESS.md) |
+
+## 这一版改了什么(相对基座)
+
+1. **品牌自有化**:界面与全仓文案里的产品名统一成 Adelie(140 个文件;`LICENSE`、
+ `THIRD-PARTY-NOTICES.md`、`changelog/` 等法律与历史原文不动);界面图标换成 Adelie 自己的
+ 标志(`packages/{web,docs,ui-gallery}/public/adelie-icon.svg`)。默认 system prompt 里含产品名,
+ 因此内核版本一并推进到 `2026-10-05`,旧 prompt 哈希进了 `KERNEL_SUPERSEDED_TAB_HASHES`。
+2. **删掉上游官网**:`packages/landing`(官网 + 博客 + 下载页,163 个文件)与只为它存在的
+ `scripts/build-site.mjs`、`.github/workflows/pages.yml` 一并删除,各处引用清理干净。
+ 上游文档站(`packages/docs`)留作内部参考。
+3. **README 重写**:两份 README(中/英)现在都写明「Adelie 是 PenguinHarness 的 fork」、
+ 上游渠道与商标归属,并把安装一节改成**本仓库已验证的从源码运行方式**。
+4. **上游发布流水线停用**:`.github/workflows/release.yml` 原本由 `v*` tag 触发,会构建并发布
+ 上游的 npm 包(`@penguinharness/*`、`@prismshadow/penguin-*`)与安装包 —— 对本仓库是错的,
+ 已改成只能手动触发(`workflow_dispatch`),Adelie 自己的发布流水线待重写。
+
+## 能不能直接装?—— 这一版只能从源码跑
+
+**本版不含任何二进制产物。** 没有 Adelie 的 npm 包、安装包、Docker 镜像或下载页:那是发布链路的
+最后一步(`FORK-PROGRESS.md` §4)。`@prismshadow/penguin-*` 那些包名、`~/.penguin/data` 数据根、
+`penguin` 命令名仍是上游拼写,改名与自己的产物一起做。
+
+从源码运行(本机实测过的命令):
+
+```bash
+pnpm install --frozen-lockfile \
+ --filter @prismshadow/penguin-core --filter @prismshadow/penguin-ui \
+ --filter @prismshadow/penguin-server --filter @prismshadow/penguin-web \
+ --filter @prismshadow/penguin-cli --filter @prismshadow/penguin-hmr
+
+pnpm -r --filter @prismshadow/penguin-core --filter @prismshadow/penguin-server \
+ --filter @prismshadow/penguin-web run build
+
+cd packages/server
+PENGUIN_HOME=<数据根> HOST=0.0.0.0 PORT=<端口> node dist/index.js
+```
+
+首次启动会打印一条「首次登录链接」,打开它认领内置 `admin` 账号并设置密码;模型在应用内的
+**模型库**页配置(需要至少一个 API key)。细节见 [README](README.md)。
+
+仓库内各 `package.json` 的版本号仍是上游的编号(`0.2.13`),**这是有意的**:Adelie 的版本号
+(本版 `v0.2.0`,接在旧 Adelie 的 `v0.1.0` 之后)与包版本一起改,属发布链路里 npm scope 改名那一步
+(`FORK-PROGRESS.md` §4.1)。
+
+> [!WARNING]
+> 上游那些安装方式(`curl https://penguin.ooo/install.sh | sh`、
+> `npm install -g @prismshadow/penguin-cli`、`docker run hiyouga/penguinharness`、
+> penguin.ooo 上的桌面安装包)装出来的是 **PenguinHarness**,不是 Adelie。
+
+## 质量门禁(本机跑过)
+
+- 单元/集成测试:**8485 通过 / 7 跳过 / 0 失败**(docs 62 · core 1346 · ui 999 · server 2552 ·
+ cli 509 · web 2886 · ui-gallery 131)
+- `pnpm lint`(oxlint)0 警告;`pnpm format:check`(prettier)干净;各包 `typecheck` 通过;
+ `sh scripts/test-installer.sh` 通过
+- 本机部署在 3004 端口真机跑通(登录、界面、图标)
+
+## 许可证与义务
+
+Adelie 是 PenguinHarness 的 fork,以同一协议 **Apache-2.0** 发布:`LICENSE`、
+`THIRD-PARTY-NOTICES.md` 与源码里的版权头一律保留;本仓库做过的改动都在提交历史与
+[`FORK-PROGRESS.md`](FORK-PROGRESS.md) 里写明。PenguinHarness / PrismShadow 的名字与商标属于上游,
+Adelie 不拿它们当自己的名号、图标或域名;上游的官网、文档、博客、Discord、X、微信、Product Hunt
+等渠道是上游的,不是 Adelie 的。
+
+## 已知待办
+
+自有化(数据根、端口、命令名)、接回旧 Adelie 的能力(用量与成本页、模型目录、审批口径、
+用户与角色)、用真模型端到端跑一条消息、npm scope 改名与发布流水线重写、旧四件产物按新基座
+更新重发 —— 清单在 [`FORK-PROGRESS.md`](FORK-PROGRESS.md)。