chore(ci): remove @hexclave/* mirror publish from npm-publish workflow

Author: BilalG1

.github/workflows/npm-publish.yaml

@@ -88,34 +88,3 @@ jobs:
 
           git commit -m "chore: update package versions"
           git push origin dev
-
-      # Hexclave rebrand mirror publish (Tier 2). Each publishable `@stackframe/*`
-      # package is re-published as `@hexclave/*` with all cross-deps pinned to one
-      # shared `@hexclave` version. Built artifacts (`dist/`) are also rewritten by
-      # the script so cross-package require()/import specifiers + the build-time
-      # package-version sentinel point at `@hexclave/*` instead of `@stackframe/*`.
-      #
-      # Hardcoded to 1.0.0 — `pnpm publish` skips versions already on npm, so
-      # after the first successful run on main this becomes a no-op. PR 3 in
-      # the rebrand sequence renames the source packages natively to
-      # `@hexclave/*` and deletes this entire mirror flow; until then, 1.0.0
-      # is the one-shot cutover version.
-      #
-      # Runs AFTER `Update package versions on dev` because that step asserts a
-      # clean working tree (`git diff --exit-code HEAD`); the rewrite below
-      # mutates package.json files in-place and would trip that assertion.
-      - name: Checkout main for Hexclave mirror rewrite
-        run: git checkout main
-
-      - name: Rewrite package names to @hexclave/*
-        run: pnpm tsx scripts/rewrite-packages-to-hexclave.ts --version=1.0.0
-
-      - name: Publish @hexclave/* mirror packages
-        # Filter to @hexclave/* so this step's correctness does not depend on
-        # `pnpm publish -r` silently skipping already-published @stackframe/*
-        # versions — pnpm's skip-existing-versions check has historically
-        # failed open on registry edge cases, and unfiltered re-publish of an
-        # existing version would 403 the whole run.
-        run: pnpm publish -r --filter "@hexclave/*" --no-git-checks --access public
-        env:
-          NPM_CONFIG_PROVENANCE: true