Telemetry and privacy

Release builds of pyscriptc send anonymous usage events to PostHog.
Telemetry exists to answer one question: which unsupported constructs block real users the most, so the roadmap follows demand.

What is sent

• cli.invoked with the subcommand name and version
• compile.finished with duration, exit code, and the list of PSxxxx fence codes hit (codes only, never source text or paths)
• compile.ran when --run executes the binary

Events carry a randomly generated, salted machine hash.
No source code, file paths, hostnames, usernames, or argument values are ever collected.

Opting out

pyscriptc telemetry disable   # persistent off
pyscriptc telemetry status    # current state

Or set PYSC_NO_TELEMETRY=1 or DO_NOT_TRACK=1.
Telemetry is always silent on CI and in development builds built without POSTHOG_PROJECT_TOKEN.

On first use the CLI prints a one-line notice that telemetry is on and how to disable it.