deepseek-harness/apps/web/tests/fixtures/time-context-every-step.patch.yml at e1cbde3af12d3c59cd79e196ca0b1d94a5de50b0 - deepseek-harness - Gitea: Git with a cup of tea

mward4/deepseek-harness

0 Fork 0

Files

T

Chinesezjc 41c29fa832 feat(schedule): ship the Schedule switch as an optional bundle

The shipped Web composition carries `time-context`, `schedule`, and
`ui-schedule` disabled. This adds
`@deepseek-ai/dsh-experimental-schedule-bundle`, whose patch sets
`disabled: false` on those three rows and inserts none, and names it in
`OPTIONAL_BUNDLES` with a runtime dependency of `apps/cli`, so every
installation ships it switched off and the Web Plugins page offers it in
the Official group.

The two Web suites and the built-Web Schedule Remote scenario enable the
rows through that bundle instead of a scenario-local fixture.

2026-09-24 21:03:26 +08:00

7 lines

303 B

YAML

Raw Blame History

 # Browser-zone assertions need a fresh reading after the non-browser preparation turn.
 # The Schedule rows stay disabled in the shipped composition; the scenario enables them
 # with the shipped `@deepseek-ai/dsh-experimental-schedule-bundle` patch.
 - id: time-context
   config:
     refreshIntervalMs: 0