mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-11-10 04:27:42 +08:00
Tianyi Cui
335c5cbe26
The runtime profile default is correct for installed applications, but the supported TypeScript CLI also runs tsx workspace aliases. In that launch, profile resolution loaded both packages/core/tools/src/index.ts and packages/core/tools/lib/index.js. The ToolRuntime instance and agent-loop consumer therefore held different private TOOL_RUNTIME_SCHEDULER symbols; the first tool call failed while reading scheduler.prepare. The source bin now explicitly selects linked profile resolution using its own .ts module identity. Built and packaged launches keep runtime resolution, and explicit runProfile overrides remain unchanged. No service or symbol identity is widened to conceal duplicate module instances. Forward the existing sourceImport option through runLoaderSmoke and select tsx/esm for headless source snapshots. This exercises the actual supported source-launch vector while retaining the same recorded Session and expected outputs. The loader-smoke subprocess test covers forwarding that hook. Evidence: the official tsx/esm compaction replay failed before the fix while loading both Tools module URLs. After the fix it loads only src/index.ts and prints COMPACTION RECOVERED. The same focused replay passes under both DSH_EXAMPLE_MODE=src and lib after rebuilding Host artifacts. The 43 CLI and loader tests passed, including runtime defaults and explicit link/dual/runtime overrides. Loader-smoke coverage passed 25 tests with 100% statements, branches, functions, and lines. Host build, full lint, and all 41 doc-sync gates passed. Recorded JSONL generations and snapshot normalization are unchanged; temporary diagnostics were removed from built artifacts.