docs: Data Center is a surface the documentation knows about

Six pages and the LLM index still described three surfaces, and the landing page still called the
library a Jira Cloud client. `jira.js/server` was missing from both subpath tables, so the one
place a reader looks for it said it does not exist.

Two counts in the changelog were measured before the naming tables settled and were wrong by the
time they shipped: two hundred and six operations share a name with a Cloud one, not a hundred and
seventy-four, and eighty-seven models, not thirty-seven.

The 3LO page now says which product it is about. A self-hosted instance is its own authorization
server, and a reader who arrives there with a Data Center instance needs to leave.

Author: MrRefactoring

CHANGELOG.md

@@ -2,7 +2,7 @@
 
 ## 6.3.0
 
-Jira Data Center gets a client. `createServerClient` is a fourth surface alongside Cloud, Agile and Service Management — not the Cloud client pointed elsewhere, because the two APIs differ in more than their address: `/rest/api/2` against `/rest/api/3`, wiki markup against Atlassian Document Format, `name` and `key` against `accountId`. Of four hundred and thirty-five operations, a hundred and seventy-four share a name with a Cloud one and thirty-seven share a schema name; nothing else is common but the transport.
+Jira Data Center gets a client. `createServerClient` is a fourth surface alongside Cloud, Agile and Service Management — not the Cloud client pointed elsewhere, because the two APIs differ in more than their address: `/rest/api/2` against `/rest/api/3`, wiki markup against Atlassian Document Format, `name` and `key` against `accountId`. Of four hundred and thirty-five operations, two hundred and six share a name with a Cloud one and eighty-seven share a model name; nothing else is common but the transport.
 
 Every one of those operations has been called against a running Jira Data Center instance. That is what the rest of these notes are: Atlassian generates the Data Center document from Java annotations rather than writing it, and it is wrong in ways reading cannot reveal.
 

README.md

@@ -454,7 +454,7 @@ The surface subpaths carry the types alongside the functions, so a type-only imp
 import type { Issue, GetIssue } from 'jira.js/cloud';
 ```
 
-The three surfaces are not re-exported from the root — they collide on a handful of names, so import from the one you mean.
+The four surfaces are not re-exported from the root — they collide on a handful of names, so import from the one you mean.
 
 > Deep imports need an `exports`-aware resolver: `moduleResolution: "bundler"`, `"node16"` or `"nodenext"`. The legacy `"node"` resolution cannot see them, and cannot load an ESM-only package either.
 

README.ru.md

@@ -451,7 +451,7 @@ const issue = await getIssue(client, { issueIdOrKey: 'KEY-1' });
 import type { Issue, GetIssue } from 'jira.js/cloud';
 ```
 
-Три поверхности не реэкспортируются из корня — они сталкиваются на десятке имён, импортируйте из нужной.
+Четыре поверхности не реэкспортируются из корня — они сталкиваются на десятке имён, импортируйте из нужной.
 
 > Глубоким импортам нужен резолвер, понимающий `exports`: `moduleResolution: "bundler"`, `"node16"` или `"nodenext"`. Легаси-резолвинг `"node"` их не видит и ESM-only пакет всё равно не загрузит.
 

docs/guide/getting-started.md

@@ -1,11 +1,15 @@
 # Getting Started
 
-`jira.js` is a TypeScript client for the Atlassian Jira Cloud REST APIs, for [Node.js](https://nodejs.org/)
-and browsers. It covers three surfaces:
+`jira.js` is a TypeScript client for the Atlassian Jira REST APIs, for [Node.js](https://nodejs.org/)
+and browsers. It covers four surfaces:
 
 - **[Jira Cloud platform](https://developer.atlassian.com/cloud/jira/platform/rest/)** — issues, projects, fields, workflows
 - **[Jira Agile](https://developer.atlassian.com/cloud/jira/software/rest/intro/)** — boards, sprints, backlog
 - **[Jira Service Management](https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/)** — requests, queues, organizations
+- **[Jira Data Center](https://developer.atlassian.com/server/jira/platform/rest/)** — the self-hosted API, platform and agile in one client
+
+The first three are Cloud. Data Center is a surface of its own rather than the Cloud one pointed at another
+host — see [Jira Data Center](./data-center).
 
 ## Install
 

docs/guide/installation.md

@@ -28,8 +28,8 @@ import { createCloudClient } from 'jira.js';
 There is no CommonJS build. `require('jira.js')` does not work; from a CommonJS module, use a dynamic
 `await import('jira.js')`.
 
-The package also exposes surface-level subpaths — `jira.js/cloud`, `jira.js/agile`, `jira.js/serviceDesk`
-and `jira.js/core` — carrying the flat functions along with every parameter and response type. See
+The package also exposes surface-level subpaths — `jira.js/cloud`, `jira.js/agile`, `jira.js/serviceDesk`,
+`jira.js/server` and `jira.js/core` — carrying the flat functions along with every parameter and response type. See
 [Tree-Shaking](./tree-shaking).
 
 ## Requirements

docs/guide/oauth2-authentication.md

@@ -5,6 +5,10 @@ stateless helpers to drive the browser consent flow, and an auto-refreshing clie
 the access token fresh, transparently handles the **rotating refresh token**, and resolves the
 `cloudId` so requests go through the Atlassian API gateway.
 
+> This page is about **Jira Cloud**. A self-hosted instance is its own authorization server: there is no
+> `cloudId` to resolve and nothing goes near `auth.atlassian.com`. See
+> [Jira Data Center](./data-center#oauth-2-0) for that flow.
+
 > ⚠️ **`clientSecret` and refresh are server-side only.** Never ship the client secret or
 > refresh token to a browser. The simple `{ accessToken }` mode (no refresh) is the only part
 > safe for a browser, and even then the token is a user credential.

docs/guide/tree-shaking.md

@@ -29,11 +29,12 @@ where it does.
 
 | Import | Contents |
 | --- | --- |
-| `jira.js` | The three factories, the error types and their predicates, the OAuth helpers |
+| `jira.js` | The four factories, the error types and their predicates, the OAuth helpers |
 | `jira.js/core` | `createClient`, the transport, errors, OAuth, multipart helpers |
 | `jira.js/cloud` | Platform API functions, parameters and response types |
 | `jira.js/agile` | Agile API functions, parameters and response types |
 | `jira.js/serviceDesk` | Service Management functions, parameters and response types |
+| `jira.js/server` | Data Center functions, parameters and response types |
 | `jira.js/browser` | Prebuilt browser bundle |
 
 The surface subpaths carry the types alongside the functions, so a type-only import costs nothing at
@@ -44,8 +45,9 @@ import type { Issue } from 'jira.js/cloud';
 import type { GetIssue } from 'jira.js/cloud';
 ```
 
-The three surfaces are not re-exported from the root, because they collide on a handful of names — import
-from the surface you mean.
+The four surfaces are not re-exported from the root, because they collide on a handful of names — import
+from the surface you mean. Data Center collides hardest: eighty-seven of its models share a name with a
+Cloud one and describe something else.
 
 > Deep imports need an `exports`-aware resolver: `moduleResolution: "bundler"`, `"node16"` or
 > `"nodenext"`. The legacy `"node"` resolution cannot see them, and cannot load an ESM-only package

docs/index.md

@@ -4,7 +4,7 @@ title: jira.js — Jira REST API client for Node.js & TypeScript
 hero:
   name: jira.js
   text: Jira REST API client
-  tagline: Type-safe client for the Jira Cloud platform, Agile and Service Management APIs — Node.js and browsers, ESM, every response validated.
+  tagline: Type-safe client for Jira — cloud or self-hosted. Node.js and browsers, ESM, every response validated.
   image:
     src: /logo.svg
     alt: jira.js
@@ -20,8 +20,8 @@ hero:
       link: https://github.com/MrRefactoring/jira.js
 features:
   - icon: 🧩
-    title: Full Cloud coverage
-    details: The Jira Cloud platform API, Agile (boards, sprints, backlog) and Jira Service Management — nearly every endpoint, one client.
+    title: Cloud and Data Center
+    details: The Jira Cloud platform API, Agile and Service Management, and the self-hosted Data Center API — nearly every endpoint, one client.
   - icon: 🔒
     title: TypeScript-first
     details: Every endpoint, parameter and model is typed, and the published package ships its sources so "go to definition" lands on the real thing.

docs/ru/guide/getting-started.md

@@ -1,11 +1,15 @@
 # Быстрый старт
 
-`jira.js` — TypeScript-клиент к REST API Atlassian Jira Cloud для [Node.js](https://nodejs.org/) и
-браузеров. Покрывает три поверхности:
+`jira.js` — TypeScript-клиент к REST API Atlassian Jira для [Node.js](https://nodejs.org/) и
+браузеров. Покрывает четыре поверхности:
 
 - **[Платформа Jira Cloud](https://developer.atlassian.com/cloud/jira/platform/rest/)** — задачи, проекты, поля, воркфлоу
 - **[Jira Agile](https://developer.atlassian.com/cloud/jira/software/rest/intro/)** — доски, спринты, бэклог
 - **[Jira Service Management](https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/)** — обращения, очереди, организации
+- **[Jira Data Center](https://developer.atlassian.com/server/jira/platform/rest/)** — self-hosted API, платформа и agile в одном клиенте
+
+Первые три — облачные. Data Center — отдельная поверхность, а не облачный клиент, направленный на другой
+хост; см. [Jira Data Center](./data-center).
 
 ## Установка
 

docs/ru/guide/installation.md

@@ -30,8 +30,8 @@ import { createCloudClient } from 'jira.js';
 Сборки CommonJS нет. `require('jira.js')` не работает; из CommonJS-модуля используйте динамический
 `await import('jira.js')`.
 
-Пакет также отдаёт подпути по поверхностям — `jira.js/cloud`, `jira.js/agile`, `jira.js/serviceDesk` и
-`jira.js/core`, — в которых лежат плоские функции вместе со всеми типами параметров и ответов. См.
+Пакет также отдаёт подпути по поверхностям — `jira.js/cloud`, `jira.js/agile`, `jira.js/serviceDesk`,
+`jira.js/server` и `jira.js/core`, — в которых лежат плоские функции вместе со всеми типами параметров и ответов. См.
 [Tree-Shaking](./tree-shaking).
 
 ## Требования