chat

Many docs pages are orphaned: nothing links to them apart from the sidebar, so readers and crawlers rarely find them. This PR gives every docs page a Read more section with four cards at the bottom of the article, above the prev/next footer. Cards are picked deterministically in lib/read-more.ts: the page's related frontmatter first, then prerequisites, then siblings from the same sidebar section, then the rest of the page tree, so every page always fills all four slots. Card titles and descriptions come from the target page's own frontmatter, nothing is duplicated. The section is injected through the MDX wrapper slot in the docs route, so it applies to all pages without touching content. To make the links topical rather than positional, 26 pages get related frontmatter additions. The 20 pages that no other page referenced (all ten api/ pages among them) now each have at least one inbound link, generally pairing guides with their API reference and back. The bundled copy of create-chat-sdk.mdx is synced to keep the byte-match test green. Official adapter pages get the same treatment with a More adapters section: same-type adapters first (platform or state, using the catalog order), topped up from the other official group. Vendor-official and community adapters are never shown, and their pages don't render the section. It reuses AdapterCard, so logos and package names match the listing page. Two small SEO fixes ride along. JSON-LD was allowlisted to three docs pages; the allowlist is gone, so all 45 now emit HowTo or TechArticle plus a BreadcrumbList. Docs and adapter detail pages also emit canonical URLs now, resolved against the existing metadataBase. Verified against the production build: all 45 docs pages and all 19 official adapter pages render exactly four cards, no page is left unreferenced, canonicals and JSON-LD are present everywhere, and pnpm validate passes. Docs-only, so no changeset.

Adds function-backed Discord bot token and application ID resolvers, plus custom webhook verification for Vercel Connect trigger-forwarded interactions. Native Discord Ed25519 verification remains the default when no custom verifier is configured. now recognizes Discord as Connect-capable, generates instead of native credential variables, and preserves for Gateway forwarding: Validated with the Discord adapter suite (284 tests), create-chat-sdk suite (206 tests), package type checks/builds, and repository lint/format checks.

Failure Workflow SDK produces an invalid workflow bundle when a Chat SDK serializable class such as , , or crosses a workflow step boundary. The Workflow compiler imports the emitted module containing each class to register its methods. In Chat SDK , tsup emits those classes in . The root entry also imports the conversation-scoping implementation added in #751, which uses from . Serializer registration therefore pulls Node-only code into the sandboxed workflow bundle before any workflow or step executes. Build warning: Deployed workflows then fail during module initialization: Minimal reproduction Running on emits the warning; deploying the output produces the runtime failure above. Fix Add a dedicated package entry for , , , , and their serialized DTO types. Make serializer code a second tsup entry and explicitly enable splitting. The serializer-bearing classes are now emitted into a shared chunk with no dependency on or its Node-only conversation context. Preserve the existing root exports and automatic behavior. Existing workflow code remains valid. Add a post-build module-graph assertion that fails if any emitted serializer registration can transitively import a Node.js builtin. Test against Workflow SDK , the compiler version that exposed the invalid bundle. Add a minor changeset for the fixed-version Chat SDK packages, producing the release line. After the change, the emitted serializer classes live in a sandbox-safe shared chunk while remains in a separate Node runtime chunk. The exact reproduction compiles successfully with and no Serde warning. Control cases The failure requires a serializable Chat class to cross a durable boundary. These cases were already safe and remain unchanged: used entirely inside a function. A Chat created and consumed within one step while returning plain data. Request handlers that convert Chat objects to plain workflow DTOs before starting a workflow. used entirely inside a step. Validation Committed beta.40 reproduction fixture: type-correct and compiled during every Chat package build with no Node builtin / Serde warning. Emitted serializer module graph: no transitive Node.js builtins. Chat package: 1,113 tests pass. Chat package typecheck passes. Repository formatting and lint checks pass. Package build passes. Full repository validation reaches the pre-existing baseline and reports unrelated unused dependencies and unlisted binaries in examples and adapter packages.