refactor(picker): split the directory-picker faces into their own packages

The browse and native backends were dual-face packages: a Node backend plus a
browser surface under one tsconfig that referenced Client packages. That put
Client projects — and through them the Client runtime — inside the Host
compiler aggregate, which builds before the generated Remote contributions
exist. Each browser half moves to its own Client package, and both backends
become Node-only.

The interaction is still one choice: the adaptive chooser mounts the backend
and its surface as a pair of Loader entries and tears both down in reverse, so
a resolved kind still swaps both faces. Compositions that pin an interaction
directly now pin the pair, and the chooser's runtime-string package list keeps
naming everything a composing app must resolve.

This commit is contained in:

imccyu

2026-08-11 19:10:50 +08:00

parent 070a2a7f1e

commit 40af20cafe

33 changed files with 407 additions and 136 deletions

									
										apps/web/tests/pin-browse-picker.overlay.yml
									
		+2
		
												View File
												
				@@ -9,3 +9,5 @@

				- insert:

				    - id: directory-picker-browse

				      name: '@deepseek-ai/dsh-host-directory-picker-browse'

				    - id: ui-directory-picker

				      name: '@deepseek-ai/dsh-client-ui-directory-picker'