Release OpenPet v0.1.4

Author: X-T-E-R

.gitignore

@@ -7,7 +7,7 @@ src-tauri/target/
 .workflow/
 AGENTS.md
 .playwright-mcp/
-codex-pet-runtime-settings-ui*.png
+openpet-settings-ui*.png
 *.log
 .env
 .env.*

README.md

@@ -61,30 +61,30 @@ The importer downloads public metadata and the WebP spritesheet for the URL you
 
 OpenPet is designed to be controlled by local agents. Install only the skills you need:
 
-- `codex-pet-cli`: CLI control path for agents that can run local commands.
-- `codex-pet-mcp`: MCP control path for agents or clients that support Model Context Protocol.
-- `codex-pet-asset`: optional pet creation / validation workflow; install only when creating or packaging pets.
+- `openpet-cli`: CLI control path for agents that can run local commands.
+- `openpet-mcp`: MCP control path for agents or clients that support Model Context Protocol.
+- `openpet-asset`: optional pet creation / validation workflow; install only when creating or packaging pets.
 
-For normal control, choose either `codex-pet-cli` or `codex-pet-mcp`. Agents that can call localhost directly can use the HTTP API guidance below without installing a separate skill.
+For normal control, choose either `openpet-cli` or `openpet-mcp`. Agents that can call localhost directly can use the HTTP API guidance below without installing a separate skill.
 
 ### Agent Hook Tip
 
-If you want OpenPet to collaborate with an existing agent, add a short note to `AGENTS.md`, `.cursorrules`, or a similar agent instruction file. Tell the agent to use an installed OpenPet skill, such as `codex-pet-cli` or `codex-pet-mcp`, for desktop-pet progress updates during long work.
+If you want OpenPet to collaborate with an existing agent, add a short note to `AGENTS.md`, `.cursorrules`, or a similar agent instruction file. Tell the agent to use an installed OpenPet skill, such as `openpet-cli` or `openpet-mcp`, for desktop-pet progress updates during long work.
 
 If several OpenPet skills are installed, let the agent choose one integration path and condense the chosen rule into its local instruction file. The rule should reference the installed skill instead of duplicating protocol or command details.
 
 ### CLI
 
 ```powershell
-python skills\codex-pet-cli\scripts\codex_pet_cli.py --help
-python skills\codex-pet-cli\scripts\codex_pet_cli.py doctor --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py status --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py event thinking --message "Reading the repo..."
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-local public\pets\nia --dry-run --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-website https://petdex.crafter.run/pets/boba
+python skills\openpet-cli\scripts\openpet_cli.py --help
+python skills\openpet-cli\scripts\openpet_cli.py doctor --json
+python skills\openpet-cli\scripts\openpet_cli.py status --json
+python skills\openpet-cli\scripts\openpet_cli.py event thinking --message "Reading the repo..."
+python skills\openpet-cli\scripts\openpet_cli.py import-local public\pets\nia --dry-run --json
+python skills\openpet-cli\scripts\openpet_cli.py import-website https://petdex.crafter.run/pets/boba
 ```
 
-In agent instructions, tell the agent to use the `codex-pet-cli` skill for status checks, progress events, or pet imports. The CLI calls the running local runtime; if OpenPet is not reachable, live commands fail safely with a clear message instead of modifying app data behind the app's back.
+In agent instructions, tell the agent to use the `openpet-cli` skill for status checks, progress events, or pet imports. The CLI calls the running local runtime; if OpenPet is not reachable, live commands fail safely with a clear message instead of modifying app data behind the app's back.
 
 ### MCP
 
@@ -95,7 +95,7 @@ The MCP bridge is for IDEs or agents that support Model Context Protocol. Open y
   "mcpServers": {
     "openpet": {
       "command": "python",
-      "args": ["skills/codex-pet-mcp/scripts/openpet_mcp_server.py"]
+      "args": ["skills/openpet-mcp/scripts/openpet_mcp_server.py"]
     }
   }
 }
@@ -146,10 +146,10 @@ You can change the runtime listen address and port in Settings. Endpoint changes
 ```powershell
 pnpm build
 cargo test --manifest-path src-tauri/Cargo.toml
-python skills\codex-pet-cli\scripts\codex_pet_cli.py --help
-python skills\codex-pet-mcp\scripts\openpet_mcp_server.py --help
-python skills\codex-pet-cli\scripts\codex_pet_cli.py doctor --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-local public\pets\nia --dry-run --json
+python skills\openpet-cli\scripts\openpet_cli.py --help
+python skills\openpet-mcp\scripts\openpet_mcp_server.py --help
+python skills\openpet-cli\scripts\openpet_cli.py doctor --json
+python skills\openpet-cli\scripts\openpet_cli.py import-local public\pets\nia --dry-run --json
 ```
 
 For release checks and bundles:

