Remove @azphalt/registry-store-vercel; fix changesets naming a non-workspace package

[HereLiesAz]

Remove @azphalt/registry-store-vercel

This was the Neon + Vercel Blob RegistryStore from the retired Vercel storefront. Nothing imports it.

• Deletes packages/registry-store-vercel and its lockfile entries (the lockfile was regenerated by pnpm install, not edited by hand).
• Removes its rows from README.md and docs/ARCHITECTURE.md.
• Drops its lines from the pending apache-2 and latest-stable-dependencies changesets. Otherwise changeset version would fail on a package that no longer exists.
• Reworded the doc comments in packages/registry that pointed at its Postgres stores as the example of a durable store.
• Marks the 2026-07-14 design doc as retired.

This doesn't stop the Vercel PR builds. Those come from the Vercel project still being connected to the repo, which is fixed in Vercel's settings, not here.

Fix the release pipeline

changeset status fails on main today with Found changeset cmp-llm-disclosure for package @azphalt/storefront-cmp which is not in the workspace. storefront-cmp is deliberately outside the pnpm workspace, so any changeset naming it blocks changeset version.

• cmp-llm-disclosure.md is deleted. I added it in Store app: disclose llm listings before install #233 and it named only that package.
• The storefront-cmp line is removed from play-application-id.md; its worker line stays.

Verification

• pnpm install --frozen-lockfile passes.
• pnpm -r typecheck is clean.
• @azphalt/registry passes 126/126 tests.
• npx changeset status now passes.

After merging (user-side)

The already published npm versions stay up. To steer people away from them:

npm deprecate @azphalt/registry-store-vercel "Retired with the Vercel storefront; implement the RegistryStore interfaces from @azphalt/registry directly."

🤖 Generated with Claude Code

https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv

---

Generated by Claude Code

Summary by Sourcery

Remove the retired Vercel registry store and clean up invalid changeset references so the workspace release pipeline remains valid.

Bug Fixes:

• Remove obsolete changesets that referenced the retired Vercel registry store and the non-workspace storefront package, allowing Changesets status and versioning to complete successfully.

Enhancements:

• Retire and remove the Neon/Vercel Blob registry store package and its repository documentation references.
• Update registry interface documentation to describe durable implementations without depending on the retired package.

Build:

• Regenerate the pnpm lockfile after removing the retired package.

Documentation:

• Mark the durable registry store design as retired and remove the package from the project architecture and package listings.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
azphalt	Error		Sep 27, 2026 10:32pm UTC

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Retires and removes the unused @azphalt/registry-store-vercel workspace package, cleans documentation and registry comments, regenerates the lockfile, and fixes pending changesets so release commands no longer reference deleted or non-workspace packages.

Flow diagram for changeset validation after package retirement

flowchart LR
    Changesets[Pending changesets] --> Status[changeset status]
    Status --> Workspace[Workspace package resolution]
    Workspace -->|all package names valid| Version[changeset version succeeds]
    Workspace -->|deleted or non-workspace package referenced| Failure[Release pipeline fails]
    Retired[Remove registry-store-vercel entries] --> Changesets
    NonWorkspace[Remove storefront-cmp entries] --> Changesets

Loading

File-Level Changes

Change	Details	Files
Removed the retired Vercel-backed registry store package and all repository references to it.	Deleted the package implementation, metadata, changelog, and contract tests. Removed the package from README and architecture documentation. Updated registry interface comments to describe durable implementations generically. Marked the related durable-store design document as retired.	packages/registry-store-vercel/CHANGELOG.md packages/registry-store-vercel/package.json packages/registry-store-vercel/readme.md packages/registry-store-vercel/src/entitlements.ts packages/registry-store-vercel/src/index.ts packages/registry-store-vercel/src/schema.ts packages/registry-store-vercel/src/seller-accounts.ts packages/registry-store-vercel/src/sessions.ts packages/registry-store-vercel/src/store.ts packages/registry-store-vercel/src/subscription-records.ts packages/registry-store-vercel/test/store-contract.test.ts packages/registry-store-vercel/test/store-contract.ts packages/registry-store-vercel/tsconfig.json README.md docs/ARCHITECTURE.md docs/superpowers/specs/2026-07-14-durable-registry-store-design.md packages/registry/src/consignment.ts packages/registry/src/entitlement-store.ts packages/registry/src/seller-account-store.ts packages/registry/src/subscription-store.ts
Removed changeset entries that reference packages outside the workspace or the deleted package so Changesets can calculate releases successfully.	Deleted the changeset naming @azphalt/storefront-cmp. Removed @azphalt/storefront-cmp while preserving the storefront-worker release entry. Removed deleted-package entries from pending release changesets and updated the dependency-release description.	.changeset/cmp-llm-disclosure.md .changeset/play-application-id.md .changeset/apache-2.md .changeset/latest-stable-dependencies.md
Regenerated the pnpm lockfile after removing the workspace package.	Removed the deleted package and its dependency resolution data from the lockfile.	pnpm-lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Failed ❌ View logs ↗		999de67	2026-09-27T22:32:56.377Z	View logs ↗

[HereLiesAz]

Two checks here are red for reasons outside this PR:

• Workers Builds: azphalt fails on every PR branch. It's the Cloudflare dashboard's own Git build for branch previews, and it fails before building anything. Fix it by disconnecting Workers Builds or correcting its build settings, not in code.
• Vercel fails because the retired Vercel project is still connected to the repo. Deleting or disconnecting the project stops it.

The checks that actually test this PR are the validate_* jobs.

---

Generated by Claude Code

[sourcery-ai]

Sorry @HereLiesAz, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 22 hours and 47 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[HereLiesAz]

OpenCode security review

⚠️ Review unavailable. Neither model answered; see the shared workflow run. This is not a finding about the pull request.