@codacy/verity-cli 0.35.0-experimental.3a13a5e → 0.35.0-experimental.7c5e75b

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.
@@ -50,26 +50,8 @@ verity standard history
50
50
  - **It prints "No Standard versions found."** → question 2 is **2b**.
51
51
  - **It fails** (for example, not signed in) → question 2 is **2b** for now.
52
52
  Step 2 checks again after sign-in.
53
-
54
- Then check whether the service writes project rules for this project:
55
-
56
- ```bash
57
- verity standard generate --status
58
- ```
59
-
60
- It prints one word, and sends nothing:
61
-
62
- - **`on`** or **`unknown`** → ask 2b, and offer "Create a new one from a repo
63
- profile" in 2a.
64
- - **`off`** or **`unsupported`** → the service would not use a profile. Do not
65
- ask 2b, and do not offer "Create a new one from a repo profile" in 2a.
66
- Pass `--profile skip`.
67
- - **It fails** (not signed in) → decide as for `unknown`. Step 2 runs it again
68
- after sign-in.
69
53
  - **`memory.trackedFiles > 0` and `memory.optedOut` is false** → question 3 applies.
70
54
  - **`trackedState.files > 0`** → question 4 applies.
71
- - **`telemetry.enabled` is false and `answers.telemetry` is not `declined`** →
72
- question 5 applies. An earlier "no" is an answer: do not ask again.
73
55
 
74
56
  ## Step 1: Ask, once, in one prompt
75
57
 
@@ -98,8 +80,7 @@ contents of their repositories.
98
80
  | `Create a new one with the built-in rules` | The new Standard becomes the next version for the whole team. It has the built-in rules only. Nothing is sent. |
99
81
 
100
82
  **2b — "Let Verity write review rules for this repository?"** (only when
101
- `artifacts.standard` is false, 2a does not apply, and the status is `on` or
102
- `unknown`)
83
+ `artifacts.standard` is false and 2a does not apply)
103
84
 
104
85
  | Option | Description |
105
86
  |---|---|
@@ -125,17 +106,6 @@ say how many files)
125
106
  | `Yes, untrack it (recommended)` | These files are machine-local and can include copies of flagged secrets. The files stay on disk, and the removal is staged. |
126
107
  | `No, not now` | Nothing changes. |
127
108
 
128
- **5 — "Send Claude Code cost and usage from this machine to Verity?"** (only
129
- when it applies)
130
-
131
- | Option | Description |
132
- |---|---|
133
- | `Yes (recommended)` | Token counts, cost, models, tool names and the repository name, from every Claude Code session on this machine. No prompts, no code, no file contents. It needs sign-in. See it on the /usage page. Turn it off any time: `verity telemetry uninstall`. |
134
- | `No` | Nothing changes, and init does not ask again. Turn it on later: `verity telemetry install`. |
135
-
136
- Say that the scope is the whole machine: Claude Code takes these settings only
137
- from user settings, never from one project.
138
-
139
109
  Do not ask when Verity reviews. All three moments are on by default: each turn,
140
110
  each commit and each push. Step 4 tells the user how to change them.
141
111
 
@@ -167,9 +137,7 @@ It prints one JSON object on stdout:
167
137
  **After a new sign-in, check the Standard again.** If Step 0 could not run
168
138
  `verity standard history` (it failed) and `artifacts.standard` is false, run it
169
139
  now. If it lists versions, ask question 2a now, in its own prompt. Its answer
170
- replaces the answer to 2b. Also run `verity standard generate --status` again.
171
- If it prints `off` or `unsupported`, the answer to 2b has no effect: pass
172
- `--profile skip`.
140
+ replaces the answer to 2b.
173
141
 
174
142
  When the user says it is approved, or asks you to check:
175
143
 
@@ -198,7 +166,7 @@ can sign the machine in to a different server, and the plugin follows that sign-
198
166
  One command. It asks nothing:
199
167
 
200
168
  ```bash
201
- verity init --yes [--standard <use|new>] --profile <send|skip> [--telemetry <on|off>] [--untrack-memory] [--untrack-state]
169
+ verity init --yes [--standard <use|new>] --profile <send|skip> [--untrack-memory] [--untrack-state]
202
170
  ```
203
171
 
204
172
  - Question 2a: `Use it` → `--standard use`. `Create a new one from a repo
@@ -208,10 +176,8 @@ verity init --yes [--standard <use|new>] --profile <send|skip> [--telemetry <on|
208
176
  Otherwise `--profile skip`.
209
177
  - When question 2 was not asked, leave `--standard` and `--profile` off.
210
178
  - `--untrack-memory` and `--untrack-state` only on a yes.
211
- - Question 5: `--telemetry on` on a yes, `--telemetry off` on a no. When it was
212
- not asked, leave `--telemetry` off.
213
- - Do not pass `--moments`. Without it, init keeps the moments the project has,
214
- or turns on all three for a new project.
179
+ - Do not pass `--moments` or `--telemetry`. Without them, init keeps the moments
180
+ the project has, or turns on all three for a new project.
215
181
  - If init exits non-zero, show its error and stop.
216
182
 
217
183
  Init is idempotent. It removes the project's own `.claude/skills/verity-*` copies
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@codacy/verity-cli",
3
- "version": "0.35.0-experimental.3a13a5e",
3
+ "version": "0.35.0-experimental.7c5e75b",
4
4
  "description": "CLI for Verity quality gate service",
5
5
  "license": "SEE LICENSE IN LICENSE",
6
6
  "homepage": "https://verity.md",