@codacy/verity-cli 0.34.5-experimental.7268b07 → 0.34.5-experimental.a8bee86

package/data/skills/verity-init/SKILL.md

@@ -36,10 +36,12 @@ Use this one report:
 - **`blocked` is true** → show the `prerequisites[].remedy` lines and stop.
 - **`hooks.versions.skew` is set** → tell the user first, in one line, with
   `hooks.versions.skew.remedy`.
-- **`artifacts.standard` is true** → this project already has a Standard here.
-  Do not ask question 2. Init keeps the Standard and sends no profile.
+- **`artifacts.standard` or `artifacts.legacyStandard` is true** → this project
+  already has a Standard here. `legacyStandard` is an old GATE.md Standard at
+  `.gate/standard.yaml`: init moves it to `.verity/` first, then keeps it. Do not
+  ask question 2. Init keeps the Standard and sends no profile.
 
-When `artifacts.standard` is false, also run:
+When both are false, also run:
 
 ```bash
 verity standard history
@@ -98,8 +100,8 @@ contents of their repositories.
 | `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. |
 
 **2b — "Let Verity write review rules for this repository?"** (only when
-`artifacts.standard` is false, 2a does not apply, and the status is `on` or
-`unknown`)
+`artifacts.standard` and `artifacts.legacyStandard` are both false, 2a does not
+apply, and the status is `on` or `unknown`)
 
 | Option | Description |
 |---|---|
@@ -165,7 +167,8 @@ It prints one JSON object on stdout:
   in a terminal later. Go to Step 3.
 
 **After a new sign-in, check the Standard again.** If Step 0 could not run
-`verity standard history` (it failed) and `artifacts.standard` is false, run it
+`verity standard history` (it failed) and `artifacts.standard` and
+`artifacts.legacyStandard` are both false, run it
 now. If it lists versions, ask question 2a now, in its own prompt. Its answer
 replaces the answer to 2b. Also run `verity standard generate --status` again.
 If it prints `off` or `unsupported`, the answer to 2b has no effect: pass
@@ -242,6 +245,15 @@ Summarise from this report and from init's output, not from memory:
   commit;
 - anything untracked, and that the staged removal is the user's to commit;
 - sign-in state;
+- formal verification, when init printed "Formal verification at push: on". Say
+  it as a fact, in init's words: at a push, Verity checks a small model of the
+  riskiest changed function and replays any counterexample on the real code;
+  that function's source is sent to Verity; only a reproduced bug blocks; turn
+  it off with `verity config formal off`. It is a default, like the moments. Do
+  not suggest turning it off, and do not connect it to the user's answers to
+  other questions;
+- when init printed that the kept Standard has no project rules yet, that line
+  and its command (`verity standard generate`);
 - each line of `next`, if any.
 
 ---
@@ -254,3 +266,5 @@ Summarise from this report and from init's output, not from memory:
 - **Do not answer a question for the user**, and do not leave a flag off because
   it seems obvious. An omitted answer is an unattended one.
 - **Do not run plain `verity login`.** See Step 2.
+- **Do not advise turning off a default** (the moments, formal verification)
+  unless the user asks. Say what it does and how to change it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/verity-cli",
-  "version": "0.34.5-experimental.7268b07",
+  "version": "0.34.5-experimental.a8bee86",
   "description": "CLI for Verity quality gate service",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://verity.md",
@@ -37,7 +37,7 @@
     "tree-sitter-javascript": "0.25.0",
     "tree-sitter-python": "0.25.0",
     "tree-sitter-typescript": "0.23.2",
-    "tsx": "^4.21.0",
+    "tsx": "^4.23.15",
     "typescript": "^5.4",
     "web-tree-sitter": "0.27.0"
   },