@decantr/telemetry 3.8.0 → 3.8.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 +3 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Optional telemetry contracts, privacy filters, clients, and sinks for Decantr.
|
|
4
4
|
|
|
5
|
-
Decantr 3.8 keeps this package for compatibility and future/private deployments. The active hosted product no longer includes registry portal analytics, PostHog dashboards, Supabase rollups, billing funnels, public telemetry ingest, or admin telemetry pages.
|
|
5
|
+
Decantr 3.8.1 keeps this package for compatibility and future/private deployments. The active hosted product no longer includes registry portal analytics, PostHog dashboards, Supabase rollups, billing funnels, public telemetry ingest, or admin telemetry pages.
|
|
6
6
|
|
|
7
7
|
## Product Stance
|
|
8
8
|
|
|
@@ -13,6 +13,7 @@ Allowed signals include command names, package versions, workflow modes, success
|
|
|
13
13
|
## Runtime Posture
|
|
14
14
|
|
|
15
15
|
- CLI telemetry is disabled by default.
|
|
16
|
+
- The CLI has no hosted default sink; callers must configure their own endpoint.
|
|
16
17
|
- MCP does not emit Decantr telemetry.
|
|
17
18
|
- The Fly API is content/reference only.
|
|
18
19
|
- Legacy event names may still contain `registry.*` for Decantr 3.x compatibility.
|
|
@@ -40,6 +41,6 @@ await telemetry.capture({
|
|
|
40
41
|
});
|
|
41
42
|
```
|
|
42
43
|
|
|
43
|
-
Constructing a client
|
|
44
|
+
Constructing a client and choosing a sink are explicit; the package does not auto-start collection or select a Decantr-hosted endpoint.
|
|
44
45
|
|
|
45
46
|
See [security permissions](https://decantr.ai/reference/security-permissions.md).
|