clavue 8.8.127 → 8.8.129

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
@@ -1,4 +1,4 @@
1
- # Clavue v8.8.127
1
+ # Clavue v8.8.129
2
2
 
3
3
  ![Clavue cover](https://unpkg.com/clavue/image.png)
4
4
 
@@ -65,8 +65,8 @@ npx -y clavue
65
65
  Run a specific version with `npx`:
66
66
 
67
67
  ```bash
68
- npx -y clavue@8.8.127 --version
69
- npx -y clavue@8.8.127
68
+ npx -y clavue@8.8.129 --version
69
+ npx -y clavue@8.8.129
70
70
  ```
71
71
 
72
72
  Install globally from npm when you want the `clavue` command to stay available:
@@ -86,7 +86,7 @@ curl -fsSL https://unpkg.com/clavue/install.sh | bash
86
86
  Install a specific version globally:
87
87
 
88
88
  ```bash
89
- curl -fsSL https://unpkg.com/clavue@8.8.127/install.sh | bash -s -- 8.8.127
89
+ curl -fsSL https://unpkg.com/clavue@8.8.129/install.sh | bash -s -- 8.8.129
90
90
  ```
91
91
 
92
92
  ## Quick Start: Custom API
@@ -150,6 +150,14 @@ On first launch, Clavue should make the setup choice obvious:
150
150
 
151
151
  After API setup, Clavue can also ask for a default permission mode. The recommended path for a trusted local development machine is the efficient development mode; the maximum-permission mode is intentionally reserved for environments you fully trust.
152
152
 
153
+ For deployments, releases, builds, packaging, and operational maintenance where file edits should proceed but shell commands must still be confirmed, use trusted ops mode:
154
+
155
+ ```bash
156
+ clavue --permission-mode trustedOps
157
+ ```
158
+
159
+ You can also set it in settings with `"permissions": { "defaultMode": "trustedOps" }`. `trustedOps` behaves like `acceptEdits` for file edit tools in the current workspace, but Bash/PowerShell commands still ask before execution. The legacy `dontAsk` permission mode is deprecated and will not activate from CLI or settings; migrate `dontAsk` defaults to `trustedOps` for release/build/deploy workflows.
160
+
153
161
  For P0-P3 development loops where the repo and machine are trusted, run:
154
162
 
155
163
  ```text
@@ -183,7 +191,7 @@ Version check:
183
191
  ```bash
184
192
  clavue --version
185
193
  npx -y clavue --version
186
- npx -y clavue@8.8.127 --version
194
+ npx -y clavue@8.8.129 --version
187
195
  # available after a global install and launcher setup
188
196
  clavue --version
189
197
  ```