Files
deepseek-harness/packages/api
Pine 6cd7c5a590 feat(plugin-inventory): offline bundle and pnpm plugin install for the desktop
Adds an install surface to the plugin-inventory gateway: availableBundles lists
the curated offline-installable optional bundles (AVAILABLE_BUNDLES); install
composes an offline bundle into the profile's dsh.profile.bundles, or for a
registry spec runs pnpm against the writable profile via the bundled Node and a
vendored pnpm (gated behind the dshAllowPluginInstall context flag, set only by
the desktop boot); uninstall removes a bundle layer. The reconcile logic from
`dsh plugin add` moves into app-boot as shared helpers. The desktop vendored
pnpm into the harness and sets the allow-install env; the plugin-list SPA gains
an installable-bundles section. Tests cover the guard, install helpers, and the
SPA section at 100% host coverage.

Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-14 18:46:39 +08:00
..
2026-08-13 18:49:33 +08:00

api/ — Remote API layers

English | 中文

The application-facing Remote stack. remotes owns BFF policy and the selected business API, while gateway implements the Typert unary RPC endpoints shared by Host and Client environments.

Package Role ctx key
remotes/ Host Agent/Session lookup policy and Client Remote contribution assembly no service; configures ctx.typert and consumes ctx.remote
gateway/ Host Typert dispatcher and Client Remote endpoint ctx.typertGateway / ctx.remote

The runtime dependency direction is remotes → gateway → connection → webserver: the BFF consumes the shared TypertClientRemote contract, Gateway delegates transport to Connection, and Connection mounts on the HTTP server. Cordis service injection and Client module metadata preserve this order without importing the concrete Gateway from the Remotes Client entry.

Known Limitations and Deferred Work

  • Connection and WebServer remain at client/connection and host/webserver; a later package-only move can place them under api/connection and api/webserver without changing their service contracts.
  • The legacy API Proxy remains at host/apiproxy as the fallback for methods not yet migrated to Remote. It consumes the Host resolver owned by api-remotes so migrated and legacy methods retain one Agent/Session identity policy.