Summary
Implement the two config simplifications discussed in Discord:
- Allow task shorthand:
"some-task": "... command" (equivalent to "some-task": { "command": "... command" })
- Allow
command to accept string[] as a shorthand for command1 && comand2 && ....
Notes
- The task string shorthand should keep the same default caching behavior as the object form (
run.cache still overrides, default remains true).
- Docs should make sequencing semantics explicit.
- These two shorthands can be combined:
"some-task": ["cmd1", "cmd2"]
- Verifiable by plan snapshot tests. (no need for e2e tests)
Summary
Implement the two config simplifications discussed in Discord:
"some-task": "... command"(equivalent to"some-task": { "command": "... command" })commandto acceptstring[]as a shorthand forcommand1 && comand2 && ....Notes
run.cachestill overrides, default remainstrue)."some-task": ["cmd1", "cmd2"]