@zerwiz/sessrumnir 0.1.8-alpha → 0.1.9

package/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,99 @@
+name: Bug report
+description: Something's broken or behaving wrong
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug. The more detail you give, the faster we can fix it.
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: A clear description of what went wrong.
+      placeholder: "When I clicked X, the app did Y, but I expected Z."
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: Tell us how to make the bug happen again.
+      placeholder: |
+        1. Open Pi Desktop
+        2. Click '...'
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect?
+      description: What should have happened instead?
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating system
+      options:
+        - Linux (AppImage)
+        - macOS (.dmg / .zip)
+        - Windows (portable .exe)
+        - Built from source
+        - Other
+    validations:
+      required: true
+
+  - type: input
+    id: os-version
+    attributes:
+      label: OS version
+      description: "e.g. Ubuntu 24.04, Fedora 40, Windows 11 22H2"
+    validations:
+      required: true
+
+  - type: input
+    id: pi-desktop-version
+    attributes:
+      label: Pi Desktop version
+      description: "Open Diagnostics and copy the App version line. Example: 0.1.8-alpha"
+    validations:
+      required: true
+
+  - type: input
+    id: pi-version
+    attributes:
+      label: Pi agent version
+      description: "Run `pi --version` in a terminal. If Pi isn't installed, write 'not installed'."
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs or error messages
+      description: |
+        Anything from the DevTools console (View > Toggle DevTools), the terminal you launched the app from, or an on-screen error.
+      render: shell
+
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: Drag-and-drop images here if they help show the problem.
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues and didn't find a duplicate.
+          required: true
+        - label: I'm on the latest release listed at https://github.com/FaqFirebase/pi-desktop/releases
+          required: true

package/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Pi coding agent (the underlying CLI)
+    url: https://github.com/earendil-works/pi/issues
+    about: If the bug is in Pi itself (the agent we wrap), report it upstream here.
+  - name: Pi Desktop releases
+    url: https://github.com/FaqFirebase/pi-desktop/releases
+    about: Grab the latest build before opening a bug.

