dsh-keys-manager 0.2.0 → 0.2.2

package/CHANGELOG.md

@@ -0,0 +1,33 @@
+# Changelog
+
+All notable changes to dsh-keys-manager are documented here. Generated from
+git log by the release-prep workflow.
+
+## [0.2.2] - 2026-10-21
+
+- 838fb85 Merge pull request #31 from btspoony/feat/unified-release-version
+- ed5baaa Merge pull request #26 from btspoony/fix/oauth-binding-and-key-test
+- 2981bd5 Merge pull request #29 from btspoony/fix/retry-step-regressions
+- 25d7fc8 Merge pull request #28 from btspoony/feat/omp-transport-cursor
+- 03352c5 Merge pull request #27 from btspoony/docs/readme-extra-providers
+- 1d498e8 Merge pull request #23 from btspoony/fix/issue-18-harvest-abort-compensation
+- be938f0 Merge pull request #25 from btspoony/feat/issue-11-coreweave-header-carrier
+- 175e827 Merge pull request #24 from btspoony/docs/readme-desktop-web-install
+
+## [0.2.1] - 2026-10-20
+
+- 83c11e1 Merge pull request #20 from btspoony/fix/authorization-inject
+
+## [0.2.0] - 2026-10-20
+
+- 74defd3 Merge pull request #17 from btspoony/feat/issue-2-phase2-oauth-pool
+- 7e7e356 Merge pull request #14 from btspoony/docs/post-merge-followups
+
+## [0.1.0] - 2026-10-19
+
+- b1380c9 Merge pull request #12 from btspoony/feat/issue-2-phase1-providers
+- 14e57ae Merge pull request #8 from btspoony/fix/post-merge-review
+- 8300083 Merge pull request #10 from btspoony/chore/initial-version-0.0.1
+- 8076b79 docs: record generated-CHANGELOG rule in AGENTS.md (#9)
+- 39d409b Merge pull request #1 from btspoony/feat/keys-manager-plugin
+- bbfcccb Initial commit

package/README.md

@@ -23,27 +23,86 @@ manager.
 - Extra built-in providers installed as ordinary `llm-pi-ai` routes.
 - OAuth account sign-in for seven pi-ai-backed providers, stored beside
   the API keys.
+- A companion transport component for providers the vendored pi-ai cannot
+  speak — Cursor (`cursor`) today — installed with the plugin.
 
 ### Extra providers
 
-`src/providers.ts` contains a curated catalog of 34 extra providers (21 from
-the original catalog plus 13 added in this release, for example SiliconFlow,
-Zhipu coding plan, Cline Pass, Ollama Cloud, and Alibaba Token Plan (CN)),
-derived from
+This catalog of 35 extra providers comes from
 [oh-my-pi](https://github.com/can1357/oh-my-pi)'s provider catalog (MIT).
-An extra id is added only when the shipped DSH catalog does not already
-declare that route id (for example, `meta` and `typesafe` are not
-duplicated); same-endpoint providers with distinct credential identities
-are kept by design.
+
+<details>
+<summary>All 35 extra providers</summary>
+
+| Provider | Route id | API key env |
+|---|---|---|
+| DeepInfra | `deepinfra` | `DEEPINFRA_API_KEY` |
+| Novita | `novita` | `NOVITA_API_KEY` |
+| StepFun | `stepfun` | `STEPFUN_API_KEY` |
+| SambaNova | `sambanova` | `SAMBANOVA_API_KEY` |
+| Qianfan | `qianfan` | `QIANFAN_API_KEY` |
+| GMI Cloud | `gmi-cloud` | `GMI_API_KEY` |
+| Synthetic | `synthetic` | `SYNTHETIC_API_KEY` |
+| ZenMux | `zenmux` | `ZENMUX_API_KEY` |
+| Kilo Gateway | `kilo` | `KILO_API_KEY` |
+| NanoGPT | `nanogpt` | `NANO_GPT_API_KEY` |
+| Venice AI | `venice` | `VENICE_API_KEY` |
+| AIML API | `aimlapi` | `AIMLAPI_API_KEY` |
+| AI& | `aiand` | `AIAND_API_KEY` |
+| Helmcode | `helmcode` | `HELMCODE_API_KEY` |
+| Alibaba Coding Plan | `alibaba-coding-plan` | `ALIBABA_CODING_PLAN_API_KEY` |
+| MiniMax Coding (Global) | `minimax-code` | `MINIMAX_CODE_API_KEY` |
+| MiniMax Coding (CN) | `minimax-code-cn` | `MINIMAX_CODE_CN_API_KEY` |
+| Umans AI Coding Plan | `umans` | `UMANS_AI_CODING_PLAN_API_KEY` |
+| Sakana AI | `sakana` | `SAKANA_API_KEY` |
+| CoralBricks | `coralbricks` | `CORAL_API_KEY` |
+| Wafer Serverless | `wafer-serverless` | `WAFER_SERVERLESS_API_KEY` |
+| Alibaba Token Plan | `alibaba-token-plan` | `ALIBABA_TOKEN_PLAN_API_KEY` |
+| Alibaba Token Plan (CN) | `alibaba-token-plan-cn` | `BAILIAN_TOKEN_PLAN_API_KEY` |
+| Charm Hyper | `charm-hyper` | `CHARM_HYPER_API_KEY`, `HYPER_API_KEY` |
+| LiteLLM Proxy | `litellm` | `LITELLM_API_KEY` |
+| SiliconFlow | `siliconflow` | `SILICONFLOW_API_KEY` |
+| SiliconFlow (CN) | `siliconflow-cn` | `SILICONFLOW_CN_API_KEY` |
+| Zhipu Coding Plan | `zhipu-coding-plan` | `ZHIPU_API_KEY` |
+| Abliteration | `abliteration` | `ABLITERATION_API_KEY`, `ABLIT_KEY` |
+| ClinePass | `cline-pass` | `CLINE_API_KEY` |
+| Command Code | `commandcode` | `COMMAND_CODE_API_KEY`, `COMMANDCODE_API_KEY` |
+| CoreWeave Serverless Inference | `coreweave` | `COREWEAVE_API_KEY` |
+| Fire Pass | `firepass` | `FIREPASS_API_KEY` |
+| Ollama Cloud | `ollama-cloud` | `OLLAMA_CLOUD_API_KEY` |
+| Yolo Auto | `yolo-auto` | `YOLO_AUTO_API_KEY` |
+
+Where two variables are listed, either is accepted; the first is the primary.
+
+CoreWeave Serverless Inference also needs `COREWEAVE_PROJECT=<team>/<project>` in the DSH process environment before it is added.
+
+</details>
 
 ## Quick start
 
+### Install — DeepSeek Harness Desktop / Web
+
+In the DeepSeek Harness Desktop or Web app, open **Plugins**, click
+**Add plugin**, enter `dsh-keys-manager` in the package field, and click
+**Install**. When the install finishes, choose **Enable now** so the plugin is
+switched on.
+
+Through the wizard, the app installs the same published npm package as the
+CLI path below, already carrying its built bundle. Refresh the DeepSeek
+Harness page afterwards so the browser half is fetched.
+
 ### Install — published package
 
 ```sh
 dsh plugin --profile web add dsh-keys-manager
 ```
 
+Installing `dsh-keys-manager` installs two bundle components. The published
+package depends on `dsh-llm-omp-transports`, so one install resolves both npm
+packages, and the plugin page lists both `dsh-keys-manager` and
+`llm-omp-transports`. Enable both: the manager owns credentials and routing,
+the transport component owns the Cursor wire protocol.
+
 ### Install — local checkout
 
 ```sh
@@ -53,13 +112,13 @@ pnpm i
 dsh plugin --profile web link .
 ```
 
-Only the published-package path avoids a local build: `dsh plugin --profile web add dsh-keys-manager` installs the npm
-tarball as-is — package lifecycle scripts (`prepare` / `prepack`) do not run
-for registry installs, and the tarball already ships the built `lib/` and
-the client bundle. The local `dsh plugin --profile web link .` path is
-different — installing a local directory runs `prepare` during `pnpm i`,
-which builds `lib/` and the client bundle, so the clone flow above needs no
-manual build step.
+The two CLI paths differ in where the build output comes from: `dsh plugin
+--profile web add dsh-keys-manager` installs the published npm tarball, which
+ships the built `lib/` and the client bundle. The local
+`dsh plugin --profile web link .` path runs `prepare` during `pnpm i`, which
+builds `lib/` and the client bundle, so the clone flow above includes that
+build step; `prepack` builds the same output when the package is packed or
+published.
 
 Refresh the Web page after installing so the browser half is fetched.
 
@@ -113,6 +172,25 @@ credential store, behind the account's `grantRef`; the manager state keeps
 the reference plus non-sensitive metadata (email, account id, expiry) — the
 same secret-free layout as API keys.
 
+### Cursor transport
+
+Cursor is served by the companion `dsh-llm-omp-transports` component on its
+own `cursor` route. It does not run through the pi-ai key pool: the route
+keeps exactly one grant at `llm-omp-transports/cursor`, refreshed
+automatically on the credential seam.
+
+- Models come from the pinned `@oh-my-pi/pi-catalog@18.12.3` table (123 rows),
+  generated into the transport at build time. The route streams text and
+  reasoning, and hands tool calls to DSH's tool loop.
+- Sign in from the **Transport accounts** section of the Keys Manager page: a
+  browser page plus a poll. The row shows identity, expiry and status; after an
+  expired or rejected grant, re-login is manual.
+- Images are not forwarded yet. The route advertises text-only input and
+  refuses image blocks with a typed error instead of dropping them.
+- The client is unofficial and presents Cursor's vendor-internal OAuth
+  identity. Read the [transports package docs](packages/llm-omp/README.md)
+  before relying on it; the risks and limits are listed there.
+
 ### Selection and failure policy
 
 - **Sticky session**: the first request of a session selects a key and binds
@@ -184,6 +262,20 @@ also support OAuth (Anthropic, GitHub Copilot, Kimi Coding, OpenAI Codex,
 OpenRouter, Radius, xAI) remain manageable through their API-key path, and
 their OAuth sign-in is available as [OAuth accounts](#oauth-accounts).
 
+## Repository layout
+
+This repository is a pnpm workspace with two published packages:
+
+| Path | npm package | Role |
+|---|---|---|
+| root | `dsh-keys-manager` | Host plugin, Keys Manager Web client, bundle patch |
+| `packages/llm-omp` | `dsh-llm-omp-transports` | Cursor (and future) transport component |
+
+The root package declares the transports package as a dependency, so the
+published Keys Manager tarball pulls the transport in rather than vendoring
+it. Both packages are released together and carry the same version; see
+[Release](docs/release.md).
+
 ## Documentation
 
 | Doc | Content |
@@ -191,6 +283,7 @@ their OAuth sign-in is available as [OAuth accounts](#oauth-accounts).
 | [Development](docs/development.md) | build and dev workflow, repository layout |
 | [Release](docs/release.md) | CI checks and the npm release flow |
 | [Known limits](docs/known-limits.md) | current design boundaries, including deferred providers |
+| [Transports package](packages/llm-omp/README.md) | Cursor transport: support status, risks, build/test, release |
 
 Chinese versions: [README.zh-CN.md](README.zh-CN.md) and the `*.zh-CN.md`
 files in `docs/` — [开发](docs/development.zh-CN.md) ·

package/README.zh-CN.md

@@ -19,19 +19,76 @@ DSH Keys Manager 是一个 DeepSeek Harness 插件，把一个提供商 API key
 - 既有 Models 提供商卡片内出现"由 Keys Manager 托管"徽标。
 - 额外内置提供商以普通 `llm-pi-ai` 路由安装。
 - 七家 pi-ai 覆盖的提供商支持 OAuth 账户登录，凭据与 API key 并存管理。
+- 随插件附带一个传输组件，服务随附 pi-ai 无法支持的提供商——目前是 Cursor（`cursor`）。
 
 ### 额外提供商
 
-`src/providers.ts` 收录 34 个精选提供商（原有 21 个加本次发布新增 13 个，例如 SiliconFlow、智谱编码套餐、Cline Pass、Ollama Cloud、Alibaba Token Plan (CN)），目录源自 [oh-my-pi](https://github.com/can1357/oh-my-pi)（MIT）。只有当随附 DSH 目录尚未声明该 route id 时才会新增条目（例如 `meta`、`typesafe` 不会重复提供）；与既有端点共享 base URL、但凭据身份不同的提供商会按设计保留。
+这 35 个额外提供商收录自
+[oh-my-pi](https://github.com/can1357/oh-my-pi) 的提供商目录（MIT）。
+
+<details>
+<summary>全部 35 个额外提供商</summary>
+
+| 提供商 | Route id | API key 环境变量 |
+|---|---|---|
+| DeepInfra | `deepinfra` | `DEEPINFRA_API_KEY` |
+| Novita | `novita` | `NOVITA_API_KEY` |
+| StepFun | `stepfun` | `STEPFUN_API_KEY` |
+| SambaNova | `sambanova` | `SAMBANOVA_API_KEY` |
+| Qianfan | `qianfan` | `QIANFAN_API_KEY` |
+| GMI Cloud | `gmi-cloud` | `GMI_API_KEY` |
+| Synthetic | `synthetic` | `SYNTHETIC_API_KEY` |
+| ZenMux | `zenmux` | `ZENMUX_API_KEY` |
+| Kilo Gateway | `kilo` | `KILO_API_KEY` |
+| NanoGPT | `nanogpt` | `NANO_GPT_API_KEY` |
+| Venice AI | `venice` | `VENICE_API_KEY` |
+| AIML API | `aimlapi` | `AIMLAPI_API_KEY` |
+| AI& | `aiand` | `AIAND_API_KEY` |
+| Helmcode | `helmcode` | `HELMCODE_API_KEY` |
+| Alibaba Coding Plan | `alibaba-coding-plan` | `ALIBABA_CODING_PLAN_API_KEY` |
+| MiniMax Coding (Global) | `minimax-code` | `MINIMAX_CODE_API_KEY` |
+| MiniMax Coding (CN) | `minimax-code-cn` | `MINIMAX_CODE_CN_API_KEY` |
+| Umans AI Coding Plan | `umans` | `UMANS_AI_CODING_PLAN_API_KEY` |
+| Sakana AI | `sakana` | `SAKANA_API_KEY` |
+| CoralBricks | `coralbricks` | `CORAL_API_KEY` |
+| Wafer Serverless | `wafer-serverless` | `WAFER_SERVERLESS_API_KEY` |
+| Alibaba Token Plan | `alibaba-token-plan` | `ALIBABA_TOKEN_PLAN_API_KEY` |
+| Alibaba Token Plan (CN) | `alibaba-token-plan-cn` | `BAILIAN_TOKEN_PLAN_API_KEY` |
+| Charm Hyper | `charm-hyper` | `CHARM_HYPER_API_KEY`, `HYPER_API_KEY` |
+| LiteLLM Proxy | `litellm` | `LITELLM_API_KEY` |
+| SiliconFlow | `siliconflow` | `SILICONFLOW_API_KEY` |
+| SiliconFlow (CN) | `siliconflow-cn` | `SILICONFLOW_CN_API_KEY` |
+| Zhipu Coding Plan | `zhipu-coding-plan` | `ZHIPU_API_KEY` |
+| Abliteration | `abliteration` | `ABLITERATION_API_KEY`, `ABLIT_KEY` |
+| ClinePass | `cline-pass` | `CLINE_API_KEY` |
+| Command Code | `commandcode` | `COMMAND_CODE_API_KEY`, `COMMANDCODE_API_KEY` |
+| CoreWeave Serverless Inference | `coreweave` | `COREWEAVE_API_KEY` |
+| Fire Pass | `firepass` | `FIREPASS_API_KEY` |
+| Ollama Cloud | `ollama-cloud` | `OLLAMA_CLOUD_API_KEY` |
+| Yolo Auto | `yolo-auto` | `YOLO_AUTO_API_KEY` |
+
+列出两个变量时二者皆可接受，第一个为主变量。
+
+CoreWeave Serverless Inference 还需在添加前把 `COREWEAVE_PROJECT=<team>/<project>` 设置到 DSH 进程环境中。
+
+</details>
 
 ## 快速开始
 
+### 安装 —— DeepSeek Harness 桌面版 / Web 版
+
+桌面版或 Web 版打开 **插件** 页面，点击 **添加插件**，在包名输入框中填入 `dsh-keys-manager` 并点击 **安装**；安装完成后选择 **立即启用** 启用插件。
+
+通过向导安装时，应用会下载与下面 CLI 路径相同的已发布 npm 包，包内已包含构建好的产物。安装完成后刷新页面，让插件的浏览器侧代码被加载。
+
 ### 安装 —— 已发布包
 
 ```sh
 dsh plugin --profile web add dsh-keys-manager
 ```
 
+安装 `dsh-keys-manager` 会安装两个 bundle 组件。已发布包依赖 `dsh-llm-omp-transports`，因此一次安装会解析两个 npm 包，插件页面会同时列出 `dsh-keys-manager` 与 `llm-omp-transports`。两者都要启用：管理器负责凭据与路由，传输组件负责 Cursor 的线协议。
+
 ### 安装 —— 本地检出
 
 ```sh
@@ -41,7 +98,7 @@ pnpm i
 dsh plugin --profile web link .
 ```
 
-只有已发布包的安装路径不会在本地执行构建：`dsh plugin --profile web add dsh-keys-manager` 按原样安装 npm tarball——注册表安装不会运行包生命周期脚本（`prepare` / `prepack`），tarball 内已带构建好的 `lib/` 与客户端 bundle。本地 `dsh plugin --profile web link .` 路径不同——安装本地目录会在 `pnpm i` 期间运行 `prepare`，构建 `lib/` 与客户端 bundle，因此上面的克隆流程不需要手动构建步骤。
+两条 CLI 安装路径的区别在于构建产物的来源：`dsh plugin --profile web add dsh-keys-manager` 安装的已发布 npm tarball 中已包含构建好的 `lib/` 与客户端 bundle。本地 `dsh plugin --profile web link .` 路径会在 `pnpm i` 期间运行 `prepare`，构建 `lib/` 与客户端 bundle，因此上面的克隆流程包含这一步构建；`prepack` 则在打包或发布时生成同样的产物。
 
 安装完成后刷新 Web 页面，让浏览器侧代码被取到。
 
@@ -65,6 +122,15 @@ dsh plugin --profile web link .
 
 添加账户只把提供商签发的授权存进 Harness 凭据存储（挂在账户的 `grantRef` 之下）；管理器状态里只存引用与非敏感元数据（邮箱、账户 ID、过期时间）——与 API key 相同的无明文布局。
 
+### Cursor 传输
+
+Cursor 由随附的 `dsh-llm-omp-transports` 组件在独立 `cursor` 路由上提供。它不经过 pi-ai key 池：该路由在 `llm-omp-transports/cursor` 只保留一条授权，并在凭据 seam 上自动刷新。
+
+- 模型来自固定的 `@oh-my-pi/pi-catalog@18.12.3` 表（123 行），构建时生成进传输包。路由支持文本与推理流，并把工具调用交给 DSH 的工具循环。
+- 在 Keys Manager 页面的 **传输账户**（`Transport accounts`）区块登录：浏览器页面加轮询。账户行显示身份、有效期与状态；授权过期或被拒后需要手动重新登录。
+- 暂不转发图片。路由按纯文本宣告输入，遇到图片块以类型化错误拒绝，而不是静默丢弃。
+- 该客户端是非官方实现，会呈现 Cursor 厂商内部的 OAuth 身份。依赖它之前请阅读[传输包文档](packages/llm-omp/README.md)，风险与限制列在那里。
+
 ### 选择与故障策略
 
 - **会话粘滞**：会话的首次请求选出一把 key 并为该会话/提供商对绑定，后续请求复用。
@@ -110,6 +176,17 @@ $DSH_HOME/keys-manager/state.json
 
 其余 DSH 目录路由都提供 API key 凭据。同时支持 OAuth 的提供商（Anthropic、GitHub Copilot、Kimi Coding、OpenAI Codex、OpenRouter、Radius、xAI）仍可经其 API key 路径管理，其 OAuth 登录则以 [OAuth 账户](#oauth-账户)形式提供。
 
+## 仓库布局
+
+本仓库是 pnpm workspace，包含两个已发布包：
+
+| 路径 | npm 包 | 职责 |
+|---|---|---|
+| 根目录 | `dsh-keys-manager` | Host 插件、Keys Manager Web 客户端、bundle patch |
+| `packages/llm-omp` | `dsh-llm-omp-transports` | Cursor（及后续）传输组件 |
+
+根包把传输包声明为依赖，因此已发布的 Keys Manager tarball 会拉取传输包，而不是把它 vendor 进来。两个包一起发布且版本号一致，详见[发布](docs/release.zh-CN.md)。
+
 ## 文档
 
 | 文档 | 内容 |
@@ -117,6 +194,7 @@ $DSH_HOME/keys-manager/state.json
 | [开发](docs/development.zh-CN.md) | 构建与开发工作流、仓库布局 |
 | [发布](docs/release.zh-CN.md) | CI 检查与 npm 发布流程 |
 | [已知限制](docs/known-limits.zh-CN.md) | 当前设计边界，含延后提供商 |
+| [传输包（英文）](packages/llm-omp/README.md) | Cursor 传输：支持状态、风险、构建/测试与发布 |
 
 英文版本：[README.md](README.md) 及 `docs/` 下的 `*.md` —— [Development](docs/development.md) · [Release](docs/release.md) · [Known limits](docs/known-limits.md)。当前设计边界速览：[已知限制](docs/known-limits.zh-CN.md)。
 

package/bundle/cordis.patch.yml

@@ -1,5 +1,8 @@
-# Mounts the Keys Manager Host plugin. The Client half is declared by
-# package.json#dsh.client and is served from lib/client.js.
+# Mounts the Keys Manager Host plugin plus its second component, the
+# llm-omp-transports transport package. The Client half is declared by package.json#dsh.client and
+# is served from lib/client.js.
 - insert:
     - id: dsh-keys-manager
       name: 'dsh-keys-manager'
+    - id: llm-omp-transports
+      name: 'dsh-llm-omp-transports'

package/lib/client/types.d.ts

@@ -1,7 +1,7 @@
 /** Browser-half domain and service contracts for the Keys Manager. */
 import type * as React from 'react';
-import type { AccountAttemptNotice, AccountAttemptPrompt, AccountAttemptView, KeyStatus, KeyView, ManagerSettings, OAuthAccountView, ProviderStatus, ProviderView, StateView } from '../domain';
-export type { AccountAttemptNotice, AccountAttemptPrompt, AccountAttemptView, KeyStatus, KeyView, ManagerSettings, OAuthAccountView, ProviderStatus, ProviderView, StateView, };
+import type { AccountAttemptNotice, AccountAttemptPrompt, AccountAttemptView, KeyStatus, KeyTestResult, KeyView, ManagerSettings, OAuthAccountView, ProviderStatus, ProviderView, StateView, TransportAccountStatus, TransportAccountView } from '../domain';
+export type { AccountAttemptNotice, AccountAttemptPrompt, AccountAttemptView, KeyStatus, KeyTestResult, KeyView, ManagerSettings, OAuthAccountView, ProviderStatus, ProviderView, StateView, TransportAccountStatus, TransportAccountView, };
 /** Locale dictionaries registered under the plugin namespace. */
 export interface LocaleDicts {
     zh: Record<string, string>;
@@ -52,6 +52,17 @@ export type AckResult = {
     ok: false;
     error: string;
 };
+/**
+ * Result of the per-row connection test. The payload is a `KeyTestResult`,
+ * not a `StateView`, so it has its own mapper instead of `call`.
+ */
+export type KeyTestOutcome = {
+    ok: true;
+    value: KeyTestResult;
+} | {
+    ok: false;
+    error: string;
+};
 /** Immutable UI snapshot. */
 export interface ClientSnapshot {
     status: 'idle' | 'loading' | 'ready' | 'error';
@@ -84,6 +95,20 @@ export interface ClientStore {
     activateAccount(provider: string, accountId: string): Promise<ActionOutcome>;
     /** Drop one account row and its stored grant payload. */
     removeAccount(provider: string, accountId: string): Promise<ActionOutcome>;
+    /**
+     * Send one minimal request with the selected key or account row. The host
+     * never changes health state; the answer only reports the outcome.
+     */
+    testKey(provider: string, keyId: string): Promise<KeyTestOutcome>;
+    /**
+     * Start the `llm-omp-transports/<route>` sign-in; resolves with the attempt
+     * view, which the login dialog polls through {@link accountAttempt}.
+     */
+    beginTransportLogin(route: string): Promise<AccountAttemptResult>;
+    /** Re-read one transport route's stored grant (activation writes nothing). */
+    activateTransportAccount(route: string): Promise<ActionOutcome>;
+    /** Delete one transport route's grant record. */
+    removeTransportAccount(route: string): Promise<ActionOutcome>;
     tick(): void;
     dismissError(): void;
 }