@decantr/cli 2.1.1 → 2.3.0

package/README.md

@@ -81,6 +81,8 @@ decantr audit
 decantr check
 decantr health --ci --fail-on error
 decantr studio --port 4319 --host 127.0.0.1
+decantr telemetry status
+decantr telemetry link --enable --org <org-slug>
 decantr content-health --ci --fail-on error
 decantr registry summary --namespace @official --json
 decantr showcase verification --json
@@ -97,12 +99,13 @@ decantr health --markdown --output health.md
 decantr health --ci --fail-on error
 decantr health --ci --fail-on warn
 decantr health --prompt <finding-id>
+decantr health --json --output decantr-health.json
 decantr health init-ci
 decantr health init-ci --fail-on warn --cli-version latest --force
 decantr health init-ci --project apps/registry
 ```
 
-Use `--json` for machines and schema validation, `--markdown` for CI summaries, and `--prompt <finding-id>` when you want a scoped remediation prompt for an AI assistant. `--ci --fail-on error` fails only when blocking errors exist; `--ci --fail-on warn` also fails on warnings.
+Use `--json` for machines and schema validation, `--markdown` for CI summaries, and `--prompt <finding-id>` when you want a scoped remediation prompt for an AI assistant. The prompt command prints instructions only; it does not modify source files. `--ci --fail-on error` fails only when blocking errors exist; `--ci --fail-on warn` also fails on warnings.
 
 `decantr health init-ci` installs `.github/workflows/decantr-health.yml` for GitHub Actions. The generated workflow installs project dependencies, writes `decantr-health.json`, gates with `decantr health --ci --fail-on error --markdown --output decantr-health.md`, appends the markdown report to the GitHub step summary, and uploads both files as artifacts. Use `--force` to replace an existing workflow, `--fail-on warn` for stricter repositories, or `--cli-version <version|latest>` to pin the package used by CI. In monorepos, add `--project <path>` from the repository root; dependency install stays at the root while health runs inside the app contract and uploads artifacts from that project path.
 
@@ -111,11 +114,32 @@ Use `--json` for machines and schema validation, `--markdown` for CI summaries,
 ```bash
 decantr studio
 decantr studio --port 4319 --host 127.0.0.1
+decantr studio --report decantr-health.json
 ```
 
-Studio is for local triage, not Decantr admin telemetry. The tabs cover Overview, Routes, Drift, Findings, Remediation, CI, and Packs without uploading source code, prompts, file paths, or project data.
+Studio is for local triage, not Decantr admin telemetry. The Overview keeps the first decision simple: pick the issue to fix first, review the full AI repair prompt before copying it, switch to manual guidance or commands, and expand project details when route/runtime/pack evidence matters. The tabs cover Overview, Routes, Drift, Findings, Remediation, CI, and Packs without uploading source code, prompts, file paths, or project data.
 
-If the project has explicitly enabled Decantr CLI telemetry, `new --telemetry`, `init --telemetry`, `check --telemetry`, `health`, and `studio` emit only aggregate product-activation metadata such as lifecycle command outcome, status, score, finding counts, CI failure outcome, Studio usage, and remediation prompt requests. They never upload the health report, finding evidence, local paths, route names, source code, or prompt text.
+Use report mode for customer-controlled reporting from CI artifacts:
+
+```bash
+decantr health --json --output decantr-health.json
+decantr studio --report decantr-health.json
+```
+
+If the project has explicitly enabled Decantr CLI telemetry, `new --telemetry`, `init --telemetry`, `analyze`, `check --telemetry`, `health`, and `studio` emit only aggregate product-activation metadata such as lifecycle command outcome, analyze counts, status, score, finding counts, CI failure outcome, Studio usage, and remediation prompt requests. They never upload the health report, finding evidence, local paths, route names, source code, package names, or prompt text.
+
+## Opted-In Telemetry Identity
+
+`decantr telemetry` lets users inspect and link the opaque install/project ids used by opted-in CLI telemetry. This is how customer org attribution becomes durable without collecting repository names, local paths, source code, prompts, private package slugs, emails, or secrets.
+
+```bash
+decantr telemetry status
+decantr telemetry status --json
+decantr login --api-key=<key>
+decantr telemetry link --enable --org <org-slug>
+```
+
+`telemetry link` calls the hosted `/v1/me/telemetry-link` endpoint with only opaque ids, optional org slug, and optional label. The API verifies org membership, writes `telemetry_identity_aliases`, clears the actor-resolution cache, audit logs the change, and emits `telemetry.identity_linked`.
 
 ## Content Health
 

package/dist/bin.js

@@ -1,4 +1,4 @@
 #!/usr/bin/env node
-import "./chunk-GOX5EJ56.js";
+import "./chunk-FSZ6OIAC.js";
 import "./chunk-WDA4SHIQ.js";
-import "./chunk-JYEEXSUX.js";
+import "./chunk-IEW2QFYI.js";

package/dist/{chunk-DPFORHLL.js → chunk-3H3HWDJA.js}

@@ -1,11 +1,11 @@
 import {
   collectCheckIssues
-} from "./chunk-LLQCXOHK.js";
+} from "./chunk-NBJCO4G5.js";
 import {
   sendProjectHealthCiFailedTelemetry,
   sendProjectHealthPromptTelemetry,
   sendProjectHealthReportTelemetry
-} from "./chunk-JYEEXSUX.js";
+} from "./chunk-IEW2QFYI.js";
 
 // src/commands/health.ts
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "fs";