@decantr/cli 2.1.2 → 2.3.1

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.
package/README.md CHANGED
@@ -81,6 +81,9 @@ decantr audit
81
81
  decantr check
82
82
  decantr health --ci --fail-on error
83
83
  decantr studio --port 4319 --host 127.0.0.1
84
+ decantr telemetry status
85
+ decantr telemetry explain
86
+ decantr telemetry link --enable --org <org-slug>
84
87
  decantr content-health --ci --fail-on error
85
88
  decantr registry summary --namespace @official --json
86
89
  decantr showcase verification --json
@@ -124,7 +127,24 @@ decantr health --json --output decantr-health.json
124
127
  decantr studio --report decantr-health.json
125
128
  ```
126
129
 
127
- 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.
130
+ 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.
131
+
132
+ ## Opted-In Telemetry Identity
133
+
134
+ `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.
135
+
136
+ ```bash
137
+ decantr telemetry status
138
+ decantr telemetry status --json
139
+ decantr telemetry explain
140
+ decantr telemetry explain --json
141
+ decantr login --api-key=<key>
142
+ decantr telemetry link --enable --org <org-slug>
143
+ ```
144
+
145
+ `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`.
146
+
147
+ `telemetry explain` prints the CLI event catalog subset, aggregate field categories, current opaque ids if they already exist, and the explicit never-collected list. It is designed for security review and customer trust conversations before a team opts in.
128
148
 
129
149
  ## Content Health
130
150
 
package/dist/bin.js CHANGED
@@ -1,4 +1,4 @@
1
1
  #!/usr/bin/env node
2
- import "./chunk-3SULF2JT.js";
2
+ import "./chunk-2JWVKBNB.js";
3
3
  import "./chunk-WDA4SHIQ.js";
4
- import "./chunk-JYEEXSUX.js";
4
+ import "./chunk-IEW2QFYI.js";