lobstah 0.6.10 → 0.7.1

package/README.md

@@ -289,10 +289,42 @@ harnesses, and by fault-injection drills. A SIGKILL'd runner respawns and
 completes. A SIGSTOP'd one is classified wedged, killed cleanly, and recovers
 with a nudge.
 
+## Telemetry 📊
+
+lobstah shares an anonymous daily count of its work, **on by default**. Once
+per UTC day the daemon sends `catches: {today, total}` for the UTC day and
+all-time, plus up to 100 `traps: [{name, today, harness, model, config}]` entries with automatically
+generated names and recorded provenance. Custom names (`--name`) and older
+names with unknown provenance stay local; their catches remain in the totals.
+Names are not hashed. A `helm` snapshot and up to 100 headless `byWorker`
+count buckets include harness, catalog-only model id, and nullable reasoning
+effort/permission-mode enums. Unknown observations stay null; custom or
+unrecognised model ids become `other`. No arbitrary config is sent.
+The payload also includes the lobstah
+version, OS family, CPU architecture, the UTC date, and a random install id
+made on your machine. It never sends repository names or paths, code, briefs,
+session ids, PR URLs, hostnames, or usernames. Hooks never send
+anything, and nothing is sent until a one-time notice has been shown in your
+terminal. The counts feed a project-wide `🦞 N` badge. Per-install rows are
+deleted after 90 days, as are per-trap and worker/config rows; retained daily
+totals have only counts, including harness/model aggregates, no names or config.
+
+- `lobstah telemetry show` prints the exact JSON that would be sent.
+- `lobstah telemetry status` shows whether it is on and why.
+- Turn it off with any one of: `lobstah telemetry disable`,
+  `[telemetry] share = false` in `~/.lobstah/config.toml`,
+  `LOBSTAH_TELEMETRY=0`, `DO_NOT_TRACK=1`, or `CI` set.
+
+No release sends anything yet: the endpoint is not set. Everything about it,
+including who receives it and how long it is kept, is in
+[PRIVACY.md](PRIVACY.md).
+
 ## Non-goals
 
 No webhooks or inbound listeners, no merge decisions in core, no tracker
-vocabulary in core, no hosted service.
+vocabulary in core, no hosted service (the one exception is the small
+anonymous telemetry endpoint in [`services/telemetry`](services/telemetry),
+which you can turn off).
 
 ## License