@codacy/verity-cli 0.33.3-experimental.80b064d → 0.33.3-experimental.911f315

package/CHANGELOG.md

@@ -64,6 +64,31 @@ installs are untouched.
   which is the ordinary case for someone whose first Verity install *is* the
   plugin.
 
+### 🎯 `/verity:init` does everything `verity init` does, in the session
+
+Under the plugin, setup used to stop short of the terminal flow: `/verity:init`
+asked about moments and intensity, then ran `verity init --yes`, which answered
+every other question for you. There was no telemetry step at all (VRT-223), a
+tracked knowledge graph or committed state was left alone without asking, and
+sign-in meant leaving Claude Code for a terminal.
+
+- **Every question is asked, in one prompt.** Moments, intensity, telemetry
+  (when it is off), whether to sign in, and — only when they apply — whether to
+  untrack the knowledge graph or committed Verity state. A re-run pre-selects
+  what you chose last time.
+- **Sign in without leaving the session.** `verity login --start` shows the
+  GitHub code and returns at once; `verity login --finish` waits for your
+  approval and logs you in. The code lives in `~/.verity/pending-login.json`
+  (owner-only, expires with the code, single use), and `--finish` refuses a code
+  started for a different Verity service. Plain `verity login` is unchanged.
+- **`verity init` takes the new answers as flags too:** `--telemetry on|off`,
+  `--untrack-memory` and `--untrack-state`. An unrecognised telemetry value is
+  refused, and `--telemetry off` over a running export turns it off.
+- **`verity doctor --json` reports `trackedState.files` and `memory.optedOut`**,
+  which is how the skill knows whether the untrack questions apply.
+- **`verity telemetry install|uninstall` update `.verity/setup.json`**, so a
+  request deferred until sign-in stops being reported as still to do.
+
 ## [0.33.3] — 2026-09-24
 
 **The knowledge seed runs once per project, not once per checkout.**

package/README.md

@@ -66,6 +66,8 @@ the one command to run instead. `verity setup` is an alias for the same command.
 | `--no-setup` | Stop after the deterministic phase; don't launch Claude Code |
 | `--no-adopt` | Don't offer the Standard the service already holds for this repo — synthesize a fresh one. Skips the request entirely |
 | `--force` | Overwrite the installed skills even when they differ |
+| `--moments <list>` · `--intensity <level>` · `--telemetry on\|off` | Answer that question without being asked. `/verity:init` asks in the Claude Code session and passes these down |
+| `--untrack-memory` · `--untrack-state` | Answer yes to the matching "stop tracking it in git?" question without being asked |
 
 Run `verity doctor` any time to see prerequisites, which phase is done, the hook
 wiring, and what is still missing.
@@ -154,6 +156,7 @@ No re-setup needed: your token, Standard, and run history all carry over.
 | **Auth & Config** | |
 | `verity login` | Log in once with GitHub — grants access to every repository you can write to |
 | `verity login --force` | Re-authenticate and refresh your grants (also how stale grants heal) |
+| `verity login --start` · `--finish` | The same login in two steps, for a caller that cannot hold a terminal open (an agent's tool call): `--start` prints the code as JSON and returns, `--finish` waits for approval (`--wait <s>`, default 100) and logs in. `--cancel` drops a pending code |
 | `verity auth register` | Register a single project (per-repo token; superseded by `verity login`) |
 | `verity token create --name <name>` | Mint a service token for CI (`--expires <days>` optional) |
 | `verity token list` | List this repository's tokens (ids and metadata only) |