It stops reporting into upstream's accounts

Every build of this fork carried upstream Tabby's own credentials as literals, so its crashes went to Eugeny's Sentry project, its launches to his Mixpanel, and a published artifact would have authenticated against his Keygen distribution account — all under a version string that means nothing there. The updater and the release-notes tab read his releases too, so this build would offer to update itself to a different program. Analytics is removed outright rather than repointed, and the two switches that fed it go with it: a toggle that no longer sends anything is worse than no toggle, because it reads as a choice the user is making.

This fork shipped upstream Tabby's own credentials as literals, and had done since the first commit. Its crashes went to Eugeny's Sentry project, its launches to his Mixpanel, and a published artifact would have authenticated against his Keygen distribution account — all under a version string that means nothing in any of them. The updater and the release-notes tab read his releases, so this build would have offered to update itself to a different program.

The Sentry DSN comes from the environment now, and an absent one skips init entirely rather than initialising a client aimed somewhere else. Mixpanel is gone. Keygen is gone: distribution is GitHub releases only, and the packagecloud step that pushed into eugeny/tabby went with it. The update and release-notes feeds, Website, Source code, Report a problem and FUNDING.yml all point at this project.

• The analytics switches were removed with the analytics. A toggle that no longer sends anything is worse than no toggle, because it reads as a choice the user is making.
• The Discord and Weblate links are upstream's community rather than this project's, and are removed rather than repointed at nothing.
• sentry-upload.mjs guards itself on the same credentials, so the three workflow steps that call it became no-ops instead of failures.

• config.service.ts's https://api.tabby.sh literal is deliberately not changed. It is compared inside a config.version < 7 migration, so changing it changes which users get their sync token cleared. It is a version check, not an endpoint.
• There is no Sentry project to point at yet, so this build reports no crashes anywhere. That is a deliberate silence, not an oversight.