README.zh-CN.md

@@ -61,30 +61,30 @@ spritesheet.webp
 
 OpenPet 面向本地 agent 控制。按需要安装对应 skill：
 
-- `codex-pet-cli`：适合能运行本地命令的 agent，走 CLI 控制路径。
-- `codex-pet-mcp`：适合支持 Model Context Protocol 的 agent 或 MCP client。
-- `codex-pet-asset`：可选的宠物创建 / 校验流程，只有创建或打包宠物时才需要。
+- `openpet-cli`：适合能运行本地命令的 agent，走 CLI 控制路径。
+- `openpet-mcp`：适合支持 Model Context Protocol 的 agent 或 MCP client。
+- `openpet-asset`：可选的宠物创建 / 校验流程，只有创建或打包宠物时才需要。
 
-日常控制桌宠时，`codex-pet-cli` 和 `codex-pet-mcp` 二选一即可。能直接请求 localhost 的 agent 可以使用下方 HTTP API 指引，不需要安装单独的 skill。
+日常控制桌宠时，`openpet-cli` 和 `openpet-mcp` 二选一即可。能直接请求 localhost 的 agent 可以使用下方 HTTP API 指引，不需要安装单独的 skill。
 
 ### Agent Hook 提示
 
-如果想让 OpenPet 和现有 agent 联动，可以在 `AGENTS.md`、`.cursorrules` 或类似 agent 指令文件里留一条简短规则：让 agent 在长任务中使用已安装的 OpenPet skill，例如 `codex-pet-cli` 或 `codex-pet-mcp`，把进度同步给桌宠。
+如果想让 OpenPet 和现有 agent 联动，可以在 `AGENTS.md`、`.cursorrules` 或类似 agent 指令文件里留一条简短规则：让 agent 在长任务中使用已安装的 OpenPet skill，例如 `openpet-cli` 或 `openpet-mcp`，把进度同步给桌宠。
 
 如果安装了多个 OpenPet skill，可以让 agent 自己选择一种集成路径，并把选择后的简短规则浓缩写进本地指令文件。规则只需要引用已安装 skill，不需要重复协议或命令细节。
 
 ### CLI
 
 ```powershell
-python skills\codex-pet-cli\scripts\codex_pet_cli.py --help
-python skills\codex-pet-cli\scripts\codex_pet_cli.py doctor --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py status --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py event thinking --message "正在阅读仓库..."
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-local public\pets\nia --dry-run --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-website https://petdex.crafter.run/pets/boba
+python skills\openpet-cli\scripts\openpet_cli.py --help
+python skills\openpet-cli\scripts\openpet_cli.py doctor --json
+python skills\openpet-cli\scripts\openpet_cli.py status --json
+python skills\openpet-cli\scripts\openpet_cli.py event thinking --message "正在阅读仓库..."
+python skills\openpet-cli\scripts\openpet_cli.py import-local public\pets\nia --dry-run --json
+python skills\openpet-cli\scripts\openpet_cli.py import-website https://petdex.crafter.run/pets/boba
 ```
 
-给 agent 的规则里可以要求它通过 `codex-pet-cli` skill 查询状态、发送进度事件或导入宠物。CLI 会调用运行中的本地 runtime；如果 OpenPet 不可访问，实时命令会安全失败并给出明确错误，而不是绕过应用私写 app data。
+给 agent 的规则里可以要求它通过 `openpet-cli` skill 查询状态、发送进度事件或导入宠物。CLI 会调用运行中的本地 runtime；如果 OpenPet 不可访问，实时命令会安全失败并给出明确错误，而不是绕过应用私写 app data。
 
 ### MCP
 
@@ -95,7 +95,7 @@ MCP bridge 适合支持 Model Context Protocol 的 IDE 或 agent。打开你的
   "mcpServers": {
     "openpet": {
       "command": "python",
-      "args": ["skills/codex-pet-mcp/scripts/openpet_mcp_server.py"]
+      "args": ["skills/openpet-mcp/scripts/openpet_mcp_server.py"]
     }
   }
 }
@@ -146,10 +146,10 @@ curl -X POST http://127.0.0.1:17321/api/import/local \
 ```powershell
 pnpm build
 cargo test --manifest-path src-tauri/Cargo.toml
-python skills\codex-pet-cli\scripts\codex_pet_cli.py --help
-python skills\codex-pet-mcp\scripts\openpet_mcp_server.py --help
-python skills\codex-pet-cli\scripts\codex_pet_cli.py doctor --json
-python skills\codex-pet-cli\scripts\codex_pet_cli.py import-local public\pets\nia --dry-run --json
+python skills\openpet-cli\scripts\openpet_cli.py --help
+python skills\openpet-mcp\scripts\openpet_mcp_server.py --help
+python skills\openpet-cli\scripts\openpet_cli.py doctor --json
+python skills\openpet-cli\scripts\openpet_cli.py import-local public\pets\nia --dry-run --json
 ```
 
 发布检查和打包：

package.json

@@ -1,6 +1,6 @@
 {
   "name": "openpet",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "private": true,
   "type": "module",
   "description": "OpenPet desktop runtime for Codex-compatible pet companions.",

skills/codex-pet-asset/SKILL.md skills/openpet-asset/SKILL.mdskills/codex-pet-asset/SKILL.md renamed to skills/openpet-asset/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: codex-pet-asset
+name: openpet-asset
 description: Create, validate, and package Codex-compatible desktop pet assets for OpenPet.
 ---
 
@@ -52,8 +52,8 @@ python scripts\validate_atlas.py <path-to-spritesheet>
 6. For local user imports, prefer the CLI:
 
 ```powershell
-python ..\codex-pet-cli\scripts\codex_pet_cli.py import-local <pet-folder> --dry-run
-python ..\codex-pet-cli\scripts\codex_pet_cli.py import-local <pet-folder>
+python ..\openpet-cli\scripts\openpet_cli.py import-local <pet-folder> --dry-run
+python ..\openpet-cli\scripts\openpet_cli.py import-local <pet-folder>
 ```
 
 ## Runtime Rules
@@ -69,7 +69,7 @@ python ..\codex-pet-cli\scripts\codex_pet_cli.py import-local <pet-folder>
 
 - `validate_atlas.py` reports `ok: true`, or another deterministic atlas check confirms dimensions/grid/cell size.
 - `pet.json` uses a safe id and relative `spritesheetPath`.
-- Imported packages validate with `python ..\codex-pet-cli\scripts\codex_pet_cli.py import-local <path> --dry-run`.
+- Imported packages validate with `python ..\openpet-cli\scripts\openpet_cli.py import-local <path> --dry-run`.
 - No white, checkerboard, or opaque rectangular background is visible in used or unused cells.
 - The pet shell shows the full `192x208` CSS cell at scale `1`.
 - Source, license status, and redistribution caveats are preserved before bundling or sharing assets.

skills/codex-pet-cli/SKILL.md skills/openpet-cli/SKILL.mdskills/codex-pet-cli/SKILL.md renamed to skills/openpet-cli/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: codex-pet-cli
+name: openpet-cli
 description: Use the OpenPet agent CLI protocol to inspect and control the local desktop pet, send status events, and import Codex-compatible local or website pet sources through the running runtime.
 ---
 
@@ -10,12 +10,12 @@ Use this skill when OpenClaw, Codex, or another local agent needs to operate Ope
 Default entry point:
 
 ```powershell
-python scripts\codex_pet_cli.py --help
+python scripts\openpet_cli.py --help
 ```
 
 ## Workflow
 
-1. Run `python scripts\codex_pet_cli.py doctor --json` when runtime reachability, app-data assumptions, or local server state matters.
+1. Run `python scripts\openpet_cli.py doctor --json` when runtime reachability, app-data assumptions, or local server state matters.
 2. Use `status`, `action`, `say`, and `event` for live control through the configured local runtime endpoint.
 3. Use `import-local <path>` to ask the running OpenPet runtime to import a local package directory, `pet.json`, or `spritesheet.webp`.
 4. Use `import-website <url>` to ask the running OpenPet runtime to import a supported HTTPS website source.
@@ -25,15 +25,15 @@ python scripts\codex_pet_cli.py --help
 ## Commands
 
 ```powershell
-python scripts\codex_pet_cli.py --help
-python scripts\codex_pet_cli.py doctor --json
-python scripts\codex_pet_cli.py status --json
-python scripts\codex_pet_cli.py action waving
-python scripts\codex_pet_cli.py say "Thinking..." --ttl-ms 4000
-python scripts\codex_pet_cli.py event success --message "Tests passed"
-python scripts\codex_pet_cli.py import-local public\pets\nia --dry-run --json
-python scripts\codex_pet_cli.py import-local <path-to-pet-folder>
-python scripts\codex_pet_cli.py import-website https://petdex.crafter.run/pets/boba
+python scripts\openpet_cli.py --help
+python scripts\openpet_cli.py doctor --json
+python scripts\openpet_cli.py status --json
+python scripts\openpet_cli.py action waving
+python scripts\openpet_cli.py say "Thinking..." --ttl-ms 4000
+python scripts\openpet_cli.py event success --message "Tests passed"
+python scripts\openpet_cli.py import-local public\pets\nia --dry-run --json
+python scripts\openpet_cli.py import-local <path-to-pet-folder>
+python scripts\openpet_cli.py import-website https://petdex.crafter.run/pets/boba
 ```
 
 ## Event Contract
@@ -52,7 +52,7 @@ python scripts\codex_pet_cli.py import-website https://petdex.crafter.run/pets/b
 - Do not load API details by default.
 - Read `references/http-api.md` only when debugging raw HTTP requests, adding routes, or explaining endpoint payloads.
 - Read `references/runtime-contract.md` only when changing import behavior, pet package validation, app-data storage, or runtime catalog assumptions.
-- Read `scripts/codex_pet_cli.py` only when modifying or debugging the CLI implementation.
+- Read `scripts/openpet_cli.py` only when modifying or debugging the CLI implementation.
 
 ## Runtime Boundaries
 
@@ -67,9 +67,9 @@ python scripts\codex_pet_cli.py import-website https://petdex.crafter.run/pets/b
 After changing this skill or CLI, run:
 
 ```powershell
-python scripts\codex_pet_cli.py --help
-python scripts\codex_pet_cli.py doctor --json
-python scripts\codex_pet_cli.py import-local ..\..\public\pets\nia --dry-run --json
+python scripts\openpet_cli.py --help
+python scripts\openpet_cli.py doctor --json
+python scripts\openpet_cli.py import-local ..\..\public\pets\nia --dry-run --json
 ```
 
 If Rust runtime contracts changed, also run:

…lls/codex-pet-cli/references/http-api.md skills/openpet-cli/references/http-api.mdskills/codex-pet-cli/references/http-api.md renamed to skills/openpet-cli/references/http-api.md skills/codex-pet-cli/references/http-api.md renamed to skills/openpet-cli/references/http-api.md

@@ -3,7 +3,7 @@
 Read this only when debugging raw HTTP behavior or changing runtime routes. For normal agent use, prefer:
 
 ```powershell
-python scripts\codex_pet_cli.py --help
+python scripts\openpet_cli.py --help
 ```
 
 ## Base URL

…x-pet-cli/references/runtime-contract.md …enpet-cli/references/runtime-contract.mdskills/codex-pet-cli/references/runtime-contract.md renamed to skills/openpet-cli/references/runtime-contract.md skills/codex-pet-cli/references/runtime-contract.md renamed to skills/openpet-cli/references/runtime-contract.md

@@ -797,7 +797,7 @@ def command_help(args: argparse.Namespace) -> int:
 
 def build_parser() -> argparse.ArgumentParser:
     parser = argparse.ArgumentParser(
-        prog="codex-pet-cli",
+        prog="openpet-cli",
         description="Control OpenPet and import Codex-compatible pet packages through the local runtime.",
     )
     parser.add_argument("--base-url", help="Runtime base URL, default derived from --port.")

…s/codex-pet-cli/scripts/codex_pet_cli.py skills/openpet-cli/scripts/openpet_cli.pyskills/codex-pet-cli/scripts/codex_pet_cli.py renamed to skills/openpet-cli/scripts/openpet_cli.py skills/codex-pet-cli/scripts/codex_pet_cli.py renamed to skills/openpet-cli/scripts/openpet_cli.py

@@ -1,5 +1,5 @@
 ---
-name: codex-pet-mcp
+name: openpet-mcp
 description: Use the OpenPet MCP bridge to inspect and control the local desktop pet, send status events, and import compatible pet sources through the running runtime.
 ---
 
@@ -29,7 +29,7 @@ For MCP clients that accept a stdio server command, point them at:
   "mcpServers": {
     "openpet": {
       "command": "python",
-      "args": ["skills/codex-pet-mcp/scripts/openpet_mcp_server.py"]
+      "args": ["skills/openpet-mcp/scripts/openpet_mcp_server.py"]
     }
   }
 }
@@ -43,7 +43,7 @@ If OpenPet is using a non-default HTTP endpoint, pass it explicitly:
     "openpet": {
       "command": "python",
       "args": [
-        "skills/codex-pet-mcp/scripts/openpet_mcp_server.py",
+        "skills/openpet-mcp/scripts/openpet_mcp_server.py",
         "--base-url",
         "http://127.0.0.1:17322"
       ]