chore: add description and keywords to package manifests

[dinwwwh]

Adds a description and keywords to every publishable package manifest — the two fields npm search ranks on, and both were missing across the ecosystem. The packages now surface in npm searches for their runtime or framework (fetch, node, fastify, aws-lambda, websocket) instead of only exact-name lookups.

Notes

• Descriptions are written from each package's README, leading with searchable terms (runtime/framework name plus "Standard Server") rather than boilerplate.
• @standardserver/shared is described as internal with a minimal keyword set so it doesn't compete with the real entry points in search results.
• Field placement follows the oRPC manifest style: description after version, keywords after repository.
• Additions only; passes eslint, sherif, and JSON validation.

[pkg-pr-new]

• @standardserver/hono-node-playground
• @standardserver/node-http-playground

@standardserver/aws-lambda

npm i https://pkg.pr.new/@standardserver/aws-lambda@73

@standardserver/core

npm i https://pkg.pr.new/@standardserver/core@73

@standardserver/fastify

npm i https://pkg.pr.new/@standardserver/fastify@73

@standardserver/fetch

npm i https://pkg.pr.new/@standardserver/fetch@73

@standardserver/node

npm i https://pkg.pr.new/@standardserver/node@73

@standardserver/peer

npm i https://pkg.pr.new/@standardserver/peer@73

@standardserver/shared

npm i https://pkg.pr.new/@standardserver/shared@73

commit: 3d30c54

[pullfrog]

✅ No new issues found.

Reviewed changes

• description on all 7 package manifests — Adds a one-line description after version to aws-lambda, core, fastify, fetch, node, peer, and shared, sourced from each package's README and leading with the searchable runtime/framework term.
• keywords on all 7 package manifests — Adds a keywords array after repository per manifest, leading with standardserver and the runtime/framework name; @standardserver/shared carries a minimal internal set per the PR's stated intent.

All 7 manifest files parse as valid JSON, field placement is consistent, and I spot-checked each description against its README — the claims (e.g. node as HTTP/2 on IncomingMessage/ServerResponse, fetch covering Deno/Bun/workers, peer over WebSocket/MessagePort) all check out. Metadata-only, no behavioral surface; nothing blocking.

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 26 untouched benchmarks
⏩ 108 skipped benchmarks¹

---

_{Comparing claude/package-json-seo-576f00 (3d30c54) with main (9892ebd)}

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. ↩