package/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,46 @@
+name: Feature request
+description: Suggest a new feature or improvement
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the suggestion. Help us understand the problem first — that's usually where the best solutions come from.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: What are you trying to do that's awkward or impossible today?
+      placeholder: "When I'm doing X, I have to manually do Y every time, and it would be much faster if..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: What would you like to see?
+      description: A clear description of the feature or change you want.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you've considered
+      description: Other approaches you've thought about, or workarounds you're using now.
+
+  - type: textarea
+    id: extra
+    attributes:
+      label: Anything else?
+      description: Mockups, links to similar features in other apps, etc.
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues and didn't find a duplicate.
+          required: true

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,56 @@
+<!--
+Thanks for contributing to Pi Desktop!
+
+Before you open this PR, please read CONTRIBUTING.md:
+https://github.com/FaqFirebase/pi-desktop/blob/master/CONTRIBUTING.md
+
+Two things people miss most often:
+1. PRs must target the `Dev` branch, not `master`.
+2. Commit messages follow Conventional Commits: <type>(<scope>): <subject>
+-->
+
+## Summary
+
+<!-- What does this PR do, and why? A few sentences is fine. -->
+
+## Related issues
+
+<!-- Link issues this PR addresses, e.g. "Closes #123". Write "None" if there isn't one. -->
+
+## Type of change
+
+<!-- Check all that apply. -->
+
+- [ ] `feat` — New feature
+- [ ] `fix` — Bug fix
+- [ ] `docs` — Documentation
+- [ ] `refactor` — Code restructuring (no behavior change)
+- [ ] `test` — Adding or updating tests
+- [ ] `chore` — Build process, dependencies, tooling
+- [ ] `perf` — Performance improvement
+- [ ] `style` — Formatting (no code change)
+
+## How was this tested?
+
+<!--
+Describe how you verified the change: manual steps in the app,
+new/updated tests, platforms tested (Linux/Windows), etc.
+-->
+
+## Screenshots
+
+<!-- For UI changes, add before/after screenshots. Delete this section otherwise. -->
+
+## Checklist
+
+- [ ] This PR targets the `Dev` branch (not `master`)
+- [ ] `npm run typecheck` passes
+- [ ] `npm run lint` passes
+- [ ] `npx tsx --test` passes
+- [ ] `npm run build` succeeds
+- [ ] The app launches and works (`npm run dev`) with no regressions
+- [ ] Tests added or updated for changed modules (colocated `*.test.ts`)
+- [ ] Electron security posture preserved (context isolation, IPC through preload bridge, validated payloads)
+- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)
+- [ ] If AI-assisted, the agent was pointed at [`AGENTS.md`](https://github.com/FaqFirebase/pi-desktop/blob/master/AGENTS.md) and its Final Delivery Checklist
+- [ ] I have read and agree to the [CLA](https://github.com/FaqFirebase/pi-desktop/blob/master/CLA.md)

package/.github/SUPPORT.md

@@ -0,0 +1,18 @@
+# Support
+
+## Response times
+
+Issues are monitored on weekdays. Weekend issues are not handled unless urgent (crash on launch, data loss, security).
+
+If your issue is urgent, label it **urgent** and briefly explain why in the description.
+
+## Before opening an issue
+
+- Check the [existing issues](https://github.com/FaqFirebase/pi-desktop/issues) for duplicates.
+- Make sure you are on the [latest release](https://github.com/FaqFirebase/pi-desktop/releases).
+- If the problem is in the Pi agent itself (not the GUI), report it [upstream](https://github.com/earendil-works/pi/issues).
+
+## Links
+
+- [Releases](https://github.com/FaqFirebase/pi-desktop/releases)
+- [Pi agent issues](https://github.com/earendil-works/pi/issues)

package/.github/workflows/build.yml

@@ -0,0 +1,133 @@
+name: Build
+
+# Nothing builds on a normal push. Builds are manual: a workflow dispatch
+# (Actions tab / gh CLI) builds all three platforms and uploads the
+# installers as artifacts — no release. Pushing a version tag (e.g.
+# v0.0.3-alpha), the deliberate "create a release" step, builds all three
+# and publishes a GitHub prerelease.
+on:
+  push:
+    tags:
+      - 'v*'
+  workflow_dispatch:
+
+# Cancel superseded runs for the same ref to save runner time.
+concurrency:
+  group: build-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  verify:
+    name: Lint & test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
+
+      - name: Set up Node.js
+        uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
+        with:
+          node-version: '22'
+          cache: 'npm'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Unit tests
+        # `**` glob file-args to `--test` need a newer Node than the pinned
+        # runner version supports, so enumerate files with `find` instead of
+        # relying on the shell/runtime to expand the pattern. `resources/` holds
+        # the shared permission-rules engine's tests, so include it too.
+        run: npx --no-install tsx --test $(find src resources -name '*.test.ts')
+
+  build:
+    name: Build (${{ matrix.os }})
+    needs: verify
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        include:
+          - os: ubuntu-latest
+            eb_args: '--linux AppImage'
+            artifacts: |
+              release/*.AppImage
+          - os: windows-latest
+            eb_args: '--win nsis portable'
+            artifacts: |
+              release/*.exe
+          - os: macos-latest
+            eb_args: '--mac dmg zip'
+            artifacts: |
+              release/*.dmg
+              release/*.zip
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
+
+      - name: Set up Node.js
+        uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
+        with:
+          node-version: '20'
+          cache: 'npm'
+
+      # Runs postinstall, which rebuilds native modules (node-pty) for Electron.
+      # NOTE: confirmed (2026-06-08) that the windows-latest runner's bundled
+      # Visual Studio already includes the Spectre-mitigated MSVC libs node-pty
+      # needs — it compiles here with no explicit install step. An earlier
+      # vs_installer step worked but added ~4 min for nothing, so it was removed.
+      # (People building from source on their own machines may still need those
+      # libs — see README.)
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Type-check
+        run: npm run typecheck
+
+      - name: Build renderer/main/preload
+        run: npm run build
+
+      - name: Package with electron-builder
+        shell: bash
+        run: npx --no-install electron-builder ${{ matrix.eb_args }} --publish never
+        env:
+          # No certificates in alpha — don't attempt to sign the macOS app.
+          CSC_IDENTITY_AUTO_DISCOVERY: 'false'
+
+      - name: Upload installers
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: installers-${{ matrix.os }}
+          path: ${{ matrix.artifacts }}
+          if-no-files-found: error
+          retention-days: 14
+
+  release:
+    name: Publish prerelease
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Download all installers
+        uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
+        with:
+          path: dist
+          merge-multiple: true
+
+      # Attaches the built installers to the release for this tag. If you
+      # pre-created the release in the GitHub UI with your own notes, those
+      # notes are preserved (no generate_release_notes, no body input). If the
+      # tag was pushed without a release, one is created with an empty body.
+      - name: Attach installers to the release
+        uses: softprops/action-gh-release@3d0d9888cb7fd7b750713d6e236d1fcb99157228 # v3.0.2
+        with:
+          prerelease: true
+          make_latest: false
+          fail_on_unmatched_files: true
+          files: dist/**/*