docs: branded, on-brand READMEs for all 5 published packages

[brentrager]

Problem

The registry pages — npm, PyPI, NuGet, crates.io, and pkg.go.dev — were showing empty / plain / un-branded READMEs for the five published smooth-operator-core packages. The repo's root README is beautifully branded; the per-package files that registries actually render were not.

What this does

Gives every published package a README that matches the repo's glowed-up branding, using the root README.md as the voice/layout template:

• Banner on top (per-language, absolute raw.githubusercontent.com URL)
• Badge row — Smoo AI platform / MIT / hosted lom.smoo.ai, plus a per-ecosystem registry badge (npm / PyPI / NuGet / crates.io / pkg.go.dev) and a language badge
• Blockquote tagline, the "it's the engine, not a notebook demo" / "verified, not vibe-coded" voice
• Install + Quickstart (verified hello-agent for that language) + Features (the full parity surface) + Streaming note + Part of Smoo AI + Links + License

Files (the file each registry reads)

Registry	File	Wired via
crates.io	rust/smooth-operator-core/README.md	Cargo.toml readme
npm	typescript/core/README.md (new)	package root
PyPI	python/core/README.md	pyproject.toml readme
NuGet	dotnet/core/README.md	csproj ..\README.md + PackageReadmeFile
pkg.go.dev	go/core/README.md (new)	package dir

Also adds per-language banners (banner-typescript/python/go/dotnet.png) rendered from the existing banner.svg with the language-specific subtitle.

Correctness

• Every image and link is an absolute URL — registries don't resolve relative paths. Verified: no ](. / src=". relative refs.
• Every quickstart mirrors the verified hello-agent example from docs/Polyglot-Engines.md, cross-checked against each engine's source (SmoothAgent/MockLlmProvider symbols, run/run/Run/RunAsync, pushText/push_text/PushText).
• Streaming notes use the real per-language method: run_with_channel (Rust), runStream (TS), run_stream (Py), RunStream (Go), RunStreamingAsync (C#).

Note

Additive only — no version bumps, no publish. Re-publishing is handled separately by the lead.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2dfe3f7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR