Sando 0.7.0 — opt-in adoption telemetry

Sando 0.7.0 — Optional adoption and retention telemetry

• Add separate, default-off installation-activity telemetry. Existing anonymous
  telemetry consent does not enable it.
• After explicit opt-in, record a random per-host/profile installation ID,
  activity date and plugin version. No account, hardware fingerprint, prompts,
  paths or tool-output content is included.
• Support observed active installations, latest active versions, weekly
  retention, 30-day inactivity and reactivation through a private reducer and
  aggregate dashboard. These are opt-in observations, not total users or
  confirmed uninstall counts.
• Respect DO_NOT_TRACK, consent revocation and disable/re-enable during
  retries. Disabling clears local IDs and queued observations; it does not
  delete server history already received.
• Enforce consent on existing F1/F4 telemetry and preserve original event
  timestamps. Keep explicitly configured local diagnostic files separate.

Enable or disable

For npm installations:

node node_modules/sandoichi/src/adoption-cli.mjs status
node node_modules/sandoichi/src/adoption-cli.mjs enable
node node_modules/sandoichi/src/adoption-cli.mjs disable

For Claude/Codex marketplace installations, use lib/adoption-cli.mjs inside
the installed Sando plugin directory. Enabling requires an interactive prompt.
See TELEMETRY.md
for retention, privacy and control details. New metrics are not backfilled from
older anonymous telemetry.