buninu 0.1.1

package/apps/jsgotty/LICENSE

@@ -0,0 +1,23 @@
+MIT License
+
+Copyright (c) 2015-2017 Iwasaki Yudai
+Copyright (c) 2021-2022 Søren L. Hansen
+Copyright (c) 2026 Dr. John(醫者小智)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/apps/jsgotty/LICENSES/Apache-2.0-zmodem.js.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "{}"
+replaced with your own identifying information. (Don't include
+the brackets.) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright {yyyy} {name of copyright owner}
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/apps/jsgotty/NOTICE

@@ -0,0 +1,21 @@
+js-gotty
+Copyright (c) 2015-2017 Iwasaki Yudai
+Copyright (c) 2021-2022 Søren L. Hansen
+Copyright (c) 2026 Dr. John(醫者小智)
+
+This project is licensed under the MIT License. See the LICENSE file in the
+repository root.
+
+This project also redistributes third-party components under their own
+licenses.
+
+Included third-party component:
+
+1. zmodem.js - ZMODEM for JavaScript
+   Copyright 2017 Gasper Software Consulting
+   Licensed under the Apache License, Version 2.0
+   Local copy of license text:
+   LICENSES/Apache-2.0-zmodem.js.txt
+
+The bundled file [static/js/zmodem.js] is byte-for-byte identical to the
+upstream npm release zmodem.js version 0.1.10 dist/zmodem.js.

package/apps/jsgotty/README.en.md

