Rewrite the JavaScript SDK section of client-sdks.mdx: TypeScript-first, one package, bindings CLI, dedicated docs site

[kaankacar]

Context

docs/tools/sdks/client-sdks.mdx is the front door for the JS SDK in the developer docs. The current section (lines 22-33) is out of date on positioning:

• It says "stellar-sdk is the JavaScript library" and never mentions the SDK is fully TypeScript.
• It does not mention that ``stellar/stellar-base is now folded into the SDK (v16), so the SDK is the only package developers need.
• It does not mention the bundled CLI for generating typed contract bindings (npx stellar/stellar-sdk generate).
• The prose uses the bare name stellar-sdk (line 28); the correct package is ``stellar/stellar-sdk.

What to do

Rewrite the JavaScript SDK section to lead with the current story. Suggested copy (adjust to page conventions):

JavaScript SDK

JavaScript SDK | Docs | NPM

The JavaScript SDK is maintained by SDF.

stellar`/stellar-sdk` is the TypeScript SDK for communicating with Stellar RPC and Horizon, and for building, signing, and submitting transactions. It is fully typed, works in Node.js and the browser, and as of v16 includes everything that used to live in stellar/stellar-base, so it is the only package you need.

It provides:

• A networking layer for Stellar RPC methods and the Horizon API.
• Facilities for building and signing transactions and for submitting them or querying network state.
• A CLI that generates fully typed TypeScript bindings for any deployed smart contract (npx stellar/stellar-sdk generate).

The SDK has its own docs site with task guides (connect and fund, send a payment, issue an asset, query and stream, handle errors, invoke a contract, contract auth) and a full API reference: https://stellar.github.io/js-stellar-sdk/

Also consider linking the agent-facing bundles the SDK docs publish (llms.txt, llms-full.txt) since this page is where tooling authors look first.

Acceptance criteria

• The section states the SDK is TypeScript.
• The section states stellar-base is bundled in as of v16.
• The section mentions the bindings CLI.
• Package name appears as ``stellar/stellar-sdk throughout.

---

Demo copy of stellar#2561 (original author: oceans404) — seeded for the triage-agent demo; content unchanged apart from neutralized mentions.

[claude]

Checked: current checkout (main), docs/tools/sdks/client-sdks.mdx lines 22-33; searched open/closed issues and open PRs for duplicates/overlap.

Evidence:

• docs/tools/sdks/client-sdks.mdx:24-33 still reads: "stellar-sdk is the JavaScript library for communicating with Stellar RPC and Horizon..." — no mention of TypeScript, no mention of stellar-base folding into the SDK at v16, no mention of the generate bindings CLI, and the package name is written as stellar-sdk rather than @stellar/stellar-sdk (line 28). The issue's claim holds against current main.
• No open PR touches docs/tools/sdks/client-sdks.mdx (gh pr list checked).
• No exact duplicate found. Fix broken JS SDK code snippets (invalid syntax, missing imports, undefined variables) #17, list-of-operations.mdx: fix insecure JS SDK links and add missing JS links for newer operations #16, Add standard cross-links from JS tutorials to the js-stellar-sdk docs site #15 are related JS-SDK-docs issues but target different files/content (broken code snippets, list-of-operations.mdx links, tutorial cross-links) — not the same defect/target as this issue.
• Title doesn't match the sd-/sk- Raven-finding pattern, so this is a regular content-gap report, not a Raven verification case.

Conclusion: confirmed-valid — the SDK positioning section is stale relative to the current JS SDK (TypeScript, v16 bundling, bindings CLI). Labeled documentation + P2 (valid gap, non-urgent). No area label applied since this repo doesn't yet define one matching this content area (e.g. dev-x/sdks).

Reopening or further comment is welcome if this reasoning is off.