chore: rename packages to @standard-server/* and drop the homepage domain

[dinwwwh]

Renames the npm scope from @standardserver/* to @standard-server/* across the whole monorepo and removes the project website, since the project no longer has a domain. Every manifest, source import, test, bench, playground, README, and the lockfile now use the new scope, and nothing in the repo references standardserver.dev anymore.

Changes

• All seven publishable packages plus the Bun/Deno test packages and playgrounds are renamed to @standard-server/*; the root package is @standard-server/repo.
• The homepage field is removed from every manifest. Playground READMEs link to the GitHub repository instead of the old domain.
• Repository URLs and README badges (codecov, CodSpeed, DeepWiki, license) now point at middleapi/standard-server, matching the actual GitHub slug. The manifests previously referenced middleapi/standardserver, which no longer matched the remote.
• The Symbol.for registry keys that tag event-stream values are now STANDARD_SERVER_EVENT_META and STANDARD_SERVER_EVENT_SOURCE. Values tagged by the old @standardserver/core are not recognized by the renamed package; the scope change already prevents the two from being installed as the same dependency, so this does not affect a normal upgrade.
• The npm keyword is standard-server. Markdown tables were realigned by the eslint fixer.

Testing

• pnpm i --frozen-lockfile succeeds, so the lockfile matches the renamed manifests.
• Lint, type-check, and sherif pass.
• Root vitest suite (1082 tests), Bun suite, and Deno suite pass.
• unbuild of all packages succeeds and the built output imports @standard-server/* as externals.

Before releasing

• The @standard-server npm scope must be claimed for the org; the release workflow publishes under it with --access=public.
• The GitHub repository settings still list https://standardserver.dev as the homepage URL. That is a repo setting, not a file in this PR.

[pkg-pr-new]

• @standard-server/hono-node-playground
• @standard-server/node-http-playground

@standard-server/aws-lambda

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/aws-lambda@88

@standard-server/core

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/core@88

@standard-server/fastify

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/fastify@88

@standard-server/fetch

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/fetch@88

@standard-server/node

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/node@88

@standard-server/peer

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/peer@88

@standard-server/shared

npm i https://pkg.pr.new/middleapi/standard-server/@standard-server/shared@88

commit: b693dc8

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 108 skipped benchmarks¹

---

_{Comparing claude/rename-package-standard-server-4f8e22 (b693dc8) with main (388fe25)²}

Footnotes

1. 108 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. No successful run was found on main (923ba83) during the generation of this report, so 388fe25 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[pullfrog]

✅ No new issues found.

Reviewed changes

• Scope rename — all seven publishable packages plus the root @standard-server/repo, the Bun/Deno test packages, and both playgrounds are renamed from @standardserver/* to @standard-server/*; every source import, manifest dependency, code comment, and pnpm-lock.yaml importer entry is updated consistently, and pnpm i --frozen-lockfile verifies the lockfile matches.
• Homepage dropped, repo metadata corrected — the homepage: https://standardserver.dev field is removed from every manifest; repository.url, codecov / CodSpeed / DeepWiki / license / npm badges, and playground links now point at middleapi/standard-server or the new scope; the npm keyword is normalized to standard-server.
• Interop keys preserved — packages/core/src/event-stream/meta.ts keeps its Symbol.for('STANDARDSERVER_EVENT_META') / STANDARDSERVER_EVENT_SOURCE registry keys so old and new package versions stay interoperable in a shared process, as the PR notes.

I verified the tree end-to-end: no standardserver (old scope or domain) remains anywhere, including .github/ workflows, scripts/, and the lockfile. The one external prerequisite — claiming the @standard-server npm scope before the release workflow runs — is already flagged in the PR body.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (default — pick a model for stronger reviews) ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes

• Renamed the interop symbol registry keys — the follow-up commit b693dc8 changes the two Symbol.for keys in packages/core/src/event-stream/meta.ts from STANDARDSERVER_EVENT_META / STANDARDSERVER_EVENT_SOURCE to STANDARD_SERVER_EVENT_META / STANDARD_SERVER_EVENT_SOURCE, retiring the last STANDARDSERVER tokens in the tree. The keys are read only through the module-local EVENT_META_SYMBOL / EVENT_SOURCE_SYMBOL constants and the public withEventMeta / unwrapEvent / getEventMeta API, so no other package is affected. The one behavioral consequence — values tagged by the old @standardserver/core scope are no longer recognized — is documented in both the commit message and the PR body, and the scope rename already prevents the two packages from being installed as the same dependency.

I reran the core event-stream test suite (4 files, 51 tests — all pass) and grep-verified there are zero remaining standardserver references in the tree.

  ^{｜ View workflow run ｜ Using DeepSeek Flash (default — pick a model for stronger reviews) ｜ 𝕏}