mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
4d1ab81f05
The seven behavior-pinning snapshots (workspace-flow, slash-flow, todo-display, session-title, session-actions, terminal-card, code-mode-fixture) asserted per-package behavior through the whole built app: every assertion now lives in the owning package's suite at equal strength (SlotTestRuntime benches assemble the same plugin apply over the production slot machinery), while the assembled layer kept re-failing on unrelated churn at 10s-timeout debugging cost. What only this lane can prove is the artifact plane: lib/client.js bundles loading through the ModuleLoader path, staged boot activation across the inject layers, per-plugin CSS injection, and a journey reaching chat content over the fixture transport. built-boot.snapshot.ts pins exactly that, and nothing else — behavior assertions belong to the package suites.