@firstpick/pi-package-webui 0.6.5 → 0.6.6

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.
package/README.md CHANGED
@@ -157,7 +157,7 @@ Optional Natural Conversation server-side voice fallback variables:
157
157
  - Side-panel theme picker backed by optional `@firstpick/pi-themes-bundle` themes when loaded.
158
158
  - Per-tab cwd changes, a clickable footer cwd picker, directory creation/search in the picker, saved path fast picks, server-persisted fast picks, and restart-safe restoration of open tabs.
159
159
  - Detected app runner dropdown for the active tab cwd, including Cargo, Bun, npm/npx/pnpm, Python/uv, Go/Golang, Zig, C/C++, Docker Compose, root/dev/scripts shell scripts, and other common project runners with live output pinned at the top of the terminal. Running app runners expose line-oriented stdin in the widget for interactive scripts. Projects can add browseable custom runners in `.pi-webui-runners.json` with a command (default `./`) plus a relative path to the file to run.
160
- - Guided Git workflow for existing repos and new repos: initialize, create README/.gitignore, initial commit, rename to `main`, add a GitHub remote, pull fetched incoming changes, stage, generate or type commit messages, push, and optionally create a PR.
160
+ - Guided Git workflow for existing repos and new repos with persistent model/reasoning preferences, review-first staging, generated or typed commit messages, explicit push/PR confirmation, and optional PR worktrees.
161
161
  - Browser support for Pi extension UI prompts, widgets, status updates, `/btw` side-question output widgets with optional context transfer/live steering, browser notifications when a tab needs an extension UI response, and an optional side-panel toggle for agent-done notifications.
162
162
  - Localhost-only Pi/Web UI update checks with a top-right update notification and confirmed restart actions: **Update Pi & restart** runs `pi update` for Pi-only updates, while **Update Pi + Packages & Restart** runs `pi update --all` plus detected Web UI/Optional Feature package-root updates for Pi plus configured, local agent, project, global npm, and global Bun package roots.
163
163
  - Feedback reactions (`👍`, `👎`, `?`) on final assistant output plus tool/bash action cards, which can ask Pi to create or update a LEARNING.
@@ -242,7 +242,7 @@ These screenshots show the v0.4.8 Web UI surfaces. Current implementations inclu
242
242
  ![Pi Web UI thinking effort picker showing off, minimal, low, medium, high, and xhigh choices](https://raw.githubusercontent.com/Firstp1ck/npm-packages/main/pi-package-webui/images/Webui_Effort_v0.4.8.png)
243
243
 
244
244
  - **What it is:** A browser picker for Pi's model thinking/reasoning effort setting.
245
- - **What you can do:** Switch between `off`, `minimal`, `low`, `medium`, `high`, and `xhigh`, confirm the effective effort in the footer, and tune speed/cost/quality before sending a prompt.
245
+ - **What you can do:** Switch between `off`, `minimal`, `low`, `medium`, `high`, `xhigh`, and `max`, confirm the effective effort in the footer, and tune speed/cost/quality before sending a prompt.
246
246
 
247
247
  ### Scoped models
248
248
 
@@ -374,7 +374,9 @@ Optional companions:
374
374
 
375
375
  ## Guided Git workflow
376
376
 
377
- The Git workflow button runs local git commands in the active Pi working directory. It now covers both empty/new projects and existing repositories.
377
+ The Git workflow button runs local git commands in the active Pi working directory. It covers both empty/new projects and existing repositories.
378
+
379
+ Before first use, run `/git-workflow-setup` in Pi or choose **Common Pi Options → Guided Git Setup** in the browser. Select an exact authenticated `provider/modelId`, a supported reasoning effort, and the workflow defaults described below. The browser preselects the active tab model when possible, but saving is always explicit. Preferences are stored globally in the Pi Web UI settings file (normally `~/.config/pi-webui/settings.json` or `$XDG_CONFIG_HOME/pi-webui/settings.json`), not in browser storage.
378
380
 
379
381
  For a new project, the browser flow can:
380
382
 
@@ -390,16 +392,26 @@ For an existing repository, the workflow can:
390
392
 
391
393
  1. Show staged, unstaged, untracked, and fetched incoming changes.
392
394
  2. Fast-forward pull fetched incoming commits when the repository is safely behind.
393
- 3. Run `git add .`.
394
- 4. Send `/git-staged-msg` to Pi and read generated commit message files from `dev/COMMIT/`.
395
- 5. Use a generated short/long message, a generated single-file default such as `updated file.txt`, or a manual **Commit input** message.
396
- 6. Run `git push`.
395
+ 3. Review/select files, preserve a non-empty staged set, or explicitly opt into `git add .`.
396
+ 4. Generate `/git-staged-msg` with the configured model, supported reasoning effort, language, and scope policy, then restore the tab's prior model/effort.
397
+ 5. Use the preferred generated short/long message, a generated single-file default such as `updated file.txt`, or a manual **Commit input** message.
398
+ 6. Show an optional pre-commit verification reminder, then require explicit confirmation before push and PR delivery actions.
399
+
400
+ The saved setup includes:
401
+
402
+ - one generation profile reused for commit messages, branch names, and PR descriptions;
403
+ - English or German output, short or long default commit choice, and automatic/never/required Conventional Commit scope;
404
+ - review/select (recommended), preserve-staged, or explicit stage-all behavior;
405
+ - ask/current-branch/PR-worktree delivery highlighting; and
406
+ - optional pre-commit verification reminders.
407
+
408
+ If the configured model or effort is unavailable, generation stops and asks you to update setup; it never silently substitutes another model. Guided Git never force-pushes automatically. Git hooks and signing configuration continue to run normally.
397
409
 
398
410
  After the message is generated, **Create PR** asks Pi to generate `dev/COMMIT/staged-branch-name.txt`, lets you confirm or edit the `type/feature-name` branch, then switches with `git switch -c` before committing. In PR mode, choose **Commit short**, **Commit long**, or type a message and use **Commit input**, then **Push and Create PR** pushes the branch, sends `/pr`, shows the generated `dev/PR/<branch>.md` description for editing/confirmation, and creates the pull request with `gh pr create`. Use **Manual branch** to skip agent branch-name generation and type the branch directly.
399
411
 
400
412
  Use the workflow process buttons to jump directly to **Initialize**, **Stage**, **Message**, **Commit**, **Push**, or PR steps when earlier work was already completed manually. Selecting **Message** lets you either run `/git-staged-msg` or type a commit message and use **Commit input** directly. Selecting **Commit** loads the current generated files from `dev/COMMIT/` before enabling the commit choices. A yellow dot means that process was selected or is available but its action has not completed in this workflow; green means the process action completed.
401
413
 
402
- This requires `/git-staged-msg` and `/pr` from `@firstpick/pi-prompts-git-pr`; branch-name generation uses `/git-branch-name` when available and otherwise sends an equivalent inline prompt. Creating the PR also requires an authenticated GitHub CLI (`gh`). Review the generated commit message, branch name, remote URL, and PR description before committing, pushing, or creating a PR.
414
+ This requires `/git-staged-msg` and `/pr` from `@firstpick/pi-prompts-git-pr`; branch-name generation uses `/git-branch-name`. Creating the PR also requires an authenticated GitHub CLI (`gh`). Review the generated commit message, branch name, remote URL, and PR description before committing, pushing, or creating a PR.
403
415
 
404
416
  ## Mobile and PWA notes
405
417