Stop committing dist/ to the repo

The dist/ exception predates publishing to npm. Now that consumers
install @patchstack/connect from the registry, the prepare script
builds dist/ on install and the publish workflow builds it before
packing — so there is no need to track build output in git.

- Untrack dist/ and drop the .gitignore exception
- Remove the "Verify committed dist is current" check from CI and
  publish workflows

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: ejntaylor

.github/workflows/ci.yml

@@ -49,9 +49,6 @@ jobs:
       - name: Build
         run: npm run build
 
-      - name: Verify committed dist is current
-        run: git diff --exit-code -- dist
-
       - name: Verify package contents
         run: npm pack --dry-run
 

.github/workflows/publish.yml

@@ -48,9 +48,6 @@ jobs:
       - name: Build
         run: npm run build
 
-      - name: Verify committed dist is current
-        run: git diff --exit-code -- dist
-
       - name: Verify package contents
         run: npm pack --dry-run
 

.gitignore

@@ -3,9 +3,7 @@ node_modules
 # used to exercise the node-modules walker. Keep those tracked.
 !tests/fixtures/**/node_modules
 !tests/fixtures/**/node_modules/**
-# dist/ is committed pre-npm-publish so consumers can `npm install github:patchstack/connect`
-# in sandboxed environments (WebContainer/StackBlitz/Bolt/Lovable) where the `prepare`
-# script can't run `tsup`. Remove this exception once the package is published to npm.
+dist
 *.log
 .DS_Store
 .env