@codacy/verity-cli 0.35.3-experimental.f980d82 → 0.35.4

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

@@ -37,9 +37,15 @@ Use this one report:
 - **`hooks.versions.skew` is set** → tell the user first, in one line, with
   `hooks.versions.skew.remedy`.
 - **`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.
+  already has a Standard file here. `legacyStandard` is an old GATE.md Standard at
+  `.gate/standard.yaml`: init moves it to `.verity/` first. Do not ask question 2,
+  and init sends no profile. The file is this machine's working copy of the
+  team's Standard: init keeps it when it is the team's or the team has none yet
+  (then it shares it), and writes the team's here when the two differ (the file
+  is kept as a copy, `.verity/standard.<time>.yaml`). Reviews read the Standard
+  on the service either way.
+- **`standard.tracked` is true** → `.verity/standard.yaml` is tracked in git, from
+  an install older than 0.36.0. Question 3b applies.
 
 When both are false, also run:
 
@@ -119,6 +125,14 @@ say how many files)
 | `Yes, untrack it (recommended)` | The files stay on disk. Their removal from the index is staged for you to commit. Generated notes stop appearing in every diff. |
 | `No, not now` | Nothing changes. `verity memory track` records it as deliberate. |
 
+**3b — "Stop tracking `.verity/standard.yaml` in git?"** (only when
+`standard.tracked` is true)
+
+| Option | Description |
+|---|---|
+| `Yes, untrack it (recommended)` | Verity keeps the Standard on the service and writes the file on each machine (`verity init`, `verity standard pull`). The file stays on disk here; its removal from the index is staged for you to commit. Teammates lose the file on their next pull and get it back with `verity standard pull`. Reviews are not affected: they read the service. |
+| `No, not now` | Nothing changes. `verity doctor` keeps reporting it; `verity standard untrack` does it later. |
+
 **4 — "Untrack committed Verity state?"** (only when `trackedState.files > 0`;
 say how many files)
 
@@ -201,7 +215,7 @@ can sign the machine in to a different server, and the plugin follows that sign-
 One command. It asks nothing:
 
 ```bash
-verity init --yes [--standard <use|new>] --profile <send|skip> [--telemetry <on|off>] [--untrack-memory] [--untrack-state]
+verity init --yes [--standard <use|new>] --profile <send|skip> [--telemetry <on|off>] [--untrack-memory] [--untrack-standard] [--untrack-state]
 ```
 
 - Question 2a: `Use it` → `--standard use`. `Create a new one from a repo
@@ -210,7 +224,7 @@ verity init --yes [--standard <use|new>] --profile <send|skip> [--telemetry <on|
 - Question 2b: `--profile send` only when the user said yes and signed in.
   Otherwise `--profile skip`.
 - When question 2 was not asked, leave `--standard` and `--profile` off.
-- `--untrack-memory` and `--untrack-state` only on a yes.
+- `--untrack-memory`, `--untrack-standard` and `--untrack-state` only on a yes.
 - Question 5: `--telemetry on` on a yes, `--telemetry off` on a no. When it was
   not asked, leave `--telemetry` off.
 - Do not pass `--moments`. Without it, init keeps the moments the project has,
@@ -235,9 +249,10 @@ verity doctor --json
 
 Summarise from this report and from init's output, not from memory:
 
-- the Standard: **kept**, **adopted** from the team, **written** from the profile
-  (with its rules), or built from the catalogue. When it is a new one that
-  replaced the team's, say which version it replaced;
+- the Standard: **kept**, **adopted** from the team (when the file here differed,
+  say that the old file is kept as a copy and where), **written** from the
+  profile (with its rules), or built from the catalogue. When it is a new one
+  that replaced the team's, say which version it replaced;
 - the moments in effect. Say: "Verity reviews every turn, every commit and every
   push. To change it, run `verity config moments`, or just ask me.";
 - what init removed (superseded skills, duplicate hooks). Those skill folders are

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

@@ -82,10 +82,13 @@ Branch on the same `doctor` output:
 - **`artifacts.standard` is true and `phases.setup.done` is true** → the
   project already has a Standard, derived or adopted. Your job is the part the CLI
   leaves empty: propose 2–5 `custom_patterns` from the codebase, show them, and on
-  the user's agreement add them to `.verity/standard.yaml` and run
-  `verity standard push`. Do NOT rewrite the rest of the Standard — `standard push`
-  auto-versions, so a full re-synthesis lands as the version everybody is then
-  held to.
+  the user's agreement run `verity standard pull` first (the file here is this
+  machine's working copy and can be behind the team's), add them to
+  `.verity/standard.yaml`, and run `verity standard push`. Do NOT rewrite the rest
+  of the Standard — `standard push` auto-versions, so a full re-synthesis lands as
+  the version everybody is then held to. A push that answers "the team's Standard
+  is vN now" means someone changed it since the pull: pull again, re-apply the
+  patterns, push again.
 - **`artifacts.verityMd` is true and the user did not pass `--force`** → already
   configured. Say "Already configured. Run `/verity-setup --force` to
   reconfigure." and stop.
@@ -249,7 +252,11 @@ The `verity` CLI handles YAML→JSON conversion automatically:
 verity standard push
 ```
 
-This reads `.verity/standard.yaml`, converts it to JSON, and uploads it. Verify the output shows `version: 1`.
+This reads `.verity/standard.yaml`, converts it to JSON, and uploads it as the next
+version after the one this machine last saw. Verify the output shows `version: 1`.
+If it answers that the team's Standard moved, run `verity standard pull`, re-apply
+the changes to the pulled file, and push again. The file is machine-local: do not
+commit it.
 
 ### Seed the knowledge base
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/verity-cli",
-  "version": "0.35.3-experimental.f980d82",
+  "version": "0.35.4",
   "description": "CLI for Verity quality gate service",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://verity.md",