@selesai/code 0.9.14 → 0.10.0

package/dist/extensions/pi-zentui/.github/ISSUE_TEMPLATE/runtime_detection.yml

@@ -0,0 +1,103 @@
+name: Runtime/language detection
+description: Request or report runtime/language detection behavior
+title: "runtime: "
+labels: ["runtime", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this for Zentui footer runtime/language segments: missing runtimes, incorrect detection, version display, or new runtime support.
+
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Pre-flight checks
+      options:
+        - label: I searched existing issues before opening this one.
+          required: true
+        - label: I checked whether the relevant runtime/version command is available in the same shell where Pi runs.
+          required: true
+
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Request type
+      options:
+        - Existing runtime not detected
+        - Existing runtime detected incorrectly
+        - Add a new runtime/language
+        - Version command/display issue
+    validations:
+      required: true
+
+  - type: input
+    id: runtime
+    attributes:
+      label: Runtime or language
+      placeholder: "Node.js, Python, Rust, Zig, etc."
+    validations:
+      required: true
+
+  - type: textarea
+    id: project-files
+    attributes:
+      label: Project files and detection signals
+      description: List relevant files in the project root and subdirectories that should influence detection.
+      placeholder: |
+        package.json
+        .node-version
+        pyproject.toml
+        src/...
+    validations:
+      required: true
+
+  - type: textarea
+    id: version-output
+    attributes:
+      label: Version command output
+      description: Include the command and output, if applicable.
+      placeholder: |
+        $ node --version
+        v20.11.1
+      render: shell
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Zentui segment
+      placeholder: "via  v20.11.1"
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Zentui segment
+    validations:
+      required: true
+
+  - type: input
+    id: zentui-version
+    attributes:
+      label: Zentui version
+      placeholder: "0.2.7 / main@abc123 / local checkout"
+    validations:
+      required: true
+
+  - type: input
+    id: pi-version
+    attributes:
+      label: Pi version
+      placeholder: "0.74.x"
+    validations:
+      required: true
+
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      placeholder: |
+        OS:
+        Shell:
+        Terminal app:
+        Install source:

package/dist/extensions/pi-zentui/.github/dependabot.yml

@@ -0,0 +1,47 @@
+version: 2
+
+updates:
+  # npm dependencies in this package
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    target-branch: "main"
+    open-pull-requests-limit: 5
+    groups:
+      # Low-noise grouped PRs for minor and patch updates.
+      minor-and-patch:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"
+      # Major npm updates are intentionally not auto-merged; keep them visible
+      # as a separate stream so reviewers can evaluate breaking changes.
+      major:
+        patterns:
+          - "*"
+        update-types:
+          - "major"
+
+  # GitHub Actions workflow versions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    target-branch: "main"
+    open-pull-requests-limit: 5
+    groups:
+      first-party-and-known:
+        patterns:
+          - "actions/*"
+          - "github/*"
+        update-types:
+          - "minor"
+          - "patch"
+      third-party-actions:
+        patterns:
+          - "*"
+        update-types:
+          - "minor"
+          - "patch"

package/dist/extensions/pi-zentui/.github/pull_request_template.md

@@ -0,0 +1,34 @@
+## Summary
+
+<!--
+Briefly describe what this PR changes and why.
+Focus on user-facing behavior: footer, editor, user-message styling, runtime/git detection, `/zentui` settings, config, or packaging.
+Link related issues with "Closes #123" or "Refs #123" where applicable.
+-->
+
+## Screenshots / recordings
+
+<!--
+Required for footer, editor, user-message, or rendering changes whenever practical.
+A short terminal recording (asciinema, GIF, or video) is preferred over a still image.
+If the change is purely internal (build, types, tests, docs), say "N/A" and explain.
+-->
+
+## Testing
+
+<!--
+Run these locally before requesting review. Tick everything that applies.
+-->
+
+- [ ] `npm run verify`
+- [ ] `npm run pack:check`
+- [ ] Manual Pi test via `npm run pi:dev` (required for UI behavior changes)
+- [ ] Added or updated tests where practical
+
+## Checklist
+
+- [ ] Preserved Nerd Font / private-use icon glyphs (no empty strings or replaced characters).
+- [ ] Updated `README.md` or config docs if user-facing behavior changed.
+- [ ] Kept the diff surgical: no unrelated refactors, formatting, or dependency churn.
+- [ ] `extensions/zentui/index.ts` stays mostly orchestration; new logic lives in a focused module.
+- [ ] Used a conventional commit-style PR title (e.g. `feat: add ...`, `fix: handle ...`).

package/dist/extensions/pi-zentui/.github/release.yml

@@ -0,0 +1,18 @@
+changelog:
+  categories:
+    - title: Features
+      labels:
+        - feat
+
+    - title: Bug fixes
+      labels:
+        - fix
+
+    - title: Other changes
+      labels:
+        - "*"
+
+  exclude:
+    labels:
+      - chore
+      - skip-changelog

package/dist/extensions/pi-zentui/.github/workflows/ci.yml

@@ -0,0 +1,79 @@
+name: CI
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  verify:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+
+      - name: Setup Node
+        uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Verify
+        run: npm run verify
+
+      - name: Dry-run pack
+        run: npm run pack:check
+
+  supported-pi-compatibility:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    strategy:
+      fail-fast: false
+      matrix:
+        pi-version: ["0.80.5", "0.82.1", "0.83.0"]
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+
+      - name: Setup Node
+        uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          cache: npm
+
+      - name: Pin matching Pi package versions
+        env:
+          PI_VERSION: ${{ matrix.pi-version }}
+        run: |
+          npm pkg set "devDependencies.@earendil-works/pi-ai=$PI_VERSION"
+          npm pkg set "devDependencies.@earendil-works/pi-coding-agent=$PI_VERSION"
+          npm pkg set "devDependencies.@earendil-works/pi-tui=$PI_VERSION"
+
+      - name: Install dependencies
+        run: npm install --no-audit --no-fund
+
+      - name: Attest Pi package versions
+        env:
+          PI_VERSION: ${{ matrix.pi-version }}
+        run: |
+          npm ls --depth=0 @earendil-works/pi-ai @earendil-works/pi-coding-agent @earendil-works/pi-tui
+          node - <<'NODE'
+          for (const name of ["pi-ai", "pi-coding-agent", "pi-tui"]) {
+            const pkg = require(`./node_modules/@earendil-works/${name}/package.json`)
+            if (pkg.version !== process.env.PI_VERSION) throw new Error(`${pkg.name}: ${pkg.version}`)
+            console.log(pkg.name, pkg.version)
+          }
+          NODE
+
+      - name: Test supported Pi version
+        run: timeout --signal=TERM --kill-after=30s 15m npm test

package/dist/extensions/pi-zentui/.github/workflows/publish.yml

@@ -0,0 +1,63 @@
+name: Publish
+run-name: Publish ${{ github.ref_name }}
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+permissions:
+  contents: read
+  id-token: write
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: npm-publish
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v7
+
+      - name: Setup Node
+        uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          registry-url: https://registry.npmjs.org
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Verify
+        run: npm run verify
+
+      - name: Dry-run pack
+        run: npm run pack:check
+
+      - name: Check tag matches package version
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          TAG="${GITHUB_REF_NAME#v}"
+          test "$VERSION" = "$TAG"
+
+      - name: Publish to npm
+        run: npm publish
+
+  release:
+    needs: publish
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - name: Create GitHub release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          REPO="${{ github.repository }}"
+          if gh release view "${GITHUB_REF_NAME}" --repo "$REPO" >/dev/null 2>&1; then
+            echo "Release ${GITHUB_REF_NAME} already exists; skipping."
+          else
+            gh release create "${GITHUB_REF_NAME}" --repo "$REPO" --generate-notes --title "${GITHUB_REF_NAME}"
+          fi

package/dist/extensions/pi-zentui/AGENTS.md

@@ -0,0 +1,107 @@
+## What this app is
+
+Zentui is a Pi extension package that gives Pi a Starship-inspired footer and an Opencode-style input UI.
+
+It shows useful session/project state at a glance:
+
+- current directory
+- git branch and git status
+- detected runtime/language and version
+- context usage
+- input/output token counts
+- running session cost
+- model/provider in the editor frame
+
+## How it works
+
+Pi loads the package from `package.json` via:
+
+```json
+"pi": {
+  "extensions": ["./extensions"]
+}
+```
+
+The extension entry point is:
+
+```text
+extensions/zentui/index.ts
+```
+
+On `session_start`, Zentui installs:
+
+- a custom footer (`footer.ts`)
+- a custom editor (`ui.ts`)
+- custom user-message styling (`user-message.ts`)
+- a project refresh timer for git/runtime status
+
+Most updates happen by syncing shared footer state and asking the TUI to re-render after Pi events like model changes, message completion, tool completion, and compaction.
+
+## Product decision: TUI composability
+
+Zentui is a set of independently selectable TUI components, not a bundled UI mode. Users can adopt User messages, Editor, Working line, selector borders, Footer, or future surfaces individually while leaving every other surface native or controlled by another extension.
+
+- Enabling or configuring one component must never require, toggle, restyle, or silently rewrite another. Each feature needs its own canonical config choice (`enabled` and/or `style` as appropriate), settings control, install/reconcile/dispose lifecycle, and ownership boundary.
+- Disabled or native must leave that surface alone. Shared infrastructure must remain behavior-neutral.
+- Prefer public Pi APIs. Safely decorate, aggregate, or delegate where possible; clean up only owned state; and fail open to native or predecessor UI.
+- Treat the unkeyed Working line as controlled exclusivity with best-effort release, not true aggregation.
+- Keep `index.ts` orchestration-only.
+
+## Important files
+
+- `extensions/zentui/index.ts` — extension orchestration and Pi event wiring.
+- `extensions/zentui/config.ts` — config file path, defaults, and config merging.
+- `extensions/zentui/footer.ts` — footer/statusline rendering.
+- `extensions/zentui/style.ts` — Starship-style terminal style rendering (`bold purple`, `fg:202`, `bg:blue`, etc.).
+- `extensions/zentui/format.ts` — small formatting helpers for counts, labels, context, cwd, and runtime segments.
+- `extensions/zentui/state.ts` — footer state shape and sync logic.
+- `extensions/zentui/git.ts` — git porcelain parsing and status summary.
+- `extensions/zentui/runtime.ts` — runtime/language detection and version lookup.
+- `extensions/zentui/settings-command.ts` — `/zentui` settings UI for color-source preferences.
+- `extensions/zentui/ui.ts` — custom editor frame.
+- `extensions/zentui/user-message.ts` — prompt-box-style user message rendering.
+
+## Config
+
+User config is created at:
+
+```text
+~/.pi/agent/zentui.json
+```
+
+Use `colors` for Starship-style color strings, hex/256-color values, or Pi theme tokens. Canonical color-source ownership is independent through `components.editor.colorSource`, `components.userMessages.colorSource`, `components.selectorBorders.colorSource`, and `components.footer.colorSource`. `/zentui` exposes separate controls for Editor, previous User messages, selector borders, and—while Starship is selected—the Footer; changing one does not change the others.
+
+## Things to preserve
+
+- Keep `index.ts` mostly orchestration; put rendering/formatting logic in focused modules.
+- Preserve Nerd Font icons. Many are private-use Unicode characters and can be easy to accidentally replace with empty strings.
+- Runtime color values should follow Starship's terminal style strings.
+- `user-message.ts` intentionally patches `UserMessageComponent`; treat it as fragile and avoid changing it unless necessary.
+- Silent fallbacks are intentional for git/runtime/config failures so the UI does not break the session.
+
+## Development
+
+Use these commands before shipping changes:
+
+```bash
+npm run fmt
+npm run verify
+npm run pack:check
+```
+
+For local Pi testing:
+
+```bash
+npm run pi:dev
+npm run pi:install-local
+```
+
+## Commit style
+
+Use conventional commit messages that match the existing history:
+
+```text
+feat: add user-facing capability
+```
+
+Keep the subject lowercase after the type, imperative, and concise. Do not use a trailing period.

package/dist/extensions/pi-zentui/CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# Contributing to pi-zentui
+
+Thanks for your interest in pi-zentui. This document covers the workflow and conventions used in this repository.
+
+## Development setup
+
+Requirements: Node.js and npm. pi-zentui is a Pi extension package, so you'll also want a working `pi` binary for local testing.
+
+```bash
+npm install
+npm run verify      # biome check + tsc --noEmit + vitest run
+npm run pack:check  # npm pack --dry-run, sanity-checks published contents
+```
+
+Before opening a pull request, please run `npm run fmt` and then `npm run verify` again.
+
+## Local Pi testing
+
+The package is loaded by Pi from `package.json` via the `pi.extensions` field. Use the dev scripts to iterate without publishing:
+
+```bash
+npm run pi:dev              # runs pi with only this extension loaded
+npm run pi:install-local    # installs the local checkout into your pi extensions
+```
+
+If your `pi` binary is not at the default path, override it:
+
+```bash
+PI_BIN=/absolute/path/to/pi npm run pi:dev
+```
+
+Manual testing is required for any change that affects the footer, editor, user-message styling, runtime/git detection, colors, or `/zentui` settings.
+
+## Coding expectations
+
+Please follow the conventions already in this repo. The most important ones:
+
+- **Preserve Nerd Font / private-use icon glyphs.** Many of the icons are private-use Unicode characters; it is easy to replace them with empty strings by accident.
+- **Keep `extensions/zentui/index.ts` orchestration-focused.** Rendering, formatting, and parsing logic belong in focused modules such as `footer.ts`, `format.ts`, `style.ts`, `git.ts`, `runtime.ts`, `ui.ts`, or `user-message.ts`.
+- **Use focused modules.** New rendering or formatting code should generally go into the matching module rather than being inlined.
+- **Silent fallbacks are intentional.** Git, runtime detection, and config lookups fail silently so that a broken environment does not break the session. Do not add throws or noisy errors for these paths without a strong reason.
+- **`user-message.ts` patches `UserMessageComponent`.** Treat it as fragile and avoid changes unless they are necessary.
+- **Runtime color values follow Starship's terminal style strings** (e.g. `bold purple`, `fg:202`, `bg:blue`).
+
+## Pull request expectations
+
+- Describe the user-facing behavior change in the PR summary.
+- Include screenshots or a short recording for footer, editor, user-message, or rendering changes.
+- Run `npm run verify` and `npm run pack:check` locally.
+- Keep the diff surgical. Don't refactor adjacent code, reformat unrelated files, or upgrade dependencies that aren't part of the fix.
+- Use a conventional commit-style subject (e.g. `feat: add ...`, `fix: handle ...`), lowercase after the type, imperative, and concise. No trailing period.
+- Reviews are assigned to `@lmilojevicc` via `CODEOWNERS`.
+
+## Reporting issues
+
+Please use the GitHub issue forms in [`.github/ISSUE_TEMPLATE/`](.github/ISSUE_TEMPLATE/) so reports include the environment, config, and Pi/Zentui version context needed to triage them:
+
+- Bug report
+- Rendering, icon, or color issue
+- Feature request
+- Runtime/language detection
+- Config or usage question
+
+For core Pi issues outside Zentui's footer, editor, and message styling, please open the issue upstream in the Pi project instead.
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the MIT license that covers this project. See [`LICENSE`](LICENSE) for the full text.

package/dist/extensions/pi-zentui/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-2026 Luka
+
+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.