npm - @hayasaka7/haya-pet - Versions diffs - 0.2.3 → 0.2.5 - Mend

@hayasaka7/haya-pet 0.2.3 → 0.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (15) hide show

package/CHANGELOG.md +8 -1
package/README.md +205 -205
package/apps/companion/README.md +2 -2
package/apps/companion/src/main/index.js +2 -2
package/apps/companion/src/main/tray-menu.js +9 -1
package/apps/companion/src/renderer/index.html +1 -1
package/apps/companion/test/tray-menu.test.mjs +9 -2
package/apps/pet-preview/index.html +2 -2
package/docs/architecture.md +1 -1
package/docs/known-issues.md +1 -1
package/docs/publishing.md +1 -1
package/native/win-window-helper/Program.cs +1 -1
package/package.json +1 -1
package/.github/workflows/ci.yml +0 -75
package/.github/workflows/release.yml +0 -61

package/CHANGELOG.md CHANGED Viewed

@@ -1,12 +1,19 @@
 # Changelog
-All notable changes to Haya Pet are documented here. This project adheres to
+All notable changes to HAYA Pet are documented here. This project adheres to
 [Semantic Versioning](https://semver.org/).
 > Note: some entries originally drafted under 0.2.0 actually landed *after* the
 > 0.2.0 npm publish; they are listed under 0.2.1, which is the first version that
 > ships them.
+## [0.2.4]
+### Fixed
+- Removed the non-functional **"Open Settings"** tray item (it had no handler).
+  A settings window is deferred until settings outgrow the tray; every current
+  setting already has a tray, CLI, or gesture home.
 ## [0.2.3]
 ### Added

package/README.md CHANGED Viewed

@@ -1,294 +1,294 @@
 <div align="center">
-# 🐾 Haya Pet
+# HAYA Pet
-### One desktop companion for all your AI terminal agents
+### Let your Codex Desktop pets follow you into every AI terminal
-A transparent, draggable desktop pet that reflects what your AI CLIs are doing —
-Codex, Claude Code, Antigravity, Aider, or any command — through one shared
-runtime with client adapters.
+HAYA Pet is a local desktop companion for Codex, Claude Code, Antigravity,
+Aider, Gemini CLI, and almost any command-line AI client. It was inspired by
+Codex Desktop pets, but fixes the part that hurts: pets generated for Codex
+Desktop should not be trapped inside Codex Desktop.
-<!-- HERO SCREENSHOT: drop a wide shot at docs/screenshots/hero.png
-     (the pet on the desktop with a couple of session bubbles) -->
+Drop in a Codex-compatible pet, wrap your AI CLI with `haya-pet run`, and the
+same little character can watch all your agent sessions from one always-on-top
+overlay.
-![Haya Pet on the desktop](docs/screenshots/hero.png)
+![HAYA Pet on the desktop](docs/screenshots/hero.png)
 </div>
 ---
-## What is this?
+## Why HAYA Pet Exists
-Most "desktop pet for an AI tool" projects build one pet per tool. Haya Pet does
-the opposite: it is **one AI Terminal Pet Runtime** that many AI clients plug
-into through adapters.
+Codex Desktop made AI pets feel personal. The problem is portability: once a pet
+is generated there, it is useful only there.
-You might be running several agents at once:
+HAYA Pet turns those pet assets into a shared runtime for the AI tools you
+actually use day to day:
 ```text
-Codex CLI       → backend repo
-Claude Code     → frontend repo
-Antigravity CLI → infra repo
-Aider           → docs repo
+Codex CLI       -> backend work
+Claude Code     -> frontend work
+Antigravity     -> infra work
+Aider / Gemini  -> docs, scripts, experiments
+Any command     -> still gets a session bubble
 ```
-Haya Pet watches all of them and presents one ambient interface:
-- **One global pet** — reflects the selected or most urgent AI session; clickable,
-  draggable, and position-persistent like a real desktop companion.
-- **Session bubbles** — one compact bubble per active session showing client,
-  project, the latest activity, and a status icon (a spinning *working* circle, a
-  green *done* check, a yellow *needs you*, or a red *failed* cross). Bubbles stack
-  by connect time — the newest session on top — so the stack never reshuffles while
-  work is in progress. A folder button beside the pet folds them away.
-## Features
-- 🪟 **Transparent, frameless, always-on-top overlay** that doesn't steal focus and
-  stays click-through outside the pet and bubbles.
-- 🖱️ **Click / double-click / drag** — click folds/unfolds the bubbles, double-click
-  expands them, drag moves the pet (position persists; bubbles stay on-screen).
-- 📏 **Resizable pet** — hover the pet and drag the corner grip to scale it
-  0.5×–2× for your screen; double-click the grip to reset. The size persists.
-- 🟢 **Live session bubbles** with per-session status icons and a folder toggle.
-- 🧠 **Normalized state model** — every client maps to a shared state vocabulary
-  (`thinking`, `running_tool`, `waiting_approval`, `reviewing`, `failed`, …).
-- 🧩 **Client adapters** with tiered support (process wrapper → PTY observer →
-  client hooks) so the daemon never bakes in client-specific logic. Default is
-  lifecycle status; richer status is opt-in (Claude Code / Codex hooks via
-  `haya-pet hooks on`, or PTY `--observe` for any client).
-- 🚀 **Zero-setup launch** — `haya-pet run …` auto-starts the overlay; no separate
-  daemon to manage.
-- 🖼️ **Codex-compatible pet assets** (1536×1872 sprite atlas, 9 actions).
-- 🔒 **Local-only & private** — no prompts, files, or screenshots leave your machine.
-- 🪟🍎🐧 **Cross-platform** core with per-OS adapters for IPC and windowing.
+Instead of one pet per app, you get **one pet for your whole AI workspace**. It
+reacts to the selected or most urgent session, while compact bubbles show what
+each running client is doing.
-## Screenshots
+## The Candy
-<!-- Drop each PNG into docs/screenshots/ with the filename shown (~800px wide).
-     Delete any row you don't have a shot for. -->
+- **Bring your Codex Desktop pets with you.** HAYA Pet scans `~/.codex/pets`, so
+  Codex-compatible pet folders can be reused without rebuilding the character.
+- **Use one pet across many AI clients.** Codex and Claude Code get richer
+  live-status hooks; everything else can connect through the generic wrapper.
+- **See all active agents at a glance.** Session bubbles show client, project,
+  latest activity, and status: working, done, needs attention, or failed.
+- **Keep your terminal native.** The default wrapper preserves normal terminal
+  input. No broken Shift+Tab just to make the pet move.
+- **Stay local.** HAYA Pet does not upload prompts, files, screenshots, or logs.
-| | |
-|---|---|
-| **The global pet** — reacting to the highest-priority session.<br>![Pet overlay](docs/screenshots/pet-overlay.png) | **Session bubbles** — one per active session, with status icons.<br>![Session bubbles](docs/screenshots/session-bubbles.png) |
-| **Folder collapsed** — bubbles tucked away beside the pet.<br>![Folder collapsed](docs/screenshots/folder-collapsed.png) | **Tray menu** — show/hide, pets, reset position, Quit.<br>![Tray menu](docs/screenshots/tray-menu.png) |
+## Quick Start
-## Documentation
+### 1. Install
-| Doc | What's in it |
-|---|---|
-| **This README** | Install + users' guide |
-| [docs/architecture.md](docs/architecture.md) | How it works, components, project structure, adapter tiers, platform matrix, native helpers, roadmap |
-| [docs/publishing.md](docs/publishing.md) | Releasing to npm (the tag → publish workflow) |
-| [docs/troubleshooting.md](docs/troubleshooting.md) | Common fixes, incl. repairing a broken Electron install |
-| [docs/known-issues.md](docs/known-issues.md) | Deferred issues with known root causes |
-| [docs/cross-os-qa.md](docs/cross-os-qa.md) | Cross-OS test matrix |
-| [apps/companion/README.md](apps/companion/README.md) | Companion (Electron) internals |
-| [PROGRESS.md](PROGRESS.md) | Detailed development log |
+From npm, when available:
----
+```bash
+npm install -g @hayasaka7/haya-pet
+```
-# Users' Guide
+From source:
-## Requirements
+```bash
+git clone <repo-url> haya-pet
+cd haya-pet
+npm install
+npm link
+```
-| Requirement | Why |
-|---|---|
-| **Node ≥ 18** | Runtime + companion (Electron) |
-| **npm** | Install + scripts |
+Prefer not to link globally? Use the CLI directly:
-> Default status is lifecycle-only and needs no extra modules. Opt-in Claude Code /
-> Codex hooks (`haya-pet hooks on`) also need none. The opt-in `--observe` PTY mode uses
-> `node-pty` (installed automatically when it can build; without it, `--observe`
-> degrades to lifecycle-only tracking).
+```bash
+node <repo>/apps/cli/src/haya-pet.js
+```
-## Install
+### 2. Add A Pet
-**From npm** *(once published — recommended for users):*
+Put a Codex-compatible pet folder in `~/.codex/pets` or `~/.haya-pet/pets`.
-```bash
-npm install -g @hayasaka7/haya-pet     # exposes the `haya-pet` command globally
+On Windows, HAYA Pet also checks `%USERPROFILE%\.codex\pets` and
+`%LOCALAPPDATA%\haya-pet\pets`.
+```text
+~/.codex/pets/my-pet/
+    pet.json
+    spritesheet.webp
 ```
-**From source** *(current):*
+Minimal `pet.json`:
+```json
+{
+  "id": "my-pet",
+  "name": "My Pet",
+  "spritesheet": "spritesheet.webp"
+}
+```
+The spritesheet format is the Codex-compatible atlas used by this project:
+1536 x 1872 pixels, 8 columns x 9 rows, 192 x 208 per frame.
+Choose the pet:
 ```bash
-git clone <repo-url> haya-pet
-cd haya-pet
-npm install
-npm link                  # makes `haya-pet` available everywhere
+haya-pet pets
+haya-pet pets use my-pet
 ```
-Prefer not to link globally? Call it directly anywhere you'd type `haya-pet`:
-`node <repo>/apps/cli/src/haya-pet.js`.
+You can also switch pets from the tray menu.
-## Run an AI session
+### 3. Run Your AI Client Through HAYA Pet
-Just wrap any command. **The first `haya-pet run` auto-starts the pet overlay** —
-there's nothing to launch first:
+The first `haya-pet run` starts the overlay automatically.
 ```bash
-haya-pet run --client codex        -- codex
-haya-pet run --client claude-code  -- claude
-haya-pet run --client generic      -- aider
-# Windows / PowerShell example:
-haya-pet run --client generic      -- powershell -Command "Start-Sleep 10"
+haya-pet run --client codex
+haya-pet run --client claude-code
+haya-pet run --client antigravity
+# Any other CLI:
+haya-pet run --client generic -- aider
+haya-pet run --client generic -- gemini
+haya-pet run --client generic -- your-ai-command --with --args
 ```
-A **session bubble** appears while the command runs (client · project · status),
-and the pet reflects the highest-priority session. On exit the bubble briefly
-shows success (a green check) or failure (a red cross), then fades.
+A bubble appears for the session. When the command exits, the bubble shows
+success or failure briefly, then fades.
+## What You Get On Screen
+| Surface | What it does |
+|---|---|
+| Global pet | Reacts to the highest-priority session and can be dragged anywhere. |
+| Session bubbles | One bubble per running AI session, ordered by connect time. |
+| Folder button | Folds the bubbles away when you want a cleaner desktop. |
+| Tray menu | Show/hide, display mode, installed pets, reset position, and quit. |
+| Resize grip | Hover the pet, drag the corner, and keep the size you like. |
+## Screenshots
+| | |
+|---|---|
+| **The global pet** - reacting to the highest-priority session.<br>![Pet overlay](docs/screenshots/pet-overlay.png) | **Session bubbles** - one per active session, with status icons.<br>![Session bubbles](docs/screenshots/session-bubbles.png) |
+| **Folder collapsed** - bubbles tucked away beside the pet.<br>![Folder collapsed](docs/screenshots/folder-collapsed.png) | **Tray menu** - show/hide, pets, reset position, quit.<br>![Tray menu](docs/screenshots/tray-menu.png) |
-> If the overlay can't be started (e.g. Electron is missing), your command still
-> runs normally and keeps its exit code — you just won't see the pet. Disable
-> auto-start with `HAYA_PET_NO_AUTOSTART=1`, or launch it yourself with `haya-pet start`.
+## Supported Clients
-### Live activity status
+HAYA Pet has two ideas of support:
-`haya-pet run` uses **native passthrough by default** — the CLI talks directly to
-your terminal, so every input mode (Shift+Tab, mouse wheel, word-edit) works
-exactly as it does without the wrapper. Out of the box, every client shows
-**lifecycle status** (a session bubble while it runs; success/failure from the
-real exit code, never from scraping "error" out of output).
+- **Connection support:** the client can be wrapped and shown as a session.
+- **Live-status support:** the pet can react to in-session states like thinking,
+  editing files, running tools, or waiting for approval.
-```bash
-haya-pet run --client claude-code -- claude   # full fidelity, lifecycle status
-haya-pet run --client codex       -- codex    # full fidelity, lifecycle status
-```
+| Client | Works today | Best mode |
+|---|---:|---|
+| Codex CLI | Yes | Wrapper + opt-in hooks, with transcript-based tool activity |
+| Claude Code | Yes | Wrapper + opt-in hooks |
+| Antigravity | Yes | Wrapper lifecycle |
+| Aider | Yes | Generic wrapper |
+| Gemini CLI | Yes | Generic wrapper |
+| Any other command | Yes | Generic wrapper, optional `--observe` |
-Two **opt-in** ways to get richer *in-session* status (thinking / running tools /
-editing files / waiting for approval):
+Default behavior is intentionally conservative: HAYA Pet shows lifecycle status
+without changing how the terminal behaves. Richer live status is opt-in.
+## Live Status
+For Codex and Claude Code, enable hooks once:
 ```bash
-# Claude Code AND Codex — live status via per-session hooks, NO terminal-fidelity
-# tradeoff. Enable once (persisted, global); the first run for each client shows a
-# one-time "review hooks" prompt you approve once.
 haya-pet hooks on
-haya-pet run --client claude-code -- claude
-haya-pet run --client codex       -- codex
-#   (per-run override without persisting: HAYA_PET_HOOKS=1 …, or $env:HAYA_PET_HOOKS=1 in PowerShell)
-#   (turn back off: haya-pet hooks off   ·   check: haya-pet hooks status)
-# Any client — coarse live status by watching output through a PTY.
-haya-pet run --observe --client codex -- codex
+haya-pet run --client codex
+haya-pet run --client claude-code
 ```
-> **Codex coverage.** Codex shows `thinking` (working) and `idle` (done) via hooks,
-> plus `running_tool` / `editing_files` via a session-transcript watcher.
-> *Waiting for approval* doesn't arrive yet because of an upstream gap where
-> Codex's `PermissionRequest` hook doesn't fire
-> ([openai/codex#16732](https://github.com/openai/codex/issues/16732)); it'll start
-> working automatically once Codex fixes it. Also: if you pass your own
-> `-p/--profile` to codex, haya-pet skips hook injection (Codex allows one
-> profile) and tells you. Claude Code has full coverage.
-> **Approval prompts resolve correctly** (Claude Code): deny → the pet returns to
-> idle the moment the denial lands in the session transcript; accept a command →
-> the pet flips to *working* a couple of seconds after the approved command
-> actually starts running (detected from the client's process tree — a real
-> event, never a timeout, so an unanswered prompt keeps warning until you decide).
-> **Why opt-in?**
-> - **Hooks (Claude Code / Codex):** injecting hooks makes the client show a
->   one-time *review hooks* trust prompt. We don't disrupt your session by default;
->   turn it on once with `haya-pet hooks on` when you're happy to approve the hooks.
-> - **`--observe` (any client):** PTY observation infers status from output, but on
->   Windows it routes input through ConPTY, which can break **Shift+Tab**, mouse
->   scroll, and word-edit. Use it only for non-interactive runs. See
->   [docs/known-issues.md](docs/known-issues.md).
-## Add and choose a pet
-A pet is a folder with `pet.json` and a 1536×1872 sprite atlas (8×9 cells of
-192×208). Drop it into a search path:
+Check or disable the setting:
-```text
-~/.codex/pets/my-pet/                     (Windows: %USERPROFILE%\.codex\pets\my-pet\)
-    pet.json          { "id": "my-pet", "name": "My Pet", "spritesheet": "spritesheet.webp" }
-    spritesheet.webp
+```bash
+haya-pet hooks status
+haya-pet hooks off
 ```
-Pets are discovered from `~/.codex/pets` and `~/.haya-pet/pets`. Then choose one:
+Why opt in? Both clients show a one-time trust prompt when hooks are added. HAYA
+Pet lets you decide when to approve that instead of surprising you in the middle
+of work.
+Codex support is useful but still partial. Hooks report `thinking` and `idle`,
+while a transcript watcher reports tool/file activity. Waiting-for-approval
+support depends on an upstream Codex hook gap:
+[openai/codex#16732](https://github.com/openai/codex/issues/16732).
+For any client, you can ask HAYA Pet to infer rough activity from terminal
+output:
 ```bash
-haya-pet pets               # list installed pets (* = selected)
-haya-pet pets use my-pet    # select; remembered on every launch
+haya-pet run --observe --client generic -- aider
 ```
-Your choice is stored and reused every time. You can also pick from the tray menu
-→ **Installed Pets**. Without a spritesheet, the pet renders labelled placeholder
-frames so everything still works.
+Use `--observe` only when you accept the PTY tradeoff. On Windows, ConPTY can
+break special input such as Shift+Tab, mouse scroll, and word-edit. The default
+non-observe mode keeps terminal input native.
-## Interact with the pet
+## Pet Controls
 | Action | Result |
 |---|---|
-| Single click | waves + folds/unfolds the session bubbles |
-| Double click | jumps + expands the bubbles |
-| Drag | moves the pet; position is saved (bubbles follow, always on-screen) |
-| Drag corner grip | resizes the pet 0.5×–2× (grip appears on hover); size is saved |
-| Double-click grip | resets the pet to its normal size |
-| Tray icon → menu | show/hide, display mode, sessions, pets, **reset position**, **Quit** |
+| Single click | Wave and fold or unfold session bubbles. |
+| Double click | Jump and expand session bubbles. |
+| Drag | Move the pet; position is saved. |
+| Drag corner grip | Resize from 0.5x to 2x; size is saved. |
+| Double-click grip | Reset to normal size. |
+| Tray icon | Open menu for display, sessions, pets, reset, and quit. |
-## Stop / exit the pet
+## Commands
 ```bash
-haya-pet stop      # ask the running overlay to quit
-```
+haya-pet run --client codex              # launch Codex with a pet session
+haya-pet run --client claude-code        # launch Claude Code with a pet session
+haya-pet run --client generic -- aider   # wrap any other command
-…or **right-click the tray icon → Quit**. `haya-pet stop` is a no-op if nothing is
-running, so it's always safe to call.
+haya-pet pets                            # list installed pets
+haya-pet pets use my-pet                 # select a pet
-## Manage the overlay
+haya-pet hooks on                        # enable live-status hooks where supported
+haya-pet hooks status
+haya-pet hooks off
-```bash
-haya-pet start     # start the overlay explicitly (usually unnecessary — run auto-starts it)
-haya-pet stop      # quit it
+haya-pet start                           # start the overlay explicitly
+haya-pet stop                            # stop the overlay
 ```
-## Troubleshooting
+If the overlay cannot start, the wrapped command still runs and keeps its real
+exit code. Disable auto-start with `HAYA_PET_NO_AUTOSTART=1`.
-Common fixes:
+## Requirements
-| Symptom | Fix |
+| Requirement | Why |
 |---|---|
-| `haya-pet: command not found` | Install globally, or `npm link` in a source checkout. |
-| Pet doesn't react to a session | Launch via `haya-pet run …`; check `HAYA_PET_NO_AUTOSTART` isn't set. |
-| Pet shows a blue placeholder box | No spritesheet — add a pet (above). |
-| Pet is off-screen | Tray menu → **Reset Position**. |
-| Can't exit | `haya-pet stop` or tray → **Quit**. |
+| Node 18 or newer | Runtime and Electron companion. |
+| npm | Install, link, and test scripts. |
+| Electron | Installed as a runtime dependency. |
+| node-pty | Optional; used only for `--observe`. |
-Full list (incl. repairing a broken Electron install): [docs/troubleshooting.md](docs/troubleshooting.md).
+## Troubleshooting
----
+| Symptom | Fix |
+|---|---|
+| `haya-pet: command not found` | Install globally, or run `npm link` from this repo. |
+| No pet appears for a session | Start the AI client through `haya-pet run ...`. |
+| Pet shows a placeholder | Add a pet folder with both `pet.json` and `spritesheet.webp`. |
+| Pet is off-screen | Use tray menu -> **Reset Position**. |
+| Overlay will not exit | Run `haya-pet stop` or tray menu -> **Quit**. |
-## Supported clients
+More fixes are in [docs/troubleshooting.md](docs/troubleshooting.md), including
+repairing a broken Electron install.
-| Client | Status | Support level |
-|---|---|---|
-| Generic CLI | ✅ | L1 process wrapper (+ L2 PTY via `--observe`) |
-| Codex | ✅ | L1 wrapper + **L4 live-status hooks** (opt-in `haya-pet hooks on`; partial — see note) |
-| Claude Code | ✅ | L1 wrapper + **L4 live-status hooks** (opt-in `haya-pet hooks on`) |
-| Antigravity | ✅ | L1 wrapper (+ L2 PTY via `--observe`) |
-| Gemini CLI / Aider / others | 🔜 | via the generic adapter |
+## Privacy
-(See [docs/architecture.md](docs/architecture.md) for the support tiers and the
-platform matrix, and [CHANGELOG.md](CHANGELOG.md) for release notes.)
+HAYA Pet is local-only by default. It does not upload prompts, files,
+screenshots, or session logs. The overlay stores only local state needed for
+pet selection, position, size, and short derived status summaries.
-## Privacy
+## Documentation
+| Doc | What it covers |
+|---|---|
+| [docs/architecture.md](docs/architecture.md) | Runtime design, adapter tiers, platform matrix, roadmap. |
+| [docs/publishing.md](docs/publishing.md) | Release and npm publishing flow. |
+| [docs/troubleshooting.md](docs/troubleshooting.md) | Common failures and repair steps. |
+| [docs/known-issues.md](docs/known-issues.md) | Current limitations and upstream gaps. |
+| [docs/cross-os-qa.md](docs/cross-os-qa.md) | Cross-OS QA checklist. |
+| [apps/companion/README.md](apps/companion/README.md) | Electron companion internals. |
+| [assets/fallback-pet/README.md](assets/fallback-pet/README.md) | Bundled fallback pet details. |
+| [PROGRESS.md](PROGRESS.md) | Development log. |
-Haya Pet is local-only by default. It does **not** upload prompts, files,
-screenshots, or session logs; it stores only short derived status summaries.
-Approvals always require explicit user action.
+## Contributing
-## Contributing & tests
+Run the full test suite:
 ```bash
-npm test     # runs the full suite (TDD; tests live in **/test/*.test.mjs)
+npm test
 ```
-See [docs/architecture.md](docs/architecture.md) to find your way around the code.
+The codebase is organized as one npm package with internal packages under
+`packages/` and apps under `apps/`. Start with
+[docs/architecture.md](docs/architecture.md) if you want to add a client adapter,
+touch the overlay, or work on pet rendering.
 ## License
-See [`LICENSE`](LICENSE).
+MIT. See [LICENSE](LICENSE).

package/apps/companion/README.md CHANGED Viewed

@@ -1,11 +1,11 @@
-# Haya Pet Companion (Electron overlay)
+# HAYA Pet Companion (Electron overlay)
 The desktop overlay app for the AI CLI pet runtime. It hosts the daemon IPC
 server, renders the global pet, and shows the session bubbles. (A reply/approval
 "task talk window" is scaffolded but parked — see below.)
 > Most users never launch this directly: `haya-pet run` auto-starts it. This doc
-> covers its internals. For installing/using Haya Pet, see the
+> covers its internals. For installing/using HAYA Pet, see the
 > [root README](../../README.md) and [docs/architecture.md](../../docs/architecture.md).
 ## Architecture

package/apps/companion/src/main/index.js CHANGED Viewed

@@ -15,7 +15,7 @@ import { clampScale } from "../../../../packages/pet-core/src/pet-scale.js";
 import { buildPetWindowOptions, PET_SIZE } from "./window-options.js";
 import { resolveSavedPosition } from "./display-manager.js";
 import { getPetScale, setPetScale, setSelectedPet, updateGlobalPetPosition } from "./position-store.js";
-import { buildTrayMenu } from "./tray-menu.js";
+import { buildTrayMenu, buildTrayTooltip } from "./tray-menu.js";
 import { createStateFile } from "./state-file.js";
 import { discoverPets } from "./pet-loader.js";
@@ -188,7 +188,7 @@ function clampPetLocal(local) {
 function createTray() {
   try {
     tray = new Tray(loadTrayIcon());
-    tray.setToolTip("Haya Pet — right-click to Quit");
+    tray.setToolTip(buildTrayTooltip());
   } catch (error) {
     // A failed tray must not take the whole app down; log and continue.
     console.error("tray unavailable:", error.message);

package/apps/companion/src/main/tray-menu.js CHANGED Viewed

@@ -9,6 +9,10 @@ const DISPLAY_MODES = Object.freeze([
   { value: "hybrid", label: "Hybrid" }
 ]);
+export function buildTrayTooltip() {
+  return "HAYA Pet";
+}
 export function buildTrayMenu(state = {}) {
   const sessions = Array.isArray(state.sessions) ? state.sessions : [];
   const pets = Array.isArray(state.pets) ? state.pets : [];
@@ -46,7 +50,11 @@ export function buildTrayMenu(state = {}) {
       checked: Boolean(state.attachBubblesToTerminals)
     },
     { id: "reset_position", label: "Reset Position" },
-    { id: "settings", label: "Open Settings" },
+    // Parked until a real settings window exists: every current setting already
+    // has a home (tray toggles, `haya-pet hooks`, drag/grip gestures), so the
+    // item would be a dead button. Re-enable once settings outgrow the tray
+    // (e.g. bubble text size, linger duration) and a handler is wired up.
+    // { id: "settings", label: "Open Settings" },
     { id: "separator", type: "separator" },
     { id: "quit", label: "Quit" }
   ];

package/apps/companion/src/renderer/index.html CHANGED Viewed

@@ -3,7 +3,7 @@
   <head>
     <meta charset="UTF-8" />
     <meta http-equiv="Content-Security-Policy" content="default-src 'self' file:; img-src 'self' file: data:; style-src 'self' 'unsafe-inline';" />
-    <title>Haya Pet</title>
+    <title>HAYA Pet</title>
     <link rel="stylesheet" href="styles.css" />
   </head>
   <body>

package/apps/companion/test/tray-menu.test.mjs CHANGED Viewed

@@ -1,6 +1,6 @@
 import assert from "node:assert/strict";
 import { test } from "../../../test/harness.mjs";
-import { buildTrayMenu } from "../src/main/tray-menu.js";
+import { buildTrayMenu, buildTrayTooltip } from "../src/main/tray-menu.js";
 const baseState = {
   petVisible: true,
@@ -13,9 +13,12 @@ const baseState = {
 test("includes the documented recovery controls", () => {
   const menu = buildTrayMenu(baseState);
   const ids = menu.map((item) => item.id);
-  for (const id of ["toggle_pet", "display_mode", "sessions", "pets", "attach_bubbles", "reset_position", "settings", "quit"]) {
+  for (const id of ["toggle_pet", "display_mode", "sessions", "pets", "attach_bubbles", "reset_position", "quit"]) {
     assert.ok(ids.includes(id), `missing ${id}`);
   }
+  // "Open Settings" is parked until a settings window exists (every current
+  // setting already has a tray/CLI/gesture home) — it must not be shown dead.
+  assert.ok(!ids.includes("settings"), "settings item should stay hidden until implemented");
 });
 test("toggles the pet label based on visibility", () => {
@@ -43,3 +46,7 @@ test("reflects the attach-bubbles checkbox state", () => {
   assert.equal(buildTrayMenu(baseState).find((i) => i.id === "attach_bubbles").checked, true);
   assert.equal(buildTrayMenu({ ...baseState, attachBubblesToTerminals: false }).find((i) => i.id === "attach_bubbles").checked, false);
 });
+test("uses the HAYA Pet brand in the tray hover text", () => {
+  assert.equal(buildTrayTooltip(), "HAYA Pet");
+});

package/apps/pet-preview/index.html CHANGED Viewed

@@ -3,13 +3,13 @@
   <head>
     <meta charset="utf-8">
     <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Haya Pet Preview</title>
+    <title>HAYA Pet Preview</title>
     <link rel="stylesheet" href="./src/preview.css">
   </head>
   <body>
     <main class="app-shell">
       <section class="toolbar" aria-label="Preview controls">
-        <h1 class="brand">Haya Pet Preview</h1>
+        <h1 class="brand">HAYA Pet Preview</h1>
         <label class="file-input">
           <span>Spritesheet</span>
           <input id="spritesheet-file" type="file" accept="image/png,image/webp">

package/docs/architecture.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Architecture
-How Haya Pet is put together. For installing and using it, see the
+How HAYA Pet is put together. For installing and using it, see the
 [README](../README.md); this doc is for contributors and the curious.
 ## Pipeline

package/docs/known-issues.md CHANGED Viewed

@@ -175,7 +175,7 @@ observation (`--observe`) or L1 lifecycle as the fallback. Current state:
     [openai/codex#16732](https://github.com/openai/codex/issues/16732)). Tool
     activity is covered by an L3 Codex transcript watcher that tails
     `~/.codex/sessions` JSONL: normal tools report `running_tool`, `apply_patch`
-    reports `editing_files`, and Haya Pet returns to `thinking` after active tool
+    reports `editing_files`, and HAYA Pet returns to `thinking` after active tool
     calls drain. `PermissionRequest` (the *waiting for approval* cue — the
     highest-value state) is **unconfirmed**; it likely depends on an
     approval-required flow and needs a dedicated test before the feature is worth

package/docs/publishing.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # Publishing
-How Haya Pet is released to npm. Most users never need this — see the
+How HAYA Pet is released to npm. Most users never need this — see the
 [README](../README.md) to install and use it.
 ## Release flow

package/native/win-window-helper/Program.cs CHANGED Viewed

@@ -1,4 +1,4 @@
-// Haya Pet — Windows window helper.
+// HAYA Pet - Windows window helper.
 //
 // Implements the line-delimited JSON helper protocol documented in
 // ../README.md. Reads one JSON request per line on stdin and writes one JSON

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@hayasaka7/haya-pet",
-  "version": "0.2.3",
+  "version": "0.2.5",
   "type": "module",
   "description": "Generic AI CLI pet runtime foundation.",
   "license": "MIT",

package/.github/workflows/ci.yml DELETED Viewed

@@ -1,75 +0,0 @@
-name: CI
-# Run code quality checks and the test suite on every push that touches code.
-on:
-  push:
-    paths:
-      - "**/*.js"
-      - "**/*.mjs"
-      - "**/*.cjs"
-      - "package.json"
-      - "package-lock.json"
-      - ".github/workflows/ci.yml"
-  pull_request:
-    paths:
-      - "**/*.js"
-      - "**/*.mjs"
-      - "**/*.cjs"
-      - "package.json"
-      - "package-lock.json"
-      - ".github/workflows/ci.yml"
-concurrency:
-  group: ci-${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
-permissions:
-  contents: read
-jobs:
-  lint:
-    name: Code quality (ESLint)
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: npm
-      - name: Install dependencies
-        # Electron's binary isn't needed for linting or tests; skip the ~150 MB
-        # download so CI is fast and isn't at the mercy of the Electron CDN.
-        env:
-          ELECTRON_SKIP_BINARY_DOWNLOAD: "1"
-        run: npm ci
-      - name: Run ESLint
-        run: npm run lint
-  test:
-    name: Tests (Node ${{ matrix.node }} on ${{ matrix.os }})
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        os: [ubuntu-latest, windows-latest, macos-latest]
-        node: [20, 22]
-    steps:
-      - uses: actions/checkout@v4
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: ${{ matrix.node }}
-          cache: npm
-      - name: Install dependencies
-        env:
-          ELECTRON_SKIP_BINARY_DOWNLOAD: "1"
-        run: npm ci
-      - name: Run the test suite
-        run: npm test

package/.github/workflows/release.yml DELETED Viewed

@@ -1,61 +0,0 @@
-name: Release
-# Publish to npm when a version tag is pushed, e.g.:
-#   npm version patch            # bumps package.json + creates a vX.Y.Z tag
-#   git push --follow-tags
-# or manually:
-#   git tag v0.1.1 && git push origin v0.1.1
-on:
-  push:
-    tags:
-      - "v*"
-permissions:
-  contents: read
-  id-token: write # required for npm provenance (--provenance)
-concurrency:
-  group: release-${{ github.ref }}
-  cancel-in-progress: false
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Check out the tagged commit
-        uses: actions/checkout@v4
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          registry-url: "https://registry.npmjs.org"
-      - name: Install dependencies
-        # Electron's binary isn't needed to test or publish; skip the ~150 MB
-        # download so CI is fast and isn't at the mercy of the Electron CDN.
-        env:
-          ELECTRON_SKIP_BINARY_DOWNLOAD: "1"
-        run: npm ci
-      - name: Run the test suite
-        run: npm test
-      - name: Verify the tag matches package.json version
-        run: |
-          TAG="${GITHUB_REF_NAME#v}"
-          PKG="$(node -p "require('./package.json').version")"
-          echo "tag=$TAG package.json=$PKG"
-          if [ "$TAG" != "$PKG" ]; then
-            echo "::error::Tag v$TAG does not match package.json version $PKG"
-            exit 1
-          fi
-      - name: Publish to npm
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        # --access public is needed for the first publish of a scoped package and
-        # harmless otherwise. --provenance attaches a signed build attestation
-        # (requires a public repo + the id-token permission above; drop it if the
-        # repo is private).
-        run: npm publish --provenance --access public