kylon-cli 0.7.4-next.1011 → 0.7.4-next.1012

package/README.md

@@ -810,7 +810,13 @@ sent as `install_id` on every record. It is created before login and reused
 across runs; deleting the file resets it, copying the configuration can
 duplicate it. It identifies an installation, not a device or a person, so these
 are pseudonymous diagnostics. If the installation cannot be read or created,
-telemetry stays off.
+records go out without `install_id`; anonymous ones require it and stay local.
+An entry that cannot be read, is not a regular file, or does not hold a valid
+`cli_…` id counts as damaged and is never replaced, because a saved computer
+connection records the id. Commands that need it (`agent link`, `connect`,
+`onboard`, `login`) stop, name the file, and print commands that first rename
+the entry aside (which never follows a link), then restore the recorded id or
+start over. A link to a valid file is read through, never written.
 
 Set `KYLON_TELEMETRY_DISABLED=1` in the CLI/daemon process environment to turn
 the whole channel off; local diagnostic logs are unchanged. Restart a running

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.7.4-next.1011",
-  "fingerprint": "16889008e0c6528ce2f47c7541a44f45a2e8506fd455e4e21a50ac905749ade3",
-  "source_commit": "d1d7d019de22ba85e95e765f7f77c4f6463b2dc3"
+  "version": "0.7.4-next.1012",
+  "fingerprint": "8c8314cb255b94469799b78da0897741a2c378fdff14d155bd68269a21980cfc",
+  "source_commit": "99845eb105e0eed97a9f9684f2c8b4feb6a47823"
 }