David Matthews

Several addressed by #4848

Potentially slightly dangerous to change the behaviour now? As a minimum we should document the behaviour.

If you specify a remote host via `--host` then it makes sense to me to use that host. However, what if you don't specify a host but have `[scheduler][run hosts]`...

I think we still need the ability to warm start a workflow that has previously been run (continuing with the existing `share` directory). The ability to trigger new flows will...

Validate before reinstall is good practise but currently not easy to do (you need to know what install/play options were used) - `cylc vrp` will address this. Another advantage of...

@hjoliver Are you happy for the Question label to be removed now?

> Does the fcm_make2 issue require [scheduling] information or is [runtime] sufficient? I think `[runtime]` is sufficient but I'm really not worried about this use case.

If possible I think this ought to fail to load in the same way as other invalid settings

> cylc outputs [--set] [--unset] Not sure about this. I think the vast majority of cases will be setting outputs (the use cases for unset are much more obscure) so...

`cylc stop` currently supports `-flow=INT` which means "Stop flow number INT from spawning more tasks". I don't really like this for 2 reasons: 1. If you `stop` a workflow can...