mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
f290a8b851
`dsh` shipped two config trees that were 43 rows the same: apps/cli/cordis.yml composed web as 74 flat rows, while the TUI booted examples/tui-agent/cordis.yml whose single `@deepseek-ai/dsh-tui-demo` row mounted twelve plugins behind a twenty-key pass-through Config. Neither file was what its location claimed — apps/cli hardcoded the "example" as the product default and the "demo" bundle was the application — and every capability change had to be made twice. - apps/cli/base.cordis.yml holds the 43 shared rows; tui.cordis.yml and web.cordis.yml are patch lists stating only what differs per surface - overlays apply as SIBLING patch lists at one include level, because include patches never cross an include boundary. Precedence: base < surface < (--config | personal ~/.dsh/config.yaml) < launcher flag/profile patches - `--config` now applies an overlay INSTEAD OF the personal one, so a demo or test tree never inherits the user's route; new `--config-replace` boots a file as the entire tree (the old `--config` behaviour). Both survive /resume - vendor/include: index each `insert`ed row as it is added so a later patch can configure or disable it. Upstream built the id index once before the patch loop, leaving every surface-only row — the whole TUI front door — silently unpatchable from user config. Logged as local modification 8 - session identity moves to dsh-agent-loop's CONFIGURED_AGENT_IDENTITIES_KEY; dsh-tui's MAIN_SESSION_ID_KEY is deleted (only the bundle read it) - delete examples/tui-agent, examples/cordis-agent, packages/examples/tui-demo; TUI tests → apps/cli/tests, cordis e2e → packages/cordis/tool-cordis/tests, examples/code-mode survives as an overlay leaf - `dsh web` gains --config, threaded into AppCLIEntry as an extra overlay Three latent defects surfaced and are fixed here: the TUI captured the optional sessionQuery service once at construction and could permanently disable /resume when it won the mount race; the session-store root silently reverted to a project-local ./.sessions; --config-replace was dropped by the resume handoff. Verified by booting each tree through the real Loader (TUI 55 entries, web 75, zero unsettled) rather than reading YAML. All eight terminal snapshots replay byte-identically; 14/14 PTY smoke, 112/112 snapshots, 25/25 doc-sync, hygiene and lint clean.
65 lines
2.8 KiB
TypeScript
65 lines
2.8 KiB
TypeScript
import { availableParallelism } from 'node:os'
|
|
import tsconfigPaths from 'vite-tsconfig-paths'
|
|
import { defineConfig } from 'vitest/config'
|
|
|
|
const DEFAULT_SNAPSHOT_MAX_CONCURRENCY = 5
|
|
|
|
function positiveIntFromEnv(name: string, fallback: number): number {
|
|
const raw = process.env[name]
|
|
if (raw === undefined || raw === '') return fallback
|
|
|
|
const value = Number(raw)
|
|
if (!Number.isInteger(value) || value < 1) {
|
|
throw new Error(`${name} must be a positive integer, got ${JSON.stringify(raw)}`)
|
|
}
|
|
return value
|
|
}
|
|
|
|
const snapshotMaxConcurrency = positiveIntFromEnv(
|
|
'DSH_SNAPSHOT_MAX_CONCURRENCY',
|
|
Math.min(DEFAULT_SNAPSHOT_MAX_CONCURRENCY, availableParallelism()),
|
|
)
|
|
|
|
// Replay is the keyless default: boot real subprocess paths from recorded model responses and diff
|
|
// assembled requests, normalized protocol or transcript output, and persisted-log expected outputs.
|
|
// `record` calls the real API and updates fixtures and expected outputs; `refresh` replays committed scripts
|
|
// and updates current expected outputs. Replay/refresh never load `.env`; only record reads a key from the
|
|
// environment or root `.env`.
|
|
if (process.env.DSH_SNAPSHOT === 'record') {
|
|
try {
|
|
process.loadEnvFile(new URL('.env', import.meta.url).pathname)
|
|
} catch (error) {
|
|
// ENOENT (no .env) is fine — the key may already be in the environment.
|
|
// Surface any other failure rather than silently recording with wrong env.
|
|
if ((error as NodeJS.ErrnoException | null)?.code !== 'ENOENT') throw error
|
|
}
|
|
}
|
|
|
|
export default defineConfig({
|
|
// Same resolution note as vitest.config.ts: bare workspace names resolve
|
|
// through the tsconfig.base.json paths facade; the native option cannot do
|
|
// this (the root tsconfig is a solution file with no paths).
|
|
plugins: [tsconfigPaths({ projects: ['./tsconfig.base.json'] })],
|
|
test: {
|
|
setupFiles: ['./scripts/test-invariants.ts'],
|
|
include: [
|
|
'scripts/**/*.snapshot.ts',
|
|
// The assembled Web snapshot executes generated client bundles; source
|
|
// mode remains the zero-build path, while lib mode requires a prior build.
|
|
...(process.env.DSH_EXAMPLE_MODE === 'lib' ? ['apps/web/tests/**/*.snapshot.ts'] : []),
|
|
'examples/*/tests/**/*.snapshot.ts',
|
|
// The shipped TUI's terminal-journey scenarios moved here with its config.
|
|
'apps/cli/tests/**/*.snapshot.ts',
|
|
'packages/sdk/*/tests/**/*.snapshot.ts',
|
|
'packages/ui/tui/tests/**/*.snapshot.ts',
|
|
],
|
|
// Each test boots a subprocess; give it room and keep the worker file singular. Replay tests
|
|
// opt into bounded in-file concurrency, while record/refresh stay serial because they write
|
|
// fixtures. The environment knob restores serial replay with value 1 on constrained machines.
|
|
testTimeout: 120_000,
|
|
hookTimeout: 30_000,
|
|
fileParallelism: false,
|
|
maxConcurrency: snapshotMaxConcurrency,
|
|
},
|
|
})
|