HyperFrames CLI gets its own sign-in; signed-in usage is no longer anonymous

Sign in again. Since v0.8.218 (Oct 29), the HyperFrames CLI signs in with its own HyperFrames OAuth client instead of sharing the HeyGen CLI's login, so one tool no longer overwrites the other's sign-in. Existing users need to run hyperframes auth login once after upgrading, and cloud work then bills to your HyperFrames plan, per the release notes. A HEYGEN_API_KEY still works as before.

Telemetry is tied to your account once you sign in. v0.8.216 changed telemetry to identify signed-in CLI users by their HyperFrames user id, and the CLI now says plainly that signed-in usage is not anonymous. Per the docs added in PR #6703, usage counters stay anonymous until you sign in and are linked to your account (email and username) after that. To opt out, run npx hyperframes telemetry disable, or set HYPERFRAMES_NO_TELEMETRY=1 or DO_NOT_TRACK=1. Feedback sent from the CLI rides the same telemetry, so the same rule applies.

Other fixes worth knowing. Render errors now name the kind of missing file rather than its path, and a project .env only sets the CLI's own settings (v0.8.217). On Windows, a locked Chrome log no longer breaks check, snapshot or render; render with no -o writes to the project's renders folder; normalize-audio no longer turns a clip down when it's already quieter than the target (v0.8.219). Playback no longer stalls at a cut, and text-to-speech ignores a foreign PYTHONPATH when looking for its voice package (v0.8.220). Snapshots read each clip once, and Ctrl+C stops preview right away (v0.8.221).

Our take: re-run the login, and if you render client work on a signed-in CLI, decide on telemetry now. Setting HYPERFRAMES_NO_TELEMETRY=1 in a shared machine's shell profile is the simplest way to keep project usage out of anyone's analytics.