fpasoterm 1.6.0

package/CHANGELOG.md

@@ -0,0 +1,230 @@
+# Changelog
+
+## 1.5.7
+
+- Added sync-folder status, cleanup, and Markdown diagnostics commands: `--sync-status`, `--sync-clean`, and `--sync-diagnostics`.
+- Added CLI Broadcast: `--broadcast <text>`, repeatable/comma-separated `--broadcast-target <pid|title>`, and guarded `--broadcast-sync` delivery through a trusted sync folder.
+- Added Rust build caching to pull-request and release GitHub Actions jobs while retaining the existing full checks and artifact builds.
+
+## 1.5.6
+
+- Added configuration inspection commands: `--config-check`, `--config-path`, and `--config-example`.
+- Added Markdown diagnostics commands: `--diagnostics`, `--copy-diagnostics`, and `--open-log-dir`.
+- Added named TOML profiles with `--profile` / `--profile-list`, including a documented profile example and early CLI validation before background launch.
+- Added PR and release quality checks for syntax, smoke tests, Cargo formatting, dependency/security scanning, and CodeQL.
+
+## 1.5.4
+
+- Kept first-run local Cargo builds attached to the CLI and displayed preparation, compiler progress, build completion, and native window startup phases before returning the prompt.
+- Appended detached Cargo build output and failure exit details to the persistent launcher log for diagnosis when a window cannot start.
+- Documented the distinct cleanup scopes of `npm uninstall -g fpasoterm` and `npm run uninstall:desktop`, including the Windows `Path`-only source-uninstaller behavior.
+
+## 1.5.3
+
+- Detached normal CLI launches before a possible local Cargo build so the invoking terminal prompt returns immediately on macOS, Linux, and Windows.
+- Added CLI startup status for cached-runtime reuse or local Cargo builds, plus elapsed launcher phases in the persistent launcher log.
+
+## 1.5.2
+
+- Fixed macOS Apple Silicon terminal cell metrics by prioritizing the native `SF Mono` and `Menlo` monospace fonts before proportional Hiragino fallbacks.
+- Migrated only the previous shipped macOS font default in memory, preserving user-selected custom font families.
+
+## 1.5.1
+
+- Restricted the npm source package to tracked Tauri source and configuration files, excluding generated build outputs.
+- Added npm ignore rules so local build, cache, diagnostic, and session files cannot be published.
+
+## 1.5.0
+
+- Added Kitty graphics protocol rendering through the xterm.js image addon, with bounded image size and storage settings under `[terminal.images]`.
+- Added `Broadcast (^B)` / `Ctrl+Shift+B` to select local windows by title/PID and send a command only to those terminals.
+- Added an explicit, short-lived trusted sync-folder broadcast channel for already-running remote fpasoterm instances sharing the same sync path and channel.
+- Added the titlebar title to automatic terminal output log filenames so logs from multiple windows are distinguishable.
+- Forwarded the terminal pixel dimensions to the PTY for Kitty-aware applications and kept `Ctrl+C` available as an interrupt fallback if a graphics layer displaces terminal focus.
+- Limited experimental Kitty graphics to the official xterm.js image addon's direct-transfer (`t=d`) support; local-file and animation extensions remain unsupported.
+- Disabled the experimental image addon by default after WebKitGTK image streams could block terminal input, and made `--dev` use a static-asset debug binary instead of a localhost development server.
+- Fixed terminal paste handling so xterm's hidden IME textarea is treated as terminal focus and `Ctrl+Shift+V` reads the host clipboard.
+
+## 1.4.7
+
+- Restored the macOS CLI wrapper at `~/.local/bin/fpasoterm`, kept the config-directory shim for compatibility, and placed the conventional user bin directory first in child-shell `PATH`.
+- Limited automatic help output to argument-validation errors; runtime failures such as a missing `--close` target now print only the actionable error.
+
+## 1.4.6
+
+- Audited every packaged-binary long and short CLI option, rejected Node-launcher-only `--dev` / `-d`, unknown options, and missing values before GUI startup, and explicitly flushed non-Windows CLI output.
+- Added the running binary version to the in-app `Help (^H)` keyboard-shortcut panel.
+- Changed CLI and Close All requests to exit each application process, so macOS does not leave fpasoterm active in the menu bar after `fpasoterm -q all`.
+
+## 1.4.5
+
+- Added a regenerated macOS user CLI shim that forwards all arguments to the current app-bundle executable, preventing stale or argument-dropping launch paths inside fpasoterm terminals.
+- Changed direct packaged binaries to reject Node-launcher-only options with help instead of silently opening a GUI window.
+
+## 1.4.4
+
+- Excluded stale instance markers with a cross-platform heartbeat so Tile counts and title suffixes reflect running windows on Windows and macOS.
+- Stabilized Tile grids, including 2x1 for two windows, 3x3 for nine windows, and 5x2 for ten windows.
+- Added the macOS application executable directory to child-shell `PATH` and detached nested GUI launches so `fpasoterm` opens another window without blocking the prompt.
+- Allocated `-2`, `-3`, and later title suffixes after the highest live suffix instead of using an ambiguous marker count.
+- Added the reserved `all` target to `fpasoterm --close` / `-q` for closing every running window from the CLI.
+- Added `fpasoterm --reset-config` / `-R` to rename the selected config as a timestamped backup, restore every platform default, and clear saved bounds so the default 1000x680 size takes effect.
+
+## 1.4.3
+
+- Reduced the default terminal font size on Intel macOS from 13px to 12px when no explicit `terminal.fontSize` is configured.
+- Consolidated logging, copy, and paste actions into the hamburger menu, with explicit `Log Start`, `Log Stop`, and `Log Show` labels.
+- Added `Ctrl+Shift+M` for the window menu and a `Help (^H)` action with `Ctrl+Shift+H` for displaying keyboard shortcuts.
+- Restored a visible `Logging` status while terminal output capture is active, left-aligned the title to avoid control overlap, and added `fpasoterm -l` / `--list` for running-window details.
+- Added `fpasoterm --close <pid|title>` / `-q` to gracefully close running windows by process ID or exact displayed title.
+
+## 1.4.2
+
+- Rejected unknown or invalid CLI arguments with an error, full help text, and exit code 2 instead of opening the application.
+- Made Windows Log Delete All continue when a sync client or another process locks a log file, falling back to emptying files that cannot be removed.
+- Added Tab, Shift+Tab, arrow, and Escape navigation with visible focus states to the titlebar menus.
+- Replaced the unreliable Windows Close All WebView with a native confirmation dialog supporting keyboard controls and the standard close button.
+- Reduced the default terminal font size on Intel macOS to 13px while preserving explicit user settings and other platform defaults.
+
+## 1.4.1
+
+- Added a Window menu `New (^N)` action and `Ctrl+Shift+N` / `Cmd+Shift+N` shortcut for opening another fpasoterm window.
+- Fixed Windows Tile target detection by checking live instance PIDs with the Windows process API instead of treating stale markers as active.
+- Made the Close All confirmation window explicit, decorated, non-transparent, visible, resizable, and larger so Windows users can cancel, confirm, or close it normally.
+
+## 1.4.0
+
+- Improved Tile sizing by converting renderer logical screen dimensions to native physical pixels with the display device pixel ratio.
+- Added an independent confirmation window for Close All, with keyboard focus, Tab navigation, Cancel, OK, and Escape handling.
+- Prevented stale Close All requests from affecting newly started windows and restored terminal focus after cancellation.
+- Added optional `--x11` support for Linux window placement diagnostics.
+
+## 1.3.6
+
+- Improved Log menu keyboard labels and shortcuts for logging, copy, and paste operations.
+- Added keyboard-accessible Log Show search with match counts, next/previous navigation, visible focus states, and panel-contained focus cycling.
+- Replaced native delete confirmations with an in-panel confirmation dialog so Delete Selected and Delete All keep focus inside the log panel.
+
+## 1.3.5
+
+- Preserved half-width katakana in terminal display and readable terminal logs instead of normalizing it to full-width katakana.
+- Added terminal selection copy support for `Ctrl+Shift+C`, right-click copy when text is selected, and host WebView clipboard integration for paste into other applications.
+- Removed the Log Show copy button and made Log Show textarea selections copy with `Ctrl+Shift+C`.
+- Added keyboard-accessible Log menu Copy/Paste buttons and arrow-key menu navigation.
+
+## 1.3.4
+
+- Fixed Windows clipboard handling for Japanese paths copied from `Log Show` by writing native UTF-16 `CF_UNICODETEXT` clipboard data directly.
+
+## 1.3.3
+
+- Removed the retired `Sync:` titlebar status UI entirely while keeping silent sync diagnostics snapshots.
+- Fixed Windows clipboard copy/paste of Japanese paths from `Log Show` by routing PowerShell clipboard fallback through UTF-8 temporary files.
+
+## 1.3.2
+
+- Removed the retired `Synced` titlebar/status wording from sync diagnostics and setup prompts.
+- Added `--version` and `-v` to both the Node launcher and packaged app binary.
+- Documented Windows overwrite-update checks for verifying the installed executable version.
+
+## 1.3.0
+
+- Added folder-based sync for explicit clipboard text and diagnostics using local sync folders such as Google Drive for desktop.
+- Added terminal output logging with `Log Start` / `Log Stop` and OSC 777 controls.
+- Added interactive `--setup-sync` configuration for first-time sync folder setup.
+- Removed the temporary web console feature and related `--web-console` options.
+
+## 1.2.2
+
+- Allowed multiple fpasoterm windows on ChromeOS/Linux by disabling GTK application-id activation.
+- Made Windows prefer PowerShell 7 (`pwsh.exe`) as the default shell when available.
+- Added the fpasoterm executable directory to Windows child terminal `Path` so `fpasoterm` commands work inside the opened terminal.
+
+## 1.2.1
+
+- Fixed Windows direct binary CLI handling for `--help`, `--show-config`, window overrides, and shell selection.
+- Added PowerShell 7 path fallback and shell value sanitization for `--shell pwsh.exe`.
+- Added pull request review documentation for the no-artifact review path.
+
+## 1.2.0
+
+- Added runtime config application from inside a running terminal via OSC 777.
+- Added visible runtime appearance examples and a default-appearance reset script.
+- Added `terminal.termName = "xterm-256color"` and exported `TERM=xterm-256color` for tmux and other terminal multiplexers.
+- Improved runtime terminal resizing after appearance and window setting changes.
+- Improved ChromeOS launcher wrapper installation, update, and uninstall behavior.
+
+## 1.1.0
+
+- Added configurable custom titlebar titles and colors via config and one-shot CLI options.
+- Added short CLI aliases for common launch options.
+- Added custom titlebar minimize and maximize/restore controls.
+- Documented titlebar options in English and Japanese.
+
+## 1.0.5
+
+- Fixed direct packaged app argument parsing so `fpasoterm.exe --shell pwsh.exe` selects the requested shell.
+- Added direct app support for `--shell=value`, `--config <path>`, and `--config=<path>`.
+
+## 1.0.4
+
+- Fixed Windows launch behavior so normal GUI launches do not open an extra console window.
+- Closed the application when the shell process exits, including `exit` from Windows shells.
+- Added `terminal.shell` and `--shell <command>` for selecting shells such as bash, fish, PowerShell, or cmd.
+- Avoided launching stale local Tauri target binaries after source changes.
+
+## 1.0.3
+
+- Fixed window size restore when launching the macOS `.app` bundle directly.
+
+## 1.0.2
+
+- Added ad-hoc macOS app signing and Release workflow verification for macOS `.app` and `.dmg` artifacts.
+- Documented that full Gatekeeper-friendly macOS distribution still requires Developer ID signing and notarization.
+
+## 1.0.1
+
+- Included macOS Tauri rendering and resizing fixes in the release version.
+
+## 1.0.0
+
+- Added a tag-driven GitHub Release workflow that builds `artifacts/` in GitHub Actions and attaches the generated files to the release.
+- Expanded release artifact generation to Linux x64, Linux arm64, macOS x64, macOS arm64, and Windows x64.
+- Bumped the package version to `1.0.0` so release tag `v1.0.0` and generated artifact names match.
+
+## 0.0.6
+
+- Replaced the desktop runtime with Tauri and moved the PTY bridge to Rust using portable-pty.
+- Kept the existing xterm.js terminal renderer, TOML config loader, plugin support, and CLI configuration commands.
+- Added Linux/WebKitGTK transparency preparation and `--disable-dmabuf` diagnostics for ChromeOS/Baguette rendering issues.
+- Removed runtime-specific launch options and old preload/main process files.
+
+## 0.0.5
+
+- Added documented known issues for ChromeOS/Baguette window placement and transparent terminal limitations.
+- Removed unsupported window position CLI overrides after ChromeOS/Baguette testing showed the compositor keeps desktop runtime windows centered.
+- Kept window size persistence while avoiding aggressive position reapplication that could freeze the OS during resize.
+- Removed temporary transparency diagnostic CLI options and related runtime code.
+
+## 0.0.4
+
+- macOS Dock and bundle icons now use the generated project assets.
+- Windows window icons now use the generated `.ico` asset.
+
+## 0.0.3
+
+- Initial fpasoterm release.
+- Added xterm.js based terminal with a shell-backed PTY.
+- Added Linux startup wrapper for the desktop runtime.
+- Added npm binary `fpasoterm`.
+- Added GitHub Actions checks and release artifact generation.
+- Added application window icon wiring and close-on-shell-exit behavior.
+- Added hicolor launcher icon generation and local desktop entry installation.
+- Local desktop installation now also installs a `fpasoterm` command into the user's local bin directory.
+- Added local desktop update and uninstall scripts for clean command, launcher, and icon management.
+- Added `~/.config/fpasoterm/User/config.toml` support, JavaScript/TypeScript user plugins, and configurable IME duplicate-input guard timing.
+- Added detached-by-default command launching plus `--help`, `--foreground`, `--config`, and window-size CLI overrides.
+- Added `--show-config`, `--enable-plugin`, and `--disable-plugin` for configuration inspection and plugin management.
+- Plugin enable/disable commands now accept file names, comma-separated lists, and repeated options.
+- Added example TOML configs under `examples/config/`.
+- Added full default configuration documentation and TypeScript plugin samples.

package/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing
+
+Thank you for improving fpasoterm.
+
+## Development
+
+Install Node.js 22+, Rust stable, and the native build prerequisites for the
+target operating system before running the commands below.
+
+- Linux: `libgtk-3-dev`, `libwebkit2gtk-4.1-dev`,
+  `libayatana-appindicator3-dev`, and `librsvg2-dev`.
+- macOS: Xcode Command Line Tools (`xcode-select --install`).
+- Windows: Visual Studio Build Tools with **Desktop development with C++** and
+  the Microsoft Edge WebView2 Runtime.
+
+```sh
+npm ci
+npm run check
+node ./bin/fpasoterm --dev
+```
+
+On Windows PowerShell, use the same launcher command with backslashes:
+
+```powershell
+node .\bin\fpasoterm --dev
+```
+
+Normal launcher invocations return the prompt immediately and print whether a
+cached runtime is used or Cargo is building one. Use
+`--foreground --console-diagnostics` only when waiting for compiler and
+desktop-process output is intentional.
+
+For IME, rendering, clipboard, and window issues, follow the forced rebuild,
+event-trace, and safe-reporting workflow in [docs/debugging.en.md](docs/debugging.en.md).
+Japanese contribution guidance is available in [CONTRIBUTING.ja.md](CONTRIBUTING.ja.md).
+
+## Pull Request Review
+
+Do not review a tagged release asset when the requested change is in a pull
+request. Check out the pull request revision, build it on the target OS, and
+launch it through the Node launcher:
+
+```sh
+gh pr checkout <number> --repo oyoguhito/fpasoterm
+npm ci
+npm run check
+node ./bin/fpasoterm
+```
+
+Detailed Windows MSI/direct-binary and macOS app-bundle procedures are in
+[docs/pr-review.en.md](docs/pr-review.en.md). Japanese review instructions are
+available in [docs/pr-review.ja.md](docs/pr-review.ja.md).
+
+Before submitting changes, run:
+
+```sh
+npm run check
+npm run scan:secrets
+desktop-file-validate extra/linux/io.github.oyoguhito.fpasoterm.desktop
+npm run build:artifacts
+```
+
+## Scope
+
+- Keep terminal rendering delegated to xterm.js and shell integration delegated to the backend PTY.
+- Keep IME switching delegated to the platform webview and the operating system.
+- Keep public documentation in both English and Japanese when user-facing behavior changes.

package/INSTALL.ja.md

@@ -0,0 +1,204 @@
+# インストール
+
+英語版: [INSTALL.md](INSTALL.md)。概要と利用方法は[日本語 README](README.ja.md)を参照してください。
+
+## npm
+
+npm registry から公開済み package をインストールします。
+
+```sh
+npm install -g fpasoterm
+fpasoterm
+```
+
+npm の自動 audit request がネットワーク上で問題になる場合、local install には `--no-audit` を使用できます。CI では repository 内の明示的な security check を継続して実行します。window を開かずに command path 上の version と build commit を確認するには次を実行します。
+
+```sh
+fpasoterm --version
+fpasoterm -v
+```
+
+Windows で新しい `.exe` または `.msi` を導入した後も古い version が表示される場合、`Path`、Start menu、pinned shortcut のいずれかが古い executable を起動しています。起動中の fpasoterm window を閉じ、新しい package を再インストールしてから更新後の shortcut で起動してください。
+
+Windows build では release executable と同じ directory に `fpasoterm.cmd` を配置します。`--version`、`--plugin-path`、`--plugin-info`などCLI専用操作にはこのconsole wrapperを使ってください。CLI操作は executable を直接実行するため、stdout、stderr、終了codeがPowerShellまたはcmdへ戻ります。通常起動は従来どおり非待機です。
+
+```powershell
+.\src-tauri\target\release\fpasoterm.cmd --version
+.\src-tauri\target\release\fpasoterm.cmd --plugin-path
+.\src-tauri\target\release\fpasoterm.cmd --help
+.\src-tauri\target\release\fpasoterm.cmd
+```
+
+同じ wrapper から PowerShell の command completion を有効化できます。
+
+```powershell
+.\src-tauri\target\release\fpasoterm.cmd --completion powershell | Out-String | Invoke-Expression
+```
+
+Bash、Zsh、Fish、永続化方法、および `cmd.exe` の制約は[コマンド補完](docs/completion.ja.md)を参照してください。
+
+## 開発用の起動
+
+Linux では Tauri/WebKitGTK の開発用 package が必要です。
+
+```sh
+sudo apt install build-essential curl libgtk-3-dev libwebkit2gtk-4.1-dev libayatana-appindicator3-dev librsvg2-dev
+```
+
+依存関係を入れた後、通常の開発起動は次の通りです。
+
+```sh
+npm install
+./scripts/run
+```
+
+リリース用 bundle を作らず、まず起動だけ確認する場合は次を使ってください。
+
+```sh
+./bin/fpasoterm --dev
+```
+
+`--dev` は既存の `src-tauri/target/release/fpasoterm` を無視して、現在のソースを Tauri dev runtime で起動します。renderer や Tauri source の修正確認では、毎回再インストールする必要はありません。
+現在のコンソールでログを見たい場合だけ `--foreground --console-diagnostics` を追加してください。
+初回の `--dev` 起動では Cargo が Tauri debug binary を作るため数分かかることがあります。2回目以降は build cache を使うため短くなります。
+
+## ローカルコマンドの更新
+
+checkout の `fpasoterm` コマンドと launcher entry をインストールする場合:
+
+```sh
+npm run install:desktop
+fpasoterm
+```
+
+checkout path、launcher icon、installed command wrapper、Rust source、renderer asset を更新した場合:
+
+```sh
+npm run update:desktop
+```
+
+この command は desktop launcher を上書きし、local runtime を再buildします。次の icon または command 起動では、更新後の checkout が使われます。
+
+`npm run update:desktop` は Linux / ChromeOS の desktop integration 用です。Windows では desktop を変更せず終了します。Windows 版は最新の `.msi` または `.exe` artifact を install して更新してください。
+
+npm でインストールした package を terminal から更新する場合:
+
+```sh
+fpasoterm --self-update
+```
+
+起動せずに現在使われている version を確認する場合:
+
+```sh
+fpasoterm --version
+fpasoterm -v
+```
+
+Windows で新しい `.exe` または `.msi` を古い版へ上書きインストールした後も古い UI が表示される場合は、まず `fpasoterm --version` を確認してください。古い version が表示される場合、`Path`、Start menu、pinned shortcut のいずれかが古い executable を起動しています。起動中の fpasoterm を閉じ、新しい installer を再実行してから更新後の shortcut で起動してください。
+
+source checkout の場合は、通常の git または jj workflow で checkout を更新した後、
+installed command、launcher entry、icons を更新します。
+
+```sh
+fpasoterm --update-desktop
+```
+
+clean な non-jj git checkout では、次で自動化できます。
+
+```sh
+fpasoterm --self-update-checkout
+```
+
+npm global install で入れた npm 管理下の `fpasoterm` command を削除する場合:
+
+```sh
+npm uninstall -g fpasoterm
+```
+
+この操作では source checkout の desktop launcher、ユーザー設定、cache、app data は削除されません。実行後も `type -a fpasoterm` で command が表示される場合は、source checkout launcher など別の install が残っています。
+
+Windows では PowerShell または Command Prompt で同じ command を実行できます。実行後は新しい terminal を開き、`where.exe fpasoterm` または `Get-Command fpasoterm -All` で別の command が残っていないか確認してください。
+
+source checkout から導入した local command、desktop launcher entry、icon、ユーザー設定、runtime cache、Tauri/WebKit app data を削除する場合:
+
+```sh
+npm run uninstall:desktop
+```
+
+Windows の `npm run uninstall:desktop` は、local testing で追加した fpasoterm 関連 directory を current user の `Path` から削除するだけです。global npm package、source checkout、ユーザー設定、cache、app data は削除しません。共有 npm directory は残します。
+
+両方を削除する場合は、source checkout 内で先に `npm run uninstall:desktop` を実行し、その後 `npm uninstall -g fpasoterm` を実行してください。
+
+ChromeOS/Baguette で透過検証中に黒、白、ちらつきが出る場合:
+
+```sh
+fpasoterm --disable-dmabuf
+```
+
+## リリース成果物
+
+現在の開発環境向けの成果物を作る場合:
+
+```sh
+npm run build:artifacts
+```
+
+生成物は `artifacts/` に出力されます。source archive は常に生成されます。platform bundle は現在の OS 向けだけなので、Linux のローカルビルドでは Linux package だけが生成されます。
+
+tag 付きの GitHub Release では、GitHub Actions で次の成果物を作成します。
+
+- source package と portable source archive
+- Linux x64 `.deb` / `.rpm`
+- ChromeOS/Baguette を含む arm64 Linux 向け `.deb` / `.rpm`
+- macOS x64 bundle
+- macOS arm64 bundle
+- Windows x64 bundle と `fpasoterm-<version>-windows-cli.cmd` console wrapper
+
+Debian package をローカルにインストールする場合:
+
+```sh
+sudo apt install ./artifacts/fpasoterm_1.3.0_arm64-linux-arm64.deb
+```
+
+## Linux Desktop Entry
+
+desktop entry template は次のファイルです。
+
+```text
+extra/linux/io.github.oyoguhito.fpasoterm.desktop
+```
+
+application icon の元画像は次の PNG です。
+
+```text
+extra/logo/fpasoterm.png
+```
+
+macOS app bundle では次を使います。
+
+```text
+extra/macos/fpasoterm.icns
+```
+
+Windows app bundle では次を使います。
+
+```text
+extra/windows/fpasoterm.ico
+```
+
+desktop entry と hicolor launcher icon を current user の data directory へインストールします。
+
+```sh
+npm run install:desktop
+```
+
+unpacked checkout を install する場合、desktop entry の `Exec=` は絶対 path の `~/.local/bin/fpasoterm` wrapper に書き換えられ、`TryExec` は設定しません。wrapper は install 時に使用した Node.js executable を記録し、一般的な `node` path も fallback として確認します。launcher environment に user shell の `PATH` が含まれない ChromeOS でも起動できるようにするためです。
+
+installed desktop entry は `StartupWMClass=fpasoterm` と `Icon=io.github.oyoguhito.fpasoterm` を使います。GTK application id は無効化しているため、CLI または launcher から複数の fpasoterm window を起動できます。launcher は fpasoterm の shelf icon と hover name を解決します。installer は hicolor icon theme に `io.github.oyoguhito.fpasoterm.png` と `fpasoterm.png` の両方を配置します。
+
+`extra/logo/fpasoterm.png` を置き換えた後は、launcher icon size を再生成します。
+
+```sh
+npm run generate:icons
+npm run update:desktop
+```