@@ -0,0 +1,290 @@
+# jsgotty / gotty.js
+
+[中文 README](README.md)
+
+## News
+### 2026/07/03 - [1.1.0]
+- Unicode 11 from upstream
+- WebGL support by `--webgl` and query args
+- Frontend help by `--help-web`
+- Added `font-size` and `font-family`
+- Added `touch-scroll-threshold` for fast scrolling
+- Added experimental single-exe build commands: `--build-exe` and `--build-for <target>`
+- Improved ZMODEM / `rz/sz` reliability for large transfers
+  * terminal mode is switched for binary transfer and restored after transfer / cancel
+  * server-side output parsers are bypassed during ZMODEM sessions
+  * ZMODEM data uses ordered WebSocket chunks with acknowledgement / retransmit handling
+- Improved `sz` download UI
+  * streams downloads to browser file writer
+  * shows current file, transferred bytes / total bytes, progress, and verbose transfer logs
+- Improved `rz` upload UI
+  * shows current file, transferred bytes / total bytes, progress, and verbose transfer logs
+  * supports back-to-back `sz` then `rz` sessions more reliably
+- `rz` / `sz` terminal commands now print completion summaries with file path and byte size
+- ZMODEM debug logs are opt-in with `JSGOTTY_ZMODEM_LOG`
+
+### 2026/06/22 - [1.0.0]
+- Added gotty cli client
+  * compatible with golang gotty
+  * jsgotty --client -h for more info
+- Added /css to list sessions
+  * when --reconnect enabled, /css can reconnect to existing sessions
+
+### 2026/04/23
+- Added optional `noWinOpenUseFetch()` on the frontend for Bun markdown TUI:
+- https://github.com/jjtseng93/bun-taskmgr
+
+### 2026/04/21
+- Added dialog text display on the frontend:
+- `alert_advanced(getTerminalText())`
+- for copying text on mobile devices
+
+## Intro
+- Expose your terminal through browsers, CLI clients, and modern web protocols.
+- This is a GoTTY-compatible server rewritten in JavaScript / Bun.
+- It is based on the original GoTTY code, with most of the new code generated by Codex.
+- It includes a frontend and WebTTY protocol implementation adjusted for `jsgotty`.
+- Original repository:
+- https://github.com/sorenisanerd/gotty
+- .
+- Keywords: Terminal, TTY, Browser, CLI Client, Session management, Kitty graphics protocol, ZMODEM
+
+### Features
+- Resumable reconnect: after the browser disconnects, you can reconnect to the original shell / PTY with a reconnect token instead of spawning a new shell.
+  * jsgotty supports two connection modes: normal mode and session mode.
+  * Use `--reconnect` or `--session` to enable session mode.
+  * See the detailed mode explanation below.
+- Kitty Graphics Protocol: displays inline terminal images.
+  * For example, `bun viu.mjs 1.png` shows an image directly in the terminal.
+  * Set `JSGOTTY_KITTY_DEBUG=1` to write the Kitty image debug log.
+  * Windows does not use Kitty protocol; it uses a custom protocol.
+- ZMODEM / `rz/sz`: select files in the browser and upload them to the remote shell.
+  * You can also download files from the remote shell.
+  * Windows does not use ZMODEM; it uses a custom protocol.
+  * Linux has been tested with uploads/downloads around an 80MB Bun binary.
+
+## Usage
+
+### Install Bun
+- Android / Termux:
+  * `pkg install npm`
+  * `npm install -g bun`
+- Other platforms:
+  * https://bun.com
+
+### Linux
+
+```sh
+bun gotty.js -w bash
+bun gotty.js -w --credential user:pass bash
+bun gotty.js -w -p 8000 fish
+
+# ↓ enables session mode
+bun gotty.js -w --reconnect fish
+bun gotty.js -w --reconnect --reconnect-time 30 fish
+bun gotty.js -w --reconnect --reconnect-time -1 fish
+
+# or npx jsgotty@latest
+
+# show server / browser help
+bun gotty.js
+bun gotty.js --help
+bun gotty.js --help-web
+# ↑ browser help is also available at /help
+```
+
+### Windows
+
+```sh
+bun gotty.js -w cmd.exe
+bun gotty.js -w powershell
+
+# ↓ enables session mode
+bun gotty.js --reconnect powershell
+
+# or npx jsgotty@latest
+
+# show server / browser help
+bun gotty.js
+bun gotty.js --help
+bun gotty.js --help-web
+# ↑ browser help is also available at /help
+```
+
+### Built-in tools
+
+```sh
+bun gotty.js --rz
+bun gotty.js --sz
+bun gotty.js --viu
+bun gotty.js --client
+```
+
+- `--rz` starts `rz.js`: upload files
+- `--sz` starts `sz.js`: download files
+- `--viu` starts `viu.mjs`: display images
+- `--client` starts `client.mjs`: command-line client
+
+### CLI Client
+
+- `client.mjs` is an interactive terminal client that connects directly to GoTTY.
+- Basic connections are compatible with Golang GoTTY.
+- Session listing, writer management, and remote PTY termination require this project's jsgotty server.
+- See the detailed mode explanation below for the difference between normal mode and session mode.
+
+#### Basic connection
+
+```sh
+# Connect to the default ws://127.0.0.1:8080/ws
+bun gotty.js --client
+
+# Connect to 127.0.0.1:8081
+bun gotty.js --client 8081
+
+# HTTP(S) page URLs and WS(S) URLs are accepted
+bun gotty.js --client https://example.com/terminal/
+
+# Connect with credentials
+bun gotty.js --client -c user:pass 8081
+```
+
+#### Session management
+
+```sh
+# List current sessions
+bun gotty.js --client -ls [target]
+
+# Resume an existing session by reconnect token or PID
+# Requires session mode
+bun gotty.js --client -r <token|pid> [target]
+
+# Disconnect the current writer while keeping the PTY session alive
+# Requires session mode
+bun gotty.js --client -d <token|pid> [target]
+
+# Terminate the matching PTY session
+bun gotty.js --client -k <token|pid> [target]
+```
+
+The first argument can also use subcommand aliases:
+
+- `ls`, `list`, `list-sessions` => `-ls`
+- `attach`, `a <token|pid>` => `-r <token|pid>`
+- `detach <token|pid>` => `-d <token|pid>`
+- `kill-session`, `stop <token|pid>` => `-k <token|pid>`
+
+- `-ls` reads the server's `/css.md` session list.
+- Open `/css` to view the session list in a browser.
+- If `/css` shows a static file list instead of sessions, the server is Golang GoTTY, not jsgotty.
+- `-r` requires session mode; it resumes the matching PTY session.
+- `-d` requires session mode; after disconnecting the session writer, the session remains alive and the next writable client can take over.
+- `-k` terminates the matching PTY/session.
+- `--arg <value>` may be repeated to pass command arguments; `--arguments <query>` passes a raw query string.
+- `--cols` and `--rows` set the initial terminal size.
+- `GOTTY_CREDENTIAL` and `GOTTY_RECONNECT_TOKEN` may be used to configure credentials and the reconnect token.
+- See "Normal Mode / Session Mode" below for PTY creation, writer/viewer roles, and reconnect retention behavior.
+- Golang GoTTY does not support the jsgotty control protocols used by `-ls`, `-r`, `-d`, and `-k`.
+
+### Wrapper
+- `wgotty` is a wrapper for Linux
+- or for Windows with `busybox64u.exe bash`
+- https://frippery.org/busybox/
+- just run `./wgotty`
+- it will detect whether Bun is installed
+- and show the installation script if needed
+
+## Normal Mode / Session Mode
+
+The `jsgotty` server has two connection modes:
+
+- Normal mode: no `--reconnect` or `--session`
+- Session mode: `--reconnect` or `--session`
+
+### Normal Mode
+
+- Each new browser or `client.mjs` connection creates a new `PtySession` and a new PTY.
+- Two clients connected at the same time are usually two different shells / PTYs. They do not share screen output, input, or process state.
+- When a client disconnects, its corresponding PTY session is closed.
+- If the browser window, tab, or websocket closes normally, the server cleans up the PTY for that connection.
+- Normal mode cannot resume an existing PTY. If the browser or CLI sends a reconnect token / PID, it will not resume the old session and will create a new PTY instead.
+- `/css` and `/css.md` still list active session PIDs and command names, but they do not provide reconnect tokens or reconnect links.
+- `client.mjs -ls` can list sessions; `-k <pid>` can terminate a session by PID; `-r` and `-d` require session mode.
+
+### Session Mode
+
+- Enable it with `--reconnect` or `--session`.
+- The first connection creates a new `PtySession` and PTY unless it provides a resumable token / PID.
+- The server generates a reconnect token for each session and sends the session PID and token to the frontend.
+- Later, a browser or CLI can use the reconnect token or PID to resume the same PTY instead of spawning a new shell.
+- Multiple clients can connect to the same PTY session.
+- The first writable client becomes the writer and can send keyboard input, resize events, ZMODEM controls, and other data to the PTY.
+- Other clients are viewers. They receive terminal output but do not write to the PTY.
+- A client can also use `--readonly` to connect explicitly as a viewer.
+- If the writer disconnects while the session still has viewers, existing viewers are not automatically promoted to writer. The next writable client that resumes the same session can become the new writer.
+- After the last client disconnects, `--reconnect-time` decides whether the PTY is kept.
+
+#### `--reconnect-time` Behavior
+- `> 0`: keep the PTY for the specified number of seconds after the last client disconnects. It can be resumed during that window; after timeout, the PTY is closed.
+- `= 0`: close the PTY immediately after the last client disconnects.
+- `< 0`: keep the PTY indefinitely until the shell exits, `-k` terminates it, or the server stops.
+
+#### Frontend Reconnect Behavior
+- When `reconnect-time > 0`, the frontend retries automatically several times within the timeout.
+- When `reconnect-time < 0`, the frontend retries once per minute.
+- On disconnect, the overlay provides a `Reconnect` button for immediate manual retry.
+- Right-click / long-press on that button lets you enter a custom reconnect token or PID.
+
+## Tested platforms
+- Windows x64: Windows 11
+- Linux x64: CachyOS
+- Android arm64: Termux Native / Proot
+- Android arm64: My App
+  * https://drive.google.com/drive/folders/18iwbKrAZfA-HoTSP9I5MzGz5xVFMZ4bg
+
+## Current implementation
+- Uses Node's built-in `http` / `https`
+- Uses `ws` for WebSocket upgrade handling
+- Uses bundled frontend assets in `./static`, including kitty overlay and WebTTY / ZMODEM frontend logic
+- Supports inline terminal images
+- Supports file upload / download
+
+### PTY backends
+- Linux / macOS: use Bun's built-in PTY via `Bun.spawn(..., { terminal: ... })`
+- Windows: use patched `node-pty`, while still launching `gotty.js` through `bun`
+  * Bun versions >= 1.3.14 use Bun's built-in PTY
+
+### Kitty intro
+- If the terminal program outputs images using Kitty Graphics Protocol on Linux, the frontend displays those images at the corresponding terminal position.
+- Windows uses a custom protocol.
+- Usage:
+
+```sh
+bun viu.mjs 1.png
+# or bun gotty.js --viu 1.png
+```
+
+### rz upload intro
+- When the remote shell runs:
+
+```sh
+bun rz.js
+# or bun gotty.js --rz
+```
+
+- The frontend opens a file picker. After selecting files, they are uploaded to the current shell directory using ZMODEM.
+
+### sz download intro
+- When the remote shell runs:
+
+```sh
+bun sz.js file.txt
+# or bun gotty.js --sz file.txt
+```
+
+- The frontend receives the ZMODEM download data and lets the browser download the file.
+
+## Notes
+- The goal is to emulate the main behavior of the original GoTTY and add additional features.
+- Bun is the primary runtime.
+- On Linux / macOS, PTY support will not work unless the program is launched with Bun.
+- GoTTY config file loading is not implemented yet.