mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-11-10 20:57:49 +08:00
sjw1231
14d3e53c19
Evaluation on the shipped compositions decided the defaults: the `dsh-base` `tool-fs` row and the Web `standard` preset enable apply_patch, keeping the SDK and Desktop `standard` tool sets equal (the SDK PTC overlay keeps the base row while the Desktop PTC preset lists its own, which the parity exceptions record); the `fs-observation-policy` row ships `disabled: true`, so write, edit, and apply_patch mutate unconditionally in every profile, and the package is classified as an optional product package. The write and edit guidance stops citing the policy as the default and the apply_patch guidance asks for enough hunk context instead of a prior read. The two recordings that capture a policy refusal re-enable the row through a per-scenario runtime.cordis.yml; the fixed-budget compaction scenarios pin `applyPatch: false` so their recorded thresholds hold; every other sidecar and recorded header follows. An upgrade guide records the default change.