Fix stale in-repo READMEs #255

Several READMEs describe APIs that no longer exist, and 6 of the 11 READMEs with TypeScript examples don't compile against master (checked with tsc, strict, nodenext, against the built packages). This issue fixes them and gives every package README the same shape, with the docs site (#250, merged in #318) as the source of truth.

Depends on: #250, merged in #318: VitePress in docs/ (base is /bus/), hosted on GitHub Pages at https://node-ts.github.io/bus, with snippets in docs/snippets/**/*.ts. Start after #295 merges, since it rewrites four of these READMEs.
Blocks: #256, which owns the root README's pitch, above-the-fold example, badges and npm metadata, and #263.

Decisions

• Depth: a hybrid. A README has install, a minimal example and, for adapters, the configuration table. Concepts and behaviour deep dives go on the site.
• Snippets: README code blocks come from the same compiled docs/snippets/**/*.ts files as the site, synced by a script whose --check mode runs in CI.
• Badges: only an npm version badge in each package README. The root README's badges are left to Discoverability: npm keywords, GitHub metadata and README above the fold #256.
• Nested READMEs: delete every packages/bus-core/src/**/README.md and move what's still true to the site.
• Sequencing: wait for Docs: move bus.node-ts.com into the repo as docs-as-code #250. The one exception is bus-core's Bus.configure().initialize() snippet, which is fixed in generate self-registering message types to restore dates and nested classes without decorators #295.
• generate self-registering message types to restore dates and nested classes without decorators #295: merges as is, and its long README content is trimmed to the template here.
• Docs links: point to the latest docs, not a versioned path, at https://node-ts.github.io/bus/<page> (not bus.node-ts.com, which only redirects there until the domain lapses). Each link is checked against the real pages in docs/.
• Low maintenance: the maintainer doesn't moderate or support a community, so READMEs have no Discussions link and no support or community wording.
• Docs ship with the change: anything still true that's removed from a README is added to the right docs/ page in the same PR, with its snippets in docs/snippets.
• package.json metadata: move the docs into the repo, hosted on github pages #318 set every package's homepage to the docs site. The wrong descriptions are handed to Discoverability: npm keywords, GitHub metadata and README above the fold #256.
• Development sections in adapter READMEs: removed, with local infra covered by docker compose up in CONTRIBUTING.md (Community health: CONTRIBUTING, templates, triage #257, merged).
• Changesets: READMEs ship in the npm packages, so the PR adds a patch changeset for every package whose README changes.

README template

# @node-ts/<package>

<One sentence: what it is, and which @node-ts/bus extension point it fills.>

[![npm](https://img.shields.io/npm/v/@node-ts/<package>)](https://www.npmjs.com/package/@node-ts/<package>)

**[Documentation](https://node-ts.github.io/bus/<page for this package>)** · [Changelog](https://github.com/node-ts/bus/blob/master/packages/<package>/CHANGELOG.md)

## Installation

Requires Node.js 24 or later.

    npm i @node-ts/<package> @node-ts/bus-core <required peers>

## Usage

<The smallest complete example, synced from docs/snippets: imports, construct, register with Bus.configure(), build(), initialize(), start().>

## Configuration        <!-- adapters only -->

<An Option | Default | Description table that matches the configuration interface's JSDoc and @default values.>

## Learn more

- <2 to 4 links to the relevant site pages>

Rules:

• Use only absolute URLs, because npm doesn't resolve relative links. Link to the latest docs.
• Don't include a Development section, or Discussions, support or community links.
• Short warnings the user needs before first use stay in, such as "set persistentMessages: true in production". Other behaviour goes on the site.

Findings

Status: ✅ already fixed on master · 🔀 fixed in #295 · ➡️ handed to another issue · blank = to do here.

What moves to the docs site (#250)

• Everything in the five packages/bus-core/src/**/README.md files that's still true:
  • handler semantics, long-running processes, poison messages;
  • custom and system message handlers;
  • workflow concepts, retried startedBy and discarding;
  • logger configuration;
  • implementing a transport or persistence.
• Adapter deep dives:
  • the RabbitMQ retry topology and the persistentMessages trade-off;
  • SQS autoProvision: false and IAM;
  • Lambda partial batch failures and FIFO behaviour.
• From generate self-registering message types to restore dates and nested classes without decorators #295: the messages and serialization guide (plain data vs generated types, limits) and bus-cli's supported types and limits.

Acceptance criteria

• Every package README follows the template, and no packages/bus-core/src/**/README.md remains.
• Every README TypeScript block is synced from a compiled file in docs/snippets/**/*.ts, using the docs' #region convention, and the sync script's --check mode runs in CI (CircleCI's docs job) after pnpm build.
• README links are checked in CI with no failures. They point to the latest docs at https://node-ts.github.io/bus/<page>, and none point to bus.node-ts.com or GitBook-only paths.
• Every adapter README's configuration table matches the options and @defaults in the configuration interface.
• Each install line lists the package's required peers.
• Every row of the findings table is resolved, or marked as fixed in generate self-registering message types to restore dates and nested classes without decorators #295 or handed to another issue.
• Content that moves is added to the docs/ site in the same PR that removes the README text, and each README links to it.