Files
modelstudioai__cli/pnpm-workspace.yaml
T

38 lines
826 B
YAML
Raw Normal View History

2026-05-28 18:37:07 +08:00
packages:
- packages/*
- tools/*
catalog:
"@types/node": ^24
2026-07-17 16:43:06 +08:00
"@types/tar-stream": ^3.1.4
2026-07-09 10:02:56 +08:00
"@types/yauzl": ^3.4.0
2026-05-28 18:37:07 +08:00
ajv: ^8.20.0
2026-06-05 13:56:24 +08:00
boxen: ^8.0.1
chalk: ^5.6.2
2026-07-17 16:43:06 +08:00
tar-stream: ^3.2.0
smol-toml: ^1.4.2
tsx: ^4.23.0
2026-05-28 18:37:07 +08:00
typescript: ^5
2026-07-21 13:55:38 +08:00
undici: ^6.27.0
2026-05-28 18:37:07 +08:00
vite: npm:@voidzero-dev/vite-plus-core@latest
vite-plus: latest
vitest: npm:@voidzero-dev/vite-plus-test@latest
yaml: ^2.8.3
2026-07-09 10:02:56 +08:00
yauzl: ^3.4.0
2026-05-28 18:37:07 +08:00
catalogMode: prefer
overrides:
vite: "catalog:"
vitest: "catalog:"
feat(dsh): add bailian-cli-dsh plugin bundle for DeepSeek Harness Expose Bailian capabilities to dsh through its service seams as one package with six subpath plugin entries and a `dsh.bundle` patch: - TokenPlan as an LLM provider - bailian_vision_describe / bailian_image_generate tools over `bl` - knowledge-base retrieval as a WebSearchProvider (`bailian-kb`) - cross-session memory: tools, pre-step recall, turn-close persist - managed-agent as a SubagentProvider TokenPlan configures the base bundle's existing pi-ai row rather than mounting a second `dsh-llm-pi-ai` instance. A second instance cannot work: pi-ai re-declares its entire built-in provider catalog to `registerConfigurableProviders`, and that directory is global, so boot fails with a duplicate on `amazon-bedrock`. Routes and vision support were probed against the live gateway. qwen3.8-max, qwen3.7-plus, qwen3.6-flash and glm-5.2 read images; qwen3.7-max rejects them with HTTP 400; the DeepSeek routes accept image content without erroring yet stay blind. The DeepSeek entries therefore do not declare image input — claiming it would turn a clean refusal into a silently wrong answer — and `bailian_vision_describe` serves them by returning text instead. Also fix `bl memory` against the v2 API, each verified live: - `profile get` used /profiles, which returns HTTP 500. The documented and working endpoint is /user_profile. - `add` read `response.memory_ids`, which the service never returns. It returns `memory_nodes`, so text output always printed "IDs: none". - `MemoryNode.created_at`/`updated_at` are unix seconds, not strings, and `UserProfileResponse.profile` did not match the wire shape. - Add the missing request parameters: --meta-data, --project-id, --project-ids, --min-score, --enable-rerank, --plan-version, --enable-judge, --enable-rewrite, --timestamp. - Add `memory profile list|detail|update|delete`, covering the four v2 profile-schema operations the CLI was missing. `plan_version: lite` is ignored by the service and still bills pro; `enable_rerank: false` is what actually selects lite, which is ~50x cheaper per search. The CLI flag and the memory plugin both send the parameter that works. Disable pnpm's autoInstallPeers: the @deepseek-ai/dsh-* rc line peers on three packages that were never published to npm, which 404s the whole workspace install. Verified the existing packages still build. Co-Authored-By: Claude <noreply@anthropic.com>
2026-08-15 01:44:28 +08:00
# The @deepseek-ai/dsh-* rc line (used only by bailian-cli-dsh) peers on
# packages that were never published: dsh-type-meta, dsh-environment,
# dsh-tasks. Auto-installing peers therefore 404s the whole workspace.
autoInstallPeers: false
2026-05-28 18:37:07 +08:00
peerDependencyRules:
allowAny:
- vite
- vitest
allowedVersions:
vite: "*"
vitest: "*"