mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
e2bde2902c
Implements docs/rfc/.../2026-06-20-extract-example-app-packages.md. Each
example was thick — a hand-rolled start.ts, an infra preamble, nested
base.yml/base-core.yml/acp-tail.yml includes, and a coupled front-door
cluster enforced only by prose. This moves the composition into packages so
each example is a thin leaf cordis.yml: pick the swappable backends, load one
app package.
New packages:
- @deepseek-ai/dsh-agent-core (packages/core/agent-core): one bundle plugin
that loads the providerless/executor-less/UI-less spine (timer + llm +
sessions + system-prompt + tools + agents + invariants + tool-bash +
agent-loop) via ctx.plugin(...) inside apply(), and forwards agent-loop's
`agents` list as its own Config (export const Config = AgentLoop.Config,
default []).
- @deepseek-ai/dsh-stdio-agent (packages/ui/stdio-agent): terminal chat APP —
agent-core + console logger + readline UI + a pre-created `main` agent, with
a bin. The demo:echo/coding front door.
- @deepseek-ai/dsh-acp-agent (packages/ui/acp-agent): ACP server APP —
agent-core + JSONL persistence + the acp bridge, NO stdout logger, with a
bin. The stdout-purity footgun is structurally unreachable from the leaf.
Amendment to the RFC: hmr stays a LEAF cordis.yml entry, not baked into
dsh-stdio-agent. hmr is a Loader-only dev plugin (throws without
--expose-internals; the in-process test tier can't even import its decorator
form), so a package statically importing it could never carry the per-file
coverage gate. Unlike the console logger, a stray hmr is not a stdout-purity
footgun, so leaving it at the leaf costs no safety. With hmr out, all three new
packages carry in-process unit specs at 100%.
Boot glue (Loader tail, .env load, snapshot-mode selection, stdin-dispose
lifecycle) moves into each app's bin; start.ts and base.yml/base-core.yml/
acp-tail.yml are deleted. Each app package gets a keyless real-load-path test
that boots through its bin + the cordis Loader (guarding the unwrapExports
export-shape bug class, postmortem 0001). ACP snapshot replay stays green
against the existing committed goldens (pure boot restructuring). RFC moved
proposed->implemented with the amendment recorded; package/example/architecture
docs and the module graph updated.
49 lines
2.5 KiB
TypeScript
49 lines
2.5 KiB
TypeScript
import tsconfigPaths from 'vite-tsconfig-paths'
|
|
import { defineConfig } from 'vitest/config'
|
|
|
|
export default defineConfig({
|
|
// Vite ≥8 warns that this plugin can be replaced by the native (experimental)
|
|
// `resolve.tsconfigPaths: true`. It cannot — keep the plugin. Tests run
|
|
// unbuilt (see AGENTS.md): bare workspace names like `cordis` or
|
|
// `@deepseek-ai/dsh-llm` must resolve to src/, and the only place that
|
|
// mapping exists is the root tsconfig.json `paths` map inherited by
|
|
// tsconfig.test.json. The native option is a bare boolean: for each
|
|
// importing file it discovers the NEAREST tsconfig.json and applies that
|
|
// file's own `paths`. Every workspace under packages/* and vendor/* has its
|
|
// own tsconfig.json without `paths`, so native resolution maps nothing,
|
|
// falls through to package.json exports (lib/, absent until `pnpm run build`),
|
|
// and every test file fails to import (verified on vite 8.0.16 /
|
|
// vitest 4.1.8). Making it work would mean copying the paths map into all
|
|
// 15 workspace tsconfigs — including vendor/* ones, which are pinned
|
|
// upstream copies (vendor/README.md). The plugin's `projects` option
|
|
// instead applies the one root map to every importer.
|
|
plugins: [tsconfigPaths({ projects: ['./tsconfig.test.json'] })],
|
|
test: {
|
|
include: ['packages/*/*/tests/**/*.spec.ts', 'examples/*/tests/**/*.spec.ts'],
|
|
coverage: {
|
|
provider: 'v8',
|
|
// Coverage measures OUR runtime source. Types-only files carry no
|
|
// executable code; vendor/ and examples/ are out of scope (examples are
|
|
// exercised by the demo smoke test instead).
|
|
include: ['packages/*/*/src/**/*.ts'],
|
|
// Types-only files carry no executable code. `bin.ts` files are
|
|
// self-executing CLI entrypoints (a top-level `await main()`): a spec
|
|
// can't import one without booting it, so they are driven by the keyless
|
|
// Loader-path smoke (a real subprocess) instead of the in-process unit
|
|
// suite — the same reason `examples/start.ts` sat out of coverage scope.
|
|
exclude: ['packages/*/*/src/types.ts', 'packages/*/*/src/bin.ts'],
|
|
// 100% or it doesn't merge (AGENTS.md: excessive tests are welcome).
|
|
// Per-file so a well-covered big file can't subsidize a bare one.
|
|
// Every v8 ignore comment must carry a reason — see AGENTS.md.
|
|
thresholds: {
|
|
perFile: true,
|
|
statements: 100,
|
|
branches: 100,
|
|
functions: 100,
|
|
lines: 100,
|
|
},
|
|
reporter: ['text', 'html'],
|
|
},
|
|
},
|
|
